Ref: 11020026
Title: Testing New LAN Manager Parameters Before Making Permanent Changes
Date:   2/1/91

Copyright 3Com Corporation, 1991.  All rights reserved.

This article explains how to make temporary changes in the LAN Manager
parameters on your server, so you can test how they affect performance
on your server without risking the loss of the current settings.

The 3+Open Lan Manager Technical Reference pages 2-46 through 2-50
give detailed explanations of the parameters that can be changed.  Some
settings can be changed from either DOS or OS/2.  (Refer to the Technical
Reference for more information.)  If you do not have the Technical Reference,
you can type NET HELP START SERVER to get a list of the parameters that can
be typed from the command line:

   NET START SERVER [/ACCESSALERT:number]
                    [/ALERTNAMES:alias;alias;...]
                    [/ALERTSCHED:number]
                    [/AUDITING:{Yes | No}]
                    [/AUTODISCONNECT:number]
                    [/DISKALERT:number]
                    [/ERRORALERT:number]
                    [/GUESTACCT:account]
                    [/LOGONALERT:number]
                    [/MAXAUDITLOG:number]
                    [/MAXCHDEVJOB:number]
                    [/MAXCHDEVQ:number]
                    [/MAXCHDEVS:number]
                    [/MAXCONNECTIONS:number]
                    [/MAXLOCKS:number]
                    [/MAXOPENS:number]
                    [/MAXSEARCHES:number]
                    [/MAXSESSOPENS:number]
                    [/MAXSESSREQS:number]
                    [/MAXSESSVCS:number]
                    [/MAXSHARES:number]
                    [/MAXUSERS:number]
                    [/NETIOALERT:number]
                    [/NUMADMIN:number]
                    [/NUMBIGBUF:number]
                    [/NUMFILETASKS:number]
                    [/NUMREQBUF:number]
                    [/SECURITY:{user | share}]
                    [/SIZREQBUF:number]
                    [/SRVANNDELTA:number]
                    [/SRVANNOUNCE:number]
                    [/SRVCOMMENT:text]
                    [/SRVHEURISTICS:string]
                    [/SRVHIDDEN:{Yes | No}]
                    [/SRVNETS:network;network;...]
                    [/SRVSERVICES:service;service;...]
                    [/USERPATH:path]


The NET START SERVER command starts the LAN Manager Server service.  (See
the MS OS/2 LAN Manager Administrator's Reference for more information about
this command.)


Making and Verifying Changes to Parameters

The following examples show how to change the MAXLOCKS parameter for both
PC servers and 3Servers.  Changing MAXLOCKS requires stopping the Server
service (because changes cannot be made while it is running), then
issuing a command to restart the service that includes the new parameters
on the command line.  If you are not satisfied with the changes, you can
revert to your original settings by stopping the server and restarting it
with no other command line options.

For a PC server, type these commands at the system prompt:

   net stop server
   net start server /maxlocks:200
   net load srvshare.pro

Now the MAXLOCKS are set to 200 (from a previous setting of, say, 150).
This will remain in effect until the server is restarted or changed via
the command line.

For a 3Server, the commands are the same but they must be executed a
little differently since there is no keyboard or monitor on the server.

From a workstation, link to the server and create a batch file which
includes the commands you want to execute on the server.  Then run the
commands remotely using the AT schedule.  The batch file would look
something like this:

   net stop server /y
   net start server /maxlocks:200
   net load srvshare.pro

To run the batch file, (called, for example, LOCKS.CMD), place it on the
server in the root directory.  Then type:

   net admin \\server /c AT 00:00 c:\locks.cmd

For more information on the AT command, refer to the 3+Open Administrator's
Reference page 3-15.  For information regarding remote administration via the
NET ADMIN command, see page 3-28 in the same reference manual.

To verify that the changes took effect, you can view the server configuration
report with the following command:

   net config server

On screen, you will see a report similar to the following:

Server name                 \\WAILEA
Server comment              rep's server
Send admin alerts to        WAILEA

Software version            LAN Manager 1.01
Server active on            NET1
Lan Manager root            C:\3OPEN\SERVER\LANMAN
User directories root       D:\3OPEN\USERS

Number of net buffers            90   Server hidden               No
Size of net buffers (byte)     4096   Auditing enabled           Yes
Number of big buffers             8   Security mode             User

Max logged on users              80   Alert interval (min)         5
Max concurrent admin              8   System error limit         200
Max resource shares             159   Net I/O error limit          5
Max resource connections        500   Passwd violation limit       5
Max open files                  150   Access violation limit       5
Max open files per session       50   Disk space limit (Kbyte)   300
Max file locks                  200

Idle session time (min)         120   Max audit log size (Kbyte) 100
The command completed successfully.

