This chapter describes how you start and stop Enterprise Server License Manager and how you use it to monitor license usage.
Enterprise Server License Manager is administrative software that runs in the background, allocating available licenses dynamically to jobs being run under Enterprise Server. It runs continuously. It communicates through the console, reporting status and activity such as that Enterprise Server License Manager process has started.
There is little to do to administer it, since it runs automatically without manual intervention. However, you can start and stop it manually and you can monitor the licenses in use, by using command-line utilities that interact with it. It accesses the license database, described in the chapter Introduction, so these utilities can be used as an alternative to AppTrack for monitoring licenses.
Enterprise Server License Manager uses named pipes for communicating between Enterprise Server and the License Manager. These named pipes reside by default in the /tmp directory (or more precisely in the directory specified by P_tmpdir in the header file /usr/include/stdio.h). The following named pipes are used:
Note: It is important to avoid destroying the ESLMF-common pipe. This can happen if, for instance, you delete all files in the P_tmpdir directory. If you do accidentally destroy this pipe, you can recover, by killing the License Manager and restarting it. See Recovering from a destroyed ESLMF-common pipe.
Enterprise Server License Manager is used in the same way as the development system License Manager. If you have the development system installed, see the section Temporary Files in the chapter Administering the License Manager in your Development System Licensing Guide.
The installation process gives you the option of automatically starting up Enterprise Server License Manager every time the system is booted. If you did not choose the automatic startup, you need to start Enterprise Server License Manager manually every time you boot the system.
To start Enterprise Server License Manager manually:
sh ./eslm
If you decide later, after the installation process, that you want to start Enterprise Server License Manager automatically at boot time, you can set this up as follows:
sh ./eslminstall
To monitor the licenses in use on each enterprise server:
./eslmfgetpv s
This shows the number of licenses allocated to each enterprise server.
To monitor the number of licenses in use:
./eslmfgetpv t
This shows the total number of licenses allocated and the total number in use.
If you have a CPU license for MTO or Micro Focus Server, you have unlimited use of the product. When you produce a license report, development license usage (DEVMTO or DEVES) is not reported and 0 is shown against the appropriate license totals.
To stop Enterprise Server License Manager running:
./eslmfgetpv k
If the ESLMF-common pipe is accidentally destroyed, you can recover, by killing the License Manager and restarting it. Note that you cannot kill it using the eslmfgetpv k command, as the utility eslmfgetpv needs to use the input LM named pipe to instruct License Manager to terminate itself. Instead, you use the operation system command (kill).
If you receive the following errors (the first from eslmfgetpv), you can resolve them as follows:
ES License Manager is not running, or cannot be contacted
Resolution: Restart License Manager using the following command (with COBDIR set to point to the COBOL deployment system, and with root privilege):
$COBDIR/bin/eslm
License Manager will normally start. However, if the previously used License Manager is still running (even though not contactable), it will not start and you receive the follwoing message.
There is already a copy of ES License Manager running!
Resolution: Terminate the previously running uncontactable License Manager and restart it as follows:
ps -fea|grep eslm32
kill My-process-id
$COBDIR/bin/eslm