 |
» |
|
|
|
Alters the characteristics of the Network Services server
processes. Syntax | |
{servername}
NSCONTROL SERVER= {ALL }[,minservers][,maxservers] |
Parameters | |
- SERVER
Dynamically alters the minimum or maximum number
of servers. - serverName
Specifies the type of server for which you want
to alter the available number of server processes. The servers that
control the network services are: - DSSERVER
The specified options apply to the server that controls
RFA, RDBA,
PTOP, and RPM.
Default minserver, maxserver values are 0, 300 respectively. - LOOPBACK
The specified options apply to the server used by
the LOOPBACK services. Default
minserver, maxserver values are 0, 300 respectively. - NFT
The specified options apply to the server that controls
NFT. Default minserver, maxserver
values are 0, 300 respectively. - NSSTATUS
The specified options apply to the server that controls
NSSTAT (and NSTATL)
services. Default minserver, maxserver values are 0, 300 respectively. - VTSERVER
The specified options apply to the server that controls
VT and REVERSE VT.
Default minserver, maxserver values are 0, 300 respectively.
- ALL
If you specify ALL
in place of a servername, the specified options apply to all servers
(NFT, DSSERVER,
LOOPBACK, NSSTATUS,
VTSERVER). Default: ALL There may be additional servers to control if other network
products, such as Personal Productivity Center, are installed. Refer
to that network product's documentation to obtain the appropriate
server names. - minservers
The minimum number of servers which will be in existence
at all times. This includes active and reserved servers. These servers
are created immediately on the initiation of Network Services and
are then kept in reserve until a service request is received. Once
the service request is completed, the server is returned to reserve
status. If necessary, additional servers are created immediately
to fit the new minimum specified. Valid range: 0-1250;
however, see the following note. Default: 0 - maxservers
The maximum number of servers. If necessary, reserved
servers will be terminated to fit the new maximum. However, a server
that is in use will not be terminated until it is returned to the
reserved server pool. Limits in the number of allowed processes and internal data
structures can prevent you from reaching the maximum number of servers.
Valid range: 0-32767; however, see the following note. Default: Varies by server
| | | |  | NOTE: The total number of all active servers may not exceed
1250. The sum of all minservers must always be 1250 or less. You
may specify a number greater than 1250 as one or more maxservers
values, but there will never be more than a total of 1250 servers
of all kinds at any one time. | | | | |
Discussion | |
The number of server processes is controlled with the SERVER
function. The maximum number of servers limits how many processes
of each server type can be in existence at any time. If the servers
are at the maximum limit and a new service request (such as a DSCOPY
or REMOTE HELLO) is received, the
request will be rejected. By setting a maximum limit, you can control
the amount of process resources available for NS 3000/iX. Because the creation and initialization of a server takes
time, using reserved servers decreases the set up time for a service
request. A reserved server is created ahead of time and is held
in reserve until a service request is received. The minimum number
of servers controls the number of reserved processes for each type
of server. The number set for the minimum does not limit the number
of concurrent users of the Network Services. If there are more concurrent
users than the minimum number of servers specified, new users can
use the Network Services, but there is a delay while the additional
servers are created. There is no simple formula for determining how many precreated
servers to specify. Since each precreated server consumes one set
of process resources, including process related system table entries
and virtual memory for stack space, the number chosen must be a
tradeoff between using system resources and allowing fast service
response. The node manager needs to estimate, on the average, the
number of concurrent users of each type of server. This number is
used for the minimum number of servers of each type. Since the DSSERVER
process is used by several services, and some of these services
are active for a long time, it makes sense to allocate a larger
number of DSSERVER servers than
NFT, VTSERVER,
LOOPBACK or NSSTATUS
servers. An alternative to allocating a greater number of DSSERVER
servers is to allocate the program files NFT.NET.SYS,
VTSERVER.NET.SYS, DSSERVER.NET.SYS,
LOOPBACK.NET.SYS, and NSSTATUS.NET.SYS.
This alternative is most advantageous for DSSERVER,
where the allocation of the program file is a significant portion
of the set up time. The NFT server
must read keywords and messages from the NFTCAT2
catalog as well as allocate the program file when the server is
created, so the performance gain is not as great as for DSSERVER. Creating reserved servers or using the allocation alternative
means that the program file is in use, just as when a program is
run. Since the program file is in use, it cannot be purged, replaced,
or backed up. Before any software installation, when the program
files are replaced or backed up, check that the program files are
not allocated and that there are no reserved servers. Example | |
The following command sets the minimum number of DSSERVER
processes to five and the maximum to 10. Five reserved DSSERVER
processes are created immediately and are available for future service
requests. The minimum number of servers, which includes both reserved
and active servers, is restricted to five. When an active server
is returned to the reserved pool, if there are already five reserved
servers, the extra server is terminated. The maximum limit means
that if there are 10 DSSERVER processes
active, any new service requests will be rejected. :NSCONTROL SERVER=DSSERVER,5,10 Example | |
If you execute the following command, there will be 10 server
processes created for NFT, 10 for
VTSERVER, 10 for DSSERVER,
10 for LOOPBACK, and 10 for NSSTATUS.
Later, when users issue service requests (such as DSCOPY
and REMOTE HELLO), they do not have to wait for
the servers to be created. The maximum number of servers is unchanged. :NSCONTROL SERVER=ALL,10 Example | |
In the following example, the node manager has chosen to allocate
the program file used for the DSSERVER
servers and to establish two reserved servers for NFT.
To limit the system resources available, the maximum number of servers
is set to 10 for both server types. In this way, performance is
improved with a minimum amount of system resources used. Notice
that the SERVER function can be
repeated; multiple instances of NSCONTROL
functions are allowed on the same command line. :ALLOCATE DSSERVER.NET.SYS
:NSCONTROL SERVER=NFT,2,10;SERVER=DSSERVER,,10
:NSCONTROL STATUS=SERVERS
SERVER MIN MAX DEBUG PIN JOBNUM STATUS SERVICES
LOOPBACK 0 300 OFF
NFT 2 10 OFF
247 RESERVED
187 RESERVED
DSSERVER 0 10 OFF
NSSTATUS 0 300 OFF
VTSERVER 0 300 OFF |
|
