* COMPONENT_NAME: (vac) C for AIX compiler * * FUNCTIONS: README * * (C) COPYRIGHT International Business Machines Corp. 1994,1996,1997,1998 * * All Rights Reserved. * Licensed Materials - Property of IBM * * US Government Users Restricted Rights - Use, duplication or * disclosure restricted by GSA ADP Schedule Contract with IBM Corp. * =========================================================================== This document describes the license management system that is used by C for AIX, Version 4.4. This system is called License Use Management (LUM) Version 4 and is similar in features to iFOR/LS. The main difference is the change of concept from a "vendor-managed" system to a "customer-managed system". This means the customer does not need to call any key centre for information. Full detail and information can be obtained from: http://www.software.ibm.com/is/lum The hardcopy README documentation that comes with the product will describe how to install and setup LUM. The concurrent network license certificate is located in /usr/vac/c44aix_c.lic. The concurrent nodelock license certificate is located in /usr/vac/c44aix_cn.lic. Both are available after installing the vac images. ------------------------- LUM Questions and Answers Q1) iFOR/LS used to store my simple nodelock password in /usr/lib/netls/conf/nodelock. Where does LUM store these passwords? A1) LUM stores simple nodelock passwords in /var/ifor/nodelock. You may want to copy your iFOR/LS passwords from /usr/lib/netls/conf/nodelock into /var/ifor/nodelock, then remove /usr/lib/netls/conf/nodelock and create a symbolic link from /var/ifor/nodelock to /usr/lib/netls/conf/nodelock. LUM V4 should automatically perform this procedure during installation. Q2) How do I configure LUM after I installed the package? A2) The following are typical answers to the configuration questions of LUM V4 during its server installation (i.e. invocation of the i4config tool). Please note your system configuration may differ and the following is just one possibility: a) Select 4 "Central Registry (and/or Network and/or Nodelock) License Server" on the first panel. b) Answer y to "Do you want this system be a Network License Server too?" c) Select 2 "Direct Binding only" as the mechanism to locate a license server. d) Answer n to "Do you want to change the Network License Server ip port number?" e) Answer n to "Do you want to change the Central Registry License Server ip port number?" f) Answer n to "Do you want to disable remote administration of this Network License Server?" g) Answer y to "Do you want this system be a Nodelock License Server too?" h) Select 1 "Default" as the desired server(s) logging level. i) Enter blank to accept the default path for the default log file(s). j) Answer y to "Do you want to modify the list of remote License Servers this system can connect to in direct binding mode (both for Administration purposes and for working as Network License Client)?" k) Select 3 "Create a new list" to the direct binding list menu. l) Enter the hostname, without the domain, of the system you are configuring LUM when prompted for the "Server network name(s)." m) Answer n to "Do you want to change the default ip port number?" n) Answer y to "Do you want the License Server(s) automatically start on this system at boot time?" o) Answer y to continue the configuration setup and write the updates to the i4ls.ini file. p) Answer y to "Do you want the License Server(s) start now?" Q3) How do I enroll concurrent-nodelock or concurrent-network certificates into LUM? A3) Invoke the /var/ifor/i4blt tool and under Enroll Product pulldown, import the licenses provided. Specify the number of licenses you purchased when prompted. If you would like to use the GUI for i4blt, then the ipfx package must be installed. In addition, the LUM server must be installed and configured. Note: with LUM V3, the enrollment tool was called i4nat. Q4) My /var filesystem is filled up due to LUM logging messages in the file /var/ifor/i4ipc.out. Can I control the size of the i4ipc.out file? A4) Yes. The size of the i4ipc.out file can be controlled by editing the /var/ifor/i4ls.ini file. You may change the values for the following two tags: "NumberOfLogFile" - This is the number of log files that are written. As a log file fills, LUM will create another one and begin writing to it. "MaxLogFileSize" - This is the size of the log files in tens of kilobytes. Q5) I have a system with many nodes (e.g. 128 node SP2.) Is there a way to configure LUM on each node without logging into them? A5) If all your nodes can be configured in the same way, then you can configure one node using "i4cfg -script" and copy the following files to the other nodes: /var/ifor/i4ls.ini /etc/ncs/glb_site.txt (if used) /etc/ncs/glb_obj.txt Q6) Occasionally, when I perform a compilation I experience a timelag in acquring an LUM license. Why? A6) The timelag may have been caused by an incorrect default value set in early versions of LUM. Check the "ReadTimeout" value in /var/ifor/i4ls.ini. If the value is set to "2", increase it to a larger number (e.g. "20") Q7) In /var/ifor/i4ipc.out, I noticed the following message for each compilation: IPCI ERROR: Unable to open Client to Server Connection. (-10 from GRLIPCInitClientWO) How do I fix this problem? A7) This message is produced by LUM. Configure your license server as concurrent-nodelock and concurrent-network. In addition, specify you want to start the license servers at system startup.