KAI C++ at Fermilab

The KAI compiler is one of the C++ compilers mandated to be supported by ZOOM as part of the Joint CDF/D0/CD Run II Computing Project. It is the C++ compiler selected by D0 and CDF for use on the UNIX platforms for Run II.

License changes as of 3/15/01

Starting 3/15/01, Fermilab has transferred day to day operations to a site license. The directions below have changed to reflect this new mode. The salient points are:

There is no longer a personal use license. All licenses are issued locked to a particular node.

The instructions for getting a Linux hostid have been updated to make life easier for our gatekeepers.

The need for a budget code has been removed. There is no longer a cost for each license, so a budget code is not required.

The site license does cover off-site collaborators. These licenses are processed in the same fashion as those of on-site machines.

If you are having license problem when updating KAI to a newer version, or if you get a message saying that
'Your license is not current enough to allow you to use this newer version of our software',
please follow the instructions for "Requesting a License at Fermilab" on this web page.

Requesting a License at Fermilab

The user/installer will send mail to kai-support@fnal.gov requesting a license and specifying the following information:

Linux

Organizational Affiliation
- CDF
- D0
- Computing Division
- other (please specify)

Platform: Linux
System's full name (results of hostname command)
Hostid ( results of /sbin/ifconfig eth0 | grep HWaddr | tr -d ':' )
Number of CPUs

enter grep processor /proc/cpuinfo | wc -l
or, enter cat /proc/cpuinfo command and count the number of processor: lines

For on-site machines, one of the following pieces of identification for the machine:

system number from the blue tag marked CD System Reference Number
manufacturer's CPU serial number, located somewhere on the machine
CPU tag number from the yellow tag marked CD Equipment Identification Number

Telephone number
IP address (results of nslookup command)
System Manager (contact name and email address)

SGI, OSF1, Solaris

Organizational Affiliation
- CDF
- D0
- Computing Division
- other (please specify)

Platform: (SGI, OSF1, Solaris)
System's full name (results of hostname command)
Hostid

SGI - results of /etc/sysinfo -s command
Solaris - results of the hostid command
OSF1 - results of netstat -i command

Number of CPUs

SGI - enter the hinv -c processor command, the first field of output is the number of processors
OSF1 - enter the psrinfo command, there will be one status line per processor
Solaris - enter the psrinfo command, there will be one status line per processor

For on-site machines, one of the following pieces of identification for the machine:

system number from the blue tag marked CD System Reference Number
manufacturer's CPU serial number, located somewhere on the machine
CPU tag number from the yellow tag marked CD Equipment Identification Number

system number and/or CPU serial/tag numbers

IP address (results of nslookup command)
Telephone number
System Manager (contact name)

Windows NT

Organizational Affiliation
- CDF
- D0
- Computing Division
- other (please specify)

Machine's Full Name

from the Control Panel, press Start, select Settings , select Control Panel
Double click on the Network entry
Click on the Identification tab
The Machine Name is the Computer Name entry

Number of CPUs

from the Control Panel, press Start, select Settings , select Control Panel
Double click on the System entry
Click on the Environment tab
In the System Variables section, look for the NUMBER_OF_PROCESSORS
the value of that variable is the number of processors in your system

For on-site machines, one of the following pieces of identification for the machine:

system number from the blue tag marked CD System Reference Number
manufacturer's CPU serial number, located somewhere on the machine
CPU tag number from the yellow tag marked CD Equipment Identification Number

IP address

from the Control Panel, press Start, select Settings , select Control Panel
Double click on the Network entry
Click on the Protocols tab
Select TCP/IP Protocol and click the Protocols button
if the radio button Specify an IP address is selected, then the IP address is given in the IP Address Field
if the radio button Optain an IP address from a DHCP server is selected, then the machine has no fixed IP address

System Manager (contact name)

AIX

An AIX version of the KAI C++ compiler is available from the vendor through Fermilab, although AIX is not a supported Run II platform. If an AIX license is required please send email to kai-support@fnal.gov.

If the request is authorized, a member of kai-support will:

send mail to cdmaint@fnal.gov with the node/user information, budget code for charge back if needed.
send mail to jackie@kai.com with the needed information to get a key
send mail to kai-support@fnal.gov saying they are handling the request.

If the request is not authorized, a member of kai-support will work with the requestor to resolve their need. The user may be asked to write a requisition; the member of kai-support may write a requisition etc.

Fermilab Licensing Terms

Fermilab has a site license for the Kai compilers. Anyone on site may request a license for their machine. The site license does cover offsite collaborators for such machines as are being used in collaboration with Fermilab research.

Packaging and installation of KAI compiler and associated tools.

The KAI compiler will be packaged as a kits product. It will NOT be proprietary since anyone can download the product from KAI anyway. One needs a key for the compiler to work. OSS will package the product for all supported platforms at Fermilab. The usual product install procedures will be followed for any machine the compiler is to be used on.

To find out which platforms/versions of the compiler are available, set up upd and type:

$upd list -a kai

To install the product, type:

$upd install kai [version] [-f flavor]

with the desired version and flavor. This also brings along the dependent product "kai_key". The file $KAI_KEY_DIR/KEYTABLE.* should be editted to add the license key information. If you had an older version of the compiler and are updating it via upd, the kai_key product should remain the same.

If you prefer to ftp the product from fnkits, instructions are available at http://www.fnal.gov/docs/products/ups/FTPinstructions

Certification of Compiler Versions

KAI Compiler versions should follow the certification process of other compilers as detailed in Division Recommendation documents. The request was that the ZOOM libraries be used as the criteria for certification. It was additionally requested that a set of extra small test cases - mainly developed as a result of problems that arise - be made into a kaitest module and also used in certification.

Support

Support will be through kai-support@fnal.gov. The members of this mail alias will be the contact people to support at KAI. If problems are obviously compiler rather than Fermilab deployment problems, you can send mail to both kai-support@fnal.gov and c++support@kai.com in parallel. A hypermail archive of the mail is accessible only by Fermilab nodes. The discussion/issues forum for the Kai Compiler will be FUE in line with other compilers and/or zoom meetings.

Information is available on packaging the product for the Fermilab environment, and the most frequent licensing errors

Fermilab at Work - Fermilab Home

kai-support@fnal.gov

Last modified: by Bruce Greenway on September 24, 2001