Increase -n when using _mprosrv

O

onire

New Member
Hai all.
i'm a new in using progress.
i use _mprosrv running in MS Windows XP SP2, here it is i write down
" @echo off
cd \dlc\bin
_mprosrv c:\,database> -N TCP -H <host> -S <port> -L 100000 "
but, there are limitation max. 20 users. is it possible to increase -n <user>?:confused:

thanks
 
XP isn't supported as a database server. So I assume this is for testing purposes. I suppose, considering your other post, your Progress version is 9.1D?

Are you using remote client connections or self service client connections or both?
You need to take a look at the following parameters:
-n (maximum number of connections to the database)
-Mn (Numer of servers to start)
-Ma (maximum number of clients per server (default 5)
-Mi (Minimum number of clients per server)

HTH,

Casper.
 
Most of the parameters you can specify for starting a Progress database do have default values. The mulit-user default for -n is 20. Most of the other default values are calculated from -n. One of the most important parameters you did not specify in your startup script is -B (buffer pool) which will be ridiculously low in your scenario.

-n is the number of processes that can connect simultaneously to the database (which is not users if your definition of a user is a humen person using a computer ...). Depending on the license (enterprise or workgroup database) the value is limited (63 for workgroup database IIRC) or unlimited (enterprise database).

-n is not just the number of remote clients or clienst connecting via shared memory to the database. You also need to take into account the background processes (like the asynchronous, before image and after image writes which you are recommended to use with the enterprise database).

HTH, RealHeavyDude.
 
Casper said:
XP isn't supported as a database server. So I assume this is for testing purposes. I suppose, considering your other post, your Progress version is 9.1D?

Are you using remote client connections or self service client connections or both?
You need to take a look at the following parameters:
-n (maximum number of connections to the database)
-Mn (Numer of servers to start)
-Ma (maximum number of clients per server (default 5)
-Mi (Minimum number of clients per server)

HTH,

Casper.
Click to expand...


that's right sir..
i'm using it for testing in MS Windows.
currently i'm using Progress 9.1D (based on my other post about Progress and Linux). actually i'm in the middle of confusing. i installed red hat but is not compatible with progress 9.1D
so i tried to use windows with _mprosrv act like server.
how do i know the different between remote client and self service client connection?
 
Regarding your compability problem with RedHad you might want to take a look into the product availability guid which will tell you if your combination of Progress / Java / OS is supported.

http://web.progress.com/de-ch/customer-service/product-life-cycle.html

Speaking of which, 9.1d is 10 years old software and is not supported anymore by Progress in any form. The last suppored version is 9.1e.

Regarding your question on connection type:
  • A self-service client is connected to the database directly via the shared memory thus is not using the network layer and is not bound to it's limitations. It connects to the database only specifying the path to the database ( -db ). But this connection is only possible if the client is running on the same machine as the database and the client version matches the database version exactly.
  • All other connections which are using the network layer ( -N -H -S ) are remote clients.
HTH, RealHeavyDude.
 
RealHeavyDude said:
Regarding your compability problem with RedHad you might want to take a look into the product availability guid which will tell you if your combination of Progress / Java / OS is supported.

http://web.progress.com/de-ch/customer-service/product-life-cycle.html

Speaking of which, 9.1d is 10 years old software and is not supported anymore by Progress in any form. The last suppored version is 9.1e.

Regarding your question on connection type:

  • A self-service client is connected to the database directly via the shared memory thus is not using the network layer and is not bound to it's limitations. It connects to the database only specifying the path to the database ( -db ). But this connection is only possible if the client is running on the same machine as the database and the client version matches the database version exactly.
  • All other connections which are using the network layer ( -N -H -S ) are remote clients.
HTH, RealHeavyDude.
Click to expand...

thanks a lot...

now, if there are limitation until 20 users (using multi-user session), is there any way that i can increase the -n parameter?
 
20 is the multi-user default. If you want to increase it, for example, to 50 you just supply -n 50 to the proserve command ( _mprosrv in your case ). All these parameters are case sensitive!



Regards, RealHeavyDude.
 
RealHeavyDude said:
20 is the multi-user default. If you want to increase it, for example, to 50 you just supply -n 50 to the proserve command ( _mprosrv in your case ). All these parameters are case sensitive!



Regards, RealHeavyDude.
Click to expand...

got it sir..
thanks a lot...


Regards, Onire
 
Note that, while you can set -n to whatever value you need, you should remain aware of your license terms. Given 9.1D ... the green sheets were probably printed on papyrus back then ... your license will be concurrent user. User = one person sitting at one device connected to at least one DB on one server. This can mean multiple concurrent sessions, multiple DBs, etc., but still counts as one. Batch processes do not count unless they out number human users, in which case you count the batch processes. So, you should monitor your usage pattern to make sure that you are compliant with your license.
 
You must log in or register to reply here.
Back
Top