License Troubleshooting

I have FlexLM 7.0 running on my Solaris 8 system and I've added my BX PRO license to its database. When I run ./lmstat, it claims I am checked in. However, when I start BX up, I'm told that no license exists. How can I get BX to checkout that license?

You need to manually set the number of file descriptors in the shell that starts the lmgrd daemon to something less than 4096. Our suggestion is to use 1024 since that was the default on Solaris 7 systems. To do so:

For csh (and its variants):
% limit descriptors 1024

For sh (and its variants)
% ulimit -H -n 1024

Restart the lmgrd and do a:
% ps -ef

You should see the ICSBX daemon running.

I am using Solaris 8 and having a problem time starting the ICSBX daemon and the lmgrd program.

You need to manually set the number of file descriptors in the shell that starts the lmgrd daemon to something less than 4096. Our suggestion is to use 1024 since that was the default on Solaris 7 systems. To do so:

For csh (and its variants):
% limit descriptors 1024

For sh (and its variants)
% ulimit -H -n 1024

Restart the lmgrd and do a:
% ps -ef

You should see the ICSBX daemon running.

I'm confused, I thought that BX used the FlexLM license server?

When you install a full, permanent license for BX PRO on UNIX systems, you will use FlexLM. Detailed instructions for installing FlexLM are provided in Appendix C of the BX Reference Manual. If you are installing a permament key, we urge you to read this section in detail to maximize your benefit from using floating licenses.

To reduce the amount of time spent installing keys, we have developed a simpler scheme for evaluation licenses. This section talks about how you install an enable an evaluation of BX PRO.

Can I evaluate Linux and Solaris simultaneously?

BX 6.1: Yes, just cut and paste the appropriate key into the key request dialog box as BX starts on the platform. Alternatively, if your startup file detects which system type you are using, just set the environment variable above to the appropriate location for that system. EPak and ViewKit share the same evaluation key on both Linux and UNIX, so you can just set it once.

BX 6.0: If you need to evaluate both a UNIX and Linux version of BX PRO with BX 6.0, do the following:

How can I put the license file somewhere else?

The environment variables ICS_LICENSE_FILE (on Linux platforms) and LM_LICENSE_FILE (on UNIX platforms) are used to specify the location of the BX PRO license file. To set the environment variable

Linux:
For csh (and its variants):
% setenv ICS_LICENSE_FILE /some_path/mylicensefile.dat

For sh (and its variants)
% export ICS_LICENSE_FILE=/some_path/mylicensefile.dat
UNIX:

For csh (and its variants):
% setenv LM_LICENSE_FILE /some_path/mylicensefile.dat

Why does my BX Evaluation on SGI always start up in Demo mode? It never asked me to install a key. How do I provide BX with my evaluation key so that I can get full use of the product?

There is a known problem with Builder Xcessory evaluations on SGI/IRIX that is fixed in the next release. If you are using IRIX, you should create a license file that contains the license key and then set the environment variable LM_LICENSE_FILE to point to it. Let's assume that you've put your evaluation license for BX in the file /some_path/mylicensefile.dat. Then depending on which UNIX shell family you are using, you would do one of the following:

For csh (and its variants):
% setenv LM_LICENSE_FILE /some_path/mylicensefile.dat

I'm using Solaris and I've just upgraded to BX 6 from BX 5. After installing BX 6, I've installed the corresponding new BX 6 keys into the FlexLM license server. Whenever I try to start BX 6, it runs in "Demo Mode" but BX 5 runs in "Full Use Mode". Why?

On UNIX platforms, ICS uses the FlexLM license server to manage the floating licenses to BX. When you purchase a new license or an upgrade license, you use commands provided by FlexLM to add these licenses to the database of the license server. This process can be confusing, and we highly recommend that new users carefully read Appendix C: License Manager, before adding attempting to add new or upgrade licenses.

Pages

Subscribe to License Troubleshooting