Kbase 16216: Connecting with multiple network protocols, use -m3 and -Mp
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Connecting with multiple network protocols, use -m3 and -Mp
Connecting with multiple network protocols, use -m3 and -Mp
The Secondary Login Broker (-m3) parameter should be used in
conjunction with the Servers per Protocol (-Mp) parameter.
This example will start a database broker which will spawn up
to 3 servers for TCP clients, up to 2 servers for SPX clients,
and 1 server for Netbios clients.
_mprosrv sports -S sportsv1 -N TCP -Mn 6 -n 30 -Mp 3
_mprosrv sports -S sportsv2 -N SPX -m3 -Mp 2
_mprosrv sports -S sportsv3 -N netbios -m3 -Mp 1
In the first _mprosrv command line, the -Mn 6 specifies that
a total of 6 servers may be spawned by the shared memory broker,
and a total of 30 users may connect to this database. Due to the
-Mp 3, only 3 of those servers may be used by TCP clients. Since
the default Maximum Clients per Server (-Ma) is 5, a total of 15
users will be able to connect via TCP.
In the second and third _mprosrv command lines, the -Mp 2 and -Mp 1
ensures that 2 servers may be spawned for SPX clients, and 1 server
may be spawned for Netbios clients. With the default Maximum Clients
per Server (-Ma) of 5, this means a total of 10 SPX clients and 5
Netbios clients will be able to connect to the database.
In this example, the consequences of using -m3 without using -Mp
are as follows:
If the first 6 remote clients that connect are all TCP clients, all
6 servers will have been spawned as TCP servers (due to the default
Minimum Clients per Server (-Mi) of 1). This will prevent any
subsequent SPX or Netbios clients from connecting. The broker will be
unable to spawn additional servers for SPX or Netbios, and you may
see either of the following errors:
(748) The server or the system has no more resources. Try a larger -n.
(1154) No servers are available. Try again later.
NOTES:
- The -m3, -Mp, -Mn, -Ma, and -Mi parameters are only valid on
shared memory systems such as NT, OS/2, Unix and VMS
- You can only start 1 shared memory broker per database
- You can only start 1 login broker per protocol
- You must start a shared memory broker before using the -m3
parameter (-m3 starts a SECONDARY broker for logins only)
- The sum total of all -Mp values for a database cannot exceed the -Mn
value for that database
- For more information about -m3, -Mp, -Mn, -Ma, and -Mi, see
Chapter 4 of the Progress System Administration Reference
and Chapter 2 of the Progress Networks Guide.
Progress Software Technical Support Note # 16216