PLBCS_SINGLEUSE

PLBCS_SINGLEUSE Keyword

PLBCS_SINGLEUSE={ON | nnn}

This optional keyword controls the number of client processes.

As a Client Keyword:

1. When set to ON, the PLBCLIENT executable only loads and executes one client process. In this case when a user attempts to load a second instance of PLBCLIENT, the first instance of the client is activated.

2. When the PLBCS_SINGLEUSE is set to a number (nnn), allow 'nnn' instances of the PLBCLIENT to be executed at the same time.

3. If the keyword is not specified, as many PLBCLIENTs as allowed by the server user license or configuration can be executed.

As a Server Keyword:

1. The version of the PLBCLIENT client MUST be a version 9.1 or later. Otherwise, a bad version message occurs when a client attempts to logon to a server.

2. The server rejects a client logon when the number of current PLBCLIENT processes at a workstation exceed the current PLBCS_SINGLEUSE limit specified at the server.

3. If a PLBCLIENT logon is rejected by the server because of the PLBCS_SINGLEUSE limit has been exceeded, the PLBCLIENT activates the last visible PLBCLIENT process that is found in the Windows OS active window list. This is consistent with the processing for the PLBCS_SINGLEUSE keyword that may be set in a PLBCLIENT INI file.

4. The PLBCS_SINGLEUSE keyword in the PLBSERVE INI can be reset or disabled when a 'PLBSERVE -r' reset license command is executed. Appropriate messages are logged when the PLBCS_SINGLEUSE keyword setting is changed.

5. When the PLBSERVE server rejects a client logon because the PLBCS_SINGLEUSE limit has been exceeded, then the following message is logged in the PLBSERVE log file:

Workstation clients exceed PLBCS_SINGLEUSE setting!
(Child Task NOT STARTED!)

6. The PLBCS_SINGLEUSE can be used at either the client or server or on both sides. The client side setting of PLBCS_SINGLEUSE can be more restrictive than the server side. If the client side limit is larger than the server setting, the server side limit always applies.