NETWARE REQUESTER FOR OS/2 January 1989 Edition Revision 1.00 (Developers Release) For NetWare Version 2.1 and Above and OS/2 Versions 1.0 and 1.1 Novell, Incorporated 122 East 1700 South P.O. Box 5900 Provo, Utah 84601 USA Copyright 1989 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express prior written consent of the publisher. Novell Part # 100-000554-001 DISCLAIMER Novell, 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 obligation to notify any person or entity of such changes. FCC WARNING Computing devices and peripherals manufactured by Novell generate, use, and can radiate radio frequency energy, and if not installed and used in accordance with the instructions in this manual, may cause interference to radio communications. Such equipment has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against radio interference when operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference, in which case the user--at his own expense--will be required to take whatever measures are necessary to correct the interference. Some components may not have been manufactured by Novell, Inc. If not, Novell has been advised by the manufacturer of the component that the component has been tested and complies with the Class A computing device limits as described above. January 1989 Edition Manual Revision 1.00 For NetWare Version 2.1 and Above Novell Part # 100-000554-001 HOW TO USE THIS MANUAL This manual explains how to use the NetWare Requester for OS/2 with workstations running OS/2. You should be familiar with OS/2 and NetWare before using this manual. Chapter 1 explains how the NetWare Requester functions with OS/2. It also lists the software, memory, and hardware requirements for workstations and file servers that will be used with the NetWare Requester. Chapter 2 explains how to install the NetWare utilities for OS/2 on a file server that will be accessed by OS/2 workstations and how to install the NetWare Requester on OS/2 workstations. Chapter 3 lists the NetWare utilities for OS/2. Each utility is explained in detail and is used in at least one example. These utilities are arranged in alphabetical order for easy reference. Appendix A provides instructions for reconfiguring the NetWare Requester. Appendix B explains how to use OS/2 and NetWare commands to customize your batch files. Appendix C lists the defaults for the NetWare Spooler and provides instructions for defining your own defaults. TABLE OF CONTENTS HOW TO USE THIS MANUAL CHAPTER 1 NETWARE SUPPORT FOR OS/2 NETWARE COMPATIBILITY WITH OS/2 . . . . . . . . . . . . . 1 - 1 NETWARE UTILITIES FOR OS/2 . . . . . . . . . . . . . . . 1 - 1 SOFTWARE REQUIREMENTS . . . . . . . . . . . . . . . . . . 1 - 2 MEMORY REQUIREMENTS . . . . . . . . . . . . . . . . . . . 1 - 2 HARDWARE REQUIREMENTS . . . . . . . . . . . . . . . . . . 1 - 2 CHAPTER 2 INSTALLING THE NETWARE UTILITIES FOR OS/2 AND THE NETWARE REQUESTER PREPARING FOR INSTALLATION . . . . . . . . . . . . . . . 2 - 1 INSTALLING NETWORK INTERFACE BOARDS . . . . . . . . . . 2 - 1 INSTALLING THE NETWARE UTILITIES FOR OS/2 ON A FILE SERVER . . . . . . . . . . . . . . . . . . . . 2 - 2 INSTALLING THE NETWARE REQUESTER ON AN OS/2 WORKSTATION . . . . . . . . . . . . . . . . . 2 - 3 LOADING THE NETWARE REQUESTER FOR OS/2 AND ATTACHING TO A FILE SERVER . . . . . . . . . . . . . 2 - 7 CHAPTER 3 COMMAND LINE UTILITIES /GLOBAL AND /PRIVATE OPTIONS . . . . . . . . . . . . . . 3 - 1 COMMAND FORMAT . . . . . . . . . . . . . . . . . . . . . 3 - 2 CONSTANTS . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2 VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2 SYMBOLS . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 3 COMMAND LINE UTILITIES ATOTAL . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 4 ATTACH . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 6 CAPTURE . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 8 CASTOFF . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 14 CASTON . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 16 ENDCAP . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 17 GRANT . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 19 HIDEFILE . . . . . . . . . . . . . . . . . . . . . . . . 3 - 23 LISTDIR . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 26 LOGIN . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 30 LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 32 MAKEUSER (Command Line Utility) . . . . . . . . . . . . . 3 - 35 MAKEUSER (Menu Utility) . . . . . . . . . . . . . . . . . 3 - 37 MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 61 NCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 65 NPRINT . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 68 PSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 71 PURGE . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 74 REMOVE . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 75 REVOKE . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 78 RIGHTS . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 82 SALVAGE . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 85 SEND . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 87 SETPASS . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 89 SHOWFILE . . . . . . . . . . . . . . . . . . . . . . . . 3 - 91 SLIST . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 93 SYSCON . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 95 inSYSTIME . . . . . . . . . . . . . . . . . . . . . . . . 3 - 175 TLIST . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 176 USERLIST . . . . . . . . . . . . . . . . . . . . . . . . 3 - 179 VERSION . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 183 WHOAMI . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 184 APPENDIX A RECONFIGURING THE NETWARE REQUESTER APPENDIX B CUSTOMIZING BATCH FILES APPENDIX C RECONFIGURING THE NETWARE SPOOLER TRADEMARKS CHAPTER 1 NETWARE SUPPORT FOR OS/2 The IBM Operating System/2 (OS/2) is a second-generation operating system for 80286- and 80386-based microcomputers. OS/2 is a single-user, multitasking operating system, designed as the successor to PC-DOS, which is a single-user, single-tasking operating system. NetWare support for OS/2 consists of the NetWare Requester, LAN drivers, and NetWare utilities, all of which run in 80286/80386 microprocessor protected mode. NETWARE COMPATIBILITY WITH OS/2 The NetWare Requester provides transparent network support for workstations running OS/2 by providing connectivity between OS/2 workstations and file servers running NetWare v2.1 or above. The NetWare Requester for OS/2 acts much the same as the NetWare shell for DOS in that they both route requests from the workstation to the network. Since the NetWare Requester files are written as device drivers rather than executable files (that can be loaded directly from the operating system prompt), the NetWare Requester and its associated files are loaded as an OS/2 module on an OS/2 workstation through the CONFIG.SYS file. NETWARE UTILITIES FOR OS/2 Novell is currently adapting NetWare utilities to run on OS/2 workstations. NetWare utilities for DOS and NetWare utilities for OS/2 will be nearly the same except for the /Private option that has been added to some NetWare utilities for OS/2. The /Private option takes advantage of the enhanced capabilities of OS/2. (The /Private option and the NetWare utilities for OS/2 are explained in Chapter 3.) The following NetWare command line utilities have been rewritten to run in protected mode under OS/2. þ ATOTAL þ MA KE US ER þ ATTACH þ MAP þ CAPTURE þ NCOPY þ CASTOFF þ NPRINT þ CASTON þ PSTAT þ ENDCAP þ PURGE þ GRANT þ REMOVE þ HIDEFILE þ REVOKE þ LISTDIR þ LO GI N þ LOGOUT þ SYSCON þ SALVAGE þ SYSTIME þ SEND þ TLIST þ SETPASS þ USERLIST þ SHOWFILE þ VERSION þ SLIST þ WHOAMI þ RIGHTS SOFTWARE REQUIREMENTS The NetWare Requester for OS/2 Version 1.0 supports the following versions of OS/2: þIBM OS/2 Standard Edition, Version 1.0 þIBM OS/2 Extended Edition, Version 1.0 The NetWare Requester for OS/2 Version 1.1 supports the following versions of OS/2: þIBM OS/2 Standard Edition, Version 1.1 þ IBM OS/2 Extended Edition, Version 1.1 The file server or external bridge that OS/2 workstations will access must be running NetWare v2.1 or above. MEMORY REQUIREMENTS OS/2 requires a minimum of 1.5MB of memory. The NetWare Requester for OS/2 requires a relatively insignificant amount of memory. Requester and IPX code, as well as communication buffers, reside in memory space allocated to the compatibility box, reducing the memory available to real-mode applications. HARDWARE REQUIREMENTS The NetWare Requester for OS/2 will run in the following machines: þIBM PC XT-286 þIBM PC AT and compatibles þ386 compatibles þIBM PS/2 Models 50, 60, 70, and 80 The following network interface boards can be used in workstations running OS/2. þIBM Token-Ring PC Adapter (standard bus and Micro Channel) þSMC ARCNET PS110 (Micro Channel) þ Novell Ethernet NE/2 (Micro Channel) þ Novell Ethernet NE1000 (standard bus) þ Novell RX-Net (standard bus) þ IBM PC Network Adapter II and II/A (standard bus and Micro Channel) þ 3Com EtherLink Series 501 (standard bus) þ 3Com EtherLink/MC 3C523 (Micro Channel) The following topologies are supported by the NetWare Requester for OS/2: þ IBM Token-Ring (using IBM Token-Ring adapters) þ ARCNET (using SMC PS110 or Novell RX-Net network interface boards) þ Ethernet (using NE/2, NE1000, 3Com EtherLink/MC 3C523, or 3Com EtherLink 3C501 network interface boards) þ IBM PC Network (PC Network Adapter II and II/A) CHAPTER 2 INSTALLING THE NETWARE UTILITIES FOR OS/2 AND THE NETWARE REQUESTER This chapter explains how to install the NetWare utilities for OS/2 on a file server running NetWare v2.1 or above. It also explains how to install the NetWare Requester on a workstation running OS/2. PREPARING FOR INSTALLATION Before you install the NetWare Requester, make sure that the OS/2 workstations and the NetWare file servers and bridges they are attached to meet the software and hardware requirements outlined below. The first file server that an OS/2 workstation attaches to must þ Be running NetWare v2.1 or above; þ Have the NetWare utilities for OS/2 in SYS:LOGIN/OS2 and SYS:PUBLIC/OS2; þ Meet the software and hardware requirements listed in Chapter 1. The workstation can then access other file servers (whether or not they have the NetWare utilities for OS/2 installed on them) as long as a drive on the workstation is mapped to a directory on a file server that contains all of the NetWare utilities for OS/2. Any OS/2 workstation attached to a file server or bridge must þ Have OS/2 installed on the hard disk; þ Meet the hardware and software requirements listed in Chapter 1. INSTALLING NETWORK INTERFACE BOARDS If you need to install a network interface board in a workstation, file server, or bridge, refer to the specific NetWare installation supplement for that board. Set file server and bridge network interface boards to any setting allowed by the hardware and software in the file server or bridge. Use the default settings for the workstation network interface boards, if possible. If you use the default settings, you will not need to modify the NetWare Requester. If you are not sure whether your network interface board is using the default setting, check the configuration option table in the installation supplement for that board. If a workstation network interface board needs to use a setting other than the default, refer to the instructions in Appendix A of this manual to reconfigure the NetWare Requester. INSTALLING THE NETWARE UTILITIES FOR OS/2 ON A FILE SERVER Some NetWare utilities have been rewritten to work with OS/2. Since OS/2 cannot use DOS utilities, regular NetWare utilities that were written for DOS will not work on an OS/2 workstation. In order for the NetWare Requester to work, the first file server accessed by an OS/2 workstation must have the NetWare utilities for OS/2 installed on it. IMPORTANT: To prevent OS/2 from accessing NetWare utilities for DOS and to prevent DOS workstations from accessing the NetWare utilities for OS/2, the two sets of utilities must be kept in separate directories. Install the NetWare utilities for OS/2 from a workstation that is attached to the file server and has a high-density floppy disk drive. During the installation program, the files containing the NetWare utilities for OS/2 will be copied from the NETWARE REQUESTER FOR OS/2 diskette to the file server. To install the NetWare utilities for OS/2 on a file server, complete the following steps. 1)Create OS2 directories in the file server's SYS:LOGIN and SYS:PUBLIC directories to copy the utilities into. You must be logged in as SUPERVISOR or have supervisor equivalence before you can create the OS/2 directories under SYS:LOGIN and SYS:PUBLIC. The ATTACH, MAP, and SLIST utilities will be copied to SYS:LOGIN/OS2. The other utilities will be copied to SYS:PUBLIC/OS2. Make sure all OS/2 users have Read, Open, and Search rights to these directories so that they can access the NetWare utilities for OS/2. 2)Map drive L to SYS:LOGIN/OS2 and drive P to SYS:PUBLIC/OS2. 3)Insert the NETWARE REQUESTER FOR OS/2 diskette into drive A. 4)Change the default drive to drive A. 5)Type SERVINST 6)Follow the instructions that appear in the prompts. The NetWare utilities for OS/2 will be copied from the diskette to SYS:LOGIN/OS2 and SYS:PUBLIC/OS2 on the file server. INSTALLING THE NETWARE REQUESTER ON AN OS/2 WORKSTATION The NetWare Requester must be installed on each OS/2 workstation that will be attached to the network. OS/2 must be installed on the workstation before you install the NetWare Requester, since you must run the installation program from the OS/2 prompt. NOTE: The installation program will automatically install the correct version of the NetWare Requester depending on the version of OS/2 you have on the workstation. During the installation program, you will choose directories to copy the NetWare Requester files into. All NetWare Requester files will be copied to the workstation's hard disk. You can copy these files to existing OS/2 directories, the root directory, a \NETWARE directory, or any other directory of your choice. It does not matter which directories you copy the NetWare Requester files into, but the directory you want to copy the files into must already exist before you run the installation program. The prompts in the installation program will show you which files can be copied to which directories. You will be asked to choose which directories to copy the files into. The directories you can choose will be similar to the following. þ Copy .DLL files to any of the following directories: \NETWARE \OS2\LIB \ (root directory) \OS2\DLL þ Copy background tasks files to any of the following directories: \NETWARE \OS2\BIN \OS2 \OS2\SYSTEM \ (root directory) þ Copy message files to any of the following directories: \NETWARE \ (root directory) \OS2\SYSTEM þ Copy device drivers to any of the following directories: \NETWARE \OS2\DEV \OS2 \OS2\SYSTEM \ (root directory) If you want to copy files to an existing directory other than those listed on the screen, press the Insert key and enter the directory name. When you have selected directories for all files, you will see a screen that lists the directories you chose. You will be asked if you want to accept these selections. To accept these selections, highlight "Yes" and press . The files will be copied to the correct directories. If you do not want to accept the selected directories, highlight "No" and press . The installation program will begin again. To install the NetWare Requester on an OS/2 workstation, complete the following steps. 1) If you want to copy all of the NetWare Requester files to one directory, create a directory (such as C:\NETWARE) on the workstation's hard disk. If you do not want to copy all of the files to a separate directory, you can copy the files to the root directory of the workstation hard disk or to the OS/2 directories where the related OS/2 files are located. In this case, you do not need to create a separate directory for these files. 2) Insert the NETWARE REQUESTER FOR OS/2 diskette into drive A. 3) Change the default drive to drive A. 4) Type INSTALL 5) Select the directories to copy the files into by following the instructions that appear in the prompts. 6) Use a text editor to copy the CONFIG.PST file into the CONFIG.SYS file, or use the following command: COPY CONFIG.SYS + CONFIG.PST CONFIG.SYS 7) Use a text editor to modify the CONFIG.SYS file by completing the following steps: A) Remove the "rem" from the beginning of the line that lists the network interface board installed in your workstation. NOTE: If you are using an SMC ARCNET PS110 network interface board, remove the "rem" from in front of the RXNET_MC.SYS driver. B) If you did not copy the NetWare Requester .DLL files to the \OS2\DLL directory or to the root directory of the workstation's hard disk, add C:\directory; to the end of the statement LIBPATH=C:\;C:\OS2;C:\OS2;INSTALL; in the CONFIG.SYS file. Replace directory with the name of the directory to which the .DLL files were copied. NOTE: The LIBPATH statement specifies a path that OS/2 uses to search for any files with the .DLL extension. Requester-related files with the .DLL extension can be placed anywhere on the workstation's hard disk, but you must specify the location of these files in the LIBPATH statement in the CONFIG.SYS file. The OS/2 LIBPATH statement may vary, depending on the version of OS/2 you have installed. 8) If you are running the optional SPX package, you must remove "rem" from the following lines in the CONFIG.SYS file: DEVICE=C:\directory\SPX.SYS RUN=C:\directory\SPDAEMON.EXE Replace directory with the names of the directories to which you copied the SPX.SYS and SPDAEMON.EXE files. 9) If you are running the optional NetBIOS package, you must remove "rem" from the following lines in the CONFIG.SYS file: DEVICE=C:\directory\NETBIOS.SYS RUN=C:\directory\NBDAEMON.EXE Replace directory with the names of the directories to which you copied the NETBIOS.SYS and NBDAEMON.EXE files. 10) Save CONFIG.SYS as an ASCII text file. In addition to any OS/2 statements, the CONFIG.SYS file should now contain statements similar to the following: rem start NetWare Spooler run=C:\NETWARE\nwspool.exe rem NetWare Requester files device=C:\NETWARE\lansup.sys rem remove the rem from the beginning of only one of the following lines rem depending on the LAN interface board installed in your workstation. device=C:\NETWARE\pcn2_mc.sys rem device=C:\NETWARE\pcn2_at.sys rem device=C:\NETWARE\rxnet_mc.sys rem device=C:\NETWARE\rxnet_at.sys rem device=C:\NETWARE\ne2.sys rem device=C:\NETWARE\ne1000.sys rem device=C:\NETWARE\token.sys rem device=C:\NETWARE\e3c501.sys device=C:\NETWARE\ipx.sys device=C:\NETWARE\nwreq.sys run=C:\NETWARE\nwdaemon.exe rem to use NETBIOS remove the rems from the following two lines rem device=C:\NETWARE\netbios.sys rem run=C:\NETWARE\nbdaemon.exe rem to use SPX remove the rems from the following two lines rem device=C:\NETWARE\spx.sys rem run=C:\NETWARE\spdaemon.exe The paths in the statements will vary according to where the NetWare Requester files were copied. The statements copied from the CONFIG.PST file to the CONFIG.SYS file reflect the adjustments in the paths. The device drivers (.SYS files) must be loaded in the order shown above. The order of the other Requester-related statements is not important. LOADING THE NETWARE REQUESTER FOR OS/2 AND ATTACHING TO A FILE SERVER After you have installed network interface boards (if necessary), copied the NetWare utilities for OS/2 into the appropriate directories on the file server, and installed the NetWare Requester for OS/2 on the workstation, you can attach to that file server by rebooting the workstation. IMPORTANT: You must specify search paths for SYS:LOGIN/OS2 and SYS:PUBLIC/OS2 so that the workstation can access the NetWare utilities for OS/2. OS/2 handles the concept of search drives itself; you cannot use NetWare to map a search drive. You must use the OS/2 PATH and DPATH commands to set search drives. If you need more information about using NetWare and OS/2 commands to set search paths and customize your batch files, refer to the information in Appendix B of this manual. After the workstation boots with OS/2, you will see messages similar to the following: Novell Link Support for OS/2 v1.00.00B (C) Copyright 1988 Novell, Inc. All Rights Reserved. Novell lan_driver_type for OS/2 V1.00.00A (C) Copyright 1988 Novell, Inc. All Rights Reserved. Novell OS/2 IPX for OS/2 V1.00.00B (C) Copyright 1988 Novell, Inc. All Rights Reserved. Novell Requester for OS/2 V1.1 (C) Copyright 1988, 1989 Novell, Inc. All Rights Reserved. Attached to server file_server. If the workstation is properly connected to a file server or bridge running NetWare v2.1 or above, the NetWare Requester will automatically attach to the nearest file server and map network drive L to SYS:LOGIN for that file server. NOTE: SYS:LOGIN and SYS:PUBLIC contain NetWare utilities for DOS. These utilities will not execute since they are written for DOS and not OS/2. Trying to run any NetWare utility for DOS (including those in SYS:LOGIN, SYS:PUBLIC, and SYS:SYSTEM) will produce an error message on the OS/2 workstation monitor. You must use SYS:LOGIN\OS2 and SYS:PUBLIC\OS2. CHAPTER 3 COMMAND LINE UTILITIES This chapter explains how to use the command line utilities that have been rewritten to work with OS/2. These utilities appear in alphabetical order. Two major sections appear under each utility heading: þ Command Format. This section includes the command format of the utility, an explanation of the command format, and a brief explanation of each option that can be used with the utility. Experienced NetWare users may want to refer only to "Command Format." þ How to Use Utility Name. This section explains the utility's purpose, gives information you need to know before using the utility, and shows you how to use the utility. Two additional sections may also appear: þ Additional Information. This section presents supplemental information about the utility. þ Related Command Line Utilities. This section lists functionally related command line utilities. /GLOBAL AND /PRIVATE OPTIONS The NetWare utilities for OS/2 function the same as those written for DOS. However, /Global and /Private options have been added to ATTACH, CAPTURE, ENDCAP, LOGOUT, and MAP. The default setting for ATTACH, CAPTURE, ENDCAP, LOGOUT, and MAP is /Global. When you use these commands in one OS/2 session without specifying the /Private option, the command affects all other sessions. When you include the /Private option, the command affects only your current (or default) session. The /Private option always overrides /Global. When a session ends, all /Private options for that session are deleted and returned to their /Global default settings. By using the /Private option, you can customize the commands for each session. You can define drive mappings that apply to all sessions or only one session. You can attach to the same file servers in all sessions or attach to different file servers in each session. You can capture an LPT port in one session without capturing it in other sessions. NOTE: Because /Global is the default setting for ATTACH, CAPTURE, ENDCAP, LOGOUT, and MAP, it is not listed as an option. Only the /Private option is listed with the options for these commands. COMMAND FORMAT The command format shows you the correct way to enter a command so that it can be interpreted by the network. The command formats appear directly under each utility heading in this chapter. Each command format can have up to three components: constants, variables, and symbols. CONSTANTS Constants appear in boldface, upper-case letters. You must include constants in your command unless they are enclosed in square brackets. Square brackets indicate that the constant is optional (see "Symbols" on the next page). Although constants appear in upper- case letters in command formats, they can be typed in either upper-case or lower-case letters in your command. VARIABLES Variables appear in lower-case letters and are italicized. Replace a variable with information pertinent to the task you want to complete. For example, if your command included the variables server and user, you would replace server with the name of the file server you want to specify and user with the name of the user you want to specify. Command formats that contain the option variable always have options specific to that utility listed below the command format. Many options can be abbreviated. The abbreviations are indicated by boldface letters. Replace the filespec variable in a command format with any path leading to and including the file you want to indicate. Replace the path variable in a command format with any directory path leading to and including the volume, directory, or subdirectory you want to indicate. SYMBOLS The following symbols may appear in command formats: [ ] Square brackets [[ ]] Nested square brackets | Vertical bar ... Ellipses Square brackets indicate that the enclosed item is optional: you can issue a command with or without using the enclosed item. Nested square brackets indicate that all enclosed items are optional. However, if you use the item(s) within the innermost brackets, you must also use the item(s) within the outer brackets. A vertical bar indicates that you must use either the item to the left of the vertical bar or to the right, but not both. Ellipses indicate that you can use the item(s) preceding the ellipses several times. ATOTAL Command Format ATOTAL Use ATOTAL to view a summary of the accounting services your network is using. These figures are helpful in determining charge rates for accounting. The ATOTAL utility compiles information from the system accounting records and lists the following: þ Total blocks read þ Total blocks written þ Total connect time in minutes þ Total service requests þ Total disk storage in blocks/day ATOTAL gives you a daily and weekly summary for services used. This information will allow you to estimate how much each service is being used for a given period of time. The totals will be listed only if accounting is installed on the file server and services are being charged for (see "Installing the Accounting Feature" on page 3-96 and "Establishing Charge Rates" on page 3-99). To use ATOTAL, complete the following steps. 1)In the SYS:SYSTEM directory, type ATOTAL You will see information similar to the following: F:\> ATOTAL Processing accounting records... After the accounting records have been processed, the daily and weekly totals for each service will be listed. 2)Because ATOTAL is likely to fill up more than one screen on the computer, you can redirect the output of ATOTAL to a file. This file can be printed or typed to the screen in pages. To redirect the output to a file, type ATOTAL > filename To print a hard copy, type NPRINT filename To view files one screen at a time, type TYPE filename | MORE or ATOTAL | MORE ATTACH Command Format ATTACH [server [/user]] [/Private] Replace server with the name of the file server you want to attach to. Replace user with your username on that file server. Use the /Private option to attach privately on different sessions. If you use the /Private option with ATTACH, you will be attached to that file server on that session only. You can also attach privately to a file server on one session and globally to that same file server on all other sessions. However, if you attach privately and globally to the same file server, you must specify whether you want to break the private connection or the global connection when you issue a logout command (see LOGOUT). How to Use ATTACH Use the ATTACH utility to attach your workstation to other file servers on your network or internetwork. The NetWare Requester will automatically attach you to the nearest file server, but you must use ATTACH to access the file server and the utilities. Executing ATTACH. You can issue an ATTACH command from any network or local drive. To attach to another file server, type ATTACH You will be prompted to enter the file server name, your username on that file server, and your password (if required). After you have entered the information correctly, you will see a message similar to the following: You are attached to server SALES. NOTE: Although ATTACH connects you to a file server, it does not create a drive mapping to that file server. To map a network drive to the newly attached file server, use the MAP command line utility. Using Variables with ATTACH. You can include variables in an ATTACH command to specify the file server you want to connect to and your username for that file server. If you want to attach to file server RECORDS, type ATTACH RECORDS You will be prompted to enter your username and password (if required). You can also include both the file server name and your username in the command. If you (as user MARTIN) want to attach to file server RECORDS, type ATTACH RECORDS/MARTIN You will be prompted to enter your password. Using the /Private Option with ATTACH. If you want to attach to a file server on one OS/2 session only, type ATTACH /P You will be prompted to enter the name of the file server, your username, and your password (if required). After you have entered the information correctly, you will see a message similar to the following: You are privately attached to server SALES You will not be attached to that file server on any session other than the one you entered the command in. However, you can attach to that same file server globally from another session without affecting the private attachment. Additional Information To verify that you are attached to a particular file server, use the WHOAMI utility. Related Command Line Utilities LOGOUT CAPTURE Command Format CAPTURE [option ...] The ellipses (...) indicate that you can use more than one option in the same CAPTURE command. However, the SHow option cannot be used with any option other than Local=n. Replace option with any combination of the following options. SHow Include this option to view the current status of LPT ports. Do not use this option with any other CAPTURE option except Local=n. Local=n Include this option to indicate which LPT port to capture--1, 2, or 3. The default is L=1. Use this option with the SH option to view the current status of a specific LPT port. Server=server Include this option to indicate which file server the data should be sent to for printing. Replace server with the name of the file server. You must be attached to that file server before you specify this option. Queue=queue Include this option to indicate which queue the print job should be sent to for printing. Replace queue with the name of a print queue. Form=form or n Include this option to specify the form on which you want the job printed. Replace form or n with the number or name of the form. Copies=n Include this option to indicate how many copies of the print job you want printed. Replace n with a number. You can specify up to 256 copies. Tabs=n Include this option to replace all tab characters in your print job with the number of spaces n (0 to 18) that you specify. Use this option only if your application does not have a print formatter. NoTabs Include this option to ensure that all the tabs in your print job arrive at the printer unchanged. Use this option only if your application does not have a print formatter. NAme=name Include this option to specify the username you want to appear on the upper half of your banner page. Replace name with a username. The default is your username. Banner=banner Include this option to specify the banner word you want to appear on the lower half of your banner page. Replace banner with any word or phrase up to 12 characters long. Use an underline character (_) to represent a space between words (for example, IN_THE_BLACK). The default is LST:. NoBanner Include this option to specify that no banner page be printed. FormFeed Include this option to enable form feed after your print job has been printed. NoFormFeed Include this option to disable form feed at the printer. Keep Use this option as a safety feature. Include the Keep option in your CAPTURE command when you plan to capture data over several hours. The Keep option ensures that the file server will keep all data it receives from your workstation in the event that your workstation hangs or loses power while you are capturing data to the file server. Fifteen minutes after your workstation hangs or loses power, the file server will send the data it captured to a network printer for printing. If you do not include the Keep option in your CAPTURE command and your workstation hangs or loses power in mid- capture, the file server will discard the partial data it has received. /Private Include this option to capture an LPT port on one OS/2 session only. NOTE: The NetWare Requester version of CAPTURE does not include the Autoendcap, NoAutoendcap, Job, CReate, Printer, or TImeout options. How to Use CAPTURE Some OS/2 applications are designed to run on networks. When you use these applications, you can print files on network printers directly from the application. Many OS/2 applications, however, are not designed to run on a network. These applications are designed to send data to a local printer through one of the parallel (LPT) printer ports on the back of a standalone computer. Use CAPTURE to enable these applications to send data from your workstation to a network printer. You must issue an ENDCAP command to end the capture of an LPT port (see ENDCAP). Printing Data from Your Application on a Network Printer. To print data from an application that is not designed to run on a network, complete the following steps. 1)Before entering your application, type CAPTURE You will see a message similar to the following: Device LPT1 re-routed to queue PRINTQ_1 on server SALES. 2)Enter your application. 3)Print your data using the print keys for your application. Your application will send the print job to an LPT port on the back of your workstation. When the print job arrives at the LPT port, CAPTURE will redirect it to the default print queue of your default file server, and it will be printed. 4)When you are finished printing from your application, exit the application and type ENDCAP You will see a message similar to the following: Global capture ended. Device LPT1: set to local mode. Printing Screen Dumps. To print the information that appears on your screen, complete the following steps. 1)Type CAPTURE You will see a message similar to the following: Device LPT1 re-routed to queue PRINTQ_1 on server SALES. 2)Make sure the information you want to print appears on your workstation screen. 3)Press simultaneously. CAPTURE will automatically send your print job to the default print queue of your default file server, and the job will be printed. 4)When you are finished, type ENDCAP You will see a message similar to the following: Global capture ended. Device LPT1: set to local mode. Using the /Private Option with CAPTURE. If you want to capture an LPT port on one session without capturing that port on other sessions, type CAPTURE /P You will see a message similar to the following: Device LPT1 re-routed to queue PRINTQ_1 on server SALES. LPT1 will not be captured on any other session. To view whether a capture is private or global, type CAPTURE SH You will see information similar to the following: LPT1: Capturing private data to server SALES, queue ROOM Banner: LPT1: Catch Form Feed: Yes Copies: 1 Tabs: Converted to 8 spaces LPT2: Capturing is not currently active LPT3: Capturing is not currently active Specifying LPT, Copies, and Queue. If you want to print three copies of the information on your workstation screen using LPT2 and queue PRINTQ_1, complete the following steps. 1)Type CAPTURE L=2 C=3 Q=PRINTQ_1 You will see a message similar to the following: Device LPT2: re-routed to queue PRINTQ_1 on server SALES 2)Press simultaneously. The cursor will quickly scroll through the workstation screen display. 3)Type ENDCAP You will see a message similar to the following: Device LPT2: set to local mode. The information on your workstation screen will be sent through LPT2 to print queue PRINTQ_1, and three copies will be printed. Specifying File Server, Banner, Name, and Form Type. Suppose you want to print a file using a printer connected to file server SUPPORT. The file will have the banner MAYMEMO, and the name TECH, and it will use form type 1 (a memo form). 1)Type CAPTURE S=SUPPORT B=MAYMEMO NA=TECH F=1 or CAPTURE S=SUPPORT B=MAYMEMO NA=TECH F=MEMO You will see a message similar to the following: Device LPT1: re-routed to printer 0 on server SUPPORT 2)Enter the application and create the file; then follow the normal print process to print the file. If the correct form (memo) is mounted, network printer 0 connected to file server SUPPORT will print one copy of the file, using the banner name MAYMEMO and the name TECH. Displaying Option Settings. If you want to see whether any captures are in progress and what the option settings for those captures are, type CAPTURE SH Your workstation screen will display messages similar to the following: LPT1: Capturing global data to server RECORDS, queue PRINTQ_0 Banner: LST Form Feed: Yes Copies: 1 Tabs: Converted to 8 spaces LPT2: Capturing is not currently active. LPT3: Capturing is not currently active. You cannot use the SHow option to issue an actual CAPTURE. However, you can reset the parameters by executing the CAPTURE command again to start a new capture. Additional Information CAPTURE Defaults. If a default print job configuration and a default form are defined on your network (using the NetWare Spooler), CAPTURE will use those defaults. If those defaults are not defined on your network, CAPTURE will use the following defaults: þ All data will be re-routed to LPT1. LPT2 and LPT3 will not be affected. þ Data will be redirected to print queue PRINTQ_0. PRINTQ_0 is mapped to Printer 0, which is attached to your default file server. þ One copy of the data will be printed. þ A banner page will be printed before the data is printed. Your username will appear on the upper half of the banner page, and banner LST: will appear on the bottom half. þ Tabs will be converted to eight spaces. þ Form feed will be enabled. To define your own default print job options, you must reconfigure the NetWare Spooler. To do this, refer to the information in Appendix C of this manual. Overriding the Capture of an LPT Port. If you issue a CAPTURE command to capture an LPT port that you have already captured, the second CAPTURE command will override the first. Related Command Line Utilities ENDCAP CASTOFF Command Format CASTOFF [Console] Include the Console option to prevent messages sent from other workstations and the file server console from reaching your workstation. Do not include the Console option if you want to receive messages from the file server console but not from other workstations. How to Use CASTOFF Use CASTOFF to prevent messages sent from workstations or the file server console from reaching your workstation. IMPORTANT: When your network station receives a message, the station will not be able to execute any further instructions until you clear the message from the station by pressing . Before starting a process that can run unattended (compiling, recalculating, or remote hookup) on a workstation, you should issue a CASTOFF command to prevent other stations from interrupting the process. Blocking Messages Sent from Other Workstations. If you want to prevent messages sent from workstations from reaching your workstation and interrupting your work, type CASTOFF You will see a message similar to the following: Broadcasts from other stations will now be rejected. To enable your workstation to receive messages from other workstations, use the CASTON utility. Blocking Messages Sent from All Network Stations. To prevent messages sent from all network stations (including all workstations and the file server console) from reaching your workstation, type CASTOFF C You will see a message similar to the following: Broadcasts from the console and other stations will now be rejected. To enable your workstation to receive messages again from other workstations and the file server console, use the CASTON utility. Related Command Line Utilities CASTON CASTON Command Format CASTON How to Use CASTON Use CASTON to allow messages sent from all network stations (workstations and the file server console) to reach your workstation. (The CASTOFF utility prevents messages from network stations from reaching your workstation.) The default setting is CASTON enabled. To allow your workstation to receive messages from network stations, type CASTON You will see a message similar to the following: Broadcast messages from the console and other stations will now be accepted. Related Command Line Utilities CASTOFF ENDCAP Command Format ENDCAP [option ...] Replace option with one of the following: Local=n Include this option to end the capture of the specified LPT port. Replace n with 1, 2, or 3. Cancel Local=n Include this option to end the capture of the specified LPT port and to discard any data without printing it. /Private Include this option to end a private capture. The ellipses (...) indicate that you can include more than one option in the same ENDCAP command. How to Use ENDCAP Use ENDCAP to end the capture of one or more of your workstation's LPT ports. Ending the Capture of an LPT Port. If you want to end the capture of LPT1, type ENDCAP LPT1 will no longer be captured. Using the /Private Option with ENDCAP. The /Private option allows you to end the private capture of an LPT port on one session without affecting any other private or global capture. If you want to end the private capture of LPT1 on one session, type the following from that session: ENDCAP /P LPTl will no longer be captured on that session. Other captures will not be affected. Customizing Your ENDCAP Command. You can customize your ENDCAP commands to fit your situation. For example, to end the capture of LPT2, specify LPT2 in your ENDCAP command by using the Local=n option. Type ENDCAP L=2 To cancel the capture of LPT2 and to discard any data waiting to be sent to a network printer, use the Cancel Local=n option. Type ENDCAP C L=2 Related Command Line Utilities CAPTURE GRANT Command Format GRANT option ... [FOR path] TO [USER] user | [GROUP] group Replace option with one or more of the following: Read Use this option to grant the Read right. Write Use this option to grant the Write right. Open Use this option to grant the Open right. Create Use this option to grant the Create right. Delete Use this option to grant the Delete right. Parental Use this option to grant the Parental right. Search Use this option to grant the Search right. Modify Use this option to grant the Modify right. NO RIGHTS Use this option to revoke all rights. All Use this option to grant all eight trustee rights. You can include ONLY or ALL BUT before any of the first eight options listed above (for example, ONLY Read). If you include ONLY, you grant only the specified right. If you include ALL BUT, you grant all rights except the specified right. The ellipses (...) indicate that you can specify more than one option in the same GRANT command. Replace path with any directory path leading to the volume, directory, or subdirectory where you want to grant rights. Replace user with the name of the user to whom you want to grant rights. The vertical bar ( | ) indicates that you can specify a user or a group in your GRANT command, but not both. Replace group with the name of the group to whom you want to grant rights. USER is optional and will have no effect on the result of your command. Use it if you find it helpful. GROUP is also optional unless a user and a group have the same name and you want to specify the group. How to Use GRANT Use GRANT to grant trustee rights to users or groups in a given directory. You can also use the SYSCON utility to grant trustee rights to users or groups. NOTE: Before you can grant rights to a user or group, the user or group must exist on the network. Supervisors can use the SYSCON or MAKEUSER utilities to create users. A user or group can have up to eight trustee rights in a directory. They are as follows: þ Read Enables you to read the contents of files þ Write Enables you to write to files þ Open Enables you to open existing files þ Create Enables you to create files or subdirectories þ Delete Enables you to delete files or subdirectories þ Parental Enables you to modify the user's trustee rights and the maximum rights mask for directories þ Search Enables you to see the list of files þ Modify Enables you to set directory or file attributes and to rename files or subdirectories Before You Begin. You must have Parental effective rights in a directory to grant trustee rights to other users or groups in that directory. You must be attached to a file server before you can grant trustee rights in any directories on that file server. (See ATTACH.) You can grant trustee rights to only one user or one group per GRANT command. Granting Rights in Your Default Directory. Suppose you want to grant the trustee rights Read, Open, and Search to user FRED in your default directory. Type GRANT R O S TO USER FRED or GRANT R O S TO FRED Granting Rights in Any Directory. Suppose you want to grant the trustee rights Read, Open, and Search to user RUTH in the ACCPAY directory. Also suppose drive P is mapped to file server COUNT, volume ACCT, directory ACCPAY as follows: Drive P: = COUNT/ACCT:ACCPAY To grant these rights to RUTH, type GRANT R O S FOR P: TO RUTH or GRANT R O S FOR COUNT/ACCT:ACCPAY TO RUTH Granting All But a Certain Right. Suppose you want to grant all rights except Parental rights to user JOE in your default directory. Type GRANT ALL BUT P TO JOE Granting a Specific Right and Revoking All Other Rights. Suppose you want to grant Read rights to user LILI and to revoke all other rights that she may currently have in your default directory. Type GRANT ONLY R TO LILI Granting All Rights. Suppose you want to grant all rights to user ALLEN in your default directory. Type GRANT ALL TO ALLEN Revoking All Rights Using the GRANT Utility. Suppose you want to revoke all rights from user ROSA in your default directory. Type GRANT NO RIGHTS TO ROSA Granting Rights to a Group. To grant trustee rights to a group, specify the group name in the command instead of a username. If a user and a group have the same name, you must use the constant GROUP before the name of the group in your GRANT command. Additional Information The GRANT, REVOKE, and REMOVE command line utilities are all closely related. When you use the GRANT utility to grant even one trustee right to a user or group, the user or group is automatically enrolled on that directory's trustee list and then given the specified right. However, if you revoke all trustee rights from a user or group using the REVOKE utility, the user or group remains enrolled as a trustee of that directory until you remove the user or group using the REMOVE utility. Related Command Line Utilities REMOVE REVOKE RIGHTS TLIST HIDEFILE Command Format HIDEFILE [drive:] [directory/] filename Replace drive with the letter of the drive that contains the file you want to hide. Replace directory with the name of the directory that contains the file you want to hide. Replace filename with the name of the file you want to hide. How to Use HIDEFILE Use HIDEFILE to hide a specified file or files, so that the file(s) will not show in a DOS directory search and cannot be deleted or copied over. The HIDEFILE utility hides files by setting the OS/2 Hidden and System file attributes (refer to your OS/2 manual for details). Hiding a file prevents it from being copied over by a COPY command that specifies the same filename. (A COPY command specifying the name of a hidden file will return a "File Creation Error" message.) Hidden files cannot be deleted, nor can they be copied to other directories. However, hidden files are still accessible to most OS/2 commands (such as the TYPE command) and can be modified. Hidden files can also be backed up and restored using the NetWare BACKUP and RESTORE utilities if you have a Novell file server. Use the SHOWFILE utility to reveal files hidden by HIDEFILE. IMPORTANT: You must have Modify rights in the specified directory to use the HIDEFILE utility in that directory. To execute the HIDEFILE utility, you must either be in the directory that contains the HIDEFILE.EXE file (usually the SYS:SYSTEM directory), or you must map a drive to that directory and specify the drive before the command. For example, if you mapped drive G: to SYS:SYSTEM, then you could type G:HIDEFILE in any directory to execute the HIDEFILE utility. How to Use HIDEFILE 1)If your default directory contains the HIDEFILE.EXE file, type HIDEFILE 2)If the file you want to hide is not in your default directory, add the appropriate directory path by typing a drive letter or specifying the directory path: HIDEFILE [drive:] [directory/] You can specify a complete or partial directory path. For example, if the file you want to hide is in the SYS:PUBLIC directory and drive F is mapped to that directory, you could type either HIDEFILE F: or HIDEFILE SYS:PUBLIC 3)Add the name of the file you want to hide: HIDEFILE [drive:] [directory/] filename When specifying a filename, you can use wildcard characters * and ?. For example, suppose you want to hide the file TEST which is located in the directory SALES. You have mapped drive G to the SYS:SYSTEM directory, which contains the HIDEFILE.EXE file. Complete the following steps. 1)Change to the SALES directory. 2)Type G:HIDEFILE TEST You will see information similar to the following: FS1/SYS:SALES TEST hidden 3)Now, if you type DIR TEST will not be listed, as shown below: Volume in drive D is SYS Directory of D:\SALES OEM DOC 2432 5-02-89 3:53p DOC 5-01-89 3:23p 2 File(s) 5566464 bytes free 4)Even though TEST is hidden, if you type TYPE TEST the contents of the file will be displayed on the workstation screen. 5)To make TEST visible again, type G:SHOWFILE TEST Now if you type DIR TEST will again appear in the directory listing. Related Commands SHOWFILE LISTDIR Command Format LISTDIR [path] [option ...] Replace path with a directory path leading to and including the volume, directory, or subdirectory you want to view. Replace option with one or more of the following: /Subdirectories Include this option to view not only the subdirectories of a given directory, but also all subsequent subdirectories. /Rights Include this option to view the maximum rights mask of specified directories. /Effective Rights Include this option to view your effective rights in specified directories. /Date or /Time Include this option to view the creation date of specified directories. /All Include this option to view the maximum rights mask and the creation date of all subdirectories and all subsequent subdirectories in a given directory. This option combines the functionality of the other four options. The ellipses (...) indicate that you can specify more than one option in the same LISTDIR command. How to Use LISTDIR Use LISTDIR to view the subdirectories of any given directory. Depending on the options you include in your LISTDIR command, you can also view the maximum rights mask of directories, the creation date of directories, your effective rights in directories, and subsequent subdirectories. Before You Begin. You must be attached to a file server before you can use LISTDIR to view the subdirectories of any directory on that file server. After you issue a LISTDIR command, you can use the keys or the Pause key to temporarily stop your screen from scrolling through all the subdirectories in a given directory. Press any key to resume scrolling. Viewing Subdirectories in Your Default Directory. To view the subdirectories in your default directory, type LISTDIR You will see a list of the subdirectories in your default directory. Viewing Subdirectories in Any Directory. To view subdirectories in a given directory, specify the directory path leading to the directory in your LISTDIR command. For example, suppose you want to view the subdirectories in the ACCPAY directory in volume ACCT on file server COUNT. Also suppose drive P is mapped as follows: Drive P: = COUNT/ACCT:ACCPAY To view the subdirectories in ACCPAY, type LISTDIR P: or LISTDIR COUNT/ACCT:ACCPAY By replacing path in the LISTDIR command format with P: or COUNT/ACCT:ACCPAY, you specify the ACCPAY directory. Viewing Subdirectories and All Subsequent Subdirectories in a Directory. Include the /Subdirectories option in your LISTDIR command if you want to view the complete structure of a directory. To view subdirectories and all subsequent subdirectories in your default directory, type LISTDIR /S To view subdirectories and all subsequent subdirectories in any directory, specify the directory path leading to that directory in your LISTDIR command. Viewing the Maximum Rights Mask of Subdirectories. Include the /Rights option in your LISTDIR command if you want to view the maximum rights mask of subdirectories in a directory. To view the maximum rights mask of subdirectories in your default directory, type LISTDIR /R To view the maximum rights mask of all subdirectories in any directory, specify the directory path leading to that directory in your LISTDIR command. Viewing the Effective Rights of Subdirectories. Include the /Effective Rights option in your LISTDIR command if you want to view the effective rights you have in the subdirectories of a directory. To view the effective rights you have in your default directory, type LISTDIR /E To view the effective rights you have in all subdirectories in any directory, specify the directory path leading to that directory in your LISTDIR command. Viewing the Creation Date of Subdirectories. If you want to see when subdirectories in a directory were created, include the /Date option in your LISTDIR command. To view the creation date and time of all subdirectories in your default directory, type LISTDIR /D or LISTDIR /T To view the creation date and time of subdirectories in any directory, specify the appropriate directory path in your LISTDIR command. Using the All Option in Your LISTDIR Command. Include the All option to view the maximum rights mask and the creation date of all subdirectories and all subsequent subdirectories in a given directory. To view all available information about the subdirectories in your default directory, type LISTDIR /A or LISTDIR /S/R/D/E To view all available information about the subdirectories in any directory, specify the directory path leading to that directory in your LISTDIR command. Using Wildcard Characters in Your LISTDIR Command. Use the wildcard characters * and ? with any LISTDIR option to specify the directories you want to view. Suppose you want to view all of your effective rights in subdirectories of your default directory that begin with S. Type LISTDIR S*.* /E Only information about subdirectories that begin with S will be listed. Related Command Line Utilities NDIR RIGHTS LOGIN Command Format LOGIN [/Private] [server/[user[option ...]]] Replace server with the name of the file server that you want to log in to. Replace user with your username. Replace option with one or more of the LOGIN options that you create. For a complete explanation of LOGIN options (also called parameters), see IF...THEN Commands on page ?. Use the /Private option to log in privately on different sessions. If you use the /Private option with LOGIN, you will be logged in to that file server on that session only. You can also log in privately to a file server on one sesion and globally to that same file server on all other sessions. However, if you log in privately and globally to the same file server, you must specify whether you want to break the private connection or the global connection when you issue a logout command (see LOGOUT). How to Use LOGIN Use LOGIN to invoke your login script for a particular file server and gain access to that server's resources. (Your access to a server's resources is always limited by your effective rights on that server.) Logging In to Your Default File Server. When you boot your workstation with the NetWare Requester, your workstation transparently attaches to the logically closest file server on your network. This file server becomes your default server until you log in to another server. To log in to your default server, type LOGIN You will then be prompted to enter your username and (if applicable) your password. Logging In to Any File Server. Suppose, as user SANDY with password BEACH, you want to log in to file server COUNT. Type LOGIN COUNT/SANDY You will see the following prompt: Enter your password: Type BEACH You will then be logged in to server COUNT. As the LOGIN command format indicates, you can also include only the name of the file server in your LOGIN command: LOGIN COUNT You will then be prompted to enter your username and password. If you do not specify a file server name or a username in your LOGIN command, you will be prompted to enter both. You will also be prompted to enter a password if one is required. Logging In without a Password. Suppose you want to log in to file server COUNT as user SANDY without a password. Type LOGIN COUNT/SANDY You would then be logged in to server COUNT. Using the /Private Option with LOGIN If you want to log in to a file server on one OS/2 session only, include the /Private option in your LOGIN command. Type LOGIN /P You will be prompted to enter the name of the file server, your username, and your password (if required). You will not be logged in to that file server on any session other than the one you entered the command in. However, you can log in to that same file server globally from another session without affecting the private login. Additional Information Including a LOGIN Command in Your STARTUP.CMD File. If you frequently log in to the same file server, you may want to include a LOGIN command in your STARTUP.CMD file. Synchronizing Passwords. If your login script attaches you to more than one file server when you log in, LOGIN will automatically check if all passwords are valid. If a password has expired, LOGIN will ask you if you want to change it. If you choose to do so, LOGIN will ask you if you want to synchronize passwords (make all passwords the same). If you answer "Yes," LOGIN will synchronize all passwords for all file servers you attach to in your login script with the same username you used to log in. If you attach to servers in your login script using a different username than the username for your default file server, those passwords will not be synchronized. Logging Out with LOGIN. Whenever you issue a LOGIN command, you not only log in to the specified file server, but you also automatically log out of any file servers to which you were attached before you issued the LOGIN command. For example, suppose you are logged in to file server COUNT and attached to servers MKTG and SALES. If you issue a LOGIN command to log in to server LEGAL, you will both log in to server LEGAL and log out of servers COUNT, MKTG, and SALES. If you want to gain access to another file server and remain logged in to your default server, use the ATTACH utility. Related Command Line Utilities ATTACH LOGOUT LOGOUT Command Format LOGOUT [server ... ] [/Private] Replace server with the name of the file server(s) you want to log out of. The ellipses (...) in the command format indicate that you can specify more than one file server. The type of logout (global or private) that you use in a session depends on the type of attachment that file server has in that particular session. If you have attached to a file server privately on one session and also to that same file server globally on all other sessions and you want to log out of the private connection, you must be in the session where you are attached privately to that file server. If you want to log out of the global connection, you must be in a session where you are attached globally to that file server. You cannot specify a private logout from a global attachment. How to Use LOGOUT Use LOGOUT to log out of one or more file servers. When you log out of a file server, you terminate your access to it. IMPORTANT: When you log out of a file server, all of your drive mappings associated with that file server disappear. Before you log out, make sure that two of your remaining drive mappings are mapped to SYS:LOGIN/OS2 and SYS:PUBLIC/OS2 of a file server you will remain attached to. If you do not have any drives mapped to these directories, you will lose access to the NetWare utilities contained in these directories and you will have to reboot your workstation. Logging Out of All File Servers. To log out of all file servers you are attached to, type LOGOUT You will see a message that shows you which file servers you have logged out of and whether the logouts were global or private. Logging Out of One File Server. To log out of one file server, specify the file server name in your LOGOUT command. For example, if you are attached to file servers RECORDS, SALES, and CORP, and you want to log out of file server SALES, type LOGOUT SALES You will be logged out of file server SALES, but you will still be attached to file servers RECORDS and CORP. You will see a message that shows you which file server you have logged out of and whether the logout was global or private. Logging Out of Multiple File Servers. To log out of more than one file server but remain attached to others, specify the file server names in the LOGOUT command. For example, if you are attached to file servers RECORDS, SALES, CORP, and LEGAL and you want to log out of RECORDS and SALES, type LOGOUT RECORDS SALES You will be logged out of RECORDS and SALES without losing your connections to CORP and LEGAL. You will see a message that shows you which file servers you have logged out of and whether the logouts were global or private. Using the /Private Option with LOGOUT. Suppose you have attached to file server ACCT globally, and you have also attached to it privately in one session. If you want to log out of the private attachment while remaining attached to file server ACCT in all other sessions, type the following from the session in which you are attached privately: LOGOUT ACCT /P You will be logged out of the private attachment while remaining attached to file server ACCT globally. Related Command Line Utilities ATTACH MAKEUSER (Command Line Utility) Command Format MAKEUSER filename How to use MAKEUSER Use MAKEUSER to process USR files created either in the MAKEUSER menu utility or with a text editor. These USR files enable a supervisor to create or delete many users with a single text file rather than creating or deleting each file individually. MAKEUSER is both a menu and a command line utility. It is in the SYS:PUBLIC directory rather than the SYS:SYSTEM directory. The menu utility allows you to create, edit, and process USR files. (USR files contain commands or keywords to create or delete multiple users. See page 31 for a complete explanation of the MAKEUSER menu utility.) Before you can use the MAKEUSER command line utility, you must create a USR file using either the MAKEUSER menu utility or a text editor. A USR file enables a supervisor to create or delete many users with a single text file rather than creating or deleting each user individually. The MAKEUSER command line utility provides a way to process USR files from outside of the MAKEUSER menu utility, but you cannot create or edit USR files using the MAKEUSER command line utility. Before you can use the MAKEUSER command line utility, you must create a USR file. The USR file you want to process with MAKEUSER must be in the current directory. For this reason, we suggest that you create a specific directory for the MAKEUSER files. How to Use MAKEUSER 1)Change to the directory containing the USR file you want to process and then type MAKEUSER filename You can type the filename with or without the .USR extension. The USR file will be scanned for any syntax or logic errors. If there are any errors, you will see a message similar to the following: Error : Line 1, Undefined keyword Warning: Line 2, Group expected Please fix the error in the file and try it again. You must correct any errors using the "Edit USR Files" option of the MAKEUSER menu utility or with a text editor. Then start over with Step 1. If there are no errors, the USR file will be processed and a report file, filename.RPT, will be placed in the current directory. You will see a message similar to the following: Check the results in filename.RPT 2)To check the results, type TYPE filename.RPT You will see a message similar to the following: User USER1 created User USER2 not created Already exists For example, suppose you want to create user accounts for students in three sections of an English class. Using the MAKEUSER menu utility or a text editor, you could create three USR files named SEC1.USR, SEC2.USR, and SEC3.USR. To process the USR file to create users in section 1 of the English class, type the following at the DOS prompt: MAKEUSER SEC1.USR The SEC1.USR file would be processed and a report file, SEC1.RPT, would be put in the current directory. To see the report file, you would type TYPE SEC1.RPT The report file would indicate which users were actually created. If any users were not created, the report would tell you why. MAKEUSER (Menu Utility) The MAKEUSER menu utility allows you to create or delete users by creating and processing USR files. These text files contain the keywords needed to create or delete multiple users. This utility is particularly valuable if you have to create and delete users on a regular basis (such as setting up user accounts for new students each semester) or if you have a large number of users to create. IMPORTANT: The system defaults set up in SYSCON do not apply to users created with MAKEUSER. How to Use MAKEUSER To use MAKEUSER, you must complete two basic steps. First, you must create a text file with the extension .USR. This text file must contain the keywords needed to create or delete multiple users. You may also optionally specify trustee rights, assign users to groups, set an accounting balance, and specify login and password restrictions. Next, you must process this file to create or delete the users according to the conditions you have specified in the USR file. If you make any errors in creating the file, you can edit the file. Each of these steps is explained in the following sections. Creating USR files. The first step in using MAKEUSER to create or delete users is to create a USR file. This file lists the user(s) you want to create, along with whatever rights and restrictions you want those users to have. You will enter the keywords needed to provide this information. Use the MAKEUSER menu utility "Create New USR File" option to create USR files. NOTE: You can also use any text editor to create USR files. Access the text editor and type the appropriate MAKEUSER keywords as explained below. Follow the instructions in the text editor documentation. Be sure the file has the .USR extension. When you create a USR file with MAKEUSER, the file is placed in the current directory. Whenever you need to edit or reprocess a USR file, you must first access the directory in which the file was created. You cannot access USR files that were created in another directory. For this reason, you may want to create a directory for all USR files. For example, you might want to create a directory USERS with subdirectories STUDENTS and ASSISTANTS. The STUDENTS directory might have subdirectories such as FALL89 and WINTER90. Then, each time you used MAKEUSER to create or delete user accounts for students in a class in the fall semester of l989, you would move to the USERS/STUDENTS/FALL89 directory before executing MAKEUSER. To create a USR file with the MAKEUSER menu utility, complete the following steps: 1)Access the directory in which you want to create the USR file. 2)Type MAKEUSER The "Available Options" menu will be displayed. 3)Highlight "Create New USR File" and press . The "Creating a new USR file" entry box will appear. 4)In this box, enter the keywords needed to create or delete users. Keywords you can use in a USR file are explained below. These keywords allow you to create and delete users as well as assign the users password/login restrictions, trustee rights, home directories, etc. You will need to carefully read the explanations of the keywords before you will be able to understand how to use them. These files allow you to set up one set of password/login restrictions, rights, home directories, etc., for a number of different users. You do not need a separate set of restrictions for each user. For example, to create three new users and create home directories for each of them in the SYS:HOME directory, you would type #HOME_DIRECTORY SYS:HOME #CREATE User1^ #CREATE User2^ #CREATE User3^ 5)After you have entered the keywords you want, save the file by pressing . The "Save Changes" confirmation box will appear. 6)Highlight "Yes" and press . The "Enter the new USR file name" box will appear. 7)Type a filename in the box and press . You will be returned to the "Available Options" menu. Processing USR files. MAKEUSER will not create or delete users until the USR file is processed. You can process a USR file in two ways. þ You can use the MAKEUSER menu utility "Process USR File" option. þ You can process a USR file from the DOS prompt by using the MAKEUSER command line utility. To process a USR file with the MAKEUSER menu utility, complete the following steps. 1)Move to the directory that contains the USR file you want to process and access the MAKEUSER utility by typing MAKEUSER The "Available Options" menu will be displayed. 2)Highlight the "Process USR File" option and press . An "Enter USR File name" entry box will appear. 3)Type the name of the USR file in the entry box and press . First the file will be scanned for any syntax errors. You may see error messages similar to the following on your screen: Keyword expected Specification exceeded the limit, the rest of the line ignored Username CHUCK already specified These errors will be reported on the screen and must be corrected with a text editor or by using the MAKEUSER "Edit USR File" option before the file can be processed (see "Editing USR Files" on page below). Once the file is successfully scanned, it will be processed. Logic errors such as "Group NOBODY could not be found" or "User Tom already exists" will be placed in a report (RPT) file, along with the results of processing the USR file. 4)You should always check the report file to see if your USR file has been processed successfully. To do this, (A) Exit the MAKEUSER utility. (B) At the DOS prompt, enter the DOS TYPE command and the name of the USR file with a .RPT extension you have just processed. For example, if the USR filename is DEPT1.USR, you would type TYPE DEPT1.RPT You would see the contents of the DEPT1.RPT file. If the results are not what you expected, you can return to the MAKEUSER utility and edit the USR file. Editing USR files. The MAKEUSER menu utility allows you to edit a USR file. This feature is especially useful for correcting errors in a USR file, but MAKEUSER will not create or change an account for a user already on the network. If you need to make changes to the USR file before you process it, complete the steps below. If you need to change the file after you have processed it, you must reprocess the file after making your corrections before changes will affect the users created by the file. If you need to make changes and do not want to reprocess the whole USR file, you can access the appropriate option in the SYSCON utility and make the desired changes. For example, to assign a new account balance to an individual user originally created with MAKEUSER, refer to "Setting up account balances for users." To edit a USR file with the MAKEUSER menu utility, complete the following steps. 1)Move to the directory that contains the USR file you want to edit and access the MAKEUSER utility by typing MAKEUSER The "Available Options" menu will be displayed. 2)Highlight the "Edit USR File" option and press . An "Enter USR File name" entry box will appear. 3)Type the name of the USR file in the entry box and press . You can also press to see a list of USR files in your current directory. Highlight the one you want to edit and press . 4)Make the appropriate changes to the file. 5)After you have entered the changes you want, save the file by pressing . The "Save Changes" confirmation box will appear. 6)Highlight "Yes" and press . You will be returned to the "Available Options" menu. Deleting USR files. You can delete USR files at the DOS prompt. First, move to the directory that contains the USR file(s) you want to delete. If you want to delete all USR files, type ERASE *.USR If you want to delete only one specific file, type ERASE filename.USR KEYWORDS USED IN MAKEUSER The MAKEUSER keywords along with a brief statement of purpose are listed alphabetically below. Each keyword is described in detail on the following pages. You enter these keywords when you create the USR file. Keyword Statement of Purpose ACCOUNT EXPIRATION Specifies when a user's account will expire ACCOUNTING Specifies amount of accounting services a user can use CLEAR or RESET Starts a new set of keywords in the same USR file CONNECTIONS Specifies maximum concurrent connections each new user can have CREATE Creates users and specifies information about them DELETE Deletes users and relative information GROUPS Assigns users to groups HOME DIRECTORY Creates home directories in a specified directory path LOGIN SCRIPT Assigns a login script to each user MAX DISK SPACE Specifies the amount of disk space a user can use PASSWORD LENGTH Specifies a password's length PASSWORD PERIOD Assigns the number of days between password expirations PASSWORD REQUIRED Requires users to have a password PURGE USER DIRECTORY Deletes the home directory and any subdirectories owned by the user REM Allows comments to be entered in the file; the comments are not processed RESTRICTED TIME Specifies when the user cannot log in to the file server STATIONS Restricts the physical workstations a user can log in from UNIQUE PASSWORD Requires a unique password when the password is changed Several restrictions apply to entering keywords. þ The CREATE or DELETE keywords must be included; all other information is optional. For this reason, we suggest you read the explanations of the CREATE and DELETE keywords first. þ All other keywords that you want to apply to specific users must precede the CREATE or DELETE keywords for those users. þ The CLEAR/RESET keyword can be used to mark the beginning of a new set of keywords within the same file. þ Each keyword must be on a separate line. þ If the same keyword is specified more than once, only the last value is used; any previous values will be ignored by the utility. For example, if "#groups gl; g2;" is specified on a line before "#groups g3;", the user will only be added to the group g3 when the file is processed. The user will not be added to groups g1, g2, and g3. Check the explanation for each keyword if you have questions. ACCOUNT EXPIRATION Keyword Format #ACCOUNT_EXPIRATION DateSpec Use this keyword to specify when the new users' accounts expire. If not used, the accounts will never expire. This keyword is used only in conjunction with ACCOUNTING. You must specify this keyword before the CREATE keyword. You must also use a full, formal date format. This keyword will apply to all users until you enter a RESET or CLEAR keyword (see the explanation under "CLEAR"). For example, to assign User1 and User2 an account expiration date of July 24, l989, use the following keywords. #account_expiration July 24, l989 #create user1^ #create user2^ ACCOUNTING Keyword Format #ACCOUNTING Balance, LowLimit This keyword specifies the Account Balance and Low Balance limit for the users you create. You must specify this keyword before the CREATE keyword. These limits must be numeric values only. The value of these units depends on what you specify as you set up the accounting system on your file server. This keyword applies only if the file server supports accounting. Both Balance and LowLimit must be specified, and Balance cannot be less than LowLimit. This keyword will apply to all users until you enter a RESET or CLEAR keyword. For example, to assign User1 a balance of 1000 and a lowlimit of -200 and User2 a balance of 500 and a low limit of 0, use the following keywords. #accounting 1000, -200 #create user1^ #clear #accounting 500, 0 #create user2^ CLEAR or RESET Keyword Format #CLEAR or #RESET These keywords allow you to start a new set of keywords in the same USR file. It is as if you are starting a new file after each CLEAR or RESET keyword. All previous keywords encountered in the USR file will have no effect on what follows the CLEAR keyword. This keyword is used if you want to use unique keywords for each user or group of users. Enter the CLEAR or RESET keywords whenever you want to start a new set of keywords. For example, suppose you want to add User1 and User2 to the group SALES. User3 will be assigned time restrictions but will not be added to the group SALES. #groups Sales #create User1^ #create User2^ #clear #restricted_time Mon, 12:00p.m.,2:00 p.m. #create User3^ CONNECTIONS Keyword Format #CONNECTIONS Number This keyword specifies the maximum concurrent connections each new user can have. If not specified, each user will have as many concurrent connections as the file server supports. You must specify this keyword before the CREATE keyword. This keyword will apply to all users until you enter a RESET or CLEAR keyword. You can specify from 1 to 100 connections. For example, suppose you want to allow User1 and User2 to log in from only one workstation at a time. Enter the following keywords: #connections 1 #create user1^ #create user2^ CREATE Keyword Format #CREATE UserName; FullName; Password; Group [,Group]; TrusteeDirectory [Rights] [,TrusteeDirectory [Rights]] Use this keyword to create users and specify information about them. Although you must include the CREATE keyword in order to create a new user, all optional keywords that apply to that user must be entered on a line that precedes the CREATE keyword. Do not confuse optional keywords with the variables included in the CREATE keyword. You must also be very careful to enter the information according to the format specified. Note that all italicized words in the command format are variables and should be replaced by the appropriate information. An explanation of each of the variables follows: UserName The account name of the user to be created. The UserName must be provided; all other variables are optional. FullName The full name of the user. The name cannot contain commas. Password The password of the user to be created. Group The group(s) that a new user will belong to. Each user is automatically assigned to the group EVERYONE. You can add a user to more than one group. The square brackets around the second group indicate that assigning users to more than one group is optional. Groups can also be assigned with the GROUP keyword. TrusteeDirectory [Rights] The list of the directories in which the user will have certain access rights. The rights can be optionally specified for each directory and must be preceded by a space. You can specify rights in more than one directory. The square brackets around the second TrusteeDirectory indicate that assigning more than one directory is optional. If all rights are to be given to the user in a given directory, specify the name of the directory followed by ALL (for example, SYS:HOME ALL). The default rights are ROS (Read, Open, Search). The following restrictions apply to the CREATE keyword: þ Separate all fields (UserName; FullName; Password; etc.) by a semicolon. If a field can contain more than one variable, separate the subfields (Group 1, Group 2) by a comma. þ To extend the information for each keyword to the next line, put a "+" after a field or sub-field (for example: "password;+" or "group1;+"). þ Do not put the same username in one USR file more than once. If you do, an error will be reported in the scanning process. þ If you do not want to specify all the variables listed above, insert a double semicolon (;;) to indicate that one field is missing, or insert a caret (^) to terminate a line at any point. The following example creates user NANCY; assigns her the full name Nancy I. Smith; assigns her a password, knockknock; makes her member of two groups, CLASS1 and CLASS5; and assigns her all trustee rights to the SYS:READ directory. #create nancy; Nancy I. Smith; knockknock; CLASS1, CLASS5;+ SYS:READ ALL To create user JACK and assign him only the password "openup," you would type #create jack;;openup;; To create user ROSALIE and not include any other variables, you would type #create rosalie^ DELETE Keyword Format #DELETE UserName [; UserName] This keyword deletes users and any information relative to the specified user(s). You can enter the DELETE keyword in the same file as the CREATE keyword. For example, in a teaching environment, you might want to delete the users of classes taught last semester as you created users for classes taught this semester. However, DELETE cannot be used with any of the same usernames that are in the CREATE list unless CLEAR or RESET separates the two instances of the same name. If you want to delete the user's home directory when you delete the user, you must precede the DELETE keywords with both the HOME_DIRECTORY and PURGE_USER_DIRECTORY keywords. Suppose you want to create users SUSAN, CHRIS, and KEN and assign them home directories. You also want to delete users JOYCE, MARK, and EV and remove their home directories. #home_directory SYS:HOME #create susan^ #create chris^ #create ken^ #purge_user_directory #delete joyce; mark; ev GROUPS Keyword Format #GROUPS Group [;Group] This keyword assigns users to a group. Only groups you have already created with SYSCON can be included. New users are automatically assigned to the group EVERYONE. New users can also be assigned to groups using the CREATE keyword. You must specify the GROUPS keyword on a line preceding the CREATE keyword. Suppose you want to assign LARRY to groups G1 and G2. Enter the following keywords. #groups g1;g2 #create larry^ HOME DIRECTORY Keyword Format #HOME_DIRECTORY DirectoryPath This keyword can be used both in creating and in deleting a user. When this keyword is used before the CREATE keyword, MAKEUSER will try to create home directories under users' names in the specified directory path. All rights are automatically assigned to the home directory. If this keyword is not used, a home directory will automatically be created in the SYS: volume. When this keyword is used with DELETE, MAKEUSER will automatically try to delete the subdirectories under the user's name in the SYS: volume. To use this keyword in creating a user, type it before the CREATE command. This keyword will apply to all users until you enter a RESET or CLEAR keyword. If this keyword was used when creating a user, it must also be specified when deleting a user. Type it before the DELETE command. If the home directory is not in the SYS: volume, the directory path must be specified. Path specifications should always have the format "vol:dir1\subdir\...." You can only specify directories that have already been created. The format for this keyword is the same, whether used with CREATE or with DELETE. For example, suppose you want to create the home directory in the SYS:NEWUSERS directory for user ROBIN. Enter the following keywords. #home_directory sys:newusers #create robin^ To delete user ROBIN and her home directory, you would enter the following keywords. #home_directory sys:newusers #purge_user_directory #delete robin^ LOGIN SCRIPT Keyword Format #LOGIN_SCRIPT FileSpec This keyword specifies the location of the file containing a login script to be copied and used as each new user's login script. The file containing the login script must already exist. You must create the file in SYSCON (NetWare stores login scripts in the MAIL directory under the user ID number) or use a text editor to create a login script file and put it in a convenient directory. It will be placed in each newly created user's mail directory. You must specify this keyword before the CREATE keyword. This keyword will apply to all users until you enter a RESET or CLEAR keyword. To assign user DAN a login script found in the file EVERYONE.LOG in the SYS:PUBLIC directory, you would enter the following keywords. #login_script sys:public/everyone.log #create dan^ MAX DISK SPACE Keyword Format #MAX_DISK_SPACE Number This keyword specifies the maximum number of disk blocks (4KB in size) allocated for each new user. The default is an unlimited number of disk blocks. Use numeric values only. The specified value will always be rounded up to a multiple of four since disk space is allocated in 4KB units. You must specify this keyword before the CREATE command. This keyword will apply to all users until you enter a RESET or CLEAR keyword. You can only use this keyword if the disk limitation option was selected during installation. For example, suppose you want to assign user KELLEY a maximum disk space of 4 megabytes (4096KB). Enter the following keywords. #max_disk_space 4096 #create kelley^ PASSWORD LENGTH Keyword Format #PASSWORD_LENGTH Length This keyword specifies the minimum length of the new users' passwords. The length must be between 1 and 20 characters. The default is five characters. You must enter PASSWORD_REQUIRED before you enter PASSWORD_LENGTH. You must specify both keywords before the CREATE keyword. This keyword will apply to all users until you enter a RESET or CLEAR keyword. For example, suppose you want to require user JAN to have a password of at least seven characters. Use the following keywords. #password_required #password_length 7 #create jan^ PASSWORD PERIOD Keyword Format #PASSWORD_PERIOD Days This keyword assigns the number of days between password expirations. If it is not used, the password will never expire. You must enter the PASSWORD_REQUIRED keyword before you enter the PASSWORD_PERIOD keyword. You may specify 1 to 365 days. You must specify this keyword before the CREATE command. This keyword will apply to all users until you enter a RESET or CLEAR keyword. For example, suppose you want to require user BILL to change his password every thirty days. Use the following keywords. #password_required #password_period 30 #create bill^ PASSWORD REQUIRED Keyword Format #PASSWORD_REQUIRED Use this keyword to require users to have a login password. If this keyword is not specified, users can decide whether or not to assign passwords to their accounts. You must enter the PASSWORD REQUIRED keyword before the PASSWORD_LENGTH, UNIQUE_PASSWORD, or PASSWORD_PERIOD keywords can be specified. You must specify this keyword before the CREATE keyword. This keyword will apply to all users until you enter a RESET or CLEAR keyword (see the explanation under "CLEAR"). For example, suppose you want to require user TRENT to have a password. Use the following keywords. #password_required #create trent^ PURGE USER DIRECTORY Keyword Format #PURGE_USER_DIRECTORY This keyword is used to delete any subdirectories owned by the user when the user is deleted. It is also used in conjunction with the HOME_DIRECTORY keyword to delete the user's home directory. You must enter this keyword before the DELETE keyword. If you want to delete the user's home directory, you must include the HOME_DIRECTORY keyword. For example, suppose you want to delete user KEN, his home directory in the SYS:HOME directory, and any subdirectories he may have created. Use the following keywords. #home_directory SYS:HOME #purge_user_directory #delete ken^ REM Keyword Format #REM or REM You may want to make comments about the information in your USR file. To do so, precede the comments with this keyword. The REM keyword must appear as the first word on the line. The rest of the line will be ignored when the file is processed. For example, to identify the contents of a USR file, include the REM keyword. #rem students in english 302 winter semester '89 #create student1^ #create student2^ #create student3^ RESTRICTED TIME Keyword Format #RESTRICTED_TIME Day, Start, End [;Day, Start, End] This keyword specifies what days during the week and what times during the day the new users cannot log in to the file server. If this keyword is not used, no restrictions apply. The following restrictions apply to the RESTRICTED_TIME keyword. þ End time cannot be earlier than Start time. (12:00 a.m. is acceptable after a p.m. start time.) þ Normal day-of-week and time-of-day formats are expected. þ Day can have the value "everyday" to indicate every day of the week. You must specify this keyword before the CREATE command. This keyword will apply to all users until you enter a RESET or CLEAR keyword. For example, suppose you want to prevent user MARCI from logging in on Monday from 8:00 a.m. to 2:00 p.m. Use the following keywords. #restricted_time mon, 8:00 am, 2:00 pm #create marci^ STATIONS Keyword Format #STATIONS Network, Station [,Station] [;Network, Station [,Station]] This keyword specifies the physical workstations from which users can log in to the file server. If this keyword is not used, users will be able to log in from any workstation. To use the STATIONS keyword, you must supply the network and station addresses. The following restrictions apply: þ Addresses must be entered in hexadecimal notation. þ Network addresses cannot have more than 8 digits; station addresses cannot have more than 12 digits. þ If all stations are to be included for any given network, you can replace the station address with "all" (i.e., Stations 12345, all). You must specify this keyword before the CREATE command. This keyword will apply to all users until you enter a RESET or CLEAR keyword. For example, suppose you want to allow user PETER to log in only from station FE and DD on Network 12345. Use the following keywords. #stations 12345, FE, DD #create peter^ UNIQUE PASSWORD Keyword Format #UNIQUE_PASSWORD When this keyword is specified, users cannot duplicate the previous eight passwords when they change their passwords. If this keyword is not specified, users can choose passwords they have used previously. You must first enter the PASSWORD_REQUIRED keyword before you enter the UNIQUE_PASSWORD keyword. You must specify this keyword before the CREATE keyword. This keyword will apply to all users until you enter a RESET or CLEAR keyword. For example, suppose you want to require user MARJ to change to a unique password every thirty days, use the following keywords. #password_required #password_period 30 #unique_password #create marj^ MAKEUSER KEYWORDS QUICK REFERENCE For your convenience, the MAKEUSER keywords along with their formats are listed alphabetically below. This list can be used as a quick reference after you are familiar with each keyword. #ACCOUNT EXPIRATION DateSpec #ACCOUNTING Balance, LowLimit #CLEAR or #RESET #CONNECTIONS Number #CREATE UserName; FullName; Password; Group [,Group]; TrusteeDirectory [Rights] [,TrusteeDirectory [Rights]] #DELETE UserName [; UserName] #GROUPS Group [;Group] #HOME_DIRECTORY DirectoryPath #LOGIN_SCRIPT FileSpec #MAX_DISK_SPACE Number #PASSWORD_LENGTH Length #PASSWORD_PERIOD Days #PASSWORD_REQUIRED #PURGE_USER_DIRECTORY #REM or REM #RESTRICTED_TIME Day, Start, End [;Day, Start, End] #STATIONS Network, Station [,Station] [;Network, Station [,Station]] #UNIQUE_PASSWORD USING MAKEUSER TO CREATE AND DELETE USERS The following examples show how to use the MAKEUSER utility to create and delete users. Creating users The following example explains how to create a USR file that will create two users; assign each a full name and password; and create a home directory for each user in the SYS:HOME directory (assuming you have created a SYS:HOME directory). 1)To access the MAKEUSER utility, type MAKEUSER The "Available Options" menu will be displayed. 2)Highlight "Create New USR File" and press . The "Create New USR File" screen will appear. 3)For this example, assume that you want to make a remark about your USR file. Since remarks need to be entered first, type #REM MAKEUSER Creating Users Example 4)Now enter the optional keywords you want to apply to the users you are creating. In this instance you want to create a home directory in the SYS:HOME directory. Type #HOME_DIRECTORY SYS:HOME You can enter as many optional keywords as you want at this point. 5)After you enter the keywords, you must create the users you need by entering the CREATE keyword, substituting the appropriate information for each of the variables. Use the following keyword format: #CREATE UserName; FullName; Password; Group1 [,Group2]; TrusteeDirectory [Rights], [TrusteeDirectory [Rights]] For this example, assume that the first user is Kirk W. Jones, whose password is "letmein." Type #CREATE kirk; Kirk W. Jones; letmein;; The last semicolon indicates that you are not assigning the user to any group and that you are not making any trustee assignments. To create the second user, Jennifer Wilson, whose password is "hello" type #CREATE jennifer; Jennifer Wilson; hello;; The last semicolon indicates that you are not assigning the user to any group and that you are not making any trustee assignments. Your USR file should look like this: #REM MAKEUSER Creating Users Example #HOME_DIRECTORY SYS:HOME #CREATE kirk; Kirk W. Jones; letmein;; #CREATE jennifer; Jennifer Wilson; hello;; 6)To save the USR file, press . A "Save Changes" confirmation box will appear. 7)Highlight "Yes" and press . The "Enter the New USR file name" entry box will appear. 8)You must assign a name to the file you have created. For this example, type the following in the box: NEW You will be returned to the "Available Options" menu. You have created a new file, NEW.USR (MAKEUSER adds the extension automatically), which can now be processed to create two new users. Processing the USR file Once you have created a USR file, you must process the file to create the users as specified in the file. When a USR file is processed, it is checked for any contradictory commands and for proper syntax. If there are any mistakes, an error message will appear on the screen indicating which line contains the error and what the error is. If any error messages occur, return to the "Available Options" menu and choose the "Edit USR File" option to correct the mistakes. If there are no mistakes, the commands listed in the file will then be executed. To process the USR file you just created, complete the following steps: 1)Highlight "Process USR File" in the "Available Options" menu, and press . The box that appears should contain the filename NEW.USR. If it does not, press to see a list of available USR files. Highlight NEW.USR. 2)Press . If you receive any error messages, check to make sure you typed the keywords exactly as described in Steps 3 through 5 of the preceding section. The file will be processed, and User1 and User2 will be created. The results will be directed to a file whose name is listed at the bottom of the screen. In this case, the file is NEW.RPT. 3)To exit MAKEUSER, press twice. Then highlight "Yes" in the "Exit Makeuser" confirmation box and press . 4)To check the report file to see if the USR file has been successfully executed, type TYPE NEW.RPT Do not assume that since the file is processed, all the commands have been executed. Logic errors, such as "Group 1 does not exist" will be reported in the .RPT file. Another way to verify that the new users have been created is to access the "User Information" option in SYSCON. Deleting users To delete users with MAKEUSER, you must create a USR file and then process it. The USR file must contain the DELETE keyword. You can delete users in the same file that you create users by including the DELETE keyword in that file. However, in this example, you will create a separate file named DELETE to delete users KIRK and JENNIFER. This example assumes you have completed the previous example in which you created these users. 1)Type MAKEUSER The "Available Options" menu will be displayed. 2)Highlight "Create New USR File" and press . The "Creating a new USR file" screen will be displayed. 3)To delete users KIRK and JENNIFER, type #HOME_DIRECTORY SYS:HOME #PURGE_USER_DIRECTORY #DELETE kirk, jennifer The DELETE keyword deletes users KIRK and JENNIFER. The PURGE_ USER_DIRECTORY keyword removes the home directory for each user. The HOME_DIRECTORY keyword specifies where the home directory is located. 4)To save the USR file, press . A "Save Changes" confirmation box will appear. 5)Highlight "Yes" and press . The "Enter the New USR file name" entry box will appear. 6)To assign a name to the file you have created, type the following in the box: DELETE You will be returned to the "Available Options" menu. You have created a new file, DELETE.USR (MAKEUSER adds the extension automatically), which can now be processed to delete two new users. 7)To process the USR file, highlight the "Process USR File" option. The DELETE filename should appear in the box. 8)Choose the file by pressing . (If you wanted to process a different file, you would press to see a list of available USR files.) MAKEUSER will scan and process the file and then place the results in the DELETE.RPT file. MAP Command Formats MAP [drive:] [/Private] Use this command format to view your current drive mappings. MAP drive:=path [/Private] MAP drive:=directory [/Private] Use these command formats to extend, map, or remap your default drive. MAP drive:=drive: [/Private] Use this command format to map or remap any network drive. MAP DEL drive: [/Private] MAP REM drive: [/Private] Use these command formats to delete a drive mapping. Replace drive with a network drive letter, such as F or G. Replace path with a directory path leading to and including the volume, directory, or subdirectory you want to map the drive to. How to Use MAP Use MAP to view your current drive mappings, to remap your network drives, or to add or delete drive mappings. Drive mappings are temporary. They disappear when you log out of or turn off your workstation. If you want to map permanent drive mappings, you must include them in your STARTUP.CMD file (see Appendix B). Viewing Your Current Drive Mappings. To view the current drive mappings of the session you are in, type MAP You will see information similar to the following: Drive A: maps to a local drive Drive B: maps to a local drive Drive C: maps to a local drive Drive F: = RECORDS/SYS:HOME/KARA Drive G: = RECORDS/SYS: Drive H: = RECORDS/ACCT:ACCDATA Drive L: = RECORDS/SYS:LOGIN/OS2 Drive P: = RECORDS/SYS:PUBLIC/OS2 MAP allows you to view the current drive mappings for that OS/2 session only. If you have used the /Private option to set any private drive mappings, the list of drive mappings will vary depending on the session. To view the mapping of a specific drive (for example, drive F), specify the drive in the command as follows: MAP F: You will see information similar to the following: Drive F:=RECORDS/SYS:HOME/KARA Remapping Your Default Drive. To remap your default drive, type MAP and the new directory path; then press . For example, suppose your default drive, drive G, is mapped to RECORDS/SYS. Also suppose you want to remap drive G to RECORDS/ACCT:ACCDATA. To remap drive G, type MAP ACCT:ACCDATA You do not have to include the file server name RECORDS in the command because server RECORDS is your default server. Mapping Network Drives. Suppose you want to map drive M on file server RECORDS to SYS:MAY. Type MAP M:=RECORDS/SYS:MAY If you are not already attached to file server RECORDS, you will be prompted to enter your username and password for server RECORDS before drive M is mapped to RECORDS/SYS:MAY. If another drive, such as drive Z, were already mapped to RECORDS/SYS:MAY, you could also type the following command to get the same result: MAP M:=Z: Extending Your Default Drive Mapping. Suppose your default drive, drive G, is mapped to RECORDS/SYS: and you want to extend it to include HOME/KARA. Type MAP G:=HOME/KARA or MAP G:=RECORDS/SYS:HOME/KARA Mapping Network Drives to the Same Path as Your Default Drive. Suppose you want to map drive S to the same path as your default drive, drive G, which is mapped to RECORDS/SYS:. Type MAP S:=RECORDS/SYS: or MAP S:=G: or MAP S:= All three commands will map drive S to RECORDS/SYS:. Using the /Private Option with MAP. Suppose you want to map drive M to RECORDS/SYS:PROGRAM on one session only. Type MAP M:=RECORDS/SYS:PROGRAM /P Drive M will be mapped to RECORDS/SYS:PROGRAM on that session only; it will not be mapped on any other session. Mapping Search Drives. You cannot use the MAP command line utility to map search drives on OS/2 workstations. See the OS/2 reference manual for information about mapping search drives with the PATH and DPATH commands. Deleting Drive Mappings. To delete a network drive mapping (for example, drive G), type one of the following commands: MAP DEL G: or MAP REM G: You cannot delete your default drive mapping. Additional Information You cannot map a local drive; however, you can map network drive E to a RAM disk. NOTE: A local drive is a drive letter mapped to a floppy disk drive or to your workstation hard disk drive. A network drive is a drive letter mapped to a disk on a file server. NCOPY Command Format NCOPY filespec [TO] [path] [filename] Replace filespec with a directory path leading to and including the file you want to copy. Replace path with a directory path leading to and including the volume, directory, or subdirectory to which you want to copy the file. Replace filename with a new filename if you want to rename the file you are copying. TO is optional in all NCOPY commands. How to Use NCOPY Use NCOPY to copy one or more files from one network directory to another. You can also use NCOPY to copy files to and from directories on local drives. Copying a File from Your Default Directory to Another Directory. Suppose you want to copy the ACC.DAT file from your default directory to G:SALES/SYS:MAJOR. Type NCOPY ACC.DAT TO G: or NCOPY ACC.DAT TO SALES/SYS:MAJOR SALES/ is optional in the second command if file server SALES is your default server. Copying a File from Any Directory to Your Default Directory. Suppose you want to copy the ACC.DAT file from G:SALES/SYS:MAJOR to your default drive, drive F. At your default drive prompt, type NCOPY G:ACC.DAT or NCOPY SALES/SYS:MAJOR/ACC.DAT SALES/ is optional in the second command if file server SALES is your default server. Copying a File from One Directory to Another on the Same File Server. Suppose drives F and G are mapped as follows: Drive F:=RECORDS/SYS:MAY Drive G:=RECORDS/ACCT:PROGRAMS Also suppose you want to copy the ACC.DAT file from the MAY directory to the PROGRAMS directory. Type NCOPY F:ACC.DAT TO G: or NCOPY SYS:MAY/ACC.DAT TO ACCT:PROGRAMS The ACC.DAT file will be copied to ACCT:PROGRAMS. Copying a File from a Directory on One File Server to a Directory on Another. Suppose drives F and G are mapped as follows: Drive F:=RECORDS/SYS:PUBLIC Drive G:=SALES/SYS:PROGRAMS Also suppose you want to copy the FINDIT.EXE file from RECORDS/SYS:PUBLIC to SALES/SYS:PROGRAMS. Type NCOPY F:FINDIT.EXE TO G: or NCOPY RECORDS/SYS:PUBLIC/FINDIT.EXE TO SALES/SYS:PROGRAMS The FINDIT.EXE file will be copied to SALES/SYS:PROGRAMS. Copying a File and Renaming It. Suppose drives S and T are mapped as follows: Drive S:=RECORDS/SYS:PROJECTS Drive T:=RECORDS/ACCT:YEAR Also suppose you want to copy the ACC.DAT file from RECORDS/SYS:PROJECTS to RECORDS/ACCT:YEAR and rename the file MAY. Type NCOPY F:ACC.DAT TO G:MAY or NCOPY SYS:PROJECTS/ACC.DAT TO ACCT:YEAR/MAY The ACC.DAT file will be copied to ACCT:YEAR and renamed MAY. Copying More Than One File with One NCOPY Command. Include wildcard characters in your command to copy several related files with one NCOPY command. For example, suppose drives S and T are mapped as follows: Drive S:=RECORDS/SYS:PROJECTS Drive T:=RECORDS/ACCT:YEAR Also suppose you want to copy all of the .EXE files in the PROJECTS directory to the YEAR directory. Type NCOPY S:*.EXE TO T: or NCOPY SYS:PROJECTS/*.EXE TO ACCT:YEAR To copy all of the files in the PROJECTS directory to the YEAR directory, replace *.EXE with *.* in the commands above. You can use the wildcard characters * or ? separately or in any combination to indicate which files you want to copy. Additional Information To copy files to and from directories when no drives are mapped to those directories, specify the appropriate path in your NCOPY command. New files retain the last update and time of original files. The last-accessed date and time and the creation date and time will change. NPRINT Command Format NPRINT filespec [option ...] Replace filespec with the path leading to and including the name of the file you want to print. You can also replace it with only the drive letter of a mapped path. The ellipses (...) indicate that you can specify more than one option in the same NPRINT command. Replace option with one or more of the following: Server=server Include this option to indicate which file server the data should be sent to for printing. Replace server with the name of the file server. Job=job name Include this option to specify the name of the print job configuration to be used. Queue=queue Include this option to indicate which queue the print job should be sent to for printing. Replace queue with the name of the queue. Form=form or n Include this option to specify the form you want to print the job on. Replace form or n with the number or name of the form. Copies=n Include this option to indicate how many copies of the job you want to print. Replace n with a number. You can specify up to 256 copies. Tabs=n Include this option to replace all tab characters in your print job with the number of spaces n (0 to 18) you specify. Use this option only if your application does not have a print formatter. NoTabs Include this option to ensure that all the tabs in your print job arrive at the printer unchanged. Use this option only if your application does not have a print formatter. NAme=name Include this option to specify the username you want to appear on the upper half of your banner page. Replace name with a username. The default name is your username. Banner=banner Include this option to specify the banner word you want to appear on the lower half of your banner page. Replace banner with any word or phrase up to twelve spaces long. Use an underline character to represent a space between words (for example, IN_THE_BLACK). The default banner is the name of the file you are printing. NoBanner Include this option to specify that no banner page be printed. FormFeed Include this option to enable form feed after your print job has been printed. FormFeed enabled is the default. NoFormFeed Include this option to disable form feed at the printer. Delete Include this option to automatically erase the file after you print it. How to Use NPRINT Use NPRINT to send files to a network printer. These files must be OS/2 text files or files that have already been formatted by an application for your specific printer. NOTE: At present, NPRINT does not allow you to specify a file with the following familiar syntax: NPRINT server/volume:directory/.../filename Instead, you must specify a file by using the following Uniform Naming Convention (UNC): NPRINT \\server\volume\directory\...\filename NPRINT also does not allow you to print multiple files or to use wildcard characters. Each NPRINT command can be no more than 128 characters long. Printing Data Using the NPRINT Defaults. Suppose you want to print the MAX.RPT file located in F:RECORDS/SYS:HOME/MAX. If drive F is your default drive, type NPRINT MAX.RPT If drive F is not your default drive, type NPRINT F:MAX.RPT or NPRINT \\RECORDS\SYS\HOME\MAX\MAX.RPT Since you did not specify in the command where or how you want the file printed, NPRINT will use default settings. If you have defined a default job configuration and a default form on your network (using the NetWare Spooler defaults), NPRINT will follow those defaults. If you have not defined your own defaults on your file server, NPRINT will use the following default settings. þ The file will be sent to the printer attached to the default file server. þ Data will be redirected to print queue PRINTQ_0. PRINTQ_0 is mapped to Printer 0, which is attached to your default file server. þ One copy of the file will be printed. þ A banner page will be printed before the file is printed. Your username will appear on the top half of the banner page, and the filename will appear on the bottom half. þ Tabs will be converted to eight spaces. þ Form feed will be enabled. To define your own printer defaults, refer to the information in Appendix C. Using NPRINT Options. You can use any combination of the NPRINT options to customize your NPRINT command. For example, suppose you want to print four copies of the MAX.RPT file located in F:RECORDS/SYS:HOME/MAX. You also want to print the word CONFIDENTIAL on the bottom half of the banner page. If drive F is your default drive, type NPRINT MAX.RPT C=4 B=CONFIDENTIAL If drive F is not your default drive, type NPRINT F:MAX.RPT C=4 B=CONFIDENTIAL or NPRINT \\RECORDS\SYS\HOME\MAX\MAX.RPT C=4 B=CONFIDENTIAL Since you did not specify a username in the command, your default username will appear on the top half of the banner page. If you do not specify a particular option in your command, the default setting for that option will be used. PSTAT Command Format PSTAT [option ...] Replace option with one or both of the following: Server=server Include this option if you want to view information about printers attached to a file server other than your default server. Replace server with the name of the file server. Printer=printer Include this option if you want to view information about a particular printer. Replace printer with the name of the printer. The ellipses (...) indicate that you can specify more than one option in the same PSTAT command. How to Use PSTAT Use PSTAT to view the following information about one or more network printers: þ The printer number. (The network installer numbered the printers during network installation.) þ Whether the printer is on-line or off-line. (A printer is on-line when the printer's power switch and on-line switch are ON.) þ Whether the printer has been activated ("Active") or deactivated ("Stopped") at the file server console. þ The kind of paper ("Form") the printer is currently using, identified by both the form number and the form name. Before You Begin. If you are not attached to the file server specified in your PSTAT command, PSTAT will automatically and transparently attach you as GUEST. However, if GUEST has a password on the server, PSTAT will prompt you for a username and a password before allowing you to continue. Viewing Information about All the Printers Connected to Your Default File Server. To view information about all the printers connected to your default file server, type PSTAT You will see information similar to the following: Server COUNT : Network Printer Information Printer Ready Status Form: number, name ---------- ----------- ---------- ------------------------------ 0 On-line Active 1, reports 1 Off-line Stopped 0, unknown name 2 On-line Stopped 1, reports This screen display shows information about all printers connected to file server COUNT. Viewing Information about One Printer Connected to Your Default File Server. To view information about Printer 1 connected to your default file server, type PSTAT P=1 You will see information similar to the following: Server COUNT : Network Printer Information Printer Ready Status Form: number, name ---------- --------- ---------- ------------------------------ 0 On-line Active 1, reports This screen display shows information about Printer 1 connected to server COUNT. Viewing Information about All the Printers Connected to Any File Server. Suppose you want to view information about all the printers connected to file server SALES. Type PSTAT S=SALES You will see information similar to the following: Server SALES : Network Printer Information Printer Ready Status Form: number, name ---------------------- ---------- ----------------------------- 0 On-line Active 1, reports 1 Off-line Stopped 0, unknown name 2 On-line Stopped 1, reports This screen display shows information about all printers connected to server SALES. Viewing Information about One Printer Connected to Any File Server. Suppose you want to view information about Printer 1 connected to file server SALES. Type PSTAT S=SALES P=1 You will see information similar to the following: Server SALES : Network Printer Information Printer Ready Status Form: number, name ---------- --------- ----------- ------------------------------ 1 On-line Active 1, reports This screen display shows information about Printer 1 connected to server SALES. Additional Information If you take a printer off-line and then quickly issue a PSTAT command, the message that appears on your screen will indicate that the printer is still on-line. When someone on your network sends a file to that printer to be printed, the file server will register that the printer is off-line. Then, when you issue a PSTAT command, the message will correctly indicate that the printer is off-line. PURGE Command Format PURGE How to use PURGE Use PURGE to permanently erase all previously erased files. You can erase files by using the OS/2 ERASE or DEL commands. A file that is erased using one of these methods can be recovered using the NetWare SALVAGE utility. However, when you issue a PURGE command after erasing files with ERASE or DEL, you permanently erase those files. PURGE only affects files that have been erased from your workstation. NOTE: A file server has a limited number of available directory entries. Each directory, file, or trustee list occupies one directory entry. When you erase a file using the OS/2 ERASE or DEL commands, you make that file inaccessible, but you do not remove the attachment between the file and the directory entry. The erased file still occupies one directory entry. The only way to free that directory entry is to issue a PURGE command. Executing a PURGE command. To permanently erase all previously erased files, type PURGE You will see a message similar to the following: All your recoverable erased files have been purged from the network. Related Command Line Utilities SALVAGE REMOVE Command Format REMOVE [USER] user | [GROUP] group [[FROM] path] [/SUBdirectory] The vertical bar ( | ) indicates that you can specify a user or a group in your REMOVE command, but not both. Replace user with the name of the user you want to remove from the trustee list of a given directory. Replace group with the name of the group you want to remove from the trustee list of a given directory. Replace path with a directory path leading to and including the volume, directory, or subdirectory from which you want to remove a user or group. Include /SUBdirectory in your command if you want to remove a user or group from the trustee lists of a given directory and its subsequent subdirectories. USER, GROUP, and FROM are optional. Include these words in your command if you find them helpful. How to Use REMOVE Use REMOVE to remove a user or group from the trustee list of a given directory. NOTE: A trustee of a directory is any user or group who has at least partial trustee rights in that directory. Each directory has a trustee list of all trustees and their rights. To add trustees to the trustee list of a directory, use the SYSCON or MAKEUSER menu utilities or the GRANT command line utility. To remove trustees, use the SYSCON or MAKEUSER menu utilities or the REMOVE command line utility. To view the trustee list of a directory, use the TLIST command line utility. Before You Begin. To remove a user or group from the trustee list of a given directory, you must have Parental effective rights in that directory. You must be attached to a file server before you can remove a user or group from the trustee list of a directory on that file server. You can remove only one user or one group from the trustee list of one directory with each REMOVE command. Removing a User or Group from the Trustee List of Your Default Directory. Suppose you want to remove user DAVE from the trustee list of your default directory. Type REMOVE USER DAVE or REMOVE DAVE To remove group STAFF from the trustee list of your default directory, type REMOVE GROUP STAFF or REMOVE STAFF Removing a User or Group from Any Directory. Suppose you want to remove user LARRY from the PROGRAMS directory. Also suppose drive G is mapped to the PROGRAMS directory as follows: Drive G: = COUNT/SYS:PROGRAMS To remove user LARRY from the trustee list of the PROGRAMS directory, type REMOVE USER LARRY FROM G: or REMOVE USER LARRY FROM COUNT/SYS:PROGRAMS You can also omit USER and FROM as follows: REMOVE LARRY G: or REMOVE LARRY COUNT/SYS:PROGRAMS To remove group STAFF from the PROGRAMS directory, substitute GROUP for USER and STAFF for LARRY in the commands above. Removing a User or Group from a Directory and Subsequent Subdirectories. Suppose you want to remove user DAVE from the trustee list of your default directory and all of its subdirectories. Type REMOVE DAVE /S or REMOVE DAVE /SUB Additional Information The GRANT, REVOKE, and REMOVE command line utilities are all closely related. When you use the GRANT utility to grant even one trustee right to a user or group, the user or group is automatically enrolled on that directory's trustee list and then given the specified right. However, if you revoke all trustee rights from a user or group using the REVOKE utility, the user or group remains enrolled as a trustee of that directory until you remove the user or group using the REMOVE utility. Related Command Line Utilities GRANT REVOKE REVOKE Command Format REVOKE option ... [FOR path] FROM [USER] user | [GROUP] group [/SUBdirectory] Replace option with one or more of the following: Read Use this option to revoke the Read right. Write Use this option to revoke the Write right. Open Use this option to revoke the Open right. Create Use this option to revoke the Create right. Delete Use this option to revoke the Delete right. Parental Use this option to revoke the Parental right. Search Use this option to revoke the Search right. Modify Use this option to revoke the Modify right. ALL Use this option to revoke all trustee rights. The ellipses (...) indicate that you can specify more than one option in the same REVOKE command. Replace path with any directory path leading to the volume, directory, or subdirectory where you want to revoke rights. If you specify a path, you must also include FOR in the command. Replace user with the name of the user whose rights you want to revoke. The vertical bar ( | ) indicates that you can specify a user or a group in your REVOKE command, but not both. Replace group with the name of the group whose rights you want to revoke. Include /SUBdirectory in your command if you want to revoke rights from a user or group in a given directory and its subsequent subdirectories. USER is optional and will have no effect on the result of your command. Use it if you find it helpful. GROUP is also optional unless a user and a group have the same name and you want to specify the group. How to Use Revoke Use REVOKE to revoke trustee rights from a user or group in a given directory. (You can also use the SYSCON menu utility to revoke trustee rights. A user or group can have up to eight trustee rights in a directory. They are as follows: Read Enables you to read the contents of files Write Enables you to write to files Open Enables you to open existing files Create Enables you to create files or subdirectories Delete Enables you to delete files or subdirectories Parental Enables you to modify the user's trustee rights and the maximum rights mask for directories Search Enables you to see the list of files Modify Enables you to set directory or file attributes and to rename files or subdirectories Before You Begin. You must have Parental effective rights in a directory to revoke trustee rights from other users or groups in that directory. You must be attached to a file server before you can revoke trustee rights in any directory on that file server. You can revoke trustee rights from only one user or one group with each REVOKE command. Revoking Rights in Your Default Directory. Suppose you want to revoke Parental and Modify rights from user REIKO in your default directory. Type REVOKE P M FROM USER REIKO or REVOKE P M FROM REIKO If you want to revoke all trustee rights from user REIKO, type REVOKE ALL FROM USER REIKO or REVOKE ALL FROM REIKO To revoke trustee rights from group STAFF in your default directory, substitute GROUP for USER and STAFF for REIKO in the examples above. Revoking Rights in Any Directory. Suppose you want to revoke Parental and Modify rights from user JULIAN in the DATA directory. Also suppose drive G is mapped to DATA as follows: Drive G: = COUNT/SYS:DATA To revoke these rights from user JULIAN, type REVOKE P M FOR G: FROM USER JULIAN or REVOKE P M FOR G: FROM JULIAN You must include FOR in the command if you specify a path. USER is optional. Including it in your command or leaving it out will not affect the result of your command. You can also indicate the appropriate directory by specifying the full directory path in the command as follows: REVOKE P M FOR COUNT/SYS:DATA FROM USER JULIAN or REVOKE P M FOR COUNT/SYS:DATA FROM JULIAN To revoke trustee rights from group STAFF in the DATA directory, substitute GROUP for USER and STAFF for JULIAN in the examples above. Revoking Rights from a User or Group in a Directory and Subsequent Subdirectories. Suppose you want to revoke Parental and Modify rights from user REIKO in your default directory and all of its subdirectories. Type REVOKE P M FROM USER REIKO /S or REVOKE P M FROM REIKO /SUB Additional Information The GRANT, REVOKE, and REMOVE command line utilities are all closely related. When you use the GRANT utility to grant even one trustee right to a user or group, the user or group is automatically enrolled on that directory's trustee list and then given the specified right. However, if you revoke all trustee rights from a user or group using the REVOKE utility, the user or group remains enrolled as a trustee of that directory until you remove the user or group using the REMOVE utility. Related Command Line Utilities GRANT REMOVE RIGHTS Command Format RIGHTS [path] Replace path with any directory path leading to the volume, directory, or subdirectory where you want to view your effective rights. How to Use RIGHTS Use RIGHTS to view your effective rights in a given directory. You can have up to eight rights in any given directory: Read Enables you to read the contents of files Write Enables you to write to files Open Enables you to open existing files Create Enables you to create files or subdirectories Delete Enables you to delete files or subdirectories Parental Enables you to modify the user's trustee rights and the maximum rights mask for directories Search Enables you to see the list of files Modify Enables you to set directory or file attributes and to rename files or subdirectories NOTE: The trustee and directory rights have been changed in NetWare v2.15. You can now use the Create right to create files and directories; the Delete right to delete files and directories; and the Modify right to change file and directory attributes. You no longer need the Parental right to create or delete directories. Rights can be restricted in two ways: þ A supervisor can define a maximum rights mask for a directory. For example, the supervisor might specify that the most rights any user can have in the ACCPAY directory are Read, Open, Create, and Search rights. þ A supervisor, or user with equivalent rights, can grant certain trustee rights to specific users. For example, the supervisor might grant user SVEN Read, Write, Open, and Search rights in the ACCPAY directory. Effective rights are the intersection of the maximum rights mask for a given directory and a user's trustee rights in that directory. For example, SVEN's effective rights in the ACCPAY directory consist of the rights that appear in both the maximum rights mask and SVEN's trustee rights: Read, Open, and Search. Viewing Your Effective Rights in Your Default Directory. To view your rights in your default directory, you can specify the directory path in your RIGHTS command. If you do not specify a directory path, the default directory will be assumed. For example, if your current directory is the SYS:PUBLIC directory on the SERVER1 file server and you want to view your effective rights in that directory, type RIGHTS If your effective rights include all rights, you will see the following information: SERVER1\SYS:PUBLIC Your effective rights are [RWOCDPSM]: You may Read from Files. (R) You may Write to Files. (W) You may Open existing Files. (O) You may Create new Files. (C) You may Make new Subdirectories. (C) You may Delete existing Files. (D) You may Erase existing Subdirectories. (D) You may Change Users' Directory Rights.(P) You may Search the Directory. (S) You may Modify File Status Flags. (M) You have ALL RIGHTS to this directory area. Viewing Your Effective Rights in Any Directory. Suppose you want to view your effective rights in the PROJECTS directory. Also suppose drive G is mapped to the PROJECTS directory on file server COUNT as follows: Drive G: = COUNT/SYS:PROJECTS Type RIGHTS G: or RIGHTS COUNT/SYS:PROJECTS You will see information similar to the following: Your Effective Rights are [RWOC SM]: You may Read from Files. (R) You may Write to Files. (W) You may Open existing Files. (O) You may Create new Files. (C) You may Make new Subdirectories. (C) You may Search the Directory. (S) You may Modify File Status Flags. (M) In this directory, your effective rights include Read, Write, Open, Create, Search, and Modify. Related Command Line Utilities LISTDIR SALVAGE Command Format SALVAGE [path] Replace path with the directory path leading to and including the volume, directory, or subdirectory you want to indicate. You can also replace path with the drive letter of the path. You do not need to specify the exact directory from which the file you want to salvage was erased. You must, however, specify the appropriate volume. How to Use SALVAGE Use SALVAGE to recover one file that has been erased and restore it to its original directory. If you erase a file that you want to recover, note the following: þ Do not log out of your file server. Once you log out, you cannot recover your erased file. þ Do not create or erase any more files on the volume from which your file was erased. SALVAGE cannot recover a file once another file has been created or deleted on the same volume. þ Do not issue a PURGE command. A PURGE command will permanently erase all previously erased files. þ Activity at other workstations on the network will not affect the file you erased. þ You must issue a SALVAGE command at the same workstation from which the file was erased. þ When you issue a SALVAGE command, you do not have to specify the exact directory from which the file was erased. You must, however, specify the appropriate volume. Salvaging a File Erased from Your Default Volume. To salvage a file you erased from your default volume, type SALVAGE The SALVAGE utility will recover the last file erased from your default volume at your workstation. If several files were erased with one ERASE or DEL command just before you entered your SALVAGE command, only the last file erased will be recovered. Salvaging a File Erased from Any Directory. Suppose you erase the file SEPT.RPT from F:=RECORDS/SYS:HOME/MGR and you want to recover the file. Before creating or deleting any more files on volume SYS, type SALVAGE RECORDS/SYS: or SALVAGE F: You will see a message similar to the following: Salvaging files on volume RECORDS/SYS: SEPT.RPT recovered. If SEPT.RPT was the last file erased from volume SYS, it will be recovered. Related Command Line Utilities PURGE SEND Command Format SEND "message" [TO] [USER] [server/]user ... SEND "message" [TO] [GROUP] [server/]group ... SEND "message" [TO] [USER] [server/]user ... [GROUP] [server/]group ... Use the first command format to send a message to one or more users; use the second to send a message to one or more groups; use the third to send a message to one or more users and one or more groups. Replace message with any string of characters up to 45 characters long minus the number of characters in your username. Include server only if the user to whom you want to send a message is not logged in to your file server. Replace server with the name of the user's file server. Replace user with the name of the user to whom you want to send a message. Replace group with the name of the group to which you want to send a message. The only time you must use the word GROUP in a SEND command is when both a user and a group have the same name and you want to send a message to the group. The ellipses (...) indicate that you can send a message to more than one user or group. How to Use SEND Use SEND to send a short message to one or more users and/or groups on your network. NOTE: Only PC workstations support the SEND utility. Before You Begin. Before you can send a message to a user or group on another file server, you must be attached to that file server. Sending a Message to a User or Group Logged In to Your Default File Server. Suppose you want to send the following message to HANS: "Meeting at 1:30 today." Type SEND "MEETING AT 1:30 TODAY" TO USER HANS or SEND "MEETING AT 1:30 TODAY" HANS You will see a message similar to the following: Message sent to COUNT/HANS (station 5). COUNT/HANS indicates that the message was sent to user HANS on file server COUNT (your default server). To send the same message to group STAFF, substitute GROUP for USER and STAFF for HANS in the examples above. Sending a Message to a User or Group on Any File Server. Suppose you want to send the following message to ISABEL: "Meeting at 1:30 today." Also suppose ISABEL is logged in to file server SALES. To send the message, type SEND "MEETING AT 1:30 TODAY" TO USER SALES/ISABEL or SEND "MEETING AT 1:30 TODAY" SALES/ISABEL You will see a message similar to the following: Message sent to SALES/ISABEL (station 5). SALES/ISABEL indicates that the message was sent to user ISABEL on file server SALES. To send the same message to group STAFF, substitute GROUP for USER and STAFF for ISABEL in the examples above. Sending a Message to Several Users or Groups. Suppose you want to send the following message to user INGA on your default file server, user HETI on server UTIL, group STAFF on server COUNT, and group DAYCREW on server SALES: "Meeting at 1:30 today." Type SEND "MEETING AT 1:30 TODAY" TO USER INGA UTIL/HETI GROUP COUNT/STAFF SALES/DAYCREW or SEND "MEETING AT 1:30 TODAY" INGA UTIL/HETI COUNT/STAFF SALES/DAYCREW (Note that because INGA is logged in to your default server, you do not have to specify a file server for INGA in the command.) SETPASS Command Format SETPASS [server] Replace server with the name of the file server for which you want to set or change your password. How to Use SETPASS Use SETPASS to set or change your password on a given file server. A password can consist of up to 127 characters, but it cannot include control characters. You must be attached to a file server before you can set or change your password on that file server. Setting a Password. To set a new password, complete the following steps. 1)To set a password on your default file server, type SETPASS To set a password on a file server other than your default server, include the name of the server in the command. For example, if you want to set a password on file server RECORDS, type SETPASS RECORDS You will see a prompt similar to the following: Enter your old password: 2)Since you do not have a password, press . You will see a prompt similar to the following: Enter your new password: 3)Type the new password and press . You will see a prompt similar to the following: Retype your new password: 4)Retype your new password and press . You will see a message similar to the following: Your password has been changed. Changing Your Password. To change your password, complete the following steps. 1)To change your password on your default file server, type SETPASS To change your password on a file server other than your default server, include the name of the file server in the command. For example, if you want to change your password on server RECORDS, type SETPASS RECORDS You will see a prompt similar to the following: Enter your old password: 2)Type your old password and press . You will see a prompt similar to the following: Enter your new password: 3)Type your new password and press . You will see a prompt similar to the following: Retype your new password: 4)Retype your new password and press . You will see a message similar to the following: Your password has been changed. SHOWFILE Command Format SHOWFILE [drive:] [directory/] filename How to Use SHOWFILE Use SHOWFILE to make a file or files hidden by the HIDEFILE utility visible again. The SHOWFILE utility makes a specified file visible by clearing the file's Hidden and System attributes. After the SHOWFILE utility is executed, a previously hidden file will again appear in a directory listing and can be changed or deleted. IMPORTANT: You must have Modify rights in the specified directory to use the SHOWFILE utility. To execute the SHOWFILE utility, you must either be in the directory that contains the SHOWFILE.EXE file (usually the SYS:SYSTEM directory), or you must map a drive to that directory and specify the drive before the command. For example, if you mapped drive G: to SYS:SYSTEM, then you could type G:SHOWFILE in any directory to execute the SHOWFILE utility. How to Use SHOWFILE 1)If your default directory contains the SHOWFILE.EXE file, type SHOWFILE 2)If the file you want to show is not in your default directory, add the appropriate directory path by typing a drive letter or specifying the directory path: SHOWFILE [drive:] [directory/] You can specify a complete or partial directory name. For example, if the file you want to hide is in the SYS:PUBLIC directory and drive F is mapped to that directory, type SHOWFILE F: or SHOWFILE SYS:PUBLIC 3)Add the name of the file you want to "show" and press the Enter key. SHOWFILE [drive:] [directory/] filename When specifying a filename, you can use wildcards (* and ?). For example, suppose you are in the directory SALES, which contains a file named TEST that has been hidden with the HIDEFILE utility. You have mapped drive G to the SYS:SYSTEM directory. 1)Type G:SHOWFILE TEST You will see information similar to the following: fileserver/SYS:SALES Test visible 2)Now, if you type DIR TEST will be shown in the directory listing, along with the other files. Related Commands HIDEFILE SLIST Command Format SLIST [file server] [/Continuous] If you want to view information about one file server only, replace file server with the name of that file server. Include the /Continuous option if you want the list of file servers to scroll down the screen without stopping. How to Use SLIST Use SLIST to view information about the file servers running on your internetwork. Viewing Information about One File Server. Suppose you want information about file server RECORDS only. Type SLIST RECORDS You will see information similar to the following: Known NetWare File Servers Network Node Address --------------------------------------------------------------------- RECORDS CED88 2608C234732 "Network" refers to the network address of each file server. File servers on the same network have the same network address. File servers on different networks (on the same internetwork) have different network addresses. "Node address" refers to the identifying number of the LAN A network interface board installed in each file server. Viewing Information about All File Servers. Suppose you want to view a list of the file servers running on your internetwork. Type SLIST You will see information similar to the following: Known NetWare File Servers Network Node Address -------------------------------------------------------------------------- RECORDS CED88 2608C234732 SALES CED87 2608C217561 MFG CED86 2608C293185 "Network" refers to the network address of each file server. File servers on the same network have the same network address. File servers on different networks (on the same internetwork) have different network addresses. "Node address" refers to the identifying number of the LAN A network interface board installed in each file server. Using Continuous Scrolling. To allow continuous scrolling with SLIST, type SLIST /C The list of all file servers running on your internetwork will scroll down the screen without stopping. Additional Information SLIST allows you to specify the wildcard characters * and ? in the command. Suppose you want to look at the information for file server XANADU, but you are not sure of the spelling. To find the information about server XANADU, type SLIST ?ANAD* You will see information similar to the following: Known NetWare File Servers Network Node Address ---------------------------------------------------------------------- CANADA CEE76 2608C233457 XANADU CEB82 2608C211237 SYSCON (Supervisor Tasks) The SYSCON (System Configuration) utility controls user, group, directory, and file server information. Since it can be run by regular users (though the tasks they can perform are limited), SYSCON is loaded into the SYS:PUBLIC directory. This section contains step-by-step instructions for completing supervisor SYSCON tasks. Because you can perform a variety of tasks with this utility, the sections are arranged alphabetically by topic for your convenience. þ Accounting þ Console operators þ Error log þ Group information þ Login restrictions þ Login scripts þ Printer mappings in the AUTOEXEC.SYS file þ User information ACCOUNTING This section explains the available accounting options and how to set up the accounting functions. The accounting feature is not automatically installed. You must activate accounting in SYSCON. ACCOUNTING OPTIONS There are several accounting options. You can choose the options that are suitable to your network environment. These options are listed below. þ Tracking when each user logs in to and out of the file server. This option is automatically selected if you choose to install accounting on your file server. When accounting is installed, an entry is placed in the file server's audit file each time a user logs in to or out of the server. No charges are made to users by this option. þ Charging each user's account for resources consumed. These charges can be made by the file server or by other types of servers such as print servers, job servers, or gateways. As network supervisor, you decide which servers have the right to charge users on your file server. þ Tracking and charging users for several different services that the file server provides. As supervisor, you decide which services you want to charge for in your environment. If a particular accounting option is not necessary for your situation, do not use that option. þ Charging users for the amount of file server disk space they are using. To use this option, you will need to install accounting on the file server and specify the amount that should be charged for disk storage. You will also have to specify how often and at what times the file server should measure the disk space users are using and charge their accounts. þ Charging users for the amount of time they use the file server, as well as the amount of work they ask the file server to do. The amount of time and work that a user is consuming is measured by the file server in four ways. These four methods are listed below. þ The amount of time the user is logged in to the file server þ The amount of data (programs or information) the user requests the file server to read from its disks þ The amount of data (programs or information) the user requests the file server to write to its disks þ The number of requests the user makes of the file server You can have the file server charge for one, some, or all of these services. If you install accounting and do not choose to charge for any services, the server will still keep track of logins and logouts. INSTALLING THE ACCOUNTING FEATURE As supervisor, you must install the accounting feature on your newly installed file server in order to take advantage of the accounting options described in the previous section. To install accounting, complete the following steps. 1)At the OS/2 prompt, type SYSCON 2)From the "Available Topics" menu, highlight "Accounting" and press . 3)The first time you highlight "Accounting," the "Install Accounting" confirmation box will appear. Highlight "Yes" and press . The accounting feature has now been installed and the file server will keep track of each login and logout. REMOVING THE ACCOUNTING FEATURE To deactivate and completely remove the accounting feature from your file server, you must first delete all accounting servers (for more information, see "Deleting Accounting Servers" on page 98). After you have deleted the last accounting server, you will be given the option of removing the accounting feature. To remove the accounting feature, complete the following steps. 1)At the OS/2 prompt, type SYSCON 2)From the "Available Topics" menu, highlight "Accounting" and press . 3)Highlight "Accounting Servers" and press . You will see a list of all servers that are currently authorized to charge for services. You must delete all accounting servers by marking each with the Mark key ( on most machines) and then pressing . 4)Once you have deleted all accounting servers, press . The "Do you wish to remove accounting" confirmation box will be displayed. 5)To remove the accounting feature, press . You will be returned to the SYSCON "Available Topics" menu. The accounting feature has been removed. If you decide you want to reinstall accounting, follow the instructions given in "Installing the Accounting Feature" on page 96. SETTING UP ACCOUNTING SERVERS As supervisor, you can authorize servers to charge for the services they provide, or revoke the server's right to charge. The current file server will automatically be authorized to charge for services. Unless you add other servers, such as print servers, no other servers will be authorized to charge for services. If you do not have other servers, skip to "Establishing Charge Rates" on page 99. If you add additional servers to your network, you can authorize them to charge for their services. To include these additional servers in the list of accounting servers, you will need to create an account for the server. The software that comes with the server should include instructions for creating an account. Follow those instructions. You will need to authorize the server to charge. If the type of server is known by the SYSCON utility, you can use SYSCON to make this authorization. If the type of server is not known by SYSCON, you will need to use the software included with the server to authorize it to charge. To use SYSCON to authorize a new server to charge for its services, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Accounting" and press . 3)Highlight "Accounting Servers" and press . You will see a list of all servers that are currently authorized to charge for services. 4)Press . The "Select Server Type" list will appear, showing the types of servers on the current file server that have been authorized to charge. (If there are no additional accounts for the types of servers known by SYSCON, a message will appear indicating no servers are authorized to charge for their services.) 5)Highlight the type of server you want to authorize to charge and press . 6)In the "Other Servers" list, highlight the server you want to authorize to charge and press . If there are several servers listed that you want to authorize to charge, mark each server using the Mark key ( on most machines). When you have marked all the servers you want to authorize, press . 7)Press to return to the "Accounting" menu. The server has now been authorized to charge users for its services. DELETING ACCOUNTING SERVERS If you no longer want to allow a server to charge for its services, you must delete the server from the "Accounting Servers" list. You can delete one or all accounting servers. If you want to delete the accounting feature from your server, see "Removing the Accounting Feature" on page 96. To delete an accounting server, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Accounting" and press . 3)Highlight "Accounting Servers" and press . You will see a list of all servers that are currently authorized to charge for services. 4)Highlight the server that you no longer want authorized to charge for its services. If you want to revoke several servers' authorization to charge, mark the desired servers using the Mark key ( on most machines). When you have marked all the servers, press . The "Delete Account Server" confirmation box will be displayed. 5)Press to confirm the deletion. The "Accounting Servers" list will again be displayed. The specified accounting server(s) will be deleted. ESTABLISHING CHARGE RATES The file server can charge for five types of services. This section describes these services or options and how to establish charge rates for each. BLOCKS READ The Blocks Read option allows you to set up charge rates for the amount of data read from the server. You can specify the amount charged for each half-hour increment. The charge is assigned per block read. One block is equal to 4096 bytes, or 4KB. BLOCKS WRITTEN The Blocks Written option allows you to set up charge rates for the amount of data written to the disk. You can specify the amount charged for each half-hour increment. The charge is assigned per block written. One block is equal to 4096 bytes, or 4KB. CONNECT TIME The Connect Time option allows you to set up charge rates for the amount of time a user is logged in to a server. You can specify the amount charged for each half-hour increment. The charge is assigned per minute. DISK STORAGE The Disk Storage option allows you to set up charge rates for each block (4096 bytes or 4KB) that is stored on the disk for one day. You can assign different charge rates for each half-hour increment. The charge is assigned per block-day (the number of blocks stored in a day). SERVICE REQUESTS The Service Requests option allows you to set charge rates for service requests. You can specify the amount charged for each half-hour increment. The charge is assigned per request received. SETTING CHARGE RATES If you plan to charge users for services provided by the file server, you will need to calculate the amount to charge the users. The amount you charge will depend on your network environment. Determine the following before setting charge rates for services. 1)Determine what your costs are and the amount you want to charge over a given period of time. 2)Determine what services you will charge for and the amount you expect to make from each service. 3)Estimate how much each service is being used. This will require you to monitor the file server for a period of time. In order for the system to record total usage for each service, you must assign a charge rate. We suggest that you assign a charge rate of 1/1 for "Disk Storage" and "Connect Time." This rate is for monitoring purposes only and has no bearing on actual charge rates. Monitor your file server for two or three weeks to determine how much each service is being used. 4)At the end of the monitoring period, use the ATOTAL utility to see total usage for each service. At the OS/2 prompt, type ATOTAL A screen will appear listing the total daily and weekly usage of each service. 5)After you have determined the amount you want to charge for each service and have a fairly good estimate of the how much each service was used, you can calculate the charge rates. Charge rates are specified as multipliers and divisors. This multiplier/divisor ratio is used to change the amount of service usage to a monetary charge. The unit of charge is completely arbitrary, but we suggest you begin with one charge unit equalling one cent. You can adjust this ratio later if it doesn't work well for your network environment. 6)Use the following formula to calculate a charge rate. (Total you want to charge for a service) = (Charge rate multiplier) (Estimated total usage of a service) (Charge rate divisor) For example, if you wanted to charge $100 a month for blocks read services and you found that 250,000 blocks were being read each month, then your charge rate would be $100/250,000. You will need to make the necessary conversion to cents (assuming one charge is equal to one cent) per block. The next three sections provide examples of how to assign charge rates. Examples ASSIGNING CONNECT TIME CHARGE RATES. Suppose you want to charge $500 a week for connect time. You decide to assign charge rates only Monday through Friday, 8:00 a.m. to 5:00 p.m. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Accounting" and press . The "Accounting" menu will be displayed. 3)Highlight "Connect Time Charge Rates" and press . The "Connect Time Charge Rates" screen will appear. The default setting is no charge for any time period. The number 1 indicates a "no charge" rate. 4)Highlight the block of time (8:00 a.m. to 5:00 p.m.) you want to assign a charge rate to. A) Use the Right-arrow key to move the cursor to Monday at 8:00 am. Then press the Mark key. (F5 is the Mark key on most machines. Press F1, or Help, twice to verify this for your machine.) B) Press the Right-arrow key until Friday at 8:00 a.m. is highlighted. The upper-left corner of the screen should read "Monday To Friday, 8:00 am To 8:29 am". C) Press the Down-arrow key until you have highlighted "Monday To Friday, 8:00 am To 4:59 pm." Press . The "Choose Charge Rate" box will be displayed. 5)Highlight "Other Charge Rate" and press . The multiplier/divisor ratio is equal to the amount you want to charge for connect time/total usage of connect time. (You will have to determine what one charge is equal to in monetary units. For this example, assume one charge is 1 cent.) You want to charge $500 per week for connect time, and you know that 100,000 minutes of connect time were used in the first week of monitoring the file server. The charge rate would be 50,000(multiplier)/100,000(divisor) or 1/2. So if a user were connected to the file server for 80 hours, the amount charged would be 4,800 minutes (units used) x 1 = 2,400 (charges) 2 (per units) 6)In the "New Charge Rate" box, leave the multiplier as 1. Press the Down-arrow key and type 2 for the divisor. Press twice and then press . The new charge rate will be indicated by a 2 on the screen. The 2 indicates that this charge rate is higher than the "no charge" rate indicated by the number 1. The numbers on the screen do not reflect the specific multiplier/divisor ratio. The multiplier/divisor ratio or charge rate (1/2) will be listed on the left side of the screen. ASSIGNING BLOCKS READ, BLOCKS WRITTEN, AND SERVICE REQUESTS CHARGE RATES. The charge rates for Blocks Read, Blocks Written, and Service Requests are assigned the same way rates are assigned for Connect Time (explained in the previous example). In these three options, charges are assigned per block (4096 bytes). Suppose you want to charge $500 a week for reading blocks. You decide to assign the charge rate for all hours. To assign charge rates, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Accounting" and press . The "Accounting" menu will be displayed. 3)Highlight "Blocks Read Charge Rates" and press . The "Blocks Read Charge Rates" screen will appear. The default setting is no charge for any time period. The number 1 indicates a "no charge" rate. 4)Highlight the block of time you want to assign a charge rate to. A) Press the Mark key. ( is the Mark key on most machines. Press F1, or Help, twice to verify this for your machine.) B) Press the Right-arrow key until the whole line is highlighted. The upper-left corner of the screen should read "Sunday to Saturday, 8:00 a.m. To 8:29 a.m." C) Press the Down-arrow key until you have blocked the whole screen, "Sunday To Saturday, 8:00 a.m. To 7:59 a.m." Now press . The "Choose Charge Rate" box will be displayed. 5)Highlight "Other Charge Rate" and press . The multiplier/divisor ratio is equal to the amount you want to charge for blocks read/total usage of connect time. (You will have to determine what one charge is equal to in monetary units. For this example, assume one charge is 1 cent.) You want to charge $500 per week for blocks read, and you know that in the first week of monitoring the file server 500,000 blocks were read. The charge rate would be 50,000(multiplier)/500,000(divisor) or 1/10. So if a user read 2,000 blocks, the amount charged would be 2,000 (units used) x 1 = 200 (charges) 10 (per units) 6)In the "New Charge Rate" box, leave the multiplier as 1. Press the Down-arrow key and type 10 for the divisor. Press twice and then . The new charge rate will be indicated by a 1 on the screen. The multiplier/divisor ratio or charge rate (1/10) will be listed on the left side of the screen. You can assign a different charge rate to different times of the day by repeating this same process. The numbers on the screen represent the charge rates, with the lowest number representing the lowest charge rate. When you look at the screen, you will immediately be able to tell which rates are higher and which are lower. ASSIGNING DISK STORAGE CHARGE RATES. Disk storage rates are assigned a little differently than the other charge rates. To assign disk storage rates, you specify how often you want the system to charge for the disk space being used. Suppose you want to charge $500 per week for disk storage. Using statistics compiled running the ATOTAL utility, you estimate that 200,000 block days of storage space will be used each week. (Block days are the units disk storage is measured in.) You want the file server to charge for storage at 2:00 a.m. each day. 1)In the "Accounting" menu, highlight "Disk Storage Charge Rates" and press . The "Disk Storage Charge Rates" screen will appear. The default setting is no charge rate. 2)Specify when disk storage usage should be charged. A) Move the cursor to Sunday at 2:00 a.m. Then press the Mark key. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) B) Move the cursor to Saturday at 2:00 a.m. "Sunday To Saturday 2:00 am To 2:29 am" should be highlighted. Press . Since you want to charge $500 (assume one charge is equal to 1 cent) for disk storage and you estimate that 200,000 block days are used, the charge rate would be 50,000 (multiplier)/200,000 (divisor) or 1/4. So if a user uses 1,000 block days, the amount charged would be 1,000 (units used) x 1 = 250 (charges) 4 (per units) 3)In the "New Charge Rate" box, leave the multiplier as 1. Press the Down-arrow key and type 4 for the divisor. Press twice and then press . The new charge rate will be indicated by a 1 on the screen. The multiplier/divisor ratio or charge rate (1/4) will be listed on the left side of the screen. SETTING UP ACCOUNT BALANCES FOR USERS As supervisor, you can assign users account balances that determine how much of a given service they can use. You can also assign a credit limit indicating how much credit the user can draw upon. You can assign a system or default account balance or you can assign individual account balances for users. Both options are explained under the next two headings. You can also increase a user's account balance. However, the user must log out and then log in again before any account balance changes will be put into effect. IMPORTANT: If you install the accounting option on your file server, you need to carefully monitor account balances. You should warn users that if they are told to log out because their account balances are too low, they should log out immediately. If users do not log out, the file server will automatically log them out. Users will lose any data that has not been saved. ASSIGNING SYSTEM OR DEFAULT ACCOUNT BALANCES To set up a default account balance (which will be automatically assigned to any user created after the default is set up), complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . The "Supervisor Options" menu will be displayed. 3)Highlight "Default Account Balance/Restrictions" and press . 4)Highlight "Account Balance" (near the bottom of the screen) and enter the account balance you want users to be given when their accounts are created. The balance will be lowered each time the user is charged for a service. The account balance is assigned in charges. An account balance of 320 indicates that the user can use up to 320 charges. The default account balance is 0. 5)After you have entered the account balance, you also have the option of allowing credit. If you do not want to allow credit, leave the default response to "Allow Unlimited Credit" at "No" and the default response to "Low Balance Limit" at 0. If you want to allow unlimited credit, highlight "Allow Unlimited Credit" and change the response to "Yes" by typing Y and pressing . If you want to allow some credit but not unlimited credit, leave the "Allow Unlimited Credit" response at "No" and highlight "Low Balance Limit." Enter the amount of credit you want each user to be given. Enter a negative number to indicate that a user can still receive services that are being charged for after his or her account balance has been used up. For example, -20 indicates that the user can receive services for 20 charges after the user's account balance is at zero. A positive number indicates that the user must always have some portion of the balance remaining. For example, 10 indicates that when the user's account drops to 10, the user will no longer be able to receive services that are charged for. 6)After you have finished entering the account balance options, press twice to return to the "Available Topics" menu. ASSIGNING ACCOUNT BALANCES TO INDIVIDUAL USERS To assign account balances to individual users, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The "User Names" list will be displayed. 3)Highlight the username you want to assign an account balance to and press . The "User Information" menu will be displayed. 4)Highlight "Account Balance" and press . 5)Enter the appropriate information and press . For an explanation of each option, see Step 5 of the preceding section, "Assigning System or Default Account Balances." USING PAUDIT WITH SYSCON ACCOUNTING The PAUDIT command allows you to look at the audit (NET$ACCT.DAT) file, which is a chronological list of logins and logouts. It also includes a chronological list of the charges made to each user. To access the audit file, at the DOS prompt, type PAUDIT This file provides a chronological list of all accounting functions. It does not compile the information according to user or type of charge. To stop the information from scrolling down the screen, press the keys simultaneously. Press the keys again to resume the scrolling. Because PAUDIT will generate a large amount of data, you may want to redirect the PAUDIT output to a file to make it more accessible. This file can be printed or typed to the screen in pages. To redirect the output, type PAUDIT > filename To print a hard copy, type NPRINT filename To view the file one screen at a time, type TYPE filename | MORE You may want to delete the NET$ACCT.DAT file after you have redirected the information to a file. The system will generate a new NET$ACCT.DAT file for future accounting records. However, the information is stored in a more compressed form (binary data) in the NET$ACCT.DAT file. If you have a billing program that will read the information directly from NET$ACCT.DAT, you may want to leave it in its original form rather than periodically deleting the file and starting over. CONSOLE OPERATORS As supervisor, you can specify which users and groups are "file server console operators." Console operators can access the FCONSOLE (file server console) menu utility from any workstation where they are logged in. FCONSOLE allows operators to issue commands directly to the file server and find out information concerning the efficiency of the file server. To access a list of currently defined console operators, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . The "Supervisor Options" menu will be displayed. 3)Highlight "File Server Console Operators" and press . The "File Server Console Operators" list will display any users or groups that are console operators. 4)As a supervisor, you can add operators to the list or delete them from it. A) To add console operators, press . In the "Other Users and Groups" list, highlight the user or group you want to be a console operator. If you want to assign more than one user or group, use the Mark key to mark them. ( is the Mark key on most machines. Press , or the Help key twice to verify this for your machine.) Then press . The users or groups are now file server console operators. B) To delete console operators, highlight the user or group you want to delete from the "File Server Console Operator" list. If you want to delete more than one user or group, use the Mark key to indicate them. Then press . Answer "Yes" in the confirmation box by pressing . The users or groups are no longer file server console operators. ERROR LOG As supervisor, you can view any errors recorded in the file server's system error log. You can also erase the error log after you have finished viewing the errors. To view or erase the error log, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . The "Supervisor Options" menu will be displayed. 3)Highlight "View File Server Error Log" and press . The "File Server Error Log" screen will list any error messages since the file server log was last cleared. It will specify the date and time of the error and identify the nature of the error. Use the arrow keys to scroll to additional error messages. If no file server messages have been recorded, you will see the following message: There are no errors recorded in the F/S error log. A complete explanation of error messages can be found in the NetWare System Messages manual. 4)To exit the error log, press . You will see the "Clear Error Log" confirmation box. If you no longer need a record of the errors, highlight "Yes" and press . If you want to keep the log, highlight "No" and press . GROUP INFORMATION As supervisor, you can use the SYSCON "Group Information" option to complete the following tasks: þ List the server groups þ Create or delete a group þ Assign users to or delete users from a group þ Assign or delete a group's trustee rights þ View a group's ID and console operator status LISTING THE SERVER GROUPS 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight the "Group Information" option and press . The groups on the current file server will be displayed. CREATING A GROUP 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . 3)Press . The "New Group Name" entry box will be displayed. 4)Type the group's name and press . The group has now been created. You can also assign the group a full name. To do this continue with Steps 5 through 7. 5)In the "Group Names" list, highlight the group whose full name you want to assign and press . The "Group Information" menu will be displayed. 6)Highlight "Full Name" and press . The "Full Name" entry box will be displayed. You can view, assign, or change the group's full name. A) VIEWING: If the group has been assigned a full name, it will be displayed here. B) ASSIGNING: If the group has not been assigned a full name, the box will be blank, and you can simply type a name. C) CHANGING: To change the group's full name, use the Backspace key to delete the old name, then type the new name. 7)Press to save the change. The group has now been added or updated and assigned a full name. DELETING A GROUP 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . The "Group Names" list will be displayed. 3)Highlight the group you want to delete. If you want to delete more than one group, press the Mark key to mark each group. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 4)In the "Delete Group" confirmation box, highlight "Yes" and press . The group has now been deleted. ASSIGNING USERS TO A GROUP 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . 3)Highlight "Member List" and press . The group members will be listed. 4)Press . The "Not Group Members" list will be displayed. 5)Highlight the user you want to add to the group. If you want to add more than one user, use the Mark key to mark each user you want to add. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Press . The users you specified are now members of the group. DELETING USERS FROM A GROUP 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . 3)Highlight the group you want to delete users from and press . Then highlight "Member List" and press . 4)Highlight the group member you want to delete. If you want to delete more than one member, use the Mark key to mark each member you want to delete. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 5)In the "Delete User from Group" confirmation box, highlight "Yes" and press . The group members you specified have now been deleted from the group. GIVING A GROUP TRUSTEE RIGHTS IN A DIRECTORY 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . 3)Highlight the group you want to give trustee rights to and press . The "Group Information" menu will be displayed. 4)Highlight "Trustee Assignments" and press . The group's trustee assignments will be listed. 5)To add trustee rights in a particular directory, press . 6)In the "Directory In Which Trustee Should be Added" entry box, specify the directory. If you know the name of the directory that you want to give the user rights in, type the full directory path and press . If you do not know the directory name, press to see a list of available file servers. Highlight the appropriate file server and press . Then you will see a list of available volumes. Highlight the appropriate volume and press . Repeat these steps to continue choosing directories until you have specified the full directory name. Press and then . NOTE: If you specify a nonexistent directory, you will be asked if you want to create that directory. The group now has all trustee rights in the directory. MODIFYING TRUSTEE RIGHTS IN A DIRECTORY To modify the group's trustee assignments in the directory, complete the following steps. 1)In the "Trustee Assignments" list, highlight the directory in which you want to modify the group's trustee rights and press . The "Trustee Rights Granted" list will appear. 2)You can delete trustee rights from or add them to this list. A) DELETING: To delete a given trustee right, highlight that right. If you want to delete more than one right, use the Mark key to mark each right you want to delete. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) After you have selected the right(s), press . Highlight "Yes" in the "Revoke Trustee Right" confirmation box and press . Press to return to the "Trustee Assignments" list. The rights have been revoked and will not be listed in the second column. B) ADDING: To add a given trustee right, press to see the "Trustee Rights Granted" list, and then press . The "Trustee Rights Not Granted" list will appear. Highlight the right you want to add. If you want to add more than one right, use the Mark key to mark each additional right. Press and then to return to the "Trustee Assignments" list. The trustee right has been added. DELETING A GROUP AS A TRUSTEE OF A DIRECTORY At times it may be necessary to delete a group's assignment as a trustee of a directory. Note, however, that deleting a group's trustee rights is not the same as deleting the group's trustee assignment. A group that does not have specific trustee assignments in a directory inherits the same rights it had in the directory's parent directory. A group that has a trustee assignment, but no trustee rights, does not inherit any rights. To delete a group as a trustee of a directory, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . 3)Highlight the group you want to remove as a trustee of the directory and press . 4)Highlight "Trustee Assignments" and press . 5)Highlight the directory from which you want to delete the group as a trustee. If you want to delete the group's trustee assignment from more than one directory, use the Mark key to mark additional directories. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 6)In the "Remove Trustee from Directory" confirmation box, highlight "Yes" and press . The group is no longer a trustee of the directory. VIEWING A GROUP'S ID AND CONSOLE OPERATOR STATUS The file server uses the group ID to keep track of the group. The group ID cannot be changed or deleted. A file server console operator can use FCONSOLE to issue commands and find out information concerning the file server. If you need to change the console operator status, access "Supervisor Options" of SYSCON. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . 3)Highlight the group whose ID and console operator status you want to view and press . 4)Highlight "Other Information" and press . The group's ID number and file server console operator status will be displayed. LOGIN RESTRICTIONS Assigning login restrictions is one means of increasing the security of your file server. By setting login restrictions, you make it difficult for unauthorized users to access the file server. There are three basic types of login restrictions: þ Account restrictions, including passwords þ Time restrictions þ Station restrictions In addition, the "Intruder Lockout Status" option allows you to lock an account when an unauthorized user is detected. This section explains each type of login restriction and how to put it into effect. Each of the restrictions can be applied to an individual user or to all users. The system defaults are set so no restrictions apply. These defaults can be modified in "Supervisor Options." ACCOUNT RESTRICTIONS When a user is created, an account is set up for that user. The user account allows the user to log in. All account restrictions are set by choosing options in the "Account Restrictions" list. To access the "Account Restrictions" list, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to assign account restrictions to. You can also assign account restrictions to multiple users by using the Mark key to mark each additional user. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Press . The "User Information" menu will be displayed. 4)Highlight "Account Restrictions" and press . The account restrictions will be listed on the screen; these restrictions are explained in the sections below. Account disabled. You can close an account temporarily without deleting it altogether. No one can log in to a disabled account. For example, you might have an account set up for a consultant who needs to access it once a month for three months. You do not want anyone else using the account while the consultant is away, but you do not want to delete the account. In this case, you might want to disable the account by completing the following steps. 1) Highlight "Account Disabled" from the "Account Restrictions" list, and change the response to "Yes" by typing Y and pressing . 2) Press to save this change and return to the "User Information" menu. Account has expiration date. You can set up a temporary account. At a specified date, the account will be automatically disabled and no one will be allowed to log in to that account until the expiration date restriction is removed or the expiration date is changed. For example, you could set the last day of a semester as the expiration date for accounts used by students. After that day, they would no longer be able to log in to their accounts. To set up the expiration date restriction, complete the following steps. 1) In the "Account Restrictions" list, highlight "Account Has Expiration Date." Change the response to "Yes" by typing Y and pressing . The "Date Account Expires" option will appear. The default is set to the first day of the next month. 2) You can change this date by typing in a new date. Use the following format: month-day-year (i.e., 11-25-89; November 25, l989; or Nov 25, 1989). Press and then to save the changes and return to the "User Information" menu. On the expiration date, the account will be disabled. To remove an expiration date restriction after the account has been disabled, complete the following steps. 1) In the "Account Restrictions" list, highlight "Account Disabled" and change the response to "No" by typing N and pressing . 2) Then highlight "Account Has Expiration Date" and change the response to "No" by typing N and pressing . Limit concurrent connections. You can limit the number of workstations a user can be logged in to. For example, you may want a user to log out from the workstation in one office before going to another office to log in to another workstation. This option also prevents anyone else from logging in with the password of a user already logged in at another location. To limit concurrent connections, complete the following steps. 1) In the "Account Restrictions" list, highlight "Limit Concurrent Connections" and change the response to "Yes" by typing Y and pressing . The default is set so the user can only log in from one workstation at a time. 2) To change the number of workstations a user can log in from, highlight "Maximum Connections." Type in the desired number of workstations (from 1 to 100, inclusive). Press and to save the change and to return to the "User Information" menu. Password restrictions. You can allow users to change a password. You can also require a password, designate a minimum password length, force periodic password changes, designate how often the password must be changed, limit grace logins, and require unique passwords. To assign password restrictions, complete the following steps: 1) At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2) Highlight "User Information" and press . The users on the current file server will be displayed. 3) Highlight the user you want to assign password restrictions to and press . 4) In the "User Information" menu, highlight "Account Restrictions" and press . You then have the following options. Allow User to Change Password. You can decide whether or not a user will be allowed to change the password of the account. The default is set to "Yes." If the "Allow User to Change Password" is set to "No," the user will also be unable to change the account's login script using SYSCON. For example, on accounts that many users will share, such as the GUEST account, you do not want one user changing the password and locking out other users. If the option is set to "No," the user cannot change the password or edit the account's login script using SYSCON. To specify whether a user can change the password, highlight "Allow User to Change Password" and change the response to "No" by typing N. Require Password. You can require a user to have a password. If you do not require a password, the user can highlight whether or not to use a password. A password must be required in order to use the "Minimum Password Length" and "Force Periodic Password Changes" options. The default is set to "No." To require a password, highlight "Require Password" and change the response to "Yes" by typing Y. Minimum Password Length If you require a password, the system will automatically set the minimum password length to five characters. To change the minimum password length, highlight "Minimum Password Length" and type in the new number. Passwords can be up to 128 characters long. Then press . Force Periodic Password Changes If you require a password and allow users to change their passwords, the system will force periodic password changes every 40 days. The screen will also list the date the password expires. You can change the number of days between forced changes or you can decide not to require password changes. Highlight "Force Periodic Changes." If you decide not to not require password changes, change the response to "No" by typing N and pressing . If you require password changes, you can change the number of days between changes by selecting "Days Between Forced Changes" and entering the new number. The new "Date Password Expires" will be shown. Limit Grace Logins If you require passwords and allow users to change them, you can also limit the number of times users can log in with an expired password. The system will automatically allow users to log in with an expired password six times. If you want to allow users to log in an unlimited number of times with an expired password, then change the "Limit Grace Logins" response to "No" by typing N. If you decide to limit grace logins, you can change the number of times users can log in with an expired password. Highlight "Grace Logins" and enter a new number. The number of "Remaining Grace Logins" will appear on the screen. Require Unique Passwords If you require passwords, you can also require users to use new passwords each time they change their password. The default is set so that unique passwords are not required. If you require unique passwords, the system will remember 8 previous passwords. A user must keep a new password for at least one day before it is remembered by the system. To require unique passwords, highlight "Require Unique Passwords" and change the response to "Yes" by typing Y. Press twice to save your changes and return to the "User Information" menu. DISK RESOURCE LIMITATION If the "Disk Resource Limitation" option was selected when the NetWare operating system was generated and installed, you can specify how much file server disk space each network user can use. If the disk resource limitation was not selected, the SYSCON "Limit Disk Space" option will not appear. You may want to limit the disk space only for one or two users. Or, you may want to limit the disk space for all users, assigning each user a different amount of disk space. (If you want to limit the disk space for all users, but assign each user the same amount of space, set the system defaults as explained under "System Default Account Restrictions" on the next page.) To limit disk space for individual users, complete the following steps. 1)In the "Account Restrictions" form, highlight "Limit Disk Space." Change the response to "Yes" by typing Y. 2)If "Limit Disk Space" is set to "Yes," you can specify how much space the user will be allocated. Select the "Maximum Disk Space" response. Enter the amount (in KB). All amounts will be rounded up to the nearest 4KB when you exit. Press to save the changes and return to the "User Information" menu. NOTE: If a user tries to use more disk space than assigned, an error message will appear indicating insufficient disk space. SYSTEM DEFAULT ACCOUNT RESTRICTIONS You can set up default account restrictions that will apply to all users created after the default restrictions have been set up. If you create a user prior to setting up the default restrictions, the defaults will not apply to that user. The default restrictions will only affect a user's account when it is first created, so changing the system defaults will affect only those users created after the system defaults have been made. To set up default account restrictions, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . 3)Highlight "Default Account Balance/Restrictions" and press . The "Default Account Balance/Restriction" menu will be displayed. The system default is set so accounts have no expiration date, no connection limitations, no password restrictions, and no disk space limitations. 4)Change the "Default Account Balance/Restrictions" menu by selecting the restrictions you want to apply to all users. Each of the options is described in the "Account Restrictions" section. If your file server supports accounting, you will also see "Account Balance" and "Allow Unlimited Credit." See "Setting Up Account Balances for Users" on page 104 for complete instructions on these options. STATION RESTRICTIONS You can restrict the physical locations that a user can log in from. The default is set so there are no station restrictions. For example, you might want users to log in only from the workstation in their own office. Or you may want to allow the user SUPERVISOR to log in from a workstation regular users do not have physical access to. In order to restrict the workstations users can log in from, you will need a list of network and node addresses for each workstation. You should have received the "NetWare File Server LAN Worksheet" with these addresses from the installer. If you did not, you can find the address of a workstation by logging in from that workstation and typing USERLIST/A at the OS/2 prompt. You can print this list using the CAPTURE command. To assign station restrictions, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight the "User Information" option and press . The users on the current file server will be displayed. 3)Highlight the user you want to assign station restrictions to and press . The "User Information" menu will be displayed. 4)Highlight "Station Restrictions" and press . If the "Allowed Login Addresses" box is empty, the user can log in from any location. 5)To restrict the workstations a user can log in from, press . The "Network Address" box will be displayed. 6)Type the network address (in hexadecimal notation) of the workstation the user can log in from and press . A confirmation box will be displayed. 7)You have two options in the "Allow Login From All Nodes" confirmation box. NOTE: The "Allow Login From All Nodes" confirmation box will only appear the first time a new network address is entered. A) Highlight "Yes" if you want the user to be able to log in from any node address on the specified network. Then press . The restriction for all nodes on the specified network will be listed in the "Allowed Login Addresses" box. B) Highlight "No" if you want to restrict the user to a single or to only a few node addresses on the network. Then press . In the "Node Address" box, enter the address of the appropriate workstation (in hexadecimal notation) and press . The network and node address of the specified workstation will be listed in the "Allowed Login Addresses" box. 8)To restrict the user to multiple node addresses on the same network, you will have to specify each node individually by repeating Steps 5 and 6. 9)To delete a station restriction, highlight the address of the station you want to delete in the "Allowed Login Addresses" list and press . Answer "Yes" to the "Delete Station Restriction" confirmation box. The station restriction will be deleted. 10)Press to return to the "User Information" menu. If a user with a station restriction tries to log in from an unauthorized station, that user will be denied access. TIME RESTRICTIONS You can restrict the hours during which users can log in. The default is set so that no time restrictions apply. For example, you might want to restrict the time that users can log in to normal working hours. ASSIGNING TIME RESTRICTIONS TO INDIVIDUAL USERS 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to assign time restrictions to. If you want to assign time restrictions to multiple users, use the Mark key to mark each user. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Press . The "User Information" menu will be displayed. 4)Highlight "Time Restrictions" and press . The "Allowed Login Times for User" box lists the time in a week in half-hour increments. The time listed in the lower right-hand corner indicates which half-hour block the cursor is on. The asterisks indicate the times when the user can log in. 5)Using the Mark key, mark the block of time during which you do not want to allow users to log in. Then press . You can also delete blocks individually. For example, suppose you want to allow users to log in from 8 a.m. to 7 p.m. In this case, it will be easiest to delete the whole screen and then insert "M-F 8 am-7 pm". Press the Mark key. Next press , , and then . The time box should now be empty. Using the arrow keys, move to "Friday from 8:00 am to 8:30 am" and press the Mark key. Press the Right-arrow key until the screen reads "Friday 8:00 am to 7:00 pm." Now press the Up-arrow key until the screen reads "Monday to Friday 8:00 am to 7:00 pm." After this block of time is defined, press . 6)Press to return to the "User Information" menu. ASSIGNING TIME RESTRICTIONS TO ALL USERS You can also change the default time restriction that is assigned to new user accounts when they are first created by modifying the default time restrictions which are set using SYSCON "Supervisor Options." 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . 3)Highlight "Default Time Restrictions" and press . The "Default Time Restrictions" box lists the time in a week in half-hour increments. The time listed in the lower right-hand corner indicates which half-hour block the cursor is on. 4)Use the Mark key to mark the block of time during which you do not want to allow users to log in. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . The specified block of time will be deleted, and the time restriction will be assigned. INTRUDER DETECTION AND LOCKOUT The intruder detection and lockout feature allows you to set conditions for recognizing an intruder. Once these conditions have been met, you can also prevent any further attempts to log in to the file server on that account. ACTIVATING INTRUDER DETECTION AND LOCKOUT If the intruder lockout status is activated, the account will make a record of any workstation that has attempted to log in with an incorrect password more than the number of times allowed. In addition, you may choose not to allow anyone to log in after a given number of unsuccessful login attempts. You can specify how many unsuccessful attempts can be made before the account will lock automatically and how long the account will remain locked before allowing a user to try logging in again. To activate the intruder detection feature, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . 3)Highlight "Intruder Detection/Lockout" and press . 4)The default for Intruder Detection is set to "No." To activate the intruder detection feature, change the "Detect Intruders" response to "Yes" by typing Y and pressing . The file server will record repeated attempts to log in to the network. You can deactivate the Intruder Detection by changing the "Detect Intruders" response to "No." To do this, type N and press . Then press to return to the "Supervisor Options" menu. 5)If you decide to use Intruder Detection, the "Intruder Detection Threshold" system defaults will appear. The "Incorrect Login Attempts" is set to seven. This means the file server will allow seven incorrect login attempts before assuming an intruder is trying to break into the account. After seven attempts, the file server will lock the account. To change this number, position the selection bar on seven, type in the new number, and press . 6)The "Bad Login Count Retention Time" is set for 30 minutes. This means that the file server will keep track of incorrect logins for 30 minutes past the time that the last incorrect login was detected. Whenever a user successfully logs in to an account or when the "Bad Login Count Retention Time" has passed, the file server will reset the number of incorrect logins. To change the "Bad Login Count Retention Time," position the cursor on the days, hours, or minutes options, type in the new numbers, and press . 7)You can also activate the Lockout security feature. This option allows you to lock an account after an intruder is detected (after the specified number of "Incorrect Login Attempts"). When you activate the "Intruder Detection" option, the "Lock Account After Detection" option is set to "Yes." If you do not want to use the Lockout feature, change the response to "No." The amount of time the account will remain locked after an intruder is detected is specified in the "Length of Account Lockout" option. The default is set to 15 minutes. To change the amount of time, move the cursor to the days, hours, or minutes options, type in the new numbers, and press . 8)After you have finished entering any changes, press to save your changes and return to the "Supervisor Options" menu. UNLOCKING USER ACCOUNTS If you want to unlock a user account that has been locked because of Intruder Detection and Lockout, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . 3)Highlight the user whose account you want to unlock and press . The "User Information" menu will be displayed. 4)Highlight "Intruder Lockout Status" and press . The "Intruder Lockout Status" box indicates that the account has been locked, when the reset time is, how much time is left until reset, and the workstation address at which the last intruder was detected. 5)To unlock the account, highlight "Account Locked," type N, and press . The incorrect login account will be reset to 0 and the account will no longer be locked. LOGIN SCRIPTS The login script is a set of instructions that directs workstations to perform specific actions when users log in to the network. As network supervisor, you can create a system-wide login script (which is the same for all users on the network) that instructs all workstations to perform the same actions when all users log in. Only network supervisors can create or modify the system login script. Each user can also create a login script. User login scripts specify drive mappings and other information needed only by the individual user. These user's login scripts execute after the system-wide login script. (Login scripts are only executed when users log in to the first file server. Users do not access a second login script when they attach to another file server.) As supervisor, you can assign one user's login script to another user. See pages ?? for a comlete explanation of the login script commands. CREATING OR MODIFYING THE SYSTEM LOGIN SCRIPT 1)At the OS/2 prompt, type SYSCON The SYSCON "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . The "Supervisor Options" menu will be displayed. 3)Highlight "System Login Script" and press . The system login script will be displayed. (If the screen is blank, no system login script has been created.) You can use any of the commands explained on pages ?? to create or modify a system-wide login script. This script will be executed for all users when they log in. 4)To exit the system login script, press . (If you have changed the login script, you will be asked to confirm that you want to save the changes before you exit.) ASSIGNING ONE USER'S LOGIN SCRIPT TO ANOTHER USER You can only assign another user's login script to a user who does not already have a login script. This is an easy way to assign many users the same login script, rather than creating each one from scratch. To assign one user's login script to another user, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . 3)Highlight the user you want to assign a login script to and press . The "User Information" menu will be displayed. 4)Highlight "Login Script" and press . The "Login Script Does Not Exist" box will appear. 5)Use the Backspace key to delete the username listed. Type in the name of the user whose login script you want to copy and press . If you want to create a new login script for the specified user, press when the "Login Script Does Not Exist" box appears as explained in the previous section. The copied login script will appear on the screen. It has now been assigned to another user. COPYING PART OF ONE USER'S LOGIN SCRIPT TO ANOTHER USER 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . 3)Highlight the user whose login script you want to copy from and press . The "User Information" menu will appear. 4)Highlight "Login Script" and press . 5)Mark the portion of the login script you want to copy using the Mark key. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Press and then to copy the highlighted portion to the paste buffer. 6)Press and highlight "No" in the "Save Changes" confirmation box since you don't want to modify the script you are copying from. Press again to return to the list of users. 7)Highlight the user whose login script you want to copy to and press . The "User Information" menu will appear. 8)Highlight "Login Script" and press . If the "Login Script Does Not Exist" box appears, press . 9)Position the cursor at the point where you want to add the lines you have copied from the first user's login script, and press . The portion of the first user's login script is now copied to the second user's login script. PRINTER MAPPINGS AND OTHER CONSOLE COMMANDS IN THE AUTOEXEC.SYS FILE As supervisor, you can create an AUTOEXEC.SYS file to store console commands you want executed each time the file server comes up. You can create the AUTOEXEC.SYS file with SYSCON or with a text editor. This file is kept in the SYS:SYSTEM directory. The most important console commands to include in the AUTOEXEC.SYS file are the printer mappings. Printer mappings indicate which printer will print or service the jobs in a given queue. NetWare v2.1 allows multiple queues to be mapped to multiple printers. The file server must be informed of which mapping the user wants to use. These mappings can be created, viewed, and changed temporarily using console commands. (For more information, see Chapter 2 of the NetWare Console Reference.) The AUTOEXEC.SYS file allows you to save the mappings permanently. If there is no AUTOEXEC.SYS file, the server will create as many default print queues as it has physical printers. Each printer will be assigned one queue, and the corresponding spooler will be initialized to place jobs in the given queue. IMPORTANT: If you do create an AUTOEXEC.SYS file, you must include at least the default printer mappings. If an AUTOEXEC.SYS file exists, the system will execute only those mappings listed in the file. It will not automatically map one print queue to each physically attached printer or spool old printer numbers into a queue as it does if there is not an AUTOEXEC.SYS file. For example, suppose your file server has two printers, PRINTER0 and PRINTER1. PRINTQ_0 and PRINTQ_1 will be created automatically by the system and mapped automatically to the respective printers when the file server first comes up. Then, after the file server is up, you decide to create a third print queue, PRINTQ_2, and map it to PRINTER0 using the console command P 0 ADD PRINTQ_2. In order for these printer mappings to be executed each time the server comes up, you need to create an AUTOEXEC.SYS file. This file needs to include both the default or automatically created mappings and the console command mappings. For the example, the AUTOEXEC.SYS file would contain the following printer mappings: P 0 ADD printq_0 P 0 ADD printq_2 P 1 ADD printq_1 (The first and third printer mappings are the system-created mappings. The second printer mapping is the console command.) In addition, you must include spooler mappings in your AUTOEXEC.SYS file. The spooler mappings allow compatibility with previous NetWare versions and allow the printing commands to function properly. For the example, your AUTOEXEC.SYS file could also contain the following spooler mappings: S 0 printq_0 S 1 printq_1 S 2 printq_2 In addition to printer and spooler mappings, you can save any other console command except the DOWN SERVER command in the AUTOEXEC.SYS file. For example, you might want to include the MONITOR command to automatically start the monitoring function. For a complete list of console commands, see the NetWare Console Reference. To create an AUTOEXEC.SYS file, complete the following steps. 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "Supervisor Options" and press . The "Supervisor Options" menu will be displayed. 3)Highlight "Edit System AUTOEXEC File" and press . The "System AUTOEXEC File" entry box will be displayed. 4)Type a list of the printer and spooler mappings you want to be executed each time the file server comes up using the following formats. P[RINTER] nn ADD [QUEUE] name S[POOL] nn [TO] [QUEUE] name For example, to add print queue LASER to printer 0 and print queue LASER2 to printer 1, you would use the following commands: P 0 ADD LASER P 1 ADD LASER2 To assign spooler 0 to the LASER print queue and spooler 1 to the LASER2 print queue, you would use the following commands: S 0 LASERJET S 1 LASERJET2 5)List any additional console commands you want to be executed each time the file server comes up. 6)Press and then to save the changes. You can modify the AUTOEXEC.SYS file by completing these same steps. Use the Backspace key to delete previous mappings and then type in the new mappings. USER INFORMATION As supervisor, you can use SYSCON to create and delete users, add users to groups, assign trustee security to users, and set up network security. NOTE: Users created with MAKEUSER will be shown in the SYSCON utility. You can delete these users or make changes to their account restrictions (login, station, time) using SYSCON. The default restrictions set up in SYSCON will not apply to the users created using MAKEUSER. CREATING A USER 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight the "User Information" option and press . The users on the current file server will be displayed. 3)Press . The "User Name" entry box will be displayed. 4)Type the new user's name. The username can be up to 47 characters long. Then press . The user has now been created. To assign the user a full name, continue with the following steps. 5)Highlight the user whose full name you want to assign and press . The "User Information" menu will be displayed. 6)Highlight "Full Name" and press . The "Full Name" entry box will be displayed. 7)You can also view, assign or change a name. A) VIEWING: If the user has been assigned a full name, it will be displayed in the box. B) ASSIGNING: If the user has not been assigned a full name, the box will be blank, and you can type a name in the box. C) CHANGING: To change the user's full name, use the Backspace key to delete the old name, then type the new name. Press to save the addition or change. The user has now been assigned a full name. DELETING A USER 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to delete. If you want to delete more than one user, use the Mark key to mark each user. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 4)In the "Delete User" confirmation box, highlight "Yes" and press . The user has now been deleted from the file server. RENAMING A USER 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to rename and press the Modify key. ( is the Modify key on most machines. Press , or the Help key, twice to verify this for your machine.) 4)Use the Backspace key to delete the old username in the "Rename User to" entry box. 5)Type the user's new username and press . The user has now been renamed. ADDING A USER TO A GROUP 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to add to a group and press . The "User Information" menu will be displayed. 4)Highlight "Groups Belonged To" and press . 5)Press to see a list of groups the user does not belong to. The "Groups Not Belonged To" entry box will be displayed. 6)Highlight the group you want to add the user to. If you want to add the user to more than one group, use the Mark key to mark each group. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Press . The user is now a member of the selected group. DELETING A USER FROM A GROUP 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to delete from a group and press . The "User Information" menu will be displayed. 4)Highlight "Groups Belonged To" and press . 5)Highlight the group you want to delete the user from. If you want to delete the user from more than one group, use the Mark key to mark the additional groups. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 6)In the "Delete User From Group" confirmation box, highlight "Yes" and press . The user has now been deleted from the group. ASSIGNING OR CHANGING A USER'S PASSWORD 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to assign a password to and press . The "User Information" menu will be displayed. 4)Highlight "Change Password" and press . The "Enter New Password" box will be displayed. 5)You can assign a user a new password or change an old one by changing the entry in the "Enter New Password" box. A) ASSIGNING: If the user has not been assigned a password, the box will be blank; type the desired password and then press . B) CHANGING: You will not be able to see the old password. To change the password, type the new password and then press . 6)Confirm the new password by retyping it in the "Retype New Password" box. Press . The new password is now assigned. ASSIGNING A USER'S SECURITY EQUIVALENCE 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user whose security equivalences you want to assign and press . The "User Information" menu will be displayed. 4)Highlight "Security Equivalences" and press . The user's security equivalences will be displayed. 5)Press . The "Other Users and Groups" list will be displayed. 6)Highlight the user or group that you want to make the user equivalent to. If you want to make the user security equivalent to more than one user or group, use the Mark key to mark each user or group. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . The security equivalence has now been assigned. DELETING A USER'S SECURITY EQUIVALENCE 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight the "User Information" option and press . The users on the current file server will be displayed. 3)Highlight the user whose security equivalence you want to delete and press . The "User Information" menu will be displayed. 4)Highlight "Security Equivalences" and press . 5)Highlight the person or group that you no longer want the user to be security equivalent to. If you want to delete the security equivalence to more than one user or group, use the Mark key to mark each user or group. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 6)In the "Delete Security Equivalence" confirmation box, highlight "Yes" and press . The security equivalence has now been deleted. MAKING A USER A TRUSTEE OF A DIRECTORY 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user you want to make a trustee of a directory and press . The "User Information" menu will be displayed. 4)Highlight "Trustee Assignments" and press . The user's trustee assignments will be displayed. 5)Press . The "Directory In Which Trustee Should be Added" entry box will be displayed. 6)Specify the directory in which you want to make the user a trustee. If you know the directory name, type it and press . NOTE: If you specify a nonexistent directory, you will be asked if you want to create that directory. If you do not know the directory name, press the key to list the available file servers. Highlight the file server you want to access and press . In the "Available Volumes" list, highlight the volume you want to access and press . In the "Network Directories" list, highlight the directory you want and press . Continue choosing directories until you have specified the full directory name. Then press and to make the user a trustee of the directory you have specified. The user now has all trustee rights in the specified directory. 7)Now you can add or delete the user's trustee rights in the directory. Press . The "Trustee Rights Granted" list will be displayed. A) DELETING: To delete a given trustee right, highlight that right. If you want to delete several rights, use the Mark key to mark them. Press . In the "Revoke Trustee Rights" confirmation box, highlight "Yes" and press . The right has been revoked. B) ADDING: To add a given trustee right, press . In the "Trustee Rights Not Granted" list, highlight the right you want to add. If you want to add several rights, use the Mark key to mark them. Press . The right has been granted. REMOVING A TRUSTEE FROM A DIRECTORY 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user whose trustee assignments you want to delete and press . The "User Information" menu will be displayed. 4)Highlight "Trustee Assignments" and press . The user's trustee assignments will be displayed. 5)Highlight the directory from which you want to remove the trustee. If you want to remove the user as a trustee of several directories, use the Mark key to mark each directory. ( is the Mark key on most machines. Press , or the Help key, twice to verify this for your machine.) Then press . 6)In the "Remove Trustee from Directory" confirmation box, highlight "Yes" and press . The user is no longer a trustee of the directory. VIEWING OTHER INFORMATION ABOUT A USER 1)At the OS/2 prompt, type SYSCON The "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . The users on the current file server will be displayed. 3)Highlight the user whose information you want to view and press . The "User Information" menu will be displayed. 4)Highlight "Other Information" and press . The "Other Information" box will be displayed listing the following: Options Description Last Login The entry shows the date and time the user last logged in. File Server This entry indicates whether or not the user is Console Operator a file server operator. This status can be modified in the SYSCON "Supervisor Options." Maximum Disk This entry indicates how much disk space the Usage user is allowed to use. (It will appear only if the "Limit Disk Space" option was set to "Yes" during network generation/installation.) This amount can be modified by selecting the "Account Restrictions" option for a particular user in the "User Information" menu and changing the "Maximum Disk Space" entry. Disk Space in Use This entry indicates how much disk space each user is using. User ID The file server keeps track of the users with this number. The user ID cannot be modified. SYSCON (User Tasks) The SYSCON (system configuration) menu utility can be used to create users and define the users' trustee rights. These rights determine the users' access to the file server's directories and the information stored there. This section contains step-by-step instructions for completing user SYSCON tasks. Although you must have supervisor rights to complete many tasks in SYSCON, as a regular user you can use SYSCON to þ See accounting charge rates; þ Work with file servers; þ See information about groups; þ See information about individual users; þ See information about yourself as a user; þ Change your password and login script. The tasks you can perform in SYSCON are determined by your rights in your current directory (the directory in which you are currently working). Rights are granted by the network supervisor. Usually, if you do not have rights to perform a certain task in SYSCON, you will not be shown the menu options needed to perform that task. (One exception to this is the "Supervisor Options" option in the "Available Topics" menu. Although you can see the "Supervisor Options" option, if you choose that option and you don't have supervisor equivalence, you will receive a message similar to the following: "No Supervisor Privileges on File Server name of your file server.") ACCOUNTING SERVICES The SYSCON "Accounting" option allows network supervisors to keep track of, and charge users for, various file server services. Regular network users can use the "Accounting" option to see which file servers use the accounting function, view which services are being charged for, and see what the charge rate is for each service. ACCESSING THE ACCOUNTING MENU To see any information about accounting services, you must first access the "Accounting" menu. 1)At the OS/2 prompt, type SYSCON The SYSCON "Available Topics" menu will be displayed. 2)Highlight "Accounting" and press . If accounting has been installed on your file server, the "Accounting" menu will be displayed. Otherwise, the message "Accounting NOT Installed On File Server file server name" will appear. VIEWING THE ACCOUNTING INFORMATION To see specific information about your file server's accounting system, access the "Accounting" menu. (See "Accessing the Accounting Menu" above for help.) Several options will appear in the "Accounting" menu. Choose the option representing the information you want to see. The options are explained below. Option Description Accounting To see a list of all the file servers on your internetwork that are set Servers up to charge for their services, highlight "Accounting Servers" and press . Blocks Read To see a table of the rates that are charged for blocks of data read Charge Rates from a disk, highlight "Blocks Read Charge Rates" and press . (Different rates can be charged at different times of the day, and not all hours of the day are displayed at once. Use the arrow keys to scroll through hours not shown.) Blocks Written To see a table of the rates the file server is charging for writing Charge Rates information to the disk, highlight "Blocks Written Charge Rates" and press . Connect Time To see if the file server is charging for the amount of time a user Charge Rates is logged in, and if so, the amount being charged, highlight "Connect Time Charge Rates" and press . Disk Storage To see if the file server is charging for the amount of data that is Charge Rates stored on its disk drives, and if so, when and how much is being charged, highlight "Disk Storage Charge Rates" and press . Service Requests To see if the file server is charging for the number of requests sent Charge Rates to it from a workstation, and if so, the amount that is being charged, highlight "Service Requests Charge Rates" and press . WORKING WITH MORE THAN ONE FILE SERVER If your network has more than one file server, you can complete the following tasks: þ List the file servers you are logged in to. þ Log in or attach to additional file servers. þ Choose the current file server. þ Change to a different username on the current file server. þ Log out of an additional file server. LISTING THE FILE SERVERS TO WHICH YOU ARE ATTACHED When you are attached to a file server, you are a potential user on that file server and have access to all the directories and files your security rights allow. At times, you may need to perform tasks that involve more than one file server; when this is the case, you can use the "Change Current Server" option to find out which file servers you are attached to. (You can only attach to file servers running NetWare v2.1 or above.) 1)At the OS/2 prompt, type SYSCON The SYSCON "Available Topics" menu will be displayed. 2)Highlight "Change Current Server" and press . A list of the file servers you are attached to and the usernames you entered when you attached will be displayed. ATTACHING TO AN ADDITIONAL FILE SERVER If other file servers on your network are running NetWare v2.1 or above, you can use SYSCON to attach to and access information from those file servers. For example, if Marketing is your default server and you want access to information in the Communications department, you could attach temporarily to the Communications file server. To access information on another file server, you must first choose that server as your "current server." To do so, see "Choosing the Current File Server" on page 140. If you are not defined as a user on the file server to which you want to attach, you can usually attach as user GUEST. GUEST is automatically created as a user on every file server when the file server is installed and generally does not have a password. You can also attach to an additional file server as one of the file server's previously defined users if you know that user's password. 1)To attach to an additional file server, first list the file servers to which you are attached. (See "Listing the File Servers to Which You Are Attached" above.) 2)To see a list of the file servers on your internetwork to which you can attach, press . 3)Highlight the file server to which you want to attach; then press . The "User Name" entry box will be displayed. 4)Type the username you want to use (for example, GUEST); then press . 5)If a password is required along with the username, the "Password" entry box will be displayed. Type in the password; then press . If either the username or password is incorrect or has not been defined, you will be denied access to the file server. See your supervisor for help. CHOOSING THE CURRENT FILE SERVER Even when you are attached to more than one file server, you can only access information from one of them at a time--the one you designate as your "current" file server. To access information from another of the file servers to which you are already attached, you must make it your "current" (or default) server. To change your current file server to another file server, complete the following steps. 1)List the file servers to which you are attached. Your current file server will be highlighted. 2)Using the arrow keys, highlight the file server that you want to make your current server; then press . CHANGING TO A DIFFERENT USERNAME ON THE CURRENT FILE SERVER You can change your username on a file server by attaching to that file server under a different username. Since you cannot change usernames on your default server, you must be attached to at least two servers in order to specify a different username. (Your default server is the file server you originally logged in to.) You can change to a different username on a file server if you know that user's password. You can also attach to any file server as GUEST, since GUEST generally does not require a password. To attach to a file server using a different username, complete the following steps: 1)To attach as another user, first list the file servers to which you are attached. (See "Listing the File Servers to Which You Are Attached" on page 139.) 2)Highlight the file server to which you want to attach and press the Modify key. ( is the Modify key on most computers. Press or twice to verify this for your computer.) The "New User Name" entry box will be displayed. 3)Type in the new username; then press . 4)If a password is required, the "Password" entry box will be displayed. Type in the password; then press . If either the username or password is incorrect or has not been defined, you will be denied access to the file server. See your network supervisor for help. You are now attached to the file server as the user whose name you entered. LOGGING OUT FROM ADDITIONAL FILE SERVERS If you are attached to more than one file server, you can log out of any file server (except your default server) from within SYSCON. 1)List the file servers to which you are attached. 2)Highlight the file server you want to log out of; then press . To log out of multiple file servers, mark the appropriate servers by highlighting each and pressing the Mark key. ( is the Mark key on most computers. Press or twice to verify this for your computer.) Then press . 3)The "Logout from Server" confirmation box will be displayed. To log out of the server(s), highlight "Yes"; then press . VIEWING FILE SERVER INFORMATION To view information about a file server, complete the following steps. 1)Highlight "File Server Information" in the SYSCON "Available Topics" menu and press . The "Known NetWare Servers" list will be displayed. 2)Highlight the file server you want to view information about; then press . The "File Server Information" inset will appear. You can view the following information about any file server on your internetwork. Option Description Server Name The name that the file server is known by on the network. NetWare Version The version of NetWare the file server is using. System Fault The level of SFT NetWare that the file server is Tolerance running. This information will not appear for file servers running versions of NetWare prior to v2.1. Transaction Indicates whether the file server supports TTS Tracking (Transaction Tracking System) recovery for database files. This information will not appear for file servers running versions of NetWare prior to v2.1. Connections The maximum number of users that can be logged in Supported to the file server at any one time. Connections The number of users currently logged in to the file In Use server. Volumes Supported The maximum number of disk volumes the file server can support. Network Address The address of the network on which the file server is located. Node Address The address of the node within the network where the file server resides. GROUP INFORMATION You can view the following information about user groups on your network: þ Full name þ Member list þ Group ID number þ Trustee assignments LISTING THE GROUPS ON A FILE SERVER To list the groups on a file server, complete the following steps. 1)At the OS/2 prompt, type SYSCON The SYSCON "Available Topics" menu will be displayed. 2)Highlight "Group Information" and press . A list of the groups on the current file server will be displayed. VIEWING INFORMATION ABOUT GROUPS You can view the full name and member list of any group. You can view the group's ID number and trustee assignments only if you are a member of that group. Option Description Full Name This inset displays the group's full name (if it has been defined by the network supervisor). Member List This inset displays the group's members (if the list has been defined by the network supervisor). Other Information This inset displays only the Group's ID number. The Group ID number is the bindery ID number of the selected group. (The file server uses this ID number to identify the group.) You can see this option only if you are a member of the group. Trustee This inset lists the directories (if any) of Assignments which the group is a trustee, and what trustee rights the group has in those directories. You can see this option only if you are a member of the group. 1)To view information about a particular group, first access the "Group Names" list. 2)Highlight the group whose group information you want to view and press . The "Group Information" menu will be displayed. 3)Then highlight the option you want to view in the "Group Information" list and press . SUPERVISOR OPTIONS Only network supervisors can use the "Supervisor Options" listed in the SYSCON "Available Topics" menu. Unless you have security equivalence to the supervisor, you will not be able to access the supervisor options. If you have supervisor security equivalence, refer to "Syscon (Supervisor Tasks)" on page ? for more information about supervisor options." USER INFORMATION You can use the "User Information" option in the "Available Options" menu to see information about yourself and other users. You can view the following information about all users: þ The users defined on the current server þ Any user's full name (if defined) and the groups to which that user belongs In addition, you can see the following information about yourself: þ Your account balance (if accounting is enabled on the server you are logged in to) þ Your account restrictions þ The last time you logged in þ Your file server console operator status þ The amount of disk space you are using þ Your user ID number þ Your security equivalences þ Your station restrictions þ Your trustee assignments You can also change your own password or view and modify your login script with "User Information." LISTING USERS To list the users on your current file server, complete the following steps. 1)At the OS/2 prompt, type SYSCON The SYSCON "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . A list of the users defined on the current file server will be displayed. VIEWING INFORMATION ABOUT OTHER USERS Unless you are a supervisor or have supervisor equivalence, the only information you can view about other users is "Full Name" and "Groups Belonged To." To view this information about other users, complete the following steps. 1)List the network users. (See "Listing Users" above.) 2)Highlight the user you want to see information about and press . The "User Information" list will be displayed. 3)Highlight either "Full Name" or "Groups Belonged To," depending upon the information you want to see, and press . VIEWING INFORMATION ABOUT YOURSELF To view information about yourself, complete the following steps. 1)List the network users. (See "Listing Users" above.) 2)Highlight your username and press . The "User Information" list will be displayed. To view user information about yourself, highlight the appropriate option in the "User Information" list and press . Each option is explained on the following pages. VIEWING YOUR ACCOUNT BALANCE To see information about your account, highlight "Account Balance" and press . The "Account Balance" inset will be displayed. NOTE: The "Account Balance" option will not appear unless accounting has been installed on the current file server. Your account balance is the amount of credit you currently have. Each time you are charged for a file server service, that amount is subtracted from your account balance. The "Account Balance" inset also indicates whether you are allowed unlimited credit. If you do not have unlimited credit, the "Low Balance Limit" will be displayed. The Low Balance Limit determines how low your account balance can drop before you stop receiving services for which you are charged. VIEWING YOUR ACCOUNT RESTRICTIONS Highlight "Account Restrictions" and press . The "Account Restrictions" inset will be displayed. You can view the following information by highlighting the appropriate option and pressing . Option Description Account Disabled If this option is set to "Yes," your account is disabled. You cannot log in to the file server again until the field is changed to "No." Account Has If this option is set to "Yes," your account is only a temporary Expiration Date account and will expire on the date entered under "Date Account Expires." Date Account If the "Account Has Expiration Date" option is set to "Yes," Expires the date the account expires is listed in this box. Limit Concurrent If this option is set to "Yes," the number of workstations from Connections which you can log in at any one time is limited. Maximum If the "Limit Concurrent Connections" option is set to "Yes," Connections this entry specifies the maximum number of stations from which you can log in. Allow User To If this option is set to "Yes," you can change your password. Change Password Require Password If this option is set to "Yes," you are required to have a password. Minimum Password If the "Require Password" option is set to "Yes," the minimum Length length of the password appears here. Force Periodic If both the "Require Password" option and this option are set Password Changes to "Yes," you must change your password at regular intervals. Days Between If the "Force Periodic Password Changes" option is set to Forced Changes "Yes," the number of days you can use your password before it expires is entered here. Date Password If the "Force Periodic Password Changes" option is set to Expires "Yes," this box indicates the date your password expires. Limit Grace If the "Force Periodic Password Changes" option and this Logins option are set to "Yes," you have a limited number of chances to change your password. If you fail to change your password within the specified limit, you will no longer be able to log in. Option Description Grace Logins If the "Limit Grace Logins" option is set to "Yes," this entry Allowed tells you the number of times you can log in after your password has expired. Remaining Grace If the "Limit Grace Logins" option is set to "Yes," this entry Logins shows the remaining number of times you can log in using an expired password. This option is reset to the number entered under "Grace Logins Allowed" when you choose a new password. Require Unique If this option is set to "Yes," you must use a new password Passwords each time you change your password. You cannot enter a previously used password. Limit Disk Space If this option is set to "No," the amount of disk space you can use is unlimited. (This option will appear only if the "Disk Limitation" option was chosen during installation.) Maximum Disk If the "Limit Disk Space" option is set to "Yes," this entry Space indicates the maximum amount of disk space you can use. (This option will appear only you chose the "Disk Limitation" option during installation.) CHANGING YOUR PASSWORD Unless you are a supervisor or have supervisor equivalence, you can change only your own password. 1)Highlight "Change Password" in the "User Information" menu and press . The "Enter Old Password" entry box will be displayed. If you did not have a password previously, the "Enter Old Password" box will not be displayed. 2)Type in your old password and press . The "Enter New Password" entry box will be displayed. 3)Type in your new password and press . The "Retype New Password" entry box will be displayed. 4)Retype your password and press . VIEWING OTHER INFORMATION ABOUT YOURSELF You can view additional information about yourself by highlighting the appropriate option below from the "User Information" list. Option Description Full Name Your full name will be displayed if the network supervisor has entered it; otherwise, "No Full Name Specified " will appear. Groups Belonged To The groups you are a member of will be displayed. Security The users and groups with whom you have security Equivalence equivalence will be listed. Station If you have been given station restrictions, the station (node) Restrictions addresses from which you can log in will be displayed. If you have no station restrictions, you can log in from any workstation on the network. Time The times during which you can log in will be displayed. You Restrictions can log in during the times that are marked with an asterisk on the table. Trustee Your trustee rights will be listed. Assignments ACCESSING YOUR LOGIN SCRIPT To access your login script so that you can customize your network environment, highlight "Login Script" and press . Your login script will be displayed. For information about creating, modifying, or viewing your login script and using login script commands, see "Login Scripts" on page 125. VIEWING OTHER INFORMATION The SYSCON utility allows you to view several miscellaneous items. If you highlight "Other Information" and press , you will see the following information. Option Description Last Login The date and time you last logged in will be shown. File Server This entry will show whether you have FCONSOLE operator Console Operator status. Maximum Disk If your file server limits the amount of disk space that you can Space use, the maximum amount available for your use will be displayed. Disk Space The amount of disk space being used by your files will be In Use shown in kilobytes. User ID Your bindery ID number will be shown. LOGIN SCRIPT COMMANDS A login script is a set of commands which customizes your network environment when you log in. For instance, you can set up permanent drive mappings, create messages for yourself, and modify your OS/2 environment. You can create login scripts with the SYSCON utility. Unless you are a network supervisor, you can create or modify a login script only for yourself. You can enter a different login script for each file server on which you have been created as a user; however, the script will be interpreted and executed only for the file server you specify when you log in. USING THE DEFAULT LOGIN SCRIPT If you do not have a login script for a certain file server, the following default script will be executed when you log in: WRITE "Good %GREETING_TIME, %LOGIN_NAME." MAP DISPLAY OFF MAP ERRORS OFF Remark: Set 1st drive to most appropriate directory. MAP *1:=SYS:; *1:=SYS:%LOGIN_NAME IF "%1"="SUPERVISOR" THEN MAP *1:=SYS:SYSTEM Remark: Set search drives (S2 machine-OS dependent). MAP *2:=SYS:PUBLIC/OS2 /%OS_VERSION Remark: Now display all the current drive settings. MAP DISPLAY ON MAP CREATING OR MODIFYING A LOGIN SCRIPT To create or change a login script, make sure that your current drive is mapped to the file server for which you are creating or modifying the login script. Then access the SYSCON menu utility by completing the following steps. 1)At the OS/2 prompt, type SYSCON The SYSCON "Available Topics" menu will be displayed. 2)Highlight "User Information" and press . A list of the users on the current file server will be displayed. 3)If you are a regular user or network supervisor and want to modify your own login script, highlight your name and press . If you are a network supervisor and want to modify another user's login script, highlight that user's name in the list and press . 4)Highlight "Login Script" and press . The login script will be displayed. Once you have accessed the login script, you can enter commands you want to be included in the login script or edit existing commands. Unless you have supervisor rights, you can create or modify only your own login script. Use the commands explained in this section to create or edit your login script so that mappings or messages you need frequently will appear on the screen when you log in. If appropriate login script commands have been entered, many convenient tasks will be performed automatically for you when you log in. NOTE: When you enter login script commands, be sure to end each line by pressing the Enter key. Words that are wrapped automatically onto the next line (because the end of the line was reached) are still considered part of the previous command. Only a few restrictions apply: þ Command lines can not exceed 150 characters. To increase readability, however, we recommend that you use only 78 characters per line--the width of your screen. þ Only one command can be entered on each line. The SYSCON utility has a self-contained screen editor and a help system that you can use to edit your login script. Press the Help key at any time during editing to receive help. When you have finished creating or modifying the login script, press the Escape key. You will be asked to specify whether you want to save your changes. To save your changes, highlight "Yes" and press . To exit SYSCON, press until the "Exit SYSCON" confirmation box appears. Then highlight "Yes" and press . LOGIN SCRIPT COMMANDS You can use the following login script commands to customize your login script: ATTACH BREAK DISPLAY AND FDISPLAY DOS VERIFY DRIVE EXIT EXTERNAL PROGRAM EXECUTION (#) FIRE PHASERS IF ... THEN INCLUDE MAP PAUSE PCCOMPATIBLE REMARK WRITE Each of the login script commands is explained in this section. The commands appear in alphabetical order. COMMAND FORMAT CONVENTIONS To execute a login script command, you must enter the appropriate command format. A command format includes keywords, variables, spacing, parameters, delimiters, or other characters and punctuation. Whenever possible, NetWare commands use the same symbols and formatting techniques that are used in OS/2 manuals. However, since some command format conventions are different, you should read this section carefully. Each part is explained below, using the following command as an example: ATTACH [file server[/username[;password]]] Parameter Explanation Keywords The main words that tell what the command is used for and that appear in upper-case letters are keywords. Keywords must be spelled exactly as shown. Although they appear in upper-case letters, keywords can be typed in either upper- or lower-case letters. In the example, ATTACH is the keyword. It indicates that the command is used to make a connection to an additional file server. Variables Words printed in italics are variables. Variables indicate information you must supply; it is information specific to your network. This information can change each time you use the command. In the example, file server, username, and password are variables. You would replace file server with the name of the file server, username with your username or the username with which you are attaching, and password with the password for that username. Square Square brackets enclose keywords, variables, or Brackets [ ] parts of either that are optional. When you type an optional word in a command format, do not include the brackets. In the example, file server is optional. Nested Square Nested square brackets enclose a word or part of a Brackets [[ ]] word that is an option within an option. If you choose to include the information within the nested brackets, you must also include the information in the outer brackets. In the example, the brackets indicate that the file server, username, and password variables are optional. If you type ATTACH, for example, you will be prompted for the rest of the information when you log in. However, if you choose to include username, you must also include file server, and if you include password, you must also include username and file server. Vertical Bar | A vertical bar separates entry choices; it is a symbol for "or." When you find items in a command format separated by a vertical bar, you can enter any one item, but not more than one. Ellipses ... Ellipses indicate that the keyword or variable immediately preceding the ellipses can be repeated as many times as you want. The keywords or variables must be separated by a space. Right and Left Right and left angle brackets indicate keys you Angle Brackets must press. Do not type either the angle brackets < > or the enclosed instructions in the command format. In the example, means you should press the Enter key after you type the command format. Other Characters Any other characters or punctuation included in a and Punctuation command format should be typed exactly as shown. ATTACH Command Format ATTACH [file server[/username[;password]]] Use the ATTACH login script command to connect to additional network file servers without interrupting the current execution of the login script. To attach to an additional network file server, enter this command in your login script. Type ATTACH You can also specify file server, username, and password. If you use the ATTACH command without supplying these variables, you will be prompted to enter them when you log in. You will be prompted to enter only those variables that you have not included. For example, if you enter ATTACH and the name of the file server in your login script, you will be prompted only to enter the login name and password for that file server when you log in. For example, suppose you want to attach to file server FS2 as the supervisor (whose password is "Pizza"). Type ATTACH FS2/SUPERVISOR;PIZZA We do not recommend that you attach to file servers from a login script unless the connection is required for supervisory reasons or for regular, frequent sharing of network resources. For occasional network communication, it is better to execute the ATTACH command line utility. If there are several file servers to which you regularly attach, we recommend that you use the same username and password on each file server (unless you attach as GUEST, since GUEST usually does not require a password). In this case, the command ATTACH FS2 will attach your workstation to FS2 and log you in using the username and password you specified when you logged in to the default file server. However, even if you use different usernames and passwords for different file servers, you can still place the ATTACH FS2 command in your login script. The login program will prompt you to enter the username and password (if a password is required) for the file server to which you are attaching. By using the same username and password on several file servers and attaching to them in your login script, you will also gain an additional advantage. If your password expires on any of the servers, the login program will let you enter a new password and synchronize your password on all other file servers for which you have a username and password. BREAK Command Format BREAK ON|OFF Use the BREAK ON command to stop the execution of your login script during the login process. If you include the BREAK OFF command in your login script, you will not be able to stop the normal execution of your login script. If you have entered the BREAK ON command in your login script, you can press CTRL/C or CTRL/BREAK at any time you want to abort the normal execution of your login script. To specify whether the execution of your login script can be stopped, enter the appropriate version of this command in your login script. Type BREAK ON or BREAK OFF Entering this command into your login script does not affect the OS/2 CTRL/BREAK check. When the BREAK option is "ON," type-ahead keyboard input will not be saved in the buffer. If you find this side effect undesirable, you may want to leave the break option in its default form: BREAK OFF. DOS VERIFY Command Format DOS VERIFY ON or DOS VERIFY OFF You can use the DOS VERIFY command to verify that data copied to a local drive has been copied correctly. The DOS COPY command, unlike the NetWare copy command (NCOPY), does not automatically verify that data has been copied to a local drive. If you want OS/2 to make the same verification, you must enter the DOS VERIFY ON command in your login script. This command may not work with some software that is copy-protected. To specify the DOS VERIFY command in your login script, type DOS VERIFY ON or DOS VERIFY OFF If the DOS VERIFY ON command has been entered in the login script, the operating system automatically verifies that data copied to a local drive using the DOS COPY command has been copied correctly. If DOS VERIFY has been set to OFF, no verification takes place. If you have entered an DOS VERIFY OFF command in your login script but still want a particular copy verified, you must add the /v option to the DOS COPY command, as in the following example: COPY filename to local drive:/v In other words, if you want to make sure that data copied to a local drive has been copied correctly, you can do any of the following: þ Enter the DOS VERIFY ON command in your login script. þ Use the NCOPY command. þ Add the /v option to the DOS COPY command. DISPLAY AND FDISPLAY Command Format [F]DISPLAY [directory/]filename Use the DISPLAY and FDISPLAY commands to display the contents of a specified text file on your workstation screen during the login process. To instruct the operating system to display a certain file for you when you log in, enter the following command, replacing directory and filename with the name of the file you want to see when you log in. Type [F]DISPLAY [directory/]filename If you enter the DISPLAY command in your login script, the exact characters contained in the file, including "garbage" such as printer and word processing codes, will appear on your workstation screen. If you enter FDISPLAY, the text in the file will be "filtered" and formatted so that only the text itself will be displayed. For example, suppose your supervisor puts messages in a public "bulletin board" file (SYS:PUBLIC/MESSAGES/SYSNEWS.TXT, in this example) and wants you to read this file when you log in. To enable the operating system to display this file automatically, you can type a command similar to the following in your login script: FDISPLAY SYS:PUBLIC/MESSAGES/SYSNEWS.TXT After the FDISPLAY command is entered, any messages the supervisor puts in the file will be displayed on your screen when you log in. For example, if the supervisor updates the SYSNEWS.TXT file with the message, "Meeting for everyone Tuesday at 2:00," you will receive the message when you log in. (If the given directory does not exist or if the given file is not found, no error message will appear on your screen when you log in.) DRIVE Command Format DRIVE n: (where n = a letter) or DRIVE *n: (where n = a number) Use the DRIVE command to specify as a default drive a drive other than the first network drive. Unless you have entered this command in your login script, your default drive is set to the first network drive, which is often initially assigned to your home directory when you log in. To specify which drive you want the operating system to recognize as your default drive, enter the DRIVE command in your login script, replacing the n variable with the appropriate drive. To specify drive J as your default drive, type DRIVE J: The drive you specify must be defined in your login script in a separate MAP command entered on any line above the DRIVE command entry. For example, suppose you expect to be working on only one project for several days, and the information for the project is located on drive S. You can use the DRIVE command to set your default drive to S (so you won't have to change the drive specification manually every time you log in). To do this, type DRIVE S: EXIT Command Format EXIT You can use the EXIT command to terminate execution of the LOGIN command line utility. Any login script command entered on any line below the EXIT statement will be ignored. This command allows you to execute .COM, .EXE, and .BAT files; and OS/2 internal commands, such as DIR. NOTE: If you use EXIT in the system login script, the users' login scripts will not execute. To terminate the execution of the LOGIN command line utility, type the following in your login script: EXIT EXTERNAL PROGRAM EXECUTION (#) Command Format #[directory/]filename parameter line Use the EXTERNAL PROGRAM EXECUTION (#) command to execute a command that is external to the login script. If you want the LOGIN utility to execute a command that is external to the login script, enter this command in the script. You can þ Specify a full or relative directory path before the filename; þ Add parameters after the filename, just as if the command were being executed manually from the OS/2 prompt. The following restrictions apply: þ The command statement must appear on its own line. þ The first character on the script line must be a pound sign (#). þ The filename must be the name of the .EXE or .COM program you want to execute (excluding the extension). þ The command should appear after MAP assignments, since the program will execute in the environment of drive mappings, default drives, and search drives set up previously in the login script. This command function will fail if the given directory is invalid, if proper security rights are lacking, if the execute file cannot be found, or if there is insufficient workstation memory to load the execute file. NOTE: Do not exit to a terminate and stay resident (TSR) program (such as SideKick or any terminal emulator that terminates and stays resident) with the EXIT command in your login script. The login script is held in memory when the External Program Execution (#) command is run. The login script is not released from memory until you return to the script and complete it or exit the script. For example, suppose user Chris wants to play NSNIPES (a network game) any time she enters "snipes" as a parameter after her login name. She would enter the following IF...THEN conditional in her login script: IF "%2" = "snipes" THEN BEGIN #NSNIPES 4 END (For an explanation of IF...THEN conditionals and the symbols used in the above example, see page 160.) When user Chris logs in and includes the SNIPES parameter (LOGIN CHRIS SNIPES), the NSNIPES command will be executed automatically, even though it is external to the login script. FIRE PHASERS Command Format FIRE PHASERS n TIMES Use the FIRE PHASERS command to generate a noise that sounds like the phaser guns your favorite space heroes fire. It can also be used to alert you that certain conditions exist. To instruct the operating system to fire the phasers automatically, type the following in your login script: FIRE PHASERS n TIMES (The n represents the number of times you want to hear this sound. You can fire phasers up to nine times). For example, suppose you want to hear the "phaser" sound four times when you log in. In your login script, type FIRE PHASERS 4 TIMES This command can be used with the IF ... THEN statement. (See below for an explanation of the IF ... THEN command.) You can specify that the sound be generated a different number of times depending on the circumstances of the login. For example, you could instruct the system to fire the phasers three times if you have new mail by entering the following command: IF NEW_MAIL = "Yes" THEN FIRE PHASERS 3 TIMES IF ... THEN Command Format IF conditional(s) THEN command You can use the IF ... THEN command to make the login process perform commands conditionally, depending on whether specified conditionals are true. Use this command to instruct the operating system to execute certain commands for you, if a specified condition(s) exists. For example, if you have the following IF ... THEN statement in your login script, your workstation screen will display AARGH... when you log in on Mondays. IF DAY_OF_WEEK="Monday" THEN WRITE "AARGH..." The conditional is the statement that follows IF. In the example given above, DAY_OF_WEEK="Monday" is the conditional. Conditionals can be made with identifier variables or command line parameters. Identifier Variables. The conditional contains identifier variables that represent variable login information, such as the date and time. In the example given above, DAY_OF_WEEK is the identifier variable. Identifier variables can be entered in either upper- or lower-case letters. Some examples of conditionals made with identifier variables follow. (For a complete list of identifier variables, see "WRITE" on page ?) IF DAY_OF_WEEK="Monday" (If it is Monday) IF GREETING_TIME IS NOT "Evening" (If it is not evening) IF "%ERROR_LEVEL" IS NOT "0" (If an error condition exists) IF MEMBER OF "GROUPNAME" (If the user is a member of the specified group) "%ERROR_LEVEL." You can use the "%ERROR_LEVEL" identifier variable as a conditional to execute a command only if certain conditions are met. "%ERROR_LEVEL" gives you control over error situations. If a command can be successfully executed, the error level will be "0." If a command cannot be executed, the error level will be represented by a value other than "0." You can use an `If "%ERROR_LEVEL"="0"' conditional to prevent the commands following the "THEN" from being executed if an error occurs. For example, if you normally need to access files on more than one file server, you could enter the following in your login script: ATTACH file server/username IF "%ERROR_LEVEL"="0" THEN MAP K:=file server/ volume:directory/subdirectory If the specified file server is down at the time you log in, an error level of "1" or some value other than "0" will be returned, and the login program will not map a drive to that server. By using the "%ERROR_LEVEL" identifier variable, you can avoid creating an error or receiving an error message. "%ERROR_LEVEL" will search for the last ATTACH or # (EXTERNAL PROGRAM EXECUTION) that was executed in the login script command. For example, if you attached to two file servers, it will search for the second ATTACH command. NOTE: Allow IF commands to "wrap" to the next line if there is not enough room on one line. Also, the "%ERROR_LEVEL" identifier can be typed with an underscore (_) or as one word ("%ERRORLEVEL"). MEMBER OF "GROUPNAME" or NOT MEMBER OF "GROUPNAME." The MEMBER OF "GROUPNAME" identifier variable can be used like any other conditional in an IF statement. The MEMBER OF "GROUPNAME" tests whether the user belongs to a certain group that the supervisor has defined on the file server. For example, you might have the following command in your login script: IF MEMBER OF "SALES" AND DAY_OF_WEEK="MONDAY" THEN WRITE "Sales meeting at 10:00; BE THERE!" If you are a member of the group SALES and it is Monday, you will receive the message "Sales meeting at 10:00; BE THERE!" when you log in. NOTE: Literal text (text that does not represent something else or is not just part of the command syntax) must be enclosed in double quotation marks (" "). For example, "Monday" and "Sales meeting at 10:00; BE THERE!" are both literal text--they will be displayed exactly as you type them. An embedded quotation mark (one that will be present in the screen display) must be preceded by a backslash (\). For example, if you want the screen display to say "Hi!" (not just Hi!), you must enter "Hi!" in the script as Write "\"Hi!\"" Command Line Parameters. You can use command line parameters in IF... THEN commands in your login script. Then when you log in, you can specify parameters that the LOGIN command will pass to your login script. When the login script is interpreted, any percent sign (%) entered in a command and followed by a number from 0 to 19 will be replaced by the corresponding parameter from your LOGIN command line. The file server name will always correspond to %0, and the login username will always correspond to %1. If you type "LOGIN file server/username" at the command line, the file server name you typed will correspond to %0 in the login script. The username will correspond to %1. The next entry in the login command line will correspond to %2 in the login script, the next entry will correspond to %3, and so on. (The parameters %2 to %19 are variable.) You could enter the following LOGIN command: LOGIN COUNT/RON SALES MARKETING LEGAL The server COUNT will correspond to %0 in the login script, the user RON will correspond to %1, the server SALES to %2, the server MARKETING to %3, and the server LEGAL to %4. Remember that command line parameters are substituted in the script command. For example, "%0"="COUNT" would become "COUNT"="COUNT" as you log in. Suppose that you want to log in to server COUNT every day, and you also want to sometimes attach to one or two other file servers on the internetwork. Type the following commands in your login script: IF "%2" DOES NOT EQUAL "" ATTACH %2 IF "%3" DOES NOT EQUAL "" ATTACH %3 Then, when you log in, specify the additional file servers (if any) that you want to attach to. For example, to log in to server COUNT and attach to servers LEGAL and COMMS, you would type the following LOGIN command: LOGIN COUNT/username LEGAL COMMS To log in to server COUNT and attach only to server LEGAL, you would type: LOGIN COUNT/username LEGAL To log in to server COUNT only, you would type: LOGIN COUNT/username To attach to different file servers, you would substitute the server names for LEGAL and COMMS. Relationships in Conditionals There are six possible relationships between the information contained in an IF ... THEN statement: equal to, not equal to, greater than, less than, greater than or equal to, and less than or equal to. You can represent equal and not equal relationships in the following ways: Equal Not Equal ----- --------- IS IS NOT = != == <> # EQUALS DOES NOT EQUAL NOT EQUAL TO The other four relationships can be represented as follows: > IS GREATER THAN < IS LESS THAN >= IS GREATER THAN OR EQUAL TO <= IS LESS THAN OR EQUAL TO Conditionals can be joined with commas or the word AND to form compound conditionals. A compound conditional is true only if all of its related conditionals are true. The following are compound conditionals: If GREETING_TIME IS "AFTERNOON" AND DAY IS "01" (If it is the afternoon of the first day of the month) If HOUR24="23", MINUTE="59", AND SECOND="59" (If it is 11:59:59 p.m.) Entering Login Script Commands The command following THEN can be a single statement or the beginning of a block of commands. The statement or block of commands will be interpreted only if all of the specified conditions are true. The following is an example of a single statement: IF NDAY_OF_WEEK="6" THEN WRITE "HOORAY! IT'S FRIDAY!" You must start a block of commands by specifying BEGIN or DO after the THEN in the IF ... THEN statement. BEGIN or DO must be entered on the same line as the conditional IF. When you have entered all the conditional *commands you want, you must end the block by specifying END. For example, you could type the following IF ... THEN statement: IF DAY_OF_WEEK="Tuesday" THEN BEGIN WRITE "Staff meeting today at 10 a.m." INCLUDE SYS:PUBLIC/UPDATE END In this case, on Tuesdays you would receive the message about staff meeting. Your login script would also process any commands or messages contained in the file SYS:PUBLIC/UPDATE. You cannot nest IF statements; that is, one IF statement cannot include another IF statement. INCLUDE Command Format INCLUDE [directory\]filename You can use the INCLUDE command to make the login script interpreter process "sub-scripts" that are not contained in the login script currently being processed. These sub-scripts are simply text files that contain valid script commands. Sub-scripts can be created and edited using any text editor or word processor. To enable the login script interpreter to process sub-scripts, type the following in your login script: INCLUDE [directory\]filename Replace the variables with the directory path and filename of the sub-script you need. NOTE: INCLUDE nesting can be 10 levels deep. This means that one script file can INCLUDE another script file which, in turn, can INCLUDE yet another script file, and so on down to 10 levels. You must have at least Open and Read rights to any directory containing a sub-script you want to use. Following are examples of different ways INCLUDE can be used. Using Text Files in a User's Login Script. Suppose a network supervisor wanted to create a special text file containing system-wide announcements. The supervisor could send the contents of this file to users by entering the command to include the text file in each user's login script. If the name of the special text file were SYS:PUBLIC\MESSAGES.INC, the supervisor could include this file in users' login scripts by entering the following in each user's login script: INCLUDE SYS:PUBLIC\MESSAGES.INC Then, if the supervisor wanted to post the message "Don't forget 7:30 a.m. meeting tomorrow," he or she could use the WRITE command to type the message in the SYS:PUBLIC\MESSAGES.INC file. When the users logged in, each user would get the message. NOTE: The INCLUDE command does not function in the same way as the DISPLAY or FDISPLAY commands. In order for it to display text as shown in this example, the included file must contain WRITE commands. Using INCLUDE to Shorten Login Scripts. The INCLUDE command can also be used to shorten many users' login scripts. The supervisor may want to create one script file, and then have each user who needs it include the script file in his or her login script with the INCLUDE command, instead of having the user manually type the extra commands in the script. MAP Command Format You can use MAP to do a variety of things, depending on the parameters (variables) you include in the command format. These commands can be entered anywhere in your login script. The command formats, along with the different parameters you can use, are listed below. Parameter Description MAP Displays the current drive mappings for all drives on the workstation. Undefined local drives (drives that have not been mapped to a directory) will not be displayed. MAP drive: [/Private] Displays the current mapping for the specified drive. MAP drive:=directory [/Private] Maps the specified drive to the given directory. Directory refers to the directory path, beginning with the volume name. MAP directory [/Private] Maps the default drive to the specified directory. Directory refers to the directory path, beginning with the volume name. MAP drive:= [/Private] Maps the specified drive to the directory that the default drive is mapped to. MAP drive:=drive: [/Private] Maps the first drive to the same directory that the second drive is mapped to. MAP drive:=directory; drive:=directory ... [/Private] Maps multiple drives to multiple directories with one command. This command has the same result as executing the command MAP drive:=directory two or more times. Directory refers to the directory path, beginning with the volume name. MAP DEL drive: [/Private] Deletes a MAP definition. MAP REM drive: [/Private] Removes a MAP definition. (Same as MAP DEL.) Use the MAP command to map a drive to a directory on the network. Before you can work in a network directory, you must have a drive mapped to that directory. When you use the MAP command to save drive mappings in your login script, you don't have to remap drives to directories every time you log in. This command is useful if you frequently use a number of directories and don't want to specify drive mappings for them every time you log in. Your workstation has 26 logical drives (assigned letters A through Z) which you can use to map to directories in all areas of the network directory structure. Some of these logical drives will automatically be assigned to local drives when you log in. Up to 16 of the 26 drives can be assigned as search drives. Specify drive mappings in your login script by entering the same commands in the login script that you would enter if you were using the regular MAP command. These mappings will be displayed when you log in, unless you have entered MAP DISPLAY OFF in your login script. When specifying drive names such as F or G, you can use an asterisk followed by a number n to represent the nth network drive. For example, if your workstation has two local drives, A and B, then *1: would map to one of two drives: either the first drive beyond the drive specified by the LASTDRIVE command found in the CONFIG.SYS configuration file (see the OS/2 manual), or drive F if no LASTDRIVE = command is used. It is generally best to use the relative specification *n:; this allows you to log in from workstations with different local drive configurations. NOTE: IBM PC AT compatibles generally have five local drives by default (depending on the version of OS/2 you are using). You can override the default by using the LASTDRIVE command in your OS/2 CONFIG.SYS file. You can map a local drive to a network directory, but you will not be able to access the local drive until you remove the network drive mapping. The network supervisor can initially assign *1: to a user's home directory. The user can redefine *1: if desired. You should assign search drives in numerical order, beginning with S1:. Following are examples of different ways MAP can be executed. If you include the following map command, drive F will be mapped to the SYS:SALES directory when you log in: MAP F:=SYS:SALES If you include the following map command, your first network drive will be mapped to the SYS:SALES directory when you log in: MAP *1:=SYS:SALES; Q:=*1:TEST Drive Q will be mapped to the subdirectory TEST relative to SYS:SALES (since you defined *1: to be mapped to the directory SYS:SALES). Other login script MAP command options include the following: Command Option Description MAP DISPLAY ON Your drive mappings will be displayed when you log in. This is the default setting. MAP DISPLAY OFF Your drive mappings will not be displayed when you log in. MAP ERRORS ON MAP error messages (messages that report serious errors encountered while mapping drive assignments) will be displayed. This is the default setting. MAP ERRORS OFF MAP error messages will not be displayed. You can use MAP DISPLAY ON and MAP DISPLAY OFF anywhere in your login script; however, you must place MAP ERRORS OFF and MAP DISPLAY OFF before the drive mappings in your login script. The MAP Command and the Shell Descriptor Area When a workstation loads the NetWare shell, it passes the information in the descriptor area to the file server. Special identifiers are assigned to each descriptor in the NetWare shell descriptor area: þ SHELL_TYPE--assigned to the shell-type descriptor þ OS--assigned to the OS/2-type descriptor þ OS_VERSION--assigned to the OS/2-version descriptor þ MACHINE--assigned to the long-machine-type descriptor þ SMACHINE--assigned to the short-machine-type descriptor You can use these identifiers within login script commands to modify your operating environment at the time you log in. Using these identifiers within the MAP command allows the file server to map a drive to the directory with the correct version of DOS. If the MAP command is inserted in the system login script (or in each individual's login script), it should appear as follows (typed on a single line): MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSION The mapped drive must be a search drive, so that OS/2 commands can be accessed from any directory on the network. The actual values for the identifiers come from the shell's descriptor area when it is sent to the file server during login. For example, the following search path could be created using the MAP command shown on the preceding page: S2:=SYS:PUBLIC\COMPAQ\MSDOS\V4.00 The directory (indicated by the identifiers in the MAP command) should already exist and have the correct OS/2 version loaded in the directory, or login will not be completed successfully. PAUSE Command Format PAUSE or WAIT You can use the PAUSE command to create a pause in the execution of the login script. You can add the PAUSE command to the login script following a message so that you will have time to read the message before it scrolls off the screen. If you include the PAUSE command, the message, "Strike a key when ready...," will appear on the workstation screen. The login program will then wait for a key to be pressed before it executes the rest of the login script. To create a pause in the execution of the login process, enter either of these commands in your login script at any point you want a pause to occur. Type PAUSE or WAIT PCCOMPATIBLE (OR COMPATIBLE) Command Format [PC]COMPATIBLE You can use the PCCOMPATIBLE command to include a filename with the "EXIT" login script command on all computers that are IBM PC compatible; you can also use it with computers that are not 100% IBM PC compatible. If your machine is an IBM PC compatible but you have changed your long machine name in your SHELL.CFG file to another name (for example, COMPAQ) in order to access a different version of OS/2, you must use the PCCOMPATIBLE (or COMPATIBLE) login script command to inform the login program that your machine is an IBM PC compatible. To make it possible to include a filename with the EXIT login script command on IBM PC compatibles, type the following anywhere before EXIT in the login script: PCCOMPATIBLE For example, if you are working on an IBM PC compatible and you want to exit to SYSCON from within your login script, type PCCOMPATIBLE EXIT "SYSCON" REMARK Command Format REMARK [text] or REM [text] or * [text] or ; [text] You can use the REMARK command to insert explanatory text into your login script. Any text following REMARK (or REM), an asterisk (*), or a semicolon (;) will be ignored when the LOGIN command interprets and executes your login script. The "remark" will not appear on your screen. Using remarks in your login script can make the script much easier for you 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 script commands will cause errors when your login script is interpreted. To add explanatory text to your login script, type the following (or one of the other variants of the REMARK command) in your login script, entering the text you need in place of the text variable. REMARK [text] The following are examples of explanatory text which you might use with the REMARK command: * Sample Text ; assign OS-dependent Search mappings REM Check for new mail. REMARK Be sure to update the PROJECTS file. WRITE Command Format WRITE [text string(s); ... identifier(s); ...] Use the WRITE command to customize your login messages. You can enter a single command or include a list of text strings or identifiers separated by semicolons (;) after any WRITE command. Each message will appear on a new line on your screen, unless you place a semicolon at the end of the WRITE command line. Then multiple WRITE commands will generate a one-line display. Text strings must be enclosed in double quotation marks (") and can include the following super-characters: \r for a carriage return \n for a new line \" for an embedded quotation mark \7 to sound a beep The following identifiers represent variable text information. (Enter them exactly as shown.) When the WRITE command is executed, the correct text will be substituted and then displayed on your workstation screen. NOTE: Identifier variables can be used with the IF ... THEN command as well as the WRITE command. They can also be used with commands for which you can specify a pathname, such as COMSPEC. Identifier Variable Screen Display HOUR Hour of the day or night (1 - 12) HOUR24 Hour (00 - 23) MINUTE Minute (00 - 59) SECOND Second (00 - 59) AM_PM Day or night (am or pm) MONTH Month number (01 - 12) MONTH_NAME Month name (January, June, etc.) DAY Day number (01 - 31) NDAY_OF_WEEK Weekday number (1 - 7, Sunday's 1) YEAR Year in full format (1989, 2016, etc.) SHORT_YEAR Year in short form (89, 16, etc.) DAY_OF_WEEK Day of week (Monday, Friday, etc.) LOGIN_NAME User's unique login name FULL_NAME User's full name (from SYSCON files) STATION Workstation number P_STATION Physical station (12 hex digits) GREETING_TIME Morning, afternoon, or evening NEW_MAIL YES or NO, indicating whether or not new mail has arrived. Your mailbox is checked automatically when you log in, and the correct value ("YES" or "NO") is assigned. OS The workstation's operating system, e.g., IBMOS/2 OS_VERSION The version of the workstation's OS/2, e.g., V1.1 MACHINE The machine which the shell was written for, e.g., IBM_PC SMACHINE Short machine name, e.g., IBM Identifier Variables Screen Display ERROR_LEVEL A value; for example, 0 (no errors) or any number other than 0 (errors) MEMBER_OF Name of group _GROUPNAME USER ID User identification number You can use WRITE command identifiers in other login script commands if the identifiers are preceded by a percent sign. These "identifier variables," as they are called, will be replaced by their actual values before the script line is interpreted. Identifier variables can also be placed within literal text strings in a WRITE statement; however, the identifier name must be in upper-case letters and preceded by a percent sign. For example, the following two lines would result in the same output: WRITE "Good "; greeting_time; ", John" WRITE "Good %GREETING_TIME, John" NOTE: Identifier variables are very useful if you intend to use different PC operating systems concurrently on different network stations. Depending upon the operating system type, you can appropriately set search drive mappings and other OS-dependent mappings for the operating system you are using when you log in. Identifier variables can also provide for the different commands required by different machine types. For example, if you are using OS/2 v1.10, you could create a SYS:PUBLIC/IBM_PC/PCDOS/V4.00 directory and place a copy of the appropriate COMMAND.COM in that directory. You could then create a similar directory for each different machine and operating system type. If your login script contained the following command, it would access the proper login command no matter which machine you execute LOGIN from: MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSION Suppose user Bill's login script contained the following WRITE command: WRITE "Hello, "; LOGIN_NAME WRITE "This is station "; STATION The following would be displayed when Bill logged in to station 16: Hello, BILL This is station 16 SYSTIME Command Format SYSTIME [server] Replace server with the name of a file server. How to Use SYSTIME Use SYSTIME to view the date and time set on any file server on your network or internetwork. When you view this information for a file server, you also synchronize the date and time on your workstation with the settings on that file server. You must be attached to a file server before you can use SYSTIME with that file server. Using SYSTIME To view the date and time on your default file server, type SYSTIME You will see a message similar to the following: Current System Time: Monday April 10, 1989 8:16 am To view the date and time on a file server other than your default file server, specify the file server in the SYSTIME command. For example, to view the date and time on file server SALES, type SYSTIME SALES You will see a message similar to the following: Current System Time: Monday April 10, 1989 8:25 am TLIST Command Format TLIST [path [ [.] USERS | [.] GROUPS]] Replace path with a directory path leading to and including the volume, directory, or subdirectory whose trustee list you want to view. To view only the user trustees of a directory, include USERS in your command. To view only the group trustees of a directory, include GROUPS in your command. Include the space and period (.) before USERS or GROUPS if you want to view the user trustees or group trustees of your default drive. How to Use TLIST Use TLIST to view the trustee list for a given directory. You must be attached to a file server before you can view the trustee list for a directory on that file server. You must also have Parental effective rights in a directory to view the trustee list for that directory. Viewing the Trustee List of a Directory. To view the trustee list of your default directory, type TLIST You will see information similar to the following: User Trustees: LYNN [RWOCDPSM] (Lynn Phillips) DAVID [R O S ] (David Ortiz) ----- Group Trustees: CLERKS [R O S ] (Accounting clerks) This screen display lists the users and groups who are trustees of your default directory. It also shows their trustee rights and gives either their full name or a brief description of the group they belong to. To view the trustee list of a directory other than your default directory, include the drive letter mapped to that path, or include the path. For example, to see the trustee list of G:RECORDS/SYS:DATA, type TLIST G: or TLIST RECORDS/SYS:DATA You will see information similar to the following: User Trustees: MIKE [RWOCDPSM] (Mike Tong) ANNA [R O S ] (Anna Hasara) ----- Groups Trustees: EDITORS [R O S ] (Technical editors) Viewing the User Trustees of a Directory. To view the user trustees of your default directory, type TLIST . USERS The period (.) in the command represents your default drive. You will see information similar to the following: User Trustees: LYNN [RWOCDPSM] (Lynn Phillips) DAVID [R O S ] (David Ortiz) To view the user trustees of a directory other than your default directory, include the drive letter mapped to that path, or include the path. For example, to see the user trustees of G:RECORDS/SYS:DATA, type TLIST G: or TLIST RECORDS/SYS:DATA You will see information similar to the following: User Trustees: MIKE [RWOCDPSM] (Mike Tong) ANNA [R O S ] (Anna Hasara) Viewing the Group Trustees of a Directory. To view the group trustees of your default directory, type TLIST . GROUPS The period (.) in the command represents your default directory. You will see information similar to the following: Group Trustees: CLERKS [R O S ] (Accounting clerks) To view the group trustees of a directory other than your default directory, include the drive letter mapped to that directory, or include the path. For example, to see the group trustees of G:RECORDS/SYS:DATA, type TLIST G: GROUPS or TLIST RECORDS/SYS:DATA GROUPS You will see information similar to the following: Group Trustees: EDITORS [R O S ] (Technical editors) USERLIST Command Format USERLIST [server/] [user] [options] Include server/ if you want to view the user list of a file server other than your default file server. Replace server with the name of the file server. Replace user with the name of a user whose connection number and login time you want to view. Replace options with one or both of the following options: /Address Include this option if you want to view the network address and the node address of each user. /Object Include this option if you want to view the object type of each user. How to Use USERLIST Use USERLIST to view a list of current users for a given file server. You can also view each user's connection number, login time, network address, and node address. The network address identifies each user's network, and the node address identifies each user's network interface board. An asterisk (*) will appear next to your username in the list of current users. You must be attached to a file server before you can view the user list for that file server. Viewing a File Server's User List. To view the user list for your default file server, type USERLIST You will see information similar to the following: Connection User Name Login Time -------------- ------------------ ------------------------- 1 JOIE 4-10-1989 8:10 am 2 *CORRINE 4-10-1989 8:23 am 3 PAULO 4-10-1989 7:59 am 4 GUY 4-10-1989 9:14 am To view the user list of a file server other than your default file server, include the name of the file server and a slash in the command (the slash (/) indicates that the name is of a file server rather than a user). Type USERLIST RECORDS You will see information similar to the following: Connection User Name Login Time ---------------------------------- ------------------------- 1 LUPE 4-10-1989 7:36 am 2 MARC 4-10-1989 8:02 am 3 *KAOCHIEN 4-10-1989 7:54 am 4 JILLIAN 4-10-1989 8:17 am Viewing Users' Network and Node Addresses. If you want to see the network and node addresses of each user on either your default file server or another file server, include /Address in your command. Type USERLIST /A or USERLIST SALES/ /A You will see information similar to the following: Connection User Name Network Node Address Login Time --------------------------- ---------- ----------------------------------- 1 JOIE CED88 2608C234732 4-10-1989 8:10 am 2 *CORRINE CED87 2608C857393 4-10-1989 8:23 am 3 PAULO CED87 2608C857202 4-10-1988 7:59 am 4 GUY CED87 2608C238948 4-10-1988 9:14 am Viewing Users' Object Types. If you want to see the object type of each user, include /Object in your command: USERLIST /O or USERLIST SALES/ /O You will see information similar to the following: Connection User Name Login Time Object Type --------------------------------------------------------------------- 1 JOIE 4-10-1989 8:10 am User 2 *CORRINE 4-10-1989 8:23 am User 3 PAULO 4-10-1989 7:59 am User 4 GUY 4-10-1989 9:14 am User Viewing Information about a Single User. To view information about user GUY on your default file server, type USERLIST GUY You will see information similar to the following: Connection User Name Login Time ---------------------------------------------------- 4 GUY 4-10-1989 9:14 am To see the network and node addresses for user GUY on either your default file server or another file server, include /All in your command: USERLIST GUY /A or USERLIST SALES/GUY /A To see the object type of user GUY on either your default file server or another file server, include /Object in your command: USERLIST GUY /O or USERLIST SALES/GUY /O Additional Information USERLIST allows you to specify the wildcard characters * and ? in the command. Suppose you want to look at the information for all users whose names start with M. Type the following command: USERLIST M* You will see information similar to the following: Connection User Name Network Node Address Login Time ---------------------------------------------------------------------------------------- 1 MAX CED88 2608C234732 4-10-1989 8:03 am 10 MARIA CED88 2608C273421 4-10-1989 8:45 am 19 MERIANNE CED87 2608C857234 4-10-1989 7:24 am VERSION Command Format VERSION [path] filename Replace path with the path leading to the utility whose version you want to view. Replace filename with the name of the utility whose version you want to view. How to Use VERSION Use VERSION to view the version of a NetWare utility for OS/2 on your file server. Suppose you want to see which version of USERLIST is on your file server. Type VERSION USERLIST You will see information similar to the following: USERLIST.EXE: NetWare OS/2 UserList, Version 1.04 WHOAMI Command Format WHOAMI [server] [option ...] Replace server with the name of the file server you want to specify. The ellipses (...) indicate that you can specify more than one option in the same WHOAMI command. Replace option with one or more of the following: /Groups Use this option to view your membership in groups on any file servers you specify. /Security Use this option to view your security equivalences in any directory on any file servers you specify. /Rights Use this option to view your rights in any directory on any file servers you specify. /All Use this option to view all of the information available with the other three options above. How to Use WHOAMI Use WHOAMI to view the following information about the file servers to which you are attached: þ The file server names þ Your username on each file server þ Your login date and time for each file server þ The groups you belong to on each file server þ Your security equivalences on each file server þ Your effective rights in every directory of each file server Viewing Who You Are on Your Network or Internetwork. To view network information about yourself, type WHOAMI You will see information similar to the following: You are user MAX attached to server RECORDS connection 1. Server RECORDS is running SFT NetWare 286 TTS v2.11. Login Time:Monday April 10, 1989 9:34 am You are user GUEST attached to server SALES connection 7. Server SALES is running SFT NetWare 286 TTS v2.11. Login Time:Monday April 10, 1989 9:45 am This screen display indicates that you are attached to the RECORDS and SALES file servers. Your username on file server RECORDS is MAX, and your username on file server SALES is GUEST. Viewing Who You Are on a Particular File Server. To view who you are on file server RECORDS, type WHOAMI RECORDS You will see information similar to the following: You are user MAX attached to server RECORDS connection 1 Server RECORDS is running SFT NetWare 286 TTS v2.11 Login Time:Monday April 10, 1989 9:34 am This screen display indicates that you are attached to file server RECORDS as user MAX. Viewing Your Group Memberships. To view your membership in groups defined on file server RECORDS, type the following command: WHOAMI RECORDS /G You will see information similar to the following: You are user MAX attached to server RECORDS connection 1 Server RECORDS is running SFT NetWare 286 TTS v2.11 Login Time:Monday April 10, 1989 9:34 am You are a member of the following Groups: EVERYONE CLERKS To view your membership in groups on all file servers to which you are attached, type WHOAMI /G You will see a list of all file servers to which you are attached, as well as a list of your group memberships on each file server. Viewing Your Security Equivalences. To view your security equivalences on file server RECORDS, type WHOAMI RECORDS /S You will see information similar to the following: You are user MAX attached to server RECORDS connection 1 Server RECORDS is running SFT NetWare TTS v2.11 Login Time: Monday April 10, 1989 9:34 am You are security equivalent to the following: EVERYONE (group) CLERKS (group) To view your security equivalences on all file servers to which you are attached, type WHOAMI /S You will see a list of all file servers to which you are attached, as well as your security equivalences on each file server. Viewing Your Effective Rights in Each Directory of a File Server. To view your effective rights in each directory on file server RECORDS, type WHOAMI RECORDS /R You will see information similar to the following: You are user MAX attached to server RECORDS connection 1 Server RECORDS is running SFT NetWare 286 TTS v2.11 Login Time: Monday April 10, 1989 9:34 am You have the following effective rights: [RWOCDPSM] RECORDS/SYS:HOME/MAX [R O S ] RECORDS/SYS:PUBLIC [RWOCD SM] RECORDS/SYS:ACCT:ACCPAY If this command displays a long list of directories and rights, use or the Pause key to make the screen pause temporarily. Press to resume scrolling. To cancel the command and return to your OS/2 prompt, press . To view your effective rights in each directory of all file servers to which you are attached, type WHOAMI /R You will see a listing of all file servers to which you are attached, as well as a list of your rights on each file server. Viewing Your Group Memberships, Security Equivalences, and Effective Rights. To view your group memberships, security equivalences, and effective rights on your default file server, type WHOAMI /G /S /R or WHOAMI /A To view this information for file server RECORDS, type WHOAMI RECORDS /G /S /R or WHOAMI RECORDS /A APPENDIX A RECONFIGURING THE NETWARE REQUESTER This appendix explains how to reconfigure the NetWare Requester defaults. If you need to reconfigure the NetWare Requester, you must create a NET.CFG file in the root directory of the workstation's hard disk. Specify only options that will change from the default settings. The NET.CFG file can also contain lines that modify the NetWare Spooler defaults (see Appendix C). To reconfigure the NetWare Requester, you must use the following section headings in the NET.CFG file: þ Link Support þ Protocol Stack IPX þ NetWare Requester þ Link Driver (name) These headings must not have any leading blanks or tabs. The options for each section can be used in any order, but they must be preceded by at least one leading blank or tab. The heading must precede the options you want to include in that section. You must end each line in the NET.CFG file with a carriage return. All numbers are written in decimal notation except where noted otherwise. The NET.CFG file can include the following options. Link Support Buffers count [buffer size] Use this option to specify the maximum number of communication buffers. Replace count with the desired number of buffers. The default is Buffers 20. Buffer size is optional. Replace buffer size with the desired size of the buffer. The default is 1,056 bytes. The total buffer space must fit into 64KB (count times buffer size). The default, using both count and buffer size, is Buffers 20 1056. Protocol Stack IPX Sockets count Use this option to specify the maximum number of sockets that IPX can have open at the workstation. Replace count with the number of sockets you want open. The default is Sockets 64. The maximum allowable value is 64 sockets. Router Mem size Use this option to specify the size (in bytes) of the router memory pool. This option will need to be modified only if you are running Nondedicated NetWare for OS/2, in which case you may need to make it bigger. The default is Router Mem 450. NetWare Requester Cache Buffers count Use this option to specify how many buffers the NetWare Requester will use for local caching of open file data. The size of these buffers is fixed and not configurable. Replace count with the number of buffers to be used. The default is Cache Buffers 8. The maximum allowable value must fit into 64KB. Sessions count Use this option to specify the number of file server connections supported. Replace count with the number of file server connections to be supported. The default is Sessions 8. The maximum number of file server connections that can be supported is 32; the minimum number of file server connections is 8. Private Drives count Use this option to specify the maximum number of private drives that can be mapped for all screen groups on the workstation. Replace count with the number of private drives you want to be able to map. The default is Private Drives 50. The maximum number of private drives you can map is 256. Request Retries count Use this option to specify the maximum number of times the workstation will try to resend a packet following a communications error. On networks that lose many packets, this retry count may need to be increased. However, increasing this number of request retries will cause a longer delay in some network functions. Replace count with the number of times you want the workstation to try to resend a packet. The default is Request Retries 20. The minimum number of request retries is 5; there is no maximum. Link Driver name To use this heading and its options, replace name with the name of the driver you are using; then use one or more of the following options. You can use these options with as many different network interface boards as you have, but you must have a separate Link Driver name heading for each board. Replace name with one of the following driver names when using this option: þ PCN2_MC þ PCN2_AT þ RXNET_MC þ RXNET_AT þ NE2 þ NE1000 þ TOKEN þ E3C501 DMA [#1 | #2] channel Use this option to specify the hardware setting of the network interface board used in the workstation. This option allows one of two DMA channels to be configured. Replace channel with the channel number to be used (the driver for the network interface board will automatically select its default channel number). If you do not specify which of the two configurable DMA channels (#1 or #2) to configure, this option automatically uses the default, which is the first configurable channel (#1). You do not need to include the #1 parameter if you are using only the default parameter. For example, if the first configurable DMA channel on your network interface board will use DMA channel 3, place the following lines in your NET.CFG file: Link Driver name DMA 3 If you are not using the default DMA channel or if you are using both DMA channels, you must specify which DMA channel (#1 or #2) will be configured. For example, if the first configurable DMA channel on your network interface board will use channel 3 and the second configurable channel will use channel 4, place the following lines in your NET.CFG file: Link Driver name DMA #1 3 DMA #2 4 Int [#1 | #2] IRQ Use this option to specify which interrupt line(s) the network interface board will use. Replace IRQ with the IRQ number required by the network interface board. If you do not specify which of the two configurable interrupt lines (#1 or #2) to configure, this option will automatically use the default, which is the first configurable interrupt line (#1). You do not need to include the #1 parameter if you are using only the default parameter. For example, if the first configurable interrupt line on your network interface board will use IRQ 2, place the following lines in your NET.CFG file: Link Driver name Int 2 If your network interface board can use two configurable interrupt lines and you want to use either both of them or only the second one, you must specify which interrupt line (#1 or #2) will be configured. For example, if the first configurable interrupt line on your network interface board will use IRQ 2 and the second configurable interrupt line will use IRQ 3, place the following lines in your NET.CFG file: Link Driver name Int #1 2 Int #2 3 Mem [#1 | #2] starting_address size Use this option to specify a memory range to be used by the network interface board. Replace starting address with the physical address (in bytes) of the memory used by the network interface board (this starting address must match the starting address configured on the network interface board). Replace size with the length (in paragraphs) of the memory address range used by the network interface board. If your network interface board has shared memory (RAM and ROM) and you want to configure either one or both, you will have to specify which memory range is to be configured. All values must be written in hexadecimal notation. For example, if you wanted to address a network interface board from D0000 to D4000 (bytes), the starting address would be D0000 and the range would be 400 (paragraphs). In this case, you would place the following lines in your NET.CFG file: Link Driver name Mem D0000 400 Port [#1 | #2] starting_port count Use this option to specify the starting port and number of ports in the range. Replace starting port with the starting I/O port number. Replace count with the number of ports in the range. If your network interface board can use two ranges and you want to use either the second range or both ranges, you must specify which range (#1 or #2) to use. All values must be written in hexadecimal notation. PS/2 Slot ? Use this option if you have inserted only one of the same kind of network interface board in the workstation. This option allows the driver for the network interface board to determine where the network interface board is located in the machine. If the driver can be used for either standard bus or Micro Channel network interface boards, this option allows the driver to determine whether the board is standard bus or Micro Channel. PS/2 Slot slot Use this option if you have inserted more than one of the same kind of network interface board in the workstation. Replace slot with the number of the slot into which you inserted the board. The slot number is found on the back of the computer. For example, if you are using two PC Network II/A network interface boards in the same workstation and you insert one board into slot one and the other board into slot two, place the following lines in your NET.CFG file: Link Driver PCN2_MC PS/2 Slot 1 Link Driver PCN2_MC PS/2 Slot 2 Send Retries count Use this option to specify the maximum number of times the network interface board driver will try to resend a packet following a communications error. Replace count with the number of times you want the driver to try resending the packet. The default value is determined by the driver. Envelope Type number Use this option to specify the media type that is used with the network interface board. Use this option with boards that support more than one media type. The default is Envelope Type 1. For example, an Ethernet network interface board might support two media types. If you want to specify Envelope Type 1 for media type CCITT 802.3, place the following lines in your NET.CFG file beneath the heading for that driver: Envelope Type 1 If you want to specify Envelope Type 2 for media type Ethernet II (DEC format), place the following lines in your NET.CFG file: Envelope Type 2 Suppose you want to reconfigure the NetWare Requester to increase the number of buffers from 20 to 25, increase the number of private drives allowed from 50 to 75, and use a PC Network II/A network interface board with the IRQ set at interrupt line 3 instead of the default. Place the following lines in your NET.CFG file: Link Support Buffers 25 NetWare Requester Private Drives 75 Link Driver PCN2_MC PS/2 Slot ? Int 3 APPENDIX B CUSTOMIZING BATCH FILES This appendix explains how to use NetWare and OS/2 commands to customize your OS/2 batch files to run with the NetWare Requester for OS/2. You must use the OS/2 PATH and DPATH commands to set search drives, since OS/2 handles the concept of search drives itself. You cannot use NetWare to map a search drive. See the OS/2 reference manual for more information about PATH and DPATH. OS/2 STARTUP.CMD FILE You can use the OS/2 STARTUP.CMD file as a type of system login script. Each time the workstation is booted, STARTUP.CMD will be executed. You can remap drive L (SYS:LOGIN/OS2) to SYS:PUBLIC/OS2 in the STARTUP.CMD file to allow the workstation to access all NetWare for OS/2 utilities from any drive. You can also include other commands in the STARTUP.CMD file. For example, suppose your STARTUP.CMD file includes the following information: CD L:OS2 L:ATTACH SALES\MARITZA L:MAP L:=SALES\SYS:PUBLIC\OS2 L:MAP F:=SALES\SYS:ACCT\MARITZA F: C:OS2INIT.CMD When you boot your workstation, your STARTUP.CMD file will be executed, and the following will happen: þ The directory will be changed to OS2. þ User MARITZA will be attached to server SALES. þ Drive L will be remapped to SALES\SYS:PUBLIC\OS2. þ Drive F will be mapped to one of MARITZA's directories. þ The drive will be changed to drive F. þ The OS2INIT.CMD file will be executed. OS/2 OS2INIT.CMD FILE You can use the OS/2 OS2INIT.CMD file as a type of session login script. Then, each time you begin a new session, OS2INIT.CMD will be executed. For example, if you include the command MAP in your OS2INIT.CMD file, you will see a list of all your drive mappings each time you begin a new OS/2 session. You can specify search paths for SYS:PUBLIC/OS2 and any other directories in your OS2INIT.CMD file so that your workstation can access the NetWare for OS/2 utilities from any drive or file server. If you want the OS2INIT.CMD file to include search paths, add the drive letters of the search paths to the end of the path statement in the file. For example, suppose you want to specify a search path for the directory containing the NetWare utilities for OS/2 so that your workstation can access the utilities from any drive. If drive L is mapped to SALES/SYS:PUBLIC/OS2 (which contains the NetWare utilities for OS/2), you would add drive L to the end of the path statement in the OS2INIT.CMD file, as follows: PATH C:\;C:\OS2;C:\INSTALL;L:; Drive L will be specified as a search path when OS2INIT.CMD is executed. APPENDIX C RECONFIGURING THE NETWARE SPOOLER This appendix explains how to reconfigure the NetWare Spooler defaults. These modifications affect all jobs printed from the workstation. If you want to reconfigure the NetWare Spooler, you must create a NET.CFG file in the root directory of the workstation's hard disk. The default print job options can be modified by adding lines to the NET.CFG file. Specify only options that will change from the default settings. The NET.CFG file can also contain lines that modify the NetWare Requester (see Appendix A). The NetWare Requester for OS/2 supports printer devices LPT1 (or PRN), LPT2, and LPT3. The heading "NetWare Spooler" must be used before any other lines in the NET.CFG file. This heading must not have any leading blanks or tabs. The remaining NetWare Spooler configuration lines can be used in any order, but they must be preceded by at least one space or tab. You can use the following lines in the NET.CFG file to reconfigure the NetWare Spooler. Line Explanation Form number Include this option to specify the form number on which you want the job printed. Replace number with the number of the form. The default is Form 0. Copies number Include this option to indicate how many copies you want printed. Replace number with the number of copies. The default is Copies 1. Keep Include this option if you want the data to be printed even though the capture is interrupted. The default is Keep enabled. No Keep Include this option if you want the print job canceled if the capture is interrupted. The default is Keep enabled. Size number Use this option to increase the tab size. Replace number with the desired number of spaces to replace each tab. The default is Size 8. Tabs Include this option to allow the Spooler to replace each tab with the number of spaces set in the Size option. The default is No Tabs enabled. No Tabs Include this option if you do not want to replace tabs with spaces. The default is No Tabs enabled. Line Explanation File filename Include this option to set the banner filename. Replace filename with the desired banner filename. The default is blank, causing "LPT : Catch" to print as the banner filename. Name Include this option to set the banner username. username Replace username with the desired username. The default is blank; no username will print. Banner Include this option if you want to print the banner. The default is Banner enabled. No Banner Include this option if you do not want to print the banner. The default is Banner enabled. FF or Include this option to print the trailing form feed. Form Feed The default is FF enabled or Form Feed enabled. No Include this option if you do not want to print the Form Feed trailing form feed. The default is FF enabled or Form Feed enabled. MaxSetup Include this option to define the maximum length of number the printer setup string. The default is MaxSetup 256. MaxReset Include this option to change the printer reset string number maximum length. The default is MaxReset 256. Suppose you want to modify the OS/2 NetWare Spooler to print three copies of all jobs on form number 1 using the filename REPORT and the username MAX. Place the following lines in the NET.CFG file: NetWare Spooler Copies 3 Form 1 File REPORT Name MAX The default print job options for all jobs printed from that workstation will then be changed. TRADEMARKS Novell, Inc., has made every effort to supply trademark information about company names, products, and services mentioned in this book. Trademarks indicated below were derived from various sources. 3Com and EtherLink are trademarks of 3Com Corporation. IBM is a registered trademark of International Business Machines Corporation. Internetwork Packet Exchange (IPX) is a trademark of Novell, Inc. Micro Channel is a trademark of International Business Machines Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Requester is a trademark of Novell, Inc. Operating System/2 and OS/2 are trademarks of International Business Machines Corporation. PC-DOS is a trademark of International Business Machines Corporation. Personal Computer AT is a registered trademark of International Business Machines Corporation. Personal Computer XT is a trademark of International Business Machines Corporation. Personal System/2 is a trademark of International Business Machines Corporation. RX-Net is a trademark of Novell, Inc. Standard Microsystems is a trademark of Standard Microsystems Corporation. Token-Ring is a trademark of International Business Machines Corporation.