home *** CD-ROM | disk | FTP | other *** search
-
- ΓòÉΓòÉΓòÉ 1. NetPM ΓòÉΓòÉΓòÉ
-
- NetPM is a full function LAN Server management tool. A wide variety of LAN
- Server capabilities can both be monitored and configured using NetPM.
-
- Users, resources and public applications can be configured with NetPM.
-
- Active User Management
- Alias Management
- Application Management
- Displaying Graphs
- Graphing Statistics
- Group Management
- Print Queue Management
- Requester Management
- Requester Statistics
- Server Management
- Server Statistics
- User Management
-
-
- ΓòÉΓòÉΓòÉ 1.1. Trademarks ΓòÉΓòÉΓòÉ
-
- IBM, OS/2 and LAN Server are trademarks of International Business Machines,
- Inc.
-
-
- ΓòÉΓòÉΓòÉ 1.2. Installation ΓòÉΓòÉΓòÉ
-
- Step 1: Copy the NetPM.EXE file onto the hard disk. If you want to run NetPM
- without referencing the directory, copy the file into a directory in the PATH
- statement.
-
- Step 2: Copy the NetPM.HLP file into a directory in the help path, or the same
- directory as the NetPM.EXE file.
-
- Step 3: Drag a program object from the templates directory to the desktop.
-
- Step 4: Set the program name to NetPM.EXE, with path information if the
- NetPM.EXE was not placed in a directory in the PATH statement.
-
- Step 5: Set the working directory to the location you want the NetPM.INI file
- written.
-
- Step 6: Set the program name to NetPM.
-
-
- ΓòÉΓòÉΓòÉ 1.3. Configuration ΓòÉΓòÉΓòÉ
-
- NetPM requires little configuration.
-
- The default server to be examined may be set from the Configuration option on
- the Config menu. If the server is local, this should be blank. Remember, server
- names begin with a double backslash '\\'.
-
- The sample interval can also be set on the configuration dialog. This is the
- time interval that NetPM will refresh it's information.
-
- The user can select to accept the default positions for the primary dialogs or
- have the program 'remember' where they were last placed by the user.
-
- The user can select the statistics graphing to autostart when the program is
- loaded.
-
-
- ΓòÉΓòÉΓòÉ 1.4. Graph Configuration ΓòÉΓòÉΓòÉ
-
- With the Graph Configuration Dialog three parameters may be set to control the
- performance graphs displayed by NetPM.
-
- The data to be displayed in the graph may be selected.
-
- The time interval for the graph may be selected.
-
- The number of intervals to be displayed. NetPM will display up to 60 intervals,
- if the display resolution permits.
-
-
- ΓòÉΓòÉΓòÉ 1.5. Registration ΓòÉΓòÉΓòÉ
-
- A version of NetPM without the data graphing features is distributed as
- shareware. Purchasers of the Commercial Version of NetPM receive the shareware
- version in the \SHAREWARE directory of the distribution diskette. The Shareware
- Version of NetPM may be freely distributed.
-
- To register the shareware version of NetPM send $249.00 to:
-
- Carl R. Neal
- Creative Assistance Software
- 9431 Kings Falls Dr.
- Charlotte, N.C. 28210 USA
-
- Shipping and Handling
- $10.00 U.S. and Canada
- $20.00 Worldwide
-
- Payment must be in U.S. funds. North Carolina residents must include the
- applicable sales tax. Make checks payable to Carl R. Neal.
-
- In addition to receiving a commercial copy of NetPM, registered users will
- receive notice of future NetPM versions and notice of problem reports.
-
- Remember to include address, contact name and telephone number. New version
- notices and problem reports will be sent to this address.
-
-
- ΓòÉΓòÉΓòÉ 1.6. Server Parameter Modification ΓòÉΓòÉΓòÉ
-
- Most of the parameters that can be changed while LAN Server is running will be
- reset to the values in IBMLAN.INI when the server or requester service is
- stopped and started.
-
- NetPM will offer to edit the IBMLAN.INI file when one of these parameters is
- changed. This is done both on a local server and a remote server.
-
- The first time NetPM modifies a IBMLAN.INI file it will create a IBMLAN.NPM
- file as a backup in the same directory as the IBMLAN.INI file being modified.
- As long as this file exists it will not be modified by NetPM. The server
- parameters present when NetPM created the file can be restored by copying
- IBMLAN.NPM to IBMLAN.INI.
-
- If the network administrator is satisfied with the modified parameters, the
- IBMLAN.NPM file can be deleted and any future modification of the server
- parameters will create a new IBMLAN.NPM file.
-
- Every effort is made to preserve the integrity of the IBMLAN.INI file. The file
- is copied to IBMLAN.TMP in the working directory, edited, and then written back
- to the IBMLAN.INI file. There is a warning to verify the IBMLAN.INI file that
- will appear if there is a failure writing back to the IBMLAN.INI file. If this
- warning appears the IBMLAN.INI file should be verified before proceeding.
-
-
- ΓòÉΓòÉΓòÉ 1.7. Problem Reports ΓòÉΓòÉΓòÉ
-
- No software is completely bug free. The wide variety of LAN configurations
- makes complete testing an impossibility. All recipients of the commercial
- version of NetPM will receive notice of any confirmed problems. The notice
- period and method will vary with the severity of reported problems.
-
- In reporting a problem, please be as detailed as possible.
-
- What dialog were you using?
- What action was attempted?
- What resulted?
- If you received a problem message, what did it say?
- What is your network configuration?
- Were you on the server?
- Were you working with a domain or additional server?
- Can you repeat the problem?
- Is there anyone who can be contacted to discuss this?
- What do you consider the problem severity?
-
-
- ΓòÉΓòÉΓòÉ 1.8. Support ΓòÉΓòÉΓòÉ
-
- The primary method of support for the Commercial version of NetPM is telephone
- support at (704) 544-0001. Voice support is available for the commercial
- version only. You must have you registration number from the distribution
- diskette to obtain voice support.
-
- The primary avenue for support of the shareware version is Creative Assistance
- Software's BBS, The Programmer's Assistant BBS (704) 544-2515. Support can also
- be found through FidoNet NetMail at 1:379/4.
-
- Support through the Compuserve Information Service can be obtained by mail to
- 70741,3451. Due to the cost of Compuserve this mail is NOT checked regularly.
-
- Only limited support will be provided to non-registered users. Registered users
- have preference in support and suggestions for future version enhancements.
-
- Support for NetPM is free. Creative Assistance Software provides LAN consulting
- services for an hourly fee.
-
-
- ΓòÉΓòÉΓòÉ 1.9. License ΓòÉΓòÉΓòÉ
-
- The NetPM program is distributed as Shareware with a 30 day trial license. Use
- of the program after 30 days without payment is in violation of the license
- agreement and copyright.
-
- The shareware version of NetPM may be freely distributed.
-
- Shareware is not freeware or public domain software. For shareware products to
- be continually upgraded and improved, there must be an interest shown through
- registrations. Please support the growth of OS/2 by registering the shareware
- you use.
-
- With the use of the program, the user holds Carl R. Neal free of all
- responsibility for loss of information or damage resulting from the use of the
- program.
-
- This Program is copyright Carl R. Neal 1993. All Rights Reserved.
-
-
- ΓòÉΓòÉΓòÉ 1.10. Warranty ΓòÉΓòÉΓòÉ
-
- This product is furnished without warranty. The only claim is that it will
- perform as specified on the author's LAN Server 3.0 Advanced network.
-
- With the use of the program, the user holds Carl R. Neal (dba Creative
- Assistance Software) free of any and all liability for loss of information,
- damage, or time resulting from the use of the program.
-
-
- ΓòÉΓòÉΓòÉ 2. Active User Management ΓòÉΓòÉΓòÉ
-
- A list of all users currently logged onto the domain of the selected server can
- be obtained by selecting Active Users from the Manage menu.
-
- After selecting a user from the Active user list, logon and session information
- is available. Session information is only available if a session is currently
- in progress.
-
- An active session may be terminated from the Session Details dialog and the
- user account deactivated to prevent the session from being re-established. If
- there is no active session the account may be deactivated from the User Detail
- dialog.
-
- The user ID will remain in the Active User list until the user logs off. A
- logoff is performed automatically by an OS/2 shutdown or another user logging
- on from the same machine.
-
- Logon Details
- Session Details
-
-
- ΓòÉΓòÉΓòÉ 2.1. Session Details ΓòÉΓòÉΓòÉ
-
- Session information for a user currently logged onto the domain of the selected
- server can be obtained by selecting Active Users from the Manage menu and then
- selecting the Session push button.
-
- Session information will be unavailable if there is no session established by
- the user.
-
- Logon information and options are:
-
- Active Time
- Connections
- Inactive Time
- Kill
- Requester
- Requester Type
- User ID
-
-
- ΓòÉΓòÉΓòÉ 2.1.1. Active Time ΓòÉΓòÉΓòÉ
-
- The time since the session was established. In HHH:MM format.
-
-
- ΓòÉΓòÉΓòÉ 2.1.2. Connections ΓòÉΓòÉΓòÉ
-
- The number of connections made across the LAN. The session may include several
- connections to different resources on the same server and connections to
- different servers in the domain.
-
-
- ΓòÉΓòÉΓòÉ 2.1.3. Inactive Time ΓòÉΓòÉΓòÉ
-
- The time without a connection in the session. This time is used for automatic
- termination of the session.
-
-
- ΓòÉΓòÉΓòÉ 2.1.4. Kill ΓòÉΓòÉΓòÉ
-
- A current session can be terminated by the Administrator by selecting Active
- Users from the Manage menu, selecting a user from the list, selecting Session
- information, and selecting the Kill push button.
-
- WARNING: Terminating a session without notice may cause data loss.
-
- To prevent the user from reestablishing the session, the user account must be
- deactivated. This can be done from the Kill Confirmation dialog or from the
- User Detail dialog.
-
-
- ΓòÉΓòÉΓòÉ 2.1.5. Requester ΓòÉΓòÉΓòÉ
-
- The requester name of the computer where the user logged on. The requester name
- is the same as the computer name.
-
-
- ΓòÉΓòÉΓòÉ 2.1.6. Requester Type ΓòÉΓòÉΓòÉ
-
- The type of Requester logged onto the network. This may include 'Downlevel' for
- LAN Server 1.0 requesters.
-
-
- ΓòÉΓòÉΓòÉ 2.1.7. User ID ΓòÉΓòÉΓòÉ
-
- The user ID logged onto the domain.
-
-
- ΓòÉΓòÉΓòÉ 2.2. Logon Details ΓòÉΓòÉΓòÉ
-
- Logon information for a user currently logged onto the domain of the selected
- server can be obtained by selecting Active Users from the Manage menu and then
- selecting the Logon push button.
-
- Comment
- Computer
- Full Name
- Logon Time
- User ID
-
-
- ΓòÉΓòÉΓòÉ 2.2.1. Comment ΓòÉΓòÉΓòÉ
-
- The user's comment. This is the user comment that may be set by the user with
- User Profile Management.
-
-
- ΓòÉΓòÉΓòÉ 2.2.2. Computer ΓòÉΓòÉΓòÉ
-
- The name of the computer being used. The computer name and the requester name
- are the same.
-
-
- ΓòÉΓòÉΓòÉ 2.2.3. Full Name ΓòÉΓòÉΓòÉ
-
- The full name from the user's record. This field may be blank.
-
-
- ΓòÉΓòÉΓòÉ 2.2.4. Logon Time ΓòÉΓòÉΓòÉ
-
- The time the user logged onto the network.
-
-
- ΓòÉΓòÉΓòÉ 2.2.5. User ID ΓòÉΓòÉΓòÉ
-
- The user's network ID.
-
-
- ΓòÉΓòÉΓòÉ 3. Alias Management ΓòÉΓòÉΓòÉ
-
- Aliases are a machine independent method of identifying resources on the
- network. This allows the network coordinator to change the LAN hardware at one
- location and not need to change the configuration on every desktop.
- Applications referencing network resources with aliases do not need to be
- reconfigured as well.
-
- NetPM allows the network administrator to manage the alias configurations with
- a selection list of all aliases within the domain.
-
- From this list the network administrator may:
-
- Adding An Alias
- Deleting An Alias
- View/Modify An Alias
-
-
- ΓòÉΓòÉΓòÉ 3.1. Adding An Alias ΓòÉΓòÉΓòÉ
-
- The 'Create' push button on the Alias Management List brings up a dialog asking
- for the type of alias (File, Printer, or Serial), the unique netname for the
- Alias and either the path (for file aliases) or the queue name (for printer and
- serial aliases.
-
- NetPM provides a list of all available print queues or serial queues, depending
- upon the alias type selection. For a file alias a custom file dialog showing
- the file system on the targeted server is provided.
-
- After the minimum information is set, NetPM will create the alias, begin
- sharing the alias and provide the network administrator with the View/Modify
- dialog to complete the configuration.
-
-
- ΓòÉΓòÉΓòÉ 3.2. Deleting An Alias. ΓòÉΓòÉΓòÉ
-
- NetPM provides an effortless method of deleting Aliases that are no longer
- needed on the network.
-
- From the Alias Management List, simply selecting an alias from the list and
- selecting the 'Delete' push button will delete the alias. A confirmation dialog
- prevents accidental deletions.
-
-
- ΓòÉΓòÉΓòÉ 3.3. Viewing An Alias ΓòÉΓòÉΓòÉ
-
- An alias may be viewed and modified by selecting the 'View' push button from
- the Alias Management List.
-
- The View/Modify dialog contains information on these items:
-
- ACL List
- Alias
- Auditing
- Location
- Max Users
- Mode
- Net Name
- Path/Queue
- Pool
- Priority
- Remark
- Server
- Type
-
-
- ΓòÉΓòÉΓòÉ 3.4. ACL List ΓòÉΓòÉΓòÉ
-
- The Access Control List is the basis of IBM LAN Server security. These
- privileges control users access to network resources.
-
- Note: Only 64 ACL entries are available for each resource. It is highly
- recommended for the network administrator use groups to control access
- to resources which may have more than 64 users.
-
- By using groups to control user access, a user may have privileges to many
- resources changed by modifying the group memberships.
-
- For file resources LAN Server will check the directories higher in the path for
- access permissions if the user is not listed in the targeted directory.
-
- NetPM provides a ACL Dialog to modify the access permissions to an alias. This
- dialog is accessed by the 'ACL List' push button on the Alias View dialog.
-
- A list of all users and a list of all groups in the domain is provided, showing
- any existing access privilege. From the ACL Dialog the 'Edit' push button may
- be used to modify the access privileges of a user or group. These changes are
- not written to the LAN Server system until the 'Set' push button is used.
-
- The privileges are:
-
- 'R' - Read. Files or data may be read from the alias.
-
- 'W' - Write. Files or data may be written to the alias. This privilege may not
- be sufficient to write files as it does not permit attribute changes by itself.
-
- 'C' - Create. Files (including spool files) may be created.
-
- 'X' - Execute. Programs may be executed. If the program needs to write to
- itself or .INI files, program execution may require additional flags. If
- temporary files are written and deleted by the program additional flags may be
- required.
-
- 'D' - Delete. Files may be deleted.
-
- 'A' - Attributes. File attributes may be changed.
-
- 'P' - Permissions. Access privileges may be changed.
-
-
- ΓòÉΓòÉΓòÉ 3.5. Alias ΓòÉΓòÉΓòÉ
-
- The Alias name. A unique Netname is required.
-
-
- ΓòÉΓòÉΓòÉ 3.6. Auditing ΓòÉΓòÉΓòÉ
-
- IBM LAN Server provides a complete auditing system to allow the network
- administrator to track usage and errors. NetPM allows the auditing for an alias
- to be controlled from an Audit Dialog accessed from the Alias View Dialog.
-
- Note: If the Auditing service is not enabled in the LAN Server configuration,
- there will be no effect from enabling auditing on an individual
- resource.
-
- The Audit dialog allows the network administrator to specify the following
- audit conditions:
-
- 'Audit All' - Audit all accesses and all failures.
-
- 'Audit None'
-
- 'ACL Changes' - Audit any changes to alias privileges.
-
- 'Failed ACL Changes' - Audit any unsuccessful changes to alias privileges.
-
- 'Opens' - Audit any file or device openings.
-
- 'Failed Opens' - Audit any failed file or device openings.
-
- 'Writes' - Audit any writes to files or devices.
-
- 'Failed Writes' - Audit any failed writes to files or devices.
-
- 'Deletes' - Audit any file deletions.
-
- 'Failed Deletes' - Audit any failed deletions.
-
-
- ΓòÉΓòÉΓòÉ 3.7. Alias Location ΓòÉΓòÉΓòÉ
-
- The location of the alias. The alias may be internal to the domain, an external
- OS/2 alias, an external DOS alias, or a external alias to be accessed by both
- OS/2 and DOS requesters.
-
-
- ΓòÉΓòÉΓòÉ 3.8. Alias Max Users ΓòÉΓòÉΓòÉ
-
- The maximum number of users to access the alias at the same time. This may be
- used to set the accesses to the number of licenses for a program or to limit
- network usage with high traffic applications.
-
- If this number is zero, no users will be able to access the alias.
-
-
- ΓòÉΓòÉΓòÉ 3.9. Alias Mode ΓòÉΓòÉΓòÉ
-
- The time the alias should be shared. This may be 'At Start Up', 'By Admin
- Action', or 'When Requested' (file aliases only).
-
-
- ΓòÉΓòÉΓòÉ 3.10. Alias Net Name ΓòÉΓòÉΓòÉ
-
- The unique Netname of the alias. For file aliases this is the alias name. For
- serial and printer aliases this is the queue name.
-
-
- ΓòÉΓòÉΓòÉ 3.11. Alias Path/Queue ΓòÉΓòÉΓòÉ
-
- For files aliases this is the server path to the root drive of the alias. For
- print and serial aliases, this is the name of the queue on the server that is
- used by the alias.
-
-
- ΓòÉΓòÉΓòÉ 3.12. Alias Pool ΓòÉΓòÉΓòÉ
-
- For serial aliases only. This is the list of devices accessed by the queue.
-
-
- ΓòÉΓòÉΓòÉ 3.13. Alias Priority ΓòÉΓòÉΓòÉ
-
- For serial aliases only. This is the priority of the alias.
-
-
- ΓòÉΓòÉΓòÉ 3.14. Alias Remark ΓòÉΓòÉΓòÉ
-
- The alias remark is a 40 maximum character string used to identify the alias in
- a user's public application folder.
-
-
- ΓòÉΓòÉΓòÉ 3.15. Alias Server ΓòÉΓòÉΓòÉ
-
- The server where the alias resides.
-
-
- ΓòÉΓòÉΓòÉ 3.16. Alias Type ΓòÉΓòÉΓòÉ
-
- The type of alias, printer, file, or serial.
-
-
- ΓòÉΓòÉΓòÉ 4. Application Management ΓòÉΓòÉΓòÉ
-
- NetPM application management begins with a list of all applications configured
- as network resources. From this list the network administrator can view,
- modify, and delete application configurations. The application may be placed in
- user's program starters.
-
- Adding An Application
- Deleting An Application
- View/Modify Applications
-
- Applications can be configured in several different methods using IBM LAN
- Server and OS/2. The complexity of the configuration required for an given
- application depends upon the application.
-
- The full Program Starter method available with LAN Server 3.0 allows the
- Network Administrator full control over who uses an application and how many
- users access an application at the same time. This method makes locating and
- running a network application transparent to the OS/2 and DOS user.
-
- Before configuring an network application for the first time, the network
- administrator should realize that all resources (network file directories,
- network printers, and network serial devices) are referenced through aliases
- and must be configured first.
-
-
- ΓòÉΓòÉΓòÉ 4.1. Adding An Application ΓòÉΓòÉΓòÉ
-
- Network applications may be added to the targeted server by selecting 'Add'
- from the Application Management list.
-
- The network administrator will be asked for the application resource name,
- which must be a unique netname, and the type of application.
-
- From this point the administrator will be provided with the Application Details
- Dialog and any additional information required may be entered.
-
- Note: The default Max Users for an application configuration created with
- NetPM is 0. For the application configuration to be useful, the number
- of users must be set to a higher number.
-
-
- ΓòÉΓòÉΓòÉ 4.2. Deleting An Application ΓòÉΓòÉΓòÉ
-
- Network applications may be deleted from the targeted server by selecting
- 'Delete' from the Application Management list.
-
- A confirmation dialog will appear to confirm the action.
-
-
- ΓòÉΓòÉΓòÉ 4.3. View/Modify Applications ΓòÉΓòÉΓòÉ
-
- Network application configurations may be viewd or modified by selecting 'View'
- from the Application Management list.
-
- From the Application Details dialog the network administrator may change many
- of the application parameters by selecting the push button beside the
- parameter.
-
- The displayed Parameters are:
-
- Application Directory
- Ask For Command Line
- Command
- Command Line
- Interface
- Name
- Program Starters
- Resources
- Remark
- Type
- Working Directory
-
-
- ΓòÉΓòÉΓòÉ 4.4. Application Directory ΓòÉΓòÉΓòÉ
-
- The files alias to be used to run the application, the drive for the
- application to use on the local workstation and the path to the application
- from the alias root.
-
- If a working directory is specified, no drive is needed.
-
-
- ΓòÉΓòÉΓòÉ 4.5. Ask For Command Line ΓòÉΓòÉΓòÉ
-
- This push button toggles the requirement for the network to ask the user for a
- command line to use with the program name.
-
-
- ΓòÉΓòÉΓòÉ 4.6. Command ΓòÉΓòÉΓòÉ
-
- The program name. The name should include the extension. ex: NetPM.EXE.
-
-
- ΓòÉΓòÉΓòÉ 4.7. Command Line ΓòÉΓòÉΓòÉ
-
- The command line to be used with the program.
-
-
- ΓòÉΓòÉΓòÉ 4.8. Interface ΓòÉΓòÉΓòÉ
-
- The type of interface for OS/2 applications. This push button toggles through
- the list of PM, Vio, and Protected.
-
- PM is for Presentation Manager programs. VIO is for programs that can be
- displayed in an OS/2 window and Protected is for full screen applications.
-
-
- ΓòÉΓòÉΓòÉ 4.9. Name ΓòÉΓòÉΓòÉ
-
- The Application Resource Name. This is the name listed in the DCDB (Domain
- Controller Data Base) for the application and referenced in program starters.
-
-
- ΓòÉΓòÉΓòÉ 4.10. Program Starters ΓòÉΓòÉΓòÉ
-
- The 'Program Starters' push button accesses a list of all user's in the domain
- and the application can be placed in the user's Public Application Folder with
- the 'ADD' push button and removed with the 'Delete' push button.
-
-
- ΓòÉΓòÉΓòÉ 4.11. Resources ΓòÉΓòÉΓòÉ
-
- An application may have access to network resources independent of the users
- configuration. These resources may be file directories, printers, and serial
- devices.
-
- The 'Resource' push button provides a list of all resources configured for the
- application. From this list resources may be added, deleted and modified.
-
- Adding A Resource
- Modifying A Resource
- Deleting A Resource
-
-
- ΓòÉΓòÉΓòÉ 4.11.1. Adding A Resource ΓòÉΓòÉΓòÉ
-
- The 'Add' push button on the Resource List accesses a Resource Definition
- Dialog.
-
- The selection dialog displays the aliases of the type selected. (Files,
- Printers, or serial devices. The alias can be assigned to a directory, a
- printer (LPTx) port or a serial (COMx) port. This assignment is where the alias
- device appears to the application.
-
- Note: While IBM LAN Server supports up to nine serial devices and printer
- ports, some applications may not be configurable to all of these ports.
-
-
- ΓòÉΓòÉΓòÉ 4.11.2. Modifying A Resource ΓòÉΓòÉΓòÉ
-
- The 'Modify' push button access the same Resource Definition Dialog as the
- 'Add' push button, but the resource definition being configured is displayed.
-
-
- ΓòÉΓòÉΓòÉ 4.11.3. Deleting A Resource ΓòÉΓòÉΓòÉ
-
- The 'Delete' push button deletes a resource definition from the application
- after a confirmation dialog provides permission.
-
-
- ΓòÉΓòÉΓòÉ 4.12. Remark ΓòÉΓòÉΓòÉ
-
- The application remark is the icon label text that will appear in the Public
- Applications folder on the user's desktop.
-
-
- ΓòÉΓòÉΓòÉ 4.13. Type ΓòÉΓòÉΓòÉ
-
- The type of network program. Possible values are: OS/2 Public, OS/2 Private,
- and DOS Public.
-
-
- ΓòÉΓòÉΓòÉ 4.14. Working Directory ΓòÉΓòÉΓòÉ
-
- The working directory for the application. The separate configuration for a
- working directory and application directory allows work files to be kept on a
- local drive or a separate network drive from the application.
-
-
- ΓòÉΓòÉΓòÉ 5. Displaying Graphs ΓòÉΓòÉΓòÉ
-
- Graphs captured by NetPM may be displayed at a later time to compare network
- performance before and after modifications.
-
- NetPM uses about 600 bytes to store a graph, and thousands of graphs may be
- stored in a single file.
-
- The option from the Captured Graph Display Window are:
-
- Contents
- Next
- Open
- Previous
- Print
-
-
- ΓòÉΓòÉΓòÉ 5.1. Contents ΓòÉΓòÉΓòÉ
-
- Under the 'File' option on the main menu the 'Contents' selection shows the
- contents of the loaded file.
-
- The machine name, type of graph and the time the capture occurred are
- displayed. From the list a graph may be selected.
-
-
- ΓòÉΓòÉΓòÉ 5.2. Next ΓòÉΓòÉΓòÉ
-
- The 'Next' and 'Previous' commands may be used to step through the graphs in a
- file one at a time.
-
-
- ΓòÉΓòÉΓòÉ 5.3. Open ΓòÉΓòÉΓòÉ
-
- A new graph file may be opened.
-
-
- ΓòÉΓòÉΓòÉ 5.4. Previous ΓòÉΓòÉΓòÉ
-
- The 'Next' and 'Previous' commands may be used to step through the graphs in a
- file one at a time.
-
-
- ΓòÉΓòÉΓòÉ 5.5. Print ΓòÉΓòÉΓòÉ
-
- Graphs, both captured and current, may be printed to any printer available to
- the local workstation.
-
- For the best print results use the standard OS/2 Job Properties Dialog to
- select landscape mode if this mode is available on the printer.
-
- NetPM will print in color if supported by the printer.
-
-
- ΓòÉΓòÉΓòÉ 6. Graphing Statistics ΓòÉΓòÉΓòÉ
-
- The Shareware version of NetPM does not offer fully functional network
- performance graphing.
-
- For an explanation of the graph labeling see: Graph Labels.
-
- To allow the user to evaluate the program's capabilities the default graph,
- Server Byte Traffic is enabled with a five minute time period. NetPM will
- automatically scale the bytes sent and received.
-
- In the commercial version, NetPM will allow the network administrator to set a
- time period from one minute to one hour for collecting statistics and display
- up 30 time periods.
-
- In the Commercial version graphs are available for:
-
- Local Requestor Byte Traffic
- Local Requestor NCB Traffic
- Server Byte Traffic
- Server File Opens
- Server Print Jobs
- Server Response Time
- Server Req Byte Traffic
- Server Req NCB Traffic
- Server Session Starts
-
- In the commercial version graph data may be captured to disk and redisplayed at
- a later time, as well as printed.
-
-
- ΓòÉΓòÉΓòÉ 6.1. Graph Labeling ΓòÉΓòÉΓòÉ
-
- The type of data being displayed is shown in the bottom left of the program
- window.
-
- The scale used in the display is shown in the middle of the bottom line of the
- graph. This value shows the amount indicated by each of the 10 divisions of the
- graph.
-
- The time period is show on the bottom right of the program window.
-
- The color code for graphs with more than one display item is shown above the
- graph in the program window.
-
- If a recorded graph is being displayed, the capture time is displayed in the
- upper right of the program window.
-
-
- ΓòÉΓòÉΓòÉ 6.2. Local Req Byte Traffic Graph ΓòÉΓòÉΓòÉ
-
- A graph of the total number of bytes sent and bytes received by the requester
- on the workstation local to NetPM during the time period set in the Graph
- Configuration Dialog. These numbers include bytes sent by applications, the
- server service and the requester itself.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.3. Local Req NCB Traffic Graph ΓòÉΓòÉΓòÉ
-
- A graph of the NCB's sent and received by the requester on the workstation
- local to NetPM during the time period set in the Graph Configuration Dialog.
- These numbers include NCB's that were not issued or failed to complete.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.4. Server Byte Traffic Graph ΓòÉΓòÉΓòÉ
-
- A graph of the total number of bytes sent and bytes received by the Server
- service during the time period set in the Graph Configuration Dialog.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.5. Server File Opens Graph ΓòÉΓòÉΓòÉ
-
- A graph of the file opens on the targeted server during the time period set in
- the Graph Configuration Dialog.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.6. Server Print Job Graph ΓòÉΓòÉΓòÉ
-
- A graph of the print jobs sent to the targeted server during the time period
- set in the Graph Configuration Dialog.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.7. Server Response Time Job Graph ΓòÉΓòÉΓòÉ
-
- A graph of the response time of the targeted server during the time period set
- in the Graph Configuration Dialog.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.8. Server Req Byte Traffic Graph ΓòÉΓòÉΓòÉ
-
- A graph of the total number of bytes sent and bytes received by the requester
- on the targeted server during the time period set in the Graph Configuration
- Dialog. These numbers include bytes sent by applications, the server service
- and the requester itself.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.9. Server Req NCB Traffic Graph ΓòÉΓòÉΓòÉ
-
- A graph of the NCB's sent and received by the requester on the targeted server
- during the time period set in the Graph Configuration Dialog. These numbers
- include NCB's that were not issued or failed to complete.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 6.10. Server Session Starts Graph ΓòÉΓòÉΓòÉ
-
- A graph of the sessions started on the targeted server during the time period
- set in the Graph Configuration Dialog.
-
- The scale is automatically set by the maximum value.
-
-
- ΓòÉΓòÉΓòÉ 7. Group Management ΓòÉΓòÉΓòÉ
-
- The network administrator may use NetPM to create new groups, delete groups,
- and view existing groups. While viewing a group users may be added and deleted
- from the group.
-
- See:
-
- Group Memberships
- Creating A Group
- Deleting A Group
- Viewing A Group
-
-
- ΓòÉΓòÉΓòÉ 7.1. Group Memberships ΓòÉΓòÉΓòÉ
-
- Group memberships may be managed from the Group Detail dialog accessed with the
- View push button. See Viewing A Group.
-
-
- ΓòÉΓòÉΓòÉ 7.2. Creating A Group ΓòÉΓòÉΓòÉ
-
- A new group in the selected server's domain may be created by selecting Groups
- from the Manage menu, and then selecting the New push button on the Group List
- dialog.
-
- The Network Administrator will then provide a name for the group and an
- optional remark. The name must be a unique netname.
-
- The Group detail dialog will then be available for including users in the
- group.
-
-
- ΓòÉΓòÉΓòÉ 7.3. Deleting A Group ΓòÉΓòÉΓòÉ
-
- An existing group in the selected server's domain may be deleted by selecting
- Groups from the Manage menu, then selecting a Group from the Group List dialog,
- and then selecting the Delete push button.
-
- A confirmation dialog will ask if this is the intended action.
-
-
- ΓòÉΓòÉΓòÉ 7.4. Viewing A Group ΓòÉΓòÉΓòÉ
-
- An existing group in the selected server's domain may be viewed by selecting
- Groups from the Manage menu, then selecting a Group from the Group List dialog,
- and then selecting the View push button.
-
- Users may be added or deleted from the group at this dialog. Two lists are
- provided, one with the members of the group and one with all users in the
- domain who are not members of the group. Multiple users in a list may be
- selected and sent to the other list with the Add or Delete push button. Single
- users may be sent to the other list with a double click of the mouse.
-
- The group remark may be changed at this dialog.
-
-
- ΓòÉΓòÉΓòÉ 8. Print Queue Management ΓòÉΓòÉΓòÉ
-
- NetPM offers management of print queues and print jobs through a Print Queue
- List accessed from the 'Manage' menu.
-
- Print queue actions:
-
- Create Print Queue
- Print Jobs
- View/Modify Print Queue
-
-
- ΓòÉΓòÉΓòÉ 8.1. Create Print Queue ΓòÉΓòÉΓòÉ
-
- To create a print queue on the targeted server select 'Create' on the Print
- Queue List.
-
- The network administrator will then be asked for a name for the print queue.
- After supplying the name NetPM will respond with the View/Modify dialog to set
- the remaining parameters.
-
-
- ΓòÉΓòÉΓòÉ 8.2. Print Jobs ΓòÉΓòÉΓòÉ
-
- Print job management is provided from the Print Queue List. The 'Jobs' push
- button will present a list of all jobs in the selected queue. The list will
- update every 30 seconds.
-
- The list of print jobs provides key information on the job:
-
- Job Queue Position
- Job ID
- User Name
- Job Status
- Job Size
- Job Document Number
-
- The network adminstrator may take any of the following actions:
-
- Details
- Kill
-
-
- ΓòÉΓòÉΓòÉ 8.2.1. Print Job Details ΓòÉΓòÉΓòÉ
-
- A view of the details of a print job can be accessed from the Print Job List,
- with the 'Details' push button.
-
- The Print Job Detail dialog allows the job priority and position to be
- modified, along with the computer to be notified when the job is complete. A
- job may be held, released or killed from the details dialog.
-
- Comment
- Driver
- Document
- Hold/Release
- Job ID
- Kill
- Notify
- Position
- Printer
- Priority
- Queue
- Size
- Status
- Submitted
- Type
- User
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.1. Comment ΓòÉΓòÉΓòÉ
-
- Any comment supplied by the program issuing the print job. For example, a print
- job creaated by aa user dropping a file icon onto the printer icon will have a
- comment of 'System'.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.2. Driver ΓòÉΓòÉΓòÉ
-
- The print driver that will be used.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.3. Document ΓòÉΓòÉΓòÉ
-
- The document name if one was supplied by the program issuing the print job.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.4. Hold/Release ΓòÉΓòÉΓòÉ
-
- The network administrator is able to hold or release a print job. The name of
- the push button will change with the status of the print job.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.5. Job ID ΓòÉΓòÉΓòÉ
-
- The system ID number of the print job. This number may be used for command line
- manipulation of the job.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.6. Kill ΓòÉΓòÉΓòÉ
-
- From the job detailss dialog the network administrator mey kill a print job.
- The job will be deleted from the queue and must be resubmitted to be printed.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.7. Notify ΓòÉΓòÉΓòÉ
-
- The computer name to be notified when the jpob is completed. This may be
- modified by the network administrator.
-
- Note: This is the computer name, not user name.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.8. Position ΓòÉΓòÉΓòÉ
-
- The position of the job in the job queue. This position may be chnaged by the
- network administrator.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.9. Printer ΓòÉΓòÉΓòÉ
-
- The name (type) of the printer being used to print the job.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.10. Priority ΓòÉΓòÉΓòÉ
-
- The job priority. The network administrator may modify this priority,
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.11. Queue ΓòÉΓòÉΓòÉ
-
- The name of the print queue.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.12. Size ΓòÉΓòÉΓòÉ
-
- The size, in bytes, of the print job.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.13. Status ΓòÉΓòÉΓòÉ
-
- The status of the job. Possible vaaluses include printing, queued, and held.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.14. Submitted ΓòÉΓòÉΓòÉ
-
- The date and time the job was submitted to the queue.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.15. Type ΓòÉΓòÉΓòÉ
-
- The type of print job. If the print driver and queue support RAW and direct
- printing, this will be shown on the job details.
-
-
- ΓòÉΓòÉΓòÉ 8.2.1.16. User ΓòÉΓòÉΓòÉ
-
- The user ID of the user submitting the print job.
-
-
- ΓòÉΓòÉΓòÉ 8.2.2. Kill A Print Job ΓòÉΓòÉΓòÉ
-
- A print job may be deleted from the print queue by the 'Kill' push button on
- the Print Job List.
-
-
- ΓòÉΓòÉΓòÉ 8.3. View/Modify Print Queue ΓòÉΓòÉΓòÉ
-
- The details of the print queue configuration may be accessed from the Print
- Queue List with the 'View' push button.
-
- The Print Queue Detail Dialog provides the following information and commands:
-
- Comment
- Delete
- Drivers
- End Time
- Hold/Release
- Name
- Printers
- Priority
- Processor
- Purge
- Separator
- Start
- Status
- Type
-
-
- ΓòÉΓòÉΓòÉ 8.3.1. Comment ΓòÉΓòÉΓòÉ
-
- The print queue comment.
-
-
- ΓòÉΓòÉΓòÉ 8.3.2. Delete ΓòÉΓòÉΓòÉ
-
- Delete the queue from the LAN Server configuration.
-
-
- ΓòÉΓòÉΓòÉ 8.3.3. Drivers ΓòÉΓòÉΓòÉ
-
- The default print driver for the queue.
-
-
- ΓòÉΓòÉΓòÉ 8.3.4. End Time ΓòÉΓòÉΓòÉ
-
- The time of day that the queue will no longer be availaable for print jobs.
-
-
- ΓòÉΓòÉΓòÉ 8.3.5. Hold/Release ΓòÉΓòÉΓòÉ
-
- The network adminitrator may plaace the queue on hold and freeze all print jobs
- in the queue. The push button will change name and function with the status of
- the queue.
-
-
- ΓòÉΓòÉΓòÉ 8.3.6. Name ΓòÉΓòÉΓòÉ
-
- The name of the queue.
-
-
- ΓòÉΓòÉΓòÉ 8.3.7. Printer ΓòÉΓòÉΓòÉ
-
- The printer which is the destination for the queue.
-
-
- ΓòÉΓòÉΓòÉ 8.3.8. Priority ΓòÉΓòÉΓòÉ
-
- The queue priority. A number from 1 to 100.
-
-
- ΓòÉΓòÉΓòÉ 8.3.9. Processor ΓòÉΓòÉΓòÉ
-
- The queue processor. With OS/2 2.1, the default queue processr is PMPRINT.
-
-
- ΓòÉΓòÉΓòÉ 8.3.10. Purge ΓòÉΓòÉΓòÉ
-
- The network administrator may purge the queue, deleting aall print jobss in the
- queue.
-
-
- ΓòÉΓòÉΓòÉ 8.3.11. Separator ΓòÉΓòÉΓòÉ
-
- The seperarator file to be printed between print jobs.
-
-
- ΓòÉΓòÉΓòÉ 8.3.12. Start ΓòÉΓòÉΓòÉ
-
- The time of day the print queue will become available for use.
-
-
- ΓòÉΓòÉΓòÉ 8.3.13. Status ΓòÉΓòÉΓòÉ
-
- The queue status.
-
-
- ΓòÉΓòÉΓòÉ 8.3.14. Type ΓòÉΓòÉΓòÉ
-
- If the queue permits RAW data or direct printing it is indicated and may be
- chanaged if supported.
-
-
- ΓòÉΓòÉΓòÉ 9. Requester Management ΓòÉΓòÉΓòÉ
-
- NetPM allows the network administrator to configure both the requester on the
- selected server and the requester on the local workstation while the requester
- is running.
-
- The administrator will be asked if the IBMLAN.INI file should be edited.
- Without editing the IBMLAN.INI file any change will be lost when the requester
- is stopped. See Server Parameter Modification.
-
- To modify the remote server requester select Servers from the Manage menu, then
- select a server, then view the server. The 'Req' push button in the server
- management dialog accesses the server requester.
-
- To modify the configuration of the local requester, select Workstation from the
- Manage menu.
-
- Only the parameters which can be modified while the requester is running may be
- set with NetPM. Manually edit the IBMLAN.INI file and stop and restart the
- requester to modify other parameters. Administrators can access the file from
- remote workstations by using the UNC file name. (Example: EPM
- \\SERVER\C$\IBMLAN\IBMLAN.INI.) The file location can be found in the Root
- field of the requester configuration. Note that the colon in the drive
- specification is replaced with a dollar sign.
-
- Parameters in the Workstation Management Dialog are:
-
- Alert Clients
- Buffers - Cache Size
- Buffers - Char Dev Size
- Buffers - Character Dev
- Buffers - Datagram
- Buffers - Error Size
- Buffers - Number
- Buffers - Size
- Char Count
- Char Time
- Char Wait
- Current Domain
- Errorlog Size
- Logon Server
- Mailslots
- Max Commands
- Max Threads
- Netname Time
- Print Time
- Requester Domain
- Requester Name
- Requester Root
- Requester User
- Requester Version
- Search Time
- Services
- Session Time
- WorkHeuristics
-
-
- ΓòÉΓòÉΓòÉ 9.1. Alert Clients ΓòÉΓòÉΓòÉ
-
- The maximum number of clients that can receive alert messages from the
- workstation.
-
-
- ΓòÉΓòÉΓòÉ 9.2. Buffers - Cache Size ΓòÉΓòÉΓòÉ
-
- The maximum size (in bytes) of an internal requester cache buffer.
-
-
- ΓòÉΓòÉΓòÉ 9.3. Buffers - Char Dev Size ΓòÉΓòÉΓòÉ
-
- The number of character pipe buffers and device buffers the requester can have.
-
-
- ΓòÉΓòÉΓòÉ 9.4. Buffers - Character Dev ΓòÉΓòÉΓòÉ
-
- The maximum size (in bytes) of a character pipe buffer and device buffer.
-
-
- ΓòÉΓòÉΓòÉ 9.5. Buffers - Datagram ΓòÉΓòÉΓòÉ
-
- The number of buffers allocated for receiving datagrams.
-
-
- ΓòÉΓòÉΓòÉ 9.6. Buffers - Error Size ΓòÉΓòÉΓòÉ
-
- The size (in bytes) of an internal requester error buffer.
-
-
- ΓòÉΓòÉΓòÉ 9.7. Buffers - Number ΓòÉΓòÉΓòÉ
-
- The number of internal buffers the requester has.
-
-
- ΓòÉΓòÉΓòÉ 9.8. Buffers - Size ΓòÉΓòÉΓòÉ
-
- The size (in bytes) of each internal buffer being used by the requester.
-
-
- ΓòÉΓòÉΓòÉ 9.9. Char Count ΓòÉΓòÉΓòÉ
-
- The number of bytes of information the requester will attempt to group together
- to send to a remote serial device resource.
-
-
- ΓòÉΓòÉΓòÉ 9.10. Char Time ΓòÉΓòÉΓòÉ
-
- The number of milliseconds the requester will wait to collect data to send to a
- remote serial device resource.
-
-
- ΓòÉΓòÉΓòÉ 9.11. Char Wait ΓòÉΓòÉΓòÉ
-
- The number of seconds the requester will wait for a remote serial device
- resource to become available.
-
-
- ΓòÉΓòÉΓòÉ 9.12. Current Domain ΓòÉΓòÉΓòÉ
-
- The domain to which the user is logged on. It is blank when no one is logged
- on.
-
-
- ΓòÉΓòÉΓòÉ 9.13. Errorlog Size ΓòÉΓòÉΓòÉ
-
- The maximum size (in kilobytes) of the error log file of a requester.
-
-
- ΓòÉΓòÉΓòÉ 9.14. Logon Server ΓòÉΓòÉΓòÉ
-
- The name of the preferred server, which validates user logon requests for this
- user.
-
- The server name should be preceded by a double backslash (\\) and should be the
- name of a domain controller or backup server.
-
- A server name of an asterisk (*) indicates that the logon request can be
- handled by any domain controller or backup server on the domain.
-
- A blank field indicates that the domain controller is the preferred logon
- server.
-
-
- ΓòÉΓòÉΓòÉ 9.15. Mailslots ΓòÉΓòÉΓòÉ
-
- The maximum number of mailslots allowed.
-
-
- ΓòÉΓòÉΓòÉ 9.16. Max Commands ΓòÉΓòÉΓòÉ
-
- The number of simultaneous network device driver commands that can be sent to
- the network.
-
-
- ΓòÉΓòÉΓòÉ 9.17. Max Threads ΓòÉΓòÉΓòÉ
-
- The number of threads the requester can dedicate to the network.
-
-
- ΓòÉΓòÉΓòÉ 9.18. Netname Time ΓòÉΓòÉΓòÉ
-
- The number of seconds an inactive, implicit UNC connection from the requester
- to the resource server will be maintained.
-
-
- ΓòÉΓòÉΓòÉ 9.19. Print Time ΓòÉΓòÉΓòÉ
-
- The number of seconds that are waited before closing inactive
- compatibility-mode print jobs.
-
-
- ΓòÉΓòÉΓòÉ 9.20. Requester Domain ΓòÉΓòÉΓòÉ
-
- The name of the domain to which the requester belongs. This is the domain the
- requester will access when it is started.
-
-
- ΓòÉΓòÉΓòÉ 9.21. Requester Name ΓòÉΓòÉΓòÉ
-
- The requester name of the computer being configured. This is also know as the
- computer name.
-
-
- ΓòÉΓòÉΓòÉ 9.22. Requester Root ΓòÉΓòÉΓòÉ
-
- The path to the IBMLAN directory (the recommended default path is d:\IBMLAN) of
- a computer. The IBMLAN.INI file is found in this directory and is the basis for
- the path to directories used by LAN Server.
-
-
- ΓòÉΓòÉΓòÉ 9.23. Requester User ΓòÉΓòÉΓòÉ
-
- The User's name logged on to the requester. This filed will be blank if no user
- is logged onto the network on the computer.
-
-
- ΓòÉΓòÉΓòÉ 9.24. Requester Version ΓòÉΓòÉΓòÉ
-
- The version number of the OS/2 LAN Server software running on the computer.
-
-
- ΓòÉΓòÉΓòÉ 9.25. Search Time ΓòÉΓòÉΓòÉ
-
- The number of seconds an inactive search will continue.
-
-
- ΓòÉΓòÉΓòÉ 9.26. Services ΓòÉΓòÉΓòÉ
-
- The number of services that can be started on the requester at any time.
-
-
- ΓòÉΓòÉΓòÉ 9.27. Session Time ΓòÉΓòÉΓòÉ
-
- The number of seconds that are waited before disconnecting an inactive session
- between a requester and a server.
-
-
- ΓòÉΓòÉΓòÉ 9.28. WorkHeuristics ΓòÉΓòÉΓòÉ
-
- Heuristic adj. 1. Aiding or guiding in discovery. 2. Designating an educational
- method by which a pupil is stimulated to make his own investigations and
- discoveries. <Gk. heuriskein. to find out>
-
- Flags used to control a requester operation. The heuristics default to values
- that are optimal for most configurations and normally need not be changed.
-
- This parameter sets a variety of requester fine-tuning options. Each digit of
- the WorkHeuristics parameter has an independent meaning. When digits are
- missing from the right-hand side of the parameter value, the system supplies
- the default specified for each missing digit.
-
- The individual positions of the WorkHeuristics are:
-
- Opportunistic File Locking
- .CMD File Optimization
- Asynchronous Locking
- Asynchronous Closing
- Buffer Pipes And Serial
- Combine R/W Locking
- Read On Opens
- Reserved
- Chain Send NCB's
- Buffer Small Read and Write
- Buffer Mode
- RAW Read and Write SMB's
- Large RAW Read Ahead
- Large RAW Write Behind
- Read Multiplexing SMB's
- Write Multiplexing SMB's
- Big Buffers For Core Reads
- Small Record Read Ahead
- Small Record Write Behind
- Reserved
- Flush Pipes And Devices
- LS30 Password Encryption
- Multiple Error Logging
- Buffer Deny Write Opens
- Buffer Read Only Files
- Read Ahead On .EXE's
- Control-C Handling
- DOS Server Opens
- NetBIOS No Ack Mode
- Write Block RAW Method
- Requester Error Msg's
- Reserved
- DosBuffer Reset Behavior
- Logon Time Interval
-
-
- ΓòÉΓòÉΓòÉ 9.28.1. Opportunistic File Locking ΓòÉΓòÉΓòÉ
-
- Character position 0. (0 Based)
-
- Requests opportunistic locking of files. The default is 1.
-
- When digit position 0 is active(1), it allows a file opened in deny-none
- sharing mode to be locked by the server. Buffering can then be used to enhance
- performance. However, the server cannot lock the file if there are outstanding
- access requests. The server assumes that the first requester is the only active
- process using that file and prevents a second requester from accessing the file
- until buffered data is flushed (written to disk) and the file is closed.
-
-
- ΓòÉΓòÉΓòÉ 9.28.2. .CMD File Optimization ΓòÉΓòÉΓòÉ
-
- Character position 1. (0 Based)
-
- Specifies performance optimization for batch (.CMD) files. Digit position 0
- (opportunistic locking) must be set to 1. The default is 1.
-
- When digit position 1 is active(1), a batch file on the server running on the
- requester is kept in the requester's buffer to prevent a request across the LAN
- for each line of the batch file.
-
- When digit position 1 is inactive, the batch file is opened and closed with
- each line processed. The buffer data is flushed when the batch file is closed.
-
-
- ΓòÉΓòÉΓòÉ 9.28.3. Asynchronous Locking ΓòÉΓòÉΓòÉ
-
- Character position 2. (0 Based)
-
- Specifies asynchronous unlock and asynchronous write-unlock.
-
- Values are:
-
- Value Meaning
- 0 Never
- 1 Always
- 2 Only on a LAN Server 3.0 virtual circuit.
-
- The default is 1.
-
- A virtual circuit is a NETBIOS session connection to another workstation over a
- LAN. With digit position 2, files in the requester buffer are unlocked in the
- buffer and processing continues without waiting for confirmation from the
- server.
-
- Any errors occurring at the server are reported later. Generally, the only
- errors that might occur are hard media errors, such as a full disk or loss of
- power to the server.
-
- Values 1 and 2 are functionally equivalent in a LAN Server 3.0 environment.
-
-
- ΓòÉΓòÉΓòÉ 9.28.4. Asynchronous Closing ΓòÉΓòÉΓòÉ
-
- Character position 3. (0 Based)
-
- Asynchronous close and asynchronous write-close, as follows:
-
- Value Meaning
- 0 Never
- 1 Always
- 2 Only on a LAN Server 3.0 virtual circuit.
-
- The default is 1.
-
- Digit position 3 performs a function similar to digit position 2 of the
- workheuristics parameter. The server sends a completion message to the
- requester for close or write-close requests before writing buffered file data
- to the fixed disk.
-
- The user is warned if all the data is not written to the fixed disk.
- Asynchronous close and asynchronous write-close are not used if the file was
- opened with the write-through flag set.
-
- Values 1 and 2 are functionally equivalent in a LAN Server 3.0 environment.
-
-
- ΓòÉΓòÉΓòÉ 9.28.5. Buffer Pipes And Serial ΓòÉΓòÉΓòÉ
-
- Character position 4. (0 Based)
-
- Buffers all named pipes and serial devices. The default is 1.
-
- Digit position 4 causes named pipe and communication device information to be
- buffered by the requester while the workstation is reading the information.
- This provides a degree of protection for the data as well as a potential
- performance improvement.
-
-
- ΓòÉΓòÉΓòÉ 9.28.6. Combine R/W Locking ΓòÉΓòÉΓòÉ
-
- Character position 5. (0 Based)
-
- Specifies combined read-lock and write-unlock, as follows:
-
- Value Meaning
- 0 Never
- 1 Always
- 2 Only on a LAN Server 3.0 virtual circuit.
-
- The default is 1.
-
- When digit position 5 is active, the lock and read requests are joined and sent
- as one command. The write and unlock requests are joined similarly.
-
- Values 1 and 2 are functionally equivalent in a LAN Server 3.0 environment.
-
-
- ΓòÉΓòÉΓòÉ 9.28.7. Read On Opens ΓòÉΓòÉΓòÉ
-
- Character position 6. (0 Based)
-
- Specifies open and read. The default is 0.
-
- When digit position 6 is active(1), a request to open a file also performs a
- read. If the size of the file is greater than the size specified by the
- sizworkbuf parameter, as much of the file as can fit in the buffer is read. If
- this action places data in the cache that might never be used, overall
- fixed-disk subsystem performance is slightly degraded.
-
- Unless the requester actually uses the data in the cache most of the time, do
- not specify open and read.
-
-
- ΓòÉΓòÉΓòÉ 9.28.8. Chain Send NCB's ΓòÉΓòÉΓòÉ
-
- Character position 8. (0 Based)
-
- Specifies the use of the chain-send NETBIOS network control block (NCB), as
- follows:
-
- Value Meaning
- 0 Never.
- 1 Do if server's buffer is larger than the workstation's buffer.
- 2 Always (to avoid copy).
-
- The default is 2.
-
- A chained-send enables the NETBIOS protocol driver to copy large data blocks
- directly from the OS/2 LAN Requester user's buffer to the network adapter card.
- An intermediate copy to the network buffers, from which the NETBIOS protocol
- driver normally copies the data to the network adapter card, is bypassed.
-
- In order for the Netlogon service to replicate user and group definitions
- across servers in a domain, digit position 8 of the workheuristics parameter
- (on additional servers) and digit position 3 of the serverheuristics parameter
- (on domain controllers) must not be set to 0. If these digit positions are set
- to 0, user and group data may not be replicated from the domain controller,
- resulting in unknown user ID's and group ID's on the additional servers.
-
-
- ΓòÉΓòÉΓòÉ 9.28.9. Buffer Small Read and Write ΓòÉΓòÉΓòÉ
-
- Character position 9. (0 Based)
-
- Buffers small read and write requests until the buffer is full, as follows:
-
- Value Meaning
- 0 Never
- 1 Always
- 2 Only on a LAN Server 3.0 virtual circuit.
-
- The default is 1.
-
- When digit position 9 is active(1) and file access mode allows, requests to
- read or write data smaller than that specified by the sizworkbuf parameter are
- performed locally in the requester's buffer. Buffering avoids additional trips
- across the LAN. The buffer is flushed when the file is closed or when the
- buffer is needed to satisfy other requests.
-
- Digit position 9 can enhance performance for applications that read, modify,
- and write back small records. Values 1 and 2 are functionally equivalent in a
- LAN Server 3.0 environment. Digit position 9 can be set to 0 if data integrity
- is a primary concern.
-
-
- ΓòÉΓòÉΓòÉ 9.28.10. Buffer Mode ΓòÉΓòÉΓòÉ
-
- Character position 10. (0 Based)
-
- Specifies buffer mode (assuming shared access is granted), as follows:
-
- Value Meaning
-
- 0 Always read buffer size amount of data if the request is smaller than
- the buffer size (sizworkbuf) and data is being read sequentially.
-
- 1 Use full buffer if file is open for reading and writing.
-
- 2 Use full buffer if reading and writing sequentially.
-
- 3 Buffer all requests smaller than the buffer size (if hits occur).
-
- The default is 3.
-
- Shared access means the file was opened in sharing mode. These options allow
- selective tuning of the buffer mode if any applications handle data in a manner
- conflicting with buffering.
-
-
- ΓòÉΓòÉΓòÉ 9.28.11. RAW Read and Write SMB's ΓòÉΓòÉΓòÉ
-
- Character position 11. (0 Based)
-
- Specifies RAW read and RAW write server message block (SMB) protocols.
-
- The default is 1.
-
- RAW read and RAW write SMB protocols transfer data across the LAN without SMB
- headers. These protocols transfer large files directly between the server
- memory and a work cache in the requester.
-
- Digit position 11 can significantly improve performance of large file transfers
- across the LAN. Digit position 11 must be active for digit positions 12 and 13
- to be functional.
-
-
- ΓòÉΓòÉΓòÉ 9.28.12. Large RAW Read Ahead ΓòÉΓòÉΓòÉ
-
- Character position 12. (0 Based)
-
- Specifies large RAW read-ahead buffer.
-
- The default is 1.
-
- Digit positions 12 and 13 provide independent control over the use of RAW SMB
- protocol for read-ahead and write-behind, respectively. Both are active by
- default, but they can be turned off to better suit a particular environment.
- Digit position 11 must be active for digit positions 12 and 13 to be
- functional.
-
-
- ΓòÉΓòÉΓòÉ 9.28.13. Large RAW Write Behind ΓòÉΓòÉΓòÉ
-
- Character position 13. (0 Based)
-
- Specifies large RAW write-behind buffer.
-
- The default is 1.
-
- Digit position 11 must be active for digit positions 12 and 13 to be
- functional.
-
-
- ΓòÉΓòÉΓòÉ 9.28.14. Read Multiplexing SMB's ΓòÉΓòÉΓòÉ
-
- Character position 14. (0 Based)
-
- Specifies read multiplexing SMB protocols.
-
- The default is 1.
-
- This SMB protocol is used for large read requests if the RAW SMB protocol
- (digit position 11) is inactive.
-
- This protocol breaks transfers into buffer-size chunks (sizworkbuf) and chains
- them together to satisfy the request.
-
-
- ΓòÉΓòÉΓòÉ 9.28.15. Write Multiplexing SMB's ΓòÉΓòÉΓòÉ
-
- Character position 15. (0 Based)
-
- Specifies write multiplexing SMB protocols.
-
- The default is 1.
-
- This SMB protocol is used for large write requests if the RAW SMB protocol
- (digit position 11) is inactive. This protocol divides transfers into
- buffer-size chunks (sizworkbuf) and chains them together to satisfy the
- request.
-
-
- ΓòÉΓòÉΓòÉ 9.28.16. Big Buffers For Core Reads ΓòÉΓòÉΓòÉ
-
- Character position 16. (0 Based)
-
- Specifies using big buffers for large core (non-RAW) reads.
-
- The default is 1.
-
- Digit position 16 is pertinent only to requests made to a core server. An
- example of a core server is PCLP, which does not recognize certain SMB types
- added to the SMB command set by LAN Server 3.0.
-
-
- ΓòÉΓòÉΓòÉ 9.28.17. Small Record Read Ahead ΓòÉΓòÉΓòÉ
-
- Character position 17. (0 Based)
-
- Specifies same-size small record read-ahead or read to sector boundary.
-
- The default is 1.
-
- When digit position 17 is active(1), requests to read small data records
- sequentially cause read-ahead in multiples of the data record size, so a full
- buffer is read and sent to the requester.
-
- For example, if the user is reading 50-byte records sequentially from a
- 4096-byte buffer, LAN Server 3.0 will read ahead to fill the buffer to 4050
- bytes. When digit position 17 is set to 0, data is read up to the next sector
- boundary, usually 512 bytes.
-
- Digit position 17 is significant only if digit position 9 of the workheuristics
- parameter is inactive. If the requester detects small data records of the same
- size being read sequentially, the requester performs this small record
- read-ahead operation.
-
-
- ΓòÉΓòÉΓòÉ 9.28.18. Small Record Write Behind ΓòÉΓòÉΓòÉ
-
- Character position 18. (0 Based)
-
- Specifies same-size small record write-behind or write to sector boundary.
-
- The default is 0.
-
- When digit position 18 is active(1), requests to write small data records cause
- write-behind in multiples of the data record size, so a full buffer is written
- to the server.
-
- When digit position 18 is set to 0, data is written up to the next sector
- boundary, usually 512 bytes.
-
- Digit position 18 is significant only if digit position 9 of the workheuristics
- parameter is inactive. If the server detects small data records of the same
- size being written sequentially, the server performs this small record
- write-behind operation.
-
-
- ΓòÉΓòÉΓòÉ 9.28.19. Flush Pipes And Devices ΓòÉΓòÉΓòÉ
-
- Character position 20. (0 Based)
-
- Flushes pipes and devices on a DosBufReset or DosClose operation.
-
- The default is 0.
-
- Digit position 20 gives the requester application more flexibility regarding
- which files, pipes, or devices are flushed (written to disk) following
- DosBufReset or DosClose operations.
-
- Value Meaning
-
- 0 Flush only files and devices opened by the caller. Spin until flushed
- (wait for confirmation before proceeding with other tasks).
-
- 1 Flush only files and devices opened by the caller. Flush only once (do
- not wait for confirmation).
-
- 2 Flush all files and all input and output of short-term pipes and
- devices. Spin until flushed.
-
- 3 Flush all files and all input and output of short-term pipes and
- devices. Flush only once.
-
- 4 Flush all files and all input and output of all pipes and devices. Spin
- until flushed.
-
- 5 Flush all files and all input and output of all pipes and devices. Flush
- only once.
-
-
- ΓòÉΓòÉΓòÉ 9.28.20. LS30 Password Encryption ΓòÉΓòÉΓòÉ
-
- Character position 21. (0 Based)
-
- Used to support LAN Server 3.0 encryption of passwords.
-
- The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 9.28.21. Multiple Error Logging ΓòÉΓòÉΓòÉ
-
- Character position 22. (0 Based)
-
- The default is 0.
-
- Controls log entries for multiple occurrences of an error. A recurring error
- can fill up the error log; use digit position 22 to keep down the number of log
- entries. If the value is other than 0, the 1st, 4th, 8th, 16th, and 32nd
- occurrences of an error are logged. After that, every subsequent 32nd
- occurrence is logged.
-
- If the value of digit position 22 is other than 0, the value also defines the
- size of an error table. The table is a record of errors that have occurred.
- Each table entry consists of an error ID number and the number of occurrences
- of that error.
-
- If an error does not match an existing entry in the table and the table is
- full, the logging facility deletes the table entry that has the lowest number
- of occurrences and records the new error information. The table size refers to
- the number of different errors allowed at one time in the table.
-
- Set the value as follows:
-
- Value Meaning
- 0 Log all occurrences.
- 1 Use error table, size 1.
- 2 Use error table, size 2.
- 3 Use error table, size 3.
- 4 Use error table, size 4.
- 5 Use error table, size 5.
- 6 Use error table, size 6.
- 7 Use error table, size 7.
- 8 Use error table, size 8.
- 9 Use error table, size 9.
-
- Typing NET ERROR at the command-line prompt will display the errors in this
- table that have been written to the error log.
-
-
- ΓòÉΓòÉΓòÉ 9.28.22. Buffer Deny Write Opens ΓòÉΓòÉΓòÉ
-
- Character position 23. (0 Based)
-
- Buffers all files opened with deny-write sharing mode.
-
- The default is 1.
-
- When digit position 23 is active(1), the server buffers all files opened with
- deny-write sharing mode, regardless of the access mode the requester used to
- open the file. The sharing mode and access mode are two different parameters of
- a DosOpen command. Digit position 23 deactivates buffering on this requester if
- an application does not work correctly with it.
-
-
- ΓòÉΓòÉΓòÉ 9.28.23. Buffer Read Only Files ΓòÉΓòÉΓòÉ
-
- Character position 24. (0 Based)
-
- Buffers all files opened with the read-only (R) attribute set.
-
- The default is 1.
-
- When digit position 24 is active(1), the server buffers all files with the
- read-only attribute set. Only read access mode will successfully open a
- read-only file. The sharing mode and access mode are two different parameters
- of a DosOpen command. Digit position 24 deactivates buffering on this requester
- if an application does not work correctly with it.
-
-
- ΓòÉΓòÉΓòÉ 9.28.24. Read Ahead On .EXE's ΓòÉΓòÉΓòÉ
-
- Character position 25. (0 Based)
-
- Reads ahead when opening for execution. Reading an executable file sequentially
- is usually, but not always, faster.
-
- The default is 1.
-
- The value of digit position 25 should be 1 if many executable files are loaded
- across the LAN. The load time for some application programs can decrease by
- more than 50%. Experiment with your particular program to determine which value
- is better (0 or 1).
-
-
- ΓòÉΓòÉΓòÉ 9.28.25. Control-C Handling ΓòÉΓòÉΓòÉ
-
- Character position 26. (0 Based)
-
- The default is 2.
-
- Handles the Interrupt (Ctrl+C) key, as follows:
-
- Value Meaning
- 0 No interrupts allowed.
- 1 Allow interrupts only on long-term operations.
- 2 Always allow interrupts.
-
-
- ΓòÉΓòÉΓòÉ 9.28.26. DOS Server Opens ΓòÉΓòÉΓòÉ
-
- Character position 27. (0 Based)
-
- The default is 0.
-
- Forces correct open mode when creating files on a core server. (A core server
- is a DOS-based LAN server, such as PC LAN Program) DOS-based servers open a new
- file in compatibility mode. Digit position 27 forces the workstation to close
- the file and then open it in the proper mode. Digit position 27 may be
- important if you use PCLP servers as external resources.
-
-
- ΓòÉΓòÉΓòÉ 9.28.27. NetBIOS No Ack Mode ΓòÉΓòÉΓòÉ
-
- Character position 28. (0 Based)
-
- The default is 1.
-
- Specifies the NETBIOS NoAck mode (transferring data without waiting for an
- acknowledgment), as follows:
-
- Value Meaning
- 0 NoAck is never used (disable NoAck).
- 1 NoAck on send only.
- 2 NoAck on receive.
- 3 NoAck on send or receive.
-
-
- ΓòÉΓòÉΓòÉ 9.28.28. Write Block RAW Method ΓòÉΓòÉΓòÉ
-
- Character position 29. (0 Based)
-
- Sends data along with the SMB write-block RAW requests.
-
- The default is 1.
-
- When digit position 29 is active(1), the requester sends a requester buffer of
- data (sizworkbuf) to the server with its request for RAW mode protocol for
- large file transfers.
-
-
- ΓòÉΓòÉΓòÉ 9.28.29. Requester Error Msg's ΓòÉΓòÉΓòÉ
-
- Character position 30. (0 Based)
-
- The default is 1.
-
- Sends a message to the screen when the requester logs an error, as follows:
-
- Value Meaning
- 0 Never
- 1 On write-fault errors only (no time out)
- 2 On write-fault and internal errors only (no time out)
- 3 On all errors (no time out)
- 4 Reserved
- 5 On write-fault errors only (time out)
- 6 On write-fault and internal errors only (time out)
- 7 On all errors (time out).
-
- Values other than 1 are normally used for debugging purposes only.
-
-
- ΓòÉΓòÉΓòÉ 9.28.30. DosBuffer Reset Behavior ΓòÉΓòÉΓòÉ
-
- Character position 31. (0 Based)
-
- The default is 2.
-
- Establishes the behavior of DosBufReset on a redirected file (not pipes or
- devices) in the DOS box. When the call to the API returns, the data in the
- buffer has been handled, as follows:
-
- Value Meaning
-
- 0 Changed data in the buffer was sent from the requester to the server.
- The server has written the data to disk.
-
- 1 Changed data in the buffer was sent from the requester to the server.
- The server has not yet written the data to disk.
- 2 DosBufReset was ignored for the files.
-
-
- ΓòÉΓòÉΓòÉ 9.28.31. Logon Time Interval ΓòÉΓòÉΓòÉ
-
- Character position 33. (0 Based)
-
- The default is 1.
-
- Establishes the time interval for performing logon validation from the domain
- controller. Digit position 33 can be set as follows :
-
- Value Meaning
- 0 5 seconds
- 1 15 seconds
- 2 30 seconds
- 3 45 seconds
- 4 60 seconds
- 5 90 seconds
- 6 2 minutes
- 7 4 minutes
- 8 8 minutes
- 9 15 minutes
-
-
- ΓòÉΓòÉΓòÉ 10. Requester Statistics ΓòÉΓòÉΓòÉ
-
- Requester statistics can be viewed for both the requester of the server being
- examined and the local workstation.
-
- These statistics will update at the period set in the NetPM configuration.
-
- For an explanation of the displayed parameters see:
-
- Auto Connect
- Buffers Needed
- Bytes
- Name
- NCB's
- Sessions
- Time
-
-
- ΓòÉΓòÉΓòÉ 10.1. Auto Connect ΓòÉΓòÉΓòÉ
-
- The number of requester autoconnects.
-
-
- ΓòÉΓòÉΓòÉ 10.2. Buffers Needed ΓòÉΓòÉΓòÉ
-
- The total of standard and big buffer failures. If this number ever changes from
- 0 the requester should be reconfigured with additional buffers.
-
-
- ΓòÉΓòÉΓòÉ 10.3. Bytes ΓòÉΓòÉΓòÉ
-
- The byte count of the network traffic is furnished for the Requester, Server
- (including Peer services), and applications.
-
- If one of the numbers becomes larger than 4 Gigabytes (Billion), the number
- will be displayed in Gigabyte increments.
-
-
- ΓòÉΓòÉΓòÉ 10.4. Name ΓòÉΓòÉΓòÉ
-
- The requester name or 'Local' for the local machine.
-
-
- ΓòÉΓòÉΓòÉ 10.5. NCB's ΓòÉΓòÉΓòÉ
-
- Network Control Block Information is furnished for the Requester, Server
- (including Peer service) and applications.
-
- The 'Total' field is the number of NCB's issued by the software.
-
- The 'Not Issued' field is the number of NCB's that the requester was unable to
- build.
-
- The 'Failed' field is the number of NCB's that failed after issue, at or before
- completion.
-
- To obtain the successful NCB's subtract both failures from the total.
-
-
- ΓòÉΓòÉΓòÉ 10.6. Sessions ΓòÉΓòÉΓòÉ
-
- The number of sessions started with any server or peer sharing.
-
- The number of sessions that failed to connect with the requested resource,
- except for "name not found" errors.
-
- The number of sessions that failed after being established.
-
-
- ΓòÉΓòÉΓòÉ 10.7. Time ΓòÉΓòÉΓòÉ
-
- The time period of the statistics in HHH:MM format.
-
-
- ΓòÉΓòÉΓòÉ 11. Server Management ΓòÉΓòÉΓòÉ
-
- A list of all servers can be accessed by selecting Servers on the Manage menu.
- After selecting a server on the list the Network Administrator can switch NetPM
- to a new server or view a server's configuration.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
- Switching Servers
- Viewing Servers
-
-
- ΓòÉΓòÉΓòÉ 11.1. Switching Servers ΓòÉΓòÉΓòÉ
-
- The server being examined by NetPM can easily be changed by selecting Servers
- in the Manage menu, then selecting a server from the list of servers, and then
- selecting the switch push button.
-
- A temporary change can be made or the default server may be changed.
-
- The default server can also be changed from the configuration menu.
-
-
- ΓòÉΓòÉΓòÉ 11.2. Server Details ΓòÉΓòÉΓòÉ
-
- Server configuration details can be viewed and modified by selecting Servers on
- the Manage menu, then selecting a server from the list, and then selecting the
- View push button.
-
- The Server View Dialog will also allow several of the configuration variables
- to be changed while the server is running.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
- Access List Age
- Admin
- Alerts
- Announce
- Audit
- Auto
- Big Buffers
- Buffers
- Buffer Size
- Circuits
- Comm Ports
- Comment
- Connections
- Delta
- Disconnect Time
- File Locks
- Group List Age
- Guest Account
- Modal
- Open Files
- Req
- Searches
- Serial Queues
- ServerHeuristics
- Server Name
- Session Opens
- Shares
- Type
- Users
- User List Age
- User Path
- Version
- Visible
-
-
- ΓòÉΓòÉΓòÉ 11.2.1. Access Control List Age ΓòÉΓòÉΓòÉ
-
- The number of days since the Access Control List was edited.
-
- Note: This is the number of 24 hour periods, not calendar days.
-
-
- ΓòÉΓòÉΓòÉ 11.2.2. Admin ΓòÉΓòÉΓòÉ
-
- The maximum number of administration level accounts as configured in
- IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.3. Alerts ΓòÉΓòÉΓòÉ
-
- Alert configuration parameters.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
- See:
-
- Alert Interval
- Alert List
- Logon Alerts
- Access Alerts
- Disk Space Alert
- Net I/O Alerts
-
-
- ΓòÉΓòÉΓòÉ 11.2.3.1. Alert Interval ΓòÉΓòÉΓòÉ
-
- The number of minutes between alerts.
-
- Repeated alerts will be held for this time. This is to prevent the person or
- computer receiving the alerts from being locked into a loop receiving alerts.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.3.2. Alert List ΓòÉΓòÉΓòÉ
-
- A list of the user accounts or computer (requester) names alerts will be sent
- to.
-
-
- ΓòÉΓòÉΓòÉ 11.2.3.3. Logon Alerts ΓòÉΓòÉΓòÉ
-
- The number of failed logons before generating an alert.
-
- Note: While several of the servers parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.3.4. Access Alerts ΓòÉΓòÉΓòÉ
-
- The number of failed file accesses before generating an alert.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.3.5. Disk Space Alert ΓòÉΓòÉΓòÉ
-
- The number of kilobytes of free disk space, at which, an administrator must be
- notified that the free space is low.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.3.6. Net I/O Alerts ΓòÉΓòÉΓòÉ
-
- The network I/O error ratio (in tenths of a percent) to allow before notifying
- an administrator.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.4. Announce ΓòÉΓòÉΓòÉ
-
- The time in seconds between server announcement of it's availability.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5. Audits ΓòÉΓòÉΓòÉ
-
- The parameters controlling the server audit records.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
- See:
-
- Audit Disabled/Enabled
- Session Logons
- Network Logons
- Sharing
- User List
- Audit Size
- Logon Limits
- Resource Access
- Permissions
- Service Changes
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.1. Audit Enabled/Disabled ΓòÉΓòÉΓòÉ
-
- Indicates if the Audit system is running. This is set by the IBMLAN.INI file on
- the server.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.2. Session Logons ΓòÉΓòÉΓòÉ
-
- Possible values are 'All' session logons, 'Good' session logons, 'Bad' session
- logons or 'None' for no session logon auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.3. Network Logons ΓòÉΓòÉΓòÉ
-
- Possible values are 'All' network logons, 'Good' network logons, 'Bad' network
- logons or 'None' for no session logon auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.4. Sharing ΓòÉΓòÉΓòÉ
-
- Possible values are 'All' share requests, 'Good' share requests, 'Bad' share
- requests or 'None' for no share request auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.5. User List ΓòÉΓòÉΓòÉ
-
- Possible values are 'Enabled' for auditing changes to the group or user account
- database or 'Disabled' for no auditing of changes.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.6. Audit Size ΓòÉΓòÉΓòÉ
-
- The size (KB) of the audit log file. Old audit records will be deleted to keep
- the file under this size.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.7. Logon Limits ΓòÉΓòÉΓòÉ
-
- Possible values are 'Enabled' for auditing user time limit violations or
- 'Disabled' for no auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.8. Resource Access ΓòÉΓòÉΓòÉ
-
- Possible values are 'Enabled' for auditing resource access as defined by the
- per-resource auditing options specified in the access control list or
- 'Disabled' for no auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.9. Permissions ΓòÉΓòÉΓòÉ
-
- Possible values are 'Enabled' for auditing changes to the access control list
- database or 'Disabled' for no auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.5.10. Service Changes ΓòÉΓòÉΓòÉ
-
- Possible values are 'Enabled' for auditing start, stops, pauses and continues
- of LAN Server services or 'Disabled' for no auditing.
-
-
- ΓòÉΓòÉΓòÉ 11.2.6. Auto ΓòÉΓòÉΓòÉ
-
- This field is set to yes when LAN Server parameters are both read from disk at
- start up and automatically saved at shutdown.
-
-
- ΓòÉΓòÉΓòÉ 11.2.7. Big Buffers ΓòÉΓòÉΓòÉ
-
- The number of Big (64KB) Buffers set in IBMLAN.INI. These buffers are used to
- provide some of the throughput advantage of LAN Server.
-
-
- ΓòÉΓòÉΓòÉ 11.2.8. Buffers ΓòÉΓòÉΓòÉ
-
- The number of standard buffers allocated in IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.9. Buffer Size ΓòÉΓòÉΓòÉ
-
- The size (in bytes) of the standard buffer as defined in IBMLAN.INI.
-
- The default is 4096.
-
-
- ΓòÉΓòÉΓòÉ 11.2.10. Circuits ΓòÉΓòÉΓòÉ
-
- The maximum number of virtual circuits per client as defined in IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.11. Comm Ports ΓòÉΓòÉΓòÉ
-
- The number of serial devices that can be shared on the server as defined in
- IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.12. Comment ΓòÉΓòÉΓòÉ
-
- The server comment. Up to 40 characters.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.13. Connections ΓòÉΓòÉΓòÉ
-
- The number of connections to netnames that are allowed on a server as defined
- in IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.14. Delta ΓòÉΓòÉΓòÉ
-
- The time in milliseconds server announcements will vary at random from the
- Announce setting. This randomizing is to avoid repeated conflicts.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.15. Disconnect Time ΓòÉΓòÉΓòÉ
-
- The amount of time (minutes) before an inactive session is terminated.
-
- This does not effect the logon unless the user modals are set for it to do so.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.16. File Locks ΓòÉΓòÉΓòÉ
-
- The number of file locks that can be active on the server as defined in
- IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.17. Group List Age ΓòÉΓòÉΓòÉ
-
- The time, in days, since the group list was edited.
-
- This is in 24 hour periods, not calendar days.
-
-
- ΓòÉΓòÉΓòÉ 11.2.18. Guest Account ΓòÉΓòÉΓòÉ
-
- The name of the guest account on the server.
-
-
- ΓòÉΓòÉΓòÉ 11.2.19. Modal ΓòÉΓòÉΓòÉ
-
- The global user account settings on the server.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
- See:
-
- Forced Logoff Time
- Maximum Password Age
- Minimum Password Age
- Minimum Password Length
- Password History Length
- Server
-
-
- ΓòÉΓòÉΓòÉ 11.2.19.1. Forced Logoff Time ΓòÉΓòÉΓòÉ
-
- The amount of time, in minutes, past the permitted logon hours when a user will
- be forced to log off.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.19.2. Maximum Password Age ΓòÉΓòÉΓòÉ
-
- The number of days before requiring users to change their password.
-
- Note: This is 24 hour periods, not calendar days.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.19.3. Minimum Password Age ΓòÉΓòÉΓòÉ
-
- The number of seconds before a user can set a new password after changing the
- password.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.19.4. Minimum Password Length ΓòÉΓòÉΓòÉ
-
- The minimum password length to permit. This may be set as high as the maximum
- password length.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.19.5. Password History Length ΓòÉΓòÉΓòÉ
-
- The number of old passwords LAN Server should retain. This record is used to
- prevent the users from repeating the old password.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 11.2.19.6. Server Name ΓòÉΓòÉΓòÉ
-
- The server name.
-
- Note: Obtaining these parameters requires another call to the server and the
- name is provided to insure that the intended server is being queried.
-
-
- ΓòÉΓòÉΓòÉ 11.2.20. Open Files ΓòÉΓòÉΓòÉ
-
- The number of files that can be open at one time, from IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.21. Searches ΓòÉΓòÉΓòÉ
-
- The number of file searches that can be running at one time, from IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.22. Serial Queues ΓòÉΓòÉΓòÉ
-
- The number of serial device queues that can coexist on the server, from
- IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23. ServerHeuristics ΓòÉΓòÉΓòÉ
-
- Heuristic adj. 1. Aiding or guiding in discovery. 2. Designating an educational
- method by which a pupil is stimulated to make his own investigations and
- discoveries. <Gk. heuriskein. to find out>
-
- The ServerHeuristics contain 20 variables defining the operation of LAN Server.
- The table is found in IBMLAN.INI.
-
- Note: The ServerHeuristics default settings do not need to be changed for most
- networks.
-
- Example:
-
- Digit position: 01234567890123456789
- Default value: 11110141111311001331
-
- In order of the position in the table:
-
- Opportunistic Locking
- Sequential Read Ahead
- Write Behind
- Chain Send NetBIOS NCB's
- Verify Incoming SMB's
- Fast Support FCB Opens
- Server Priority
- Auto Buffer Memory
- Audit And Error Handling
- Full Buffer Deny Write
- Audit And Error Interval
- Share Leniency
- Multiple DOS NetBIOS
- Big Buffer Read Ahead
- Convert Path Specifications
- Acknowledge Timeout
- Validate I/O Controls
- Big Buffer Retain Time
- Big Buffer Fail Time
- Startup Block Mode
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.1. Opportunistic Locking ΓòÉΓòÉΓòÉ
-
- Specifies opportunistic locking when opening files. Opportunistic locking
- allows the server to assume that the first requester of the file is the only
- active process using that file. The server buffers reads and writes of the file
- while preventing a second requester from accessing the file until the buffered
- data is flushed and the file is closed. The buffering can occur even if the
- user opened the file in deny-none sharing mode. The default is 1.
-
- For opportunistic locking to occur, both digit position 0 of the
- serverheuristics parameter on the server and digit position 0 of the
- workheuristics parameter on the requester must be active (1).
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.2. Sequential Read Ahead ΓòÉΓòÉΓòÉ
-
- Specifies read-ahead when the requester is performing sequential access.
- Read-ahead means read additional data to attempt to determine what the
- requester may need. The default is 1.
-
- Digit position 1 pertains to reading ahead to the server's buffers (big buffers
- and requester buffers) from the file system and cache.
-
- Value Meaning
- 0 Do not use read-ahead.
- 1 Use single read-ahead thread.
- 2 Use asynchronous read-ahead thread.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.3. Write Behind ΓòÉΓòÉΓòÉ
-
- Specifies write-behind. Write-behind means tell the requester that a write is
- completed before actually performing the write. If the write generates an
- error, the error appears on a subsequent write. Files opened for write-through
- do not use write-behind. The default is 1.
-
- Digit position 2 pertains to writing behind from the server's buffers (big
- buffers and requester buffers) to the file system and cache.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.4. Chain Send NetBIOS NCB's ΓòÉΓòÉΓòÉ
-
- Specifies the use of the chain-send NETBIOS network control block (NCB). The
- default is 1.
-
- A chained-send enables the NETBIOS protocol driver to copy large data blocks
- directly from server memory to the network adapter card. An intermediate copy
- to the network buffers, from which the NETBIOS protocol driver normally copies
- the data to the network adapter card, is bypassed.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.5. Verify Incoming SMB's ΓòÉΓòÉΓòÉ
-
- Checks all incoming SMB's for correct format. This is useful with mixed
- versions and brands of network software on the LAN. The default is 0.
-
- To prevent wasted processor cycles in an OS/2 LAN Server environment, do not
- change the default value of digit position 4.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 0.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.6. Fast Support FCB Opens ΓòÉΓòÉΓòÉ
-
- Supports file control block (FCB) opens (collapses all FCB opens for a file to
- a single open). This is only useful for DOS applications on the network. The
- default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.7. Server Priority ΓòÉΓòÉΓòÉ
-
- Sets the priority for the server. The default is 4.
-
- Server priority determines how often other applications can access the
- processor. For example, changing the priority from 4 to 5 causes applications
- on the server to respond more quickly but slows response to requests from the
- network.
-
- Priority Class of Priority Level of Class
- 0 3 31
- 1 3 23
- 2 3 15
- 3 3 7
- 4 3 0
- 5 2 31
- 6 2 23
- 7 2 15
- 8 2 7
- 9 2 0
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 4.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.8. Auto Buffer Memory ΓòÉΓòÉΓòÉ
-
- Automatically allocates additional memory (up to maxsearches) for directory
- searches if the allocated memory is not sufficient. If DOS requesters are on
- the network, set digit position 7 to 1. The default is 1.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.9. Audit And Error Handling ΓòÉΓòÉΓòÉ
-
- Write records to the audit trail only when the scavenger wakes up on the
- interval set by digit position 10. The scavenger is a high-priority server
- thread that monitors the network for errors, writes to the error log and audit
- trail, disconnects inactive sessions, and sends alerts.
-
- When digit position 8 is set to 0, any write to the audit trail wakes the
- scavenger. Digit position 10 controls the wake-up interval of the scavenger.
- The default is 1. Does not apply to servers accessing 386HPFS disk space only.
- The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.10. Full Buffer Deny Write ΓòÉΓòÉΓòÉ
-
- Does full buffering (as controlled by digit positions 1 and 2 of the
- ServerHeuristics parameter) when a file is opened with deny-write sharing mode.
- When digit position 9 is set to 0, deny-write access has no buffering for any
- requester using this server. The default is 1.
-
- If an application breaks while buffering deny-write opened files, use digit
- position 9 to disable buffering for all requesters.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.11. Audit And Error Interval ΓòÉΓòÉΓòÉ
-
- Sets the interval for the scavenger to wake up. The scavenger is a thread of
- the server process that performs the following tasks:
-
- Automatic disconnection of sessions.
-
- Sending administrative alerts.
-
- Writing to the audit trail file
-
- Set this entry as follows:
-
- Value Meaning
- 0 5 seconds
- 1 10 seconds
- 2 15 seconds
- 3 20 seconds
- 4 25 seconds
- 5 30 seconds
- 6 35 seconds
- 7 40 seconds
- 8 45 seconds
- 9 50 seconds.
-
- The default is 1. Digit position 8 can cause the scavenger to wake up at other
- times.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.12. Share Leniency ΓòÉΓòÉΓòÉ
-
- Allows compatibility-mode opens of certain types of files by translating them
- to sharing mode opens with deny-none. This is useful for sharing executable and
- other types of files.
-
- Digit position 11 controls how strictly the server enforces compatibility opens
- for read-only. In the strictest sense of compatibility opening, if any file is
- opened with a sharing mode set, or if another session has that file open in
- compatibility mode, a compatibility-mode open of that file fails.
-
- The settings of digit position 11 relax the strictness of compatibility opens.
- The first level allows different DOS LAN Requester workstations to run the same
- programs. The second level extends to batch files. The third level translates
- compatibility-mode opens into deny-none sharing mode while maintaining access
- authority (read-only, write-only, or read-write). Not all applications support
- this mode of operation. The default is 3.
-
- Values for digit position 11 of the serverheuristics parameter include:
-
- Value Meaning
-
- 0 Always use compatibility-mode opens.
-
- 1 Use deny-none sharing mode if read-only access to .EXE or .COM files is
- requested. Use compatibility mode for a .BAT file or if write access to .EXE or
- .COM files is requested.
-
- 2 Use deny-none sharing mode if read-only access to .EXE or .COM files is
- requested. Use deny-write sharing mode if read-only access to .BAT files is
- requested. Use compatibility mode if write access to .EXE, .COM, or .BAT files
- is requested.
-
- 3 Use deny-none sharing mode on all compatibility-mode opens.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.13. Multiple DOS NetBIOS ΓòÉΓòÉΓòÉ
-
- Allow DOS LAN Requester workstations to use a second NETBIOS session when
- sending printer requests. If digit position 12 is not set to 1, a second
- NETBIOS session ends any previous sessions set up for that DOS LAN Requester
- workstation. If these sessions are used, ensure that there are enough NETBIOS
- sessions available on the server. Setting this parameter to 1 only allows the
- usage of additional sessions, it does not configure for the use of those
- sessions. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.14. Big Buffer Read Ahead ΓòÉΓòÉΓòÉ
-
- Set the number of 64KB buffers (big buffers) used for read-ahead. Possible
- values are 0 to 9, where 0 means read-ahead is disabled. If set to a value
- larger than the numbigbuf parameter value, this digit position is reset to the
- numbigbuf parameter value minus 1.
-
- Each 64KB buffer is divided into sixteen 4KB read-ahead buffers. Allocate more
- than one big buffer here if you are processing many files with small reads
- simultaneously. Increasing the value of this parameter requires additional
- NETBIOS commands. The value of this digit position usually should not be set
- above 4 or 5. The default is 1.
-
- Using 64KB (big buffers) for read-ahead involves a trade-off between large file
- transfers and small-record read and write operations. Provided there are two
- 64KB buffers remaining in the server for each requester doing concurrent large
- file transfers, you can use the remaining 64KB buffers for read-ahead without a
- penalty.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.15. Convert Path Specifications ΓòÉΓòÉΓòÉ
-
- Convert incoming path specifications into the most basic format that LAN Server
- 3.0 understands. This conversion includes changing lowercase characters to
- uppercase characters and changing the slashes used in path names to
- backslashes (/ to \). The default is 0.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 0.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.16. Acknowledge Timeout ΓòÉΓòÉΓòÉ
-
- This digit position has two functions:
-
- First, it sets the time the server waits before transmitting an error message
- indicating access denied because of a previous opportunistic lock. Set a longer
- time when the network is subject to long delays. The default value is 0. Digit
- position 15 values can be set as follows:
-
- Value Oplock Timeout NETBIOS Timeout
- 0 35 seconds 34 seconds
- 1 70 seconds 69 seconds
- 2 140 seconds 127 seconds
- 3 210 seconds 127 seconds
- 4 280 seconds 127 seconds
- 5 350 seconds 127 seconds
- 6 420 seconds 127 seconds
- 7 490 seconds 127 seconds
- 8 560 seconds 127 seconds
- 9 640 seconds No timeout
-
- If a second requester requests opening an Oplocked file, the server notifies
- the first requester to flush buffers and close the file. If the first
- requester does not respond within the time defined by digit position 15, the
- server sends an Access denied message to the second requester.
-
- The server can lock a file opened in deny-none sharing mode (as long as there
- are no other requests to access the file), so that buffering can be used to
- enhance performance. The server provides exclusive use of the file to the first
- requester, preventing the second requester from accessing the file until buffer
- data is flushed (written to disk) and the file is closed.
-
- Second, the NETBIOS timeout is the length of time the server waits for an
- acknowledgment response from a requester being sent a NETBIOS message. If a
- response is not received prior to this timeout, the server will disconnect the
- session to that requester. The default value of 34 seconds may not be long
- enough if the requester and server are separated by a congested bridge or slow
- telecommunications lines.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.17. Validate I/O Controls ΓòÉΓòÉΓòÉ
-
- Validates the input/output controls (IOCTLs) across the network. When digit
- position 16 is set to 1, the server accepts only generic device IOCTLs
- (categories 01H, 05H, and 0BH). The default is 1.
-
- Note: When digit position 16 is set to 0, the server can receive incorrect
- IOCTL pointers because of differences in device drivers between vendors.
- This can shut down the server. Set digit position 16 to 0 when using
- certain device drivers, such as custom-built drivers.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 1.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.18. Big Buffer Retain Time ΓòÉΓòÉΓòÉ
-
- Determines how long the server maintains unused, dynamic big buffers before
- freeing the memory. This digit can range from 0 through 9. The default is 3 (1
- minute).
-
- Digit Meaning
- 0 0 seconds
- 1 1 second
- 2 10 seconds
- 3 1 minute
- 4 5 minutes
- 5 10 minutes
- 6 20 minutes
- 7 40 minutes
- 8 1 hour
- 9 Maintain big buffers indefinitely.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 3.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.19. Big Buffer Fail Time ΓòÉΓòÉΓòÉ
-
- Determines how long the server waits after failing to allocate a big buffer
- before trying again. The server processes the request it received using the
- request buffers if no big buffers are currently available. This digit can be
- from 0 to 5. The default is 3 (1 minute).
-
- Digit Meaning
- 0 0 seconds
- 1 1 second
- 2 10 seconds
- 3 1 minute
- 4 5 minutes
- 5 10 minutes.
-
- Does not apply to servers accessing 386HPFS disk space only. The default is 3.
-
-
- ΓòÉΓòÉΓòÉ 11.2.23.20. Startup Block Mode ΓòÉΓòÉΓòÉ
-
- Determines what block mode the server should specify at session startup time.
- This block mode determines whether raw writes and reads are allowed on the
- session. This digit can be 0 or 1. The default is 1.
-
- Digit Meaning
- 0 Neither Read Block RAW nor Write Block RAW are supported.
- 1 Both Read Block RAW and Write Block RAW are supported.
-
-
- ΓòÉΓòÉΓòÉ 11.2.24. Server Name ΓòÉΓòÉΓòÉ
-
- The network name of the server. This name must be distinct from all alias,
- user, and computer names.
-
-
- ΓòÉΓòÉΓòÉ 11.2.25. Session Opens ΓòÉΓòÉΓòÉ
-
- The number of files that can be opened in one session, from IBMLAN.INI
-
-
- ΓòÉΓòÉΓòÉ 11.2.26. Shares ΓòÉΓòÉΓòÉ
-
- The number of netnames a server can accommodate, from IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.27. Type ΓòÉΓòÉΓòÉ
-
- The type of server. Possible types are:
-
- Workstation
- Standalone
- SQL Server
- Domain Controller
- Backup Domain Controller
- Timesource
- Apple
- Novell
-
-
- ΓòÉΓòÉΓòÉ 11.2.28. Users ΓòÉΓòÉΓòÉ
-
- The maximum numbers of users as configured in IBMLAN.INI.
-
-
- ΓòÉΓòÉΓòÉ 11.2.29. User List Age ΓòÉΓòÉΓòÉ
-
- The age, in days, of the user list.
-
- Note: This is 24 hour periods, not calendar days.
-
-
- ΓòÉΓòÉΓòÉ 11.2.30. User Path ΓòÉΓòÉΓòÉ
-
- The path to the user directories.
-
-
- ΓòÉΓòÉΓòÉ 11.2.31. Version ΓòÉΓòÉΓòÉ
-
- The version of the network software.
-
-
- ΓòÉΓòÉΓòÉ 11.2.32. Visible ΓòÉΓòÉΓòÉ
-
- The server may be hidden from the network and the name not provided.
-
- Note: While several of the server parameters may be changed with NetPM, many
- of these settings are drawn from the IBMLAN.INI file and will be reset
- to those values when the server is stopped and restarted.
-
-
- ΓòÉΓòÉΓòÉ 12. Server Statistics ΓòÉΓòÉΓòÉ
-
- This information is obtained with a single API call to the server and utilizes
- very little of the server's resources.
-
- For an explanation of the individual fields select:
-
- Auto Disconnects
- Average Response
- Buffers Needed
- Bytes Rcvd
- Bytes Sent
- Closed By Error
- Devices Opened
- Files Opened
- Large Buffers Needed
- Password Violations
- Print Jobs
- Server Errors
- Sessions Started
- Statistics Time
-
-
- ΓòÉΓòÉΓòÉ 12.1. Auto Disconnects ΓòÉΓòÉΓòÉ
-
- The number of sessions that have timed out and been automatically terminated.
-
- The user's local logon will not have been terminated.
-
-
- ΓòÉΓòÉΓòÉ 12.2. Average Response ΓòÉΓòÉΓòÉ
-
- The average response time, in milliseconds, for the server to respond to
- requests. This field provides a measure of server load.
-
-
- ΓòÉΓòÉΓòÉ 12.3. Buffers Needed ΓòÉΓòÉΓòÉ
-
- This field should always be zero. Any other number indicates a need to
- reconfigure the server.
-
-
- ΓòÉΓòÉΓòÉ 12.4. Bytes Rcvd ΓòÉΓòÉΓòÉ
-
- The count of bytes received by the server from the network. This total can be
- used with the bytes sent to calculate the network load of the individual
- server.
-
-
- ΓòÉΓòÉΓòÉ 12.5. Bytes Sent ΓòÉΓòÉΓòÉ
-
- The count of bytes sent from the server onto the network. This total can be
- used with the bytes received to calculate the network load of the individual
- server.
-
-
- ΓòÉΓòÉΓòÉ 12.6. Closed By Error ΓòÉΓòÉΓòÉ
-
- The number of server sessions closed due to errors. Any number other than zero
- in this field is an indication of a problem needing the attention of the
- network administrator.
-
-
- ΓòÉΓòÉΓòÉ 12.7. Devices Opened ΓòÉΓòÉΓòÉ
-
- This is the count of comm ports or other devices being opened on the server.
-
-
- ΓòÉΓòÉΓòÉ 12.8. Files Opened ΓòÉΓòÉΓòÉ
-
- This is the count of all files opened on the server. Remember, a single program
- may open and close data files many times during a single execution.
-
-
- ΓòÉΓòÉΓòÉ 12.9. Large Buffers Needed ΓòÉΓòÉΓòÉ
-
- This field should always be zero. Any other number indicates a need to
- reconfigure the server.
-
-
- ΓòÉΓòÉΓòÉ 12.10. Password Violations ΓòÉΓòÉΓòÉ
-
- The number of server password violations. A rapid increase in this number will
- indicate a determined unauthorized access attempt.
-
-
- ΓòÉΓòÉΓòÉ 12.11. Print Jobs ΓòÉΓòÉΓòÉ
-
- This is the total of print jobs being sent to the server print spools. This
- will not include print jobs where the printer is not on the server.
-
-
- ΓòÉΓòÉΓòÉ 12.12. Server Errors ΓòÉΓòÉΓòÉ
-
- The number of server system errors. Any number other than zero in this field is
- an indication of a problem needing the attention of the network administrator.
-
-
- ΓòÉΓòÉΓòÉ 12.13. Sessions Started ΓòÉΓòÉΓòÉ
-
- The number of server sessions started. Each session may have multiple
- connections with a server.
-
-
- ΓòÉΓòÉΓòÉ 12.14. Statistics Time ΓòÉΓòÉΓòÉ
-
- The network statistics can be cleared from the LAN Server by anyone with
- administrator access. This is the time since either the server was started or
- the statistics were last cleared.
-
- NetPM will not clear the statistics unless the Graphing system is running. To
- avoid clearing the statistics, set the graphing Autostart to off in the
- configuration menu.
-
- The format of the time is in HOURS:MINUTES.
-
-
- ΓòÉΓòÉΓòÉ 13. User Management ΓòÉΓòÉΓòÉ
-
- By making the User selection on the Manage menu, NetPM provides the Network
- Administrator with a list of all network users in the domain of the selected
- server.
-
- All changes made will result in changes being made to the Domain Controller
- Data Base. These changes are made on the selected server by NetPM and the
- propagation time through the network will be dependant upon the configuration
- of the domain controller.
-
- Three primary actions are available from the User List.
-
- A selected user account may be deleted.
-
- A selected user account may be cloned for a quick addition. The cloning
- includes group memberships and application starter information.
-
- A selected user account may be viewed and modified if desired.
-
- Cloning A User Account
- Deleting A User Account
- Viewing A User Account
-
-
- ΓòÉΓòÉΓòÉ 13.1. Cloning A User Account ΓòÉΓòÉΓòÉ
-
- User accounts may be cloned by making the User selection on the Manage menu,
- then selecting a user from the user list and then selecting the Clone push
- button.
-
- When the account is cloned individual access permissions are not set. The new
- user is included in the same groups and will inherit all access permissions
- granted the groups.
-
- The operator will be asked to provide:
-
- User ID
- User Password
-
- These fields will be copied from the selected user account into the new user
- account:
-
- Privilege
- Flags
- Authorizations
- Expiration Date
- Maximum Storage
- Country Code
- Code Page
- Script Path
- Workstation Restrictions
- Logon Hour Restrictions
- Preferred Server
- Group Memberships
- Public Applications In Starter
- Logon Assignments
-
- These settings are NOT copied:
-
- Full Name
- Home Directory
- Comment
- User Comment
- Logons
- Last Logon
- Last Logoff
- Bad Password Count
- Password Age
-
-
- ΓòÉΓòÉΓòÉ 13.2. Deleting A User Account ΓòÉΓòÉΓòÉ
-
- A user account may be deleted by making the User selection on the Manage menu,
- then selecting a user from the user list and then selecting the Delete push
- button.
-
- The user is automatically deleted from all groups.
-
-
- ΓòÉΓòÉΓòÉ 13.3. View A User Account ΓòÉΓòÉΓòÉ
-
- A detailed view of the user account can be obtained by making the User
- selection on the Manage menu, then selecting a user from the user list and then
- selecting the View push button.
-
- For items that are editable by the system administrator, a push button is
- provided under the field name to access a dialog to change the field settings.
-
- Account Expires
- Apps
- Authorizations
- Bad Passwords
- Code Page
- Comment
- Country Code
- Flags
- Full Name
- Groups
- Home Directory
- Last Logoff
- Last Logon
- Logon Assignments
- Logon Hours
- Logons
- Maximum Storage
- Name
- Password
- Password Age
- Preferred Server
- Privilege
- Script Path
- User Comment
- Workstations
-
-
- ΓòÉΓòÉΓòÉ 13.3.1. Account Expires ΓòÉΓòÉΓòÉ
-
- The time and date when the account will expire. An expired account is the
- equivalent of a disabled account. 'N/A' in the field means that there is no
- limit.
-
-
- ΓòÉΓòÉΓòÉ 13.3.2. Applications ΓòÉΓòÉΓòÉ
-
- The Public and Private applications found in the users starter list. To make
- changes in this list use the Application List from the main menu.
-
-
- ΓòÉΓòÉΓòÉ 13.3.3. Authorizations ΓòÉΓòÉΓòÉ
-
- This field grants operator privilege (accounts, print, comm, and server) to
- users. The possible privileges are:
-
- Print Operator
- Comm Operator
- Server Operator
- Accounts Operator
-
-
- ΓòÉΓòÉΓòÉ 13.3.4. Bad Passwords ΓòÉΓòÉΓòÉ
-
- The number of attempts to validate a bad password. This field can only be set
- by the system.
-
-
- ΓòÉΓòÉΓòÉ 13.3.5. Code Page ΓòÉΓòÉΓòÉ
-
- The OS/2 code page for the language choice of the user.
-
- Defaults to the Server Code Page.
-
-
- ΓòÉΓòÉΓòÉ 13.3.6. Comment ΓòÉΓòÉΓòÉ
-
- A field containing an optional comment or remark about the user. The string
- can be blank, or can have as many as 48 characters.
-
- No Information Required.
-
-
- ΓòÉΓòÉΓòÉ 13.3.7. Country Code ΓòÉΓòÉΓòÉ
-
- The OS/2 country code for the user's language choice. This is used by the LAN
- Server software to generate messages in the appropriate language whenever
- possible.
-
-
- ΓòÉΓòÉΓòÉ 13.3.8. Flags ΓòÉΓòÉΓòÉ
-
- A LAN Server field that determines whether a logon script is to be executed and
- whether the user's account is enabled.
-
- The values are:
-
- Logon Script Enabled.
- Account Disabled.
- Home Directory Required.
- Password Not Required.
- User Cannot Change Password.
-
-
- ΓòÉΓòÉΓòÉ 13.3.9. Full Name ΓòÉΓòÉΓòÉ
-
- A field containing the full name of the user. The string can be blank or can
- have as many as 48 characters.
-
- This information is used by LAN aware programs and is not required by LAN
- Server.
-
-
- ΓòÉΓòÉΓòÉ 13.3.10. Groups ΓòÉΓòÉΓòÉ
-
- A list of all groups in the domain that the user has membership. To make
- changes in this list use the Group List from the main menu.
-
-
- ΓòÉΓòÉΓòÉ 13.3.11. Home Directory ΓòÉΓòÉΓòÉ
-
- A string specifying the path to the user's home directory. This string can take
- one of two forms. The first form defines the drive of the user that will be
- assigned to the home directory. It can have as many as 260 bytes.
-
- x:\machineID\Y$\pathname
-
- Where x is the drive letter to be assigned, machineID is the name of the server
- that holds the home directory, y is the drive letter on the server where the
- home directory exists, and pathname is the remaining path to the directory.
-
- The second form defines a first-available drive specification for the home
- directory:
-
- \\machineID\Y$\pathname
-
- Where machineID, y, and pathname are defined as in the preceding example.
-
- To define a home directory at the root of a server's drive, omit \pathname from
- either of the previous forms.
-
- It is important to ensure that this field follows the correct format or users
- may not get their home directory at logon time.
-
- The push button next to the Home Directory field will allow you to set the
- users home directory, but will not create it if it doesn't exist. Access
- privilege for the user will be set if the directory exists.
-
- Note: One form of the home directory field requires the standard "\\" in front
- of the server name, the other does not.
-
-
- ΓòÉΓòÉΓòÉ 13.3.12. Last Logoff ΓòÉΓòÉΓòÉ
-
- The time and date when the last Logoff occurred. This field can only be set by
- the system.
-
-
- ΓòÉΓòÉΓòÉ 13.3.13. Logon Assignments ΓòÉΓòÉΓòÉ
-
- The automatic logon assignments for a user are listed from the User Details
- dialog with the 'Logon Assignment' push button.
-
- Resources may be added and deleted from the Logon Assignment list with an
- integrated dialog showing a list of aliases and possible devices.
-
-
- ΓòÉΓòÉΓòÉ 13.3.14. Last Logon ΓòÉΓòÉΓòÉ
-
- The time and date when the last logon occurred. This field can only be set by
- the system.
-
-
- ΓòÉΓòÉΓòÉ 13.3.15. Logon Hours ΓòÉΓòÉΓòÉ
-
- The hours a user may logon to the network. This information is set in one hour
- increments. NetPM displays the permitted hours with red indicating hours the
- user will be blocked from logging on and green for the hours a user is
- permitted to logon.
-
- The action of this setting depend upon the User Modal setting.
-
- This setting may not disconnect an active session, and simply prevent the user
- ID from being used for a logon during the set time periods.
-
- The User Modal 'Force Off' time must be set for the amount of time desired
- before terminating the user session.
-
-
- ΓòÉΓòÉΓòÉ 13.3.16. Logons ΓòÉΓòÉΓòÉ
-
- The number of times the account has been used to logon to the network. This
- field can only be set by the system.
-
-
- ΓòÉΓòÉΓòÉ 13.3.17. Maximum Storage ΓòÉΓòÉΓòÉ
-
- This number is the maximum storage allotted for the home directory. Units are
- kilobytes (KB). An entry of -1 means unlimited storage. The field is not
- enforced by the system but is available to utilities such as CHKSTOR, which can
- be used to generate reports and send alerts when they determine that users have
- exceeded their maximum storage.
-
- Using the LAN Server AT command for CHKSTOR is highly recommended.
-
-
- ΓòÉΓòÉΓòÉ 13.3.18. User Name ΓòÉΓòÉΓòÉ
-
- The user account ID. This may not be changed.
-
-
- ΓòÉΓòÉΓòÉ 13.3.19. Password ΓòÉΓòÉΓòÉ
-
- The user's password is not displayed, or made available in any way. However, a
- new password can be entered for the user's account.
-
- This maintains users responsibility for their password, but allows the network
- administrator to provide a new password for those users who have difficulty
- remembering their password.
-
-
- ΓòÉΓòÉΓòÉ 13.3.20. Password Age ΓòÉΓòÉΓòÉ
-
- The number of days since the password was set. Note that this is not date
- referenced and will increase at the time of day the password was set.
-
-
- ΓòÉΓòÉΓòÉ 13.3.21. Preferred Server ΓòÉΓòÉΓòÉ
-
- The name of the preferred server, which validates user logon requests for this
- user. The server name should be preceded by a double backslash (\\) and should
- be the name of a domain controller or backup server on the domain.
-
- A server name of an asterisk (\\*) indicates that the logon request can be
- handled by any domain controller or backup server on the domain. A blank string
- indicates that the domain controller is the preferred logon server.
-
-
- ΓòÉΓòÉΓòÉ 13.3.22. Privilege ΓòÉΓòÉΓòÉ
-
- The user's network access level. Additional access levels may be granted on
- individual computers. The network access levels are Guest, User, and
- Administrator.
-
-
- ΓòÉΓòÉΓòÉ 13.3.23. Script Path ΓòÉΓòÉΓòÉ
-
- A string indicating the path name of the user's logon script (.CMD, .EXE, .BAT,
- or .PRO file). It can have no extension at all. If the file has no extension,
- it is assumed to be a .CMD or .BAT file.
-
- The script path must be specified relative to the Netlogon service SCRIPTS
- path. It can have as many as 260 characters. A blank field indicates no logon
- script exists.
-
-
- ΓòÉΓòÉΓòÉ 13.3.24. User Comment ΓòÉΓòÉΓòÉ
-
- A user-settable field, through User Profile Management. The string can have as
- many as 48 characters.
-
- No information required.
-
-
- ΓòÉΓòÉΓòÉ 13.3.25. Workstations ΓòÉΓòÉΓòÉ
-
- A list of requesters from which a user is permitted to log on. A blank field
- means all requesters are allowed. (To disallow logon, the account disabled flag
- must be set.) Up to eight requesters may be specified. The list of requesters
- can include IBM NETBIOS permanent names, which are listed as machine ID's,
- consisting of 12 hexadecimal characters. IBM NETBIOS permanent names are
- entered in the requester as follows: 16DF.02AC.7DE9