C Version 5.0 for AIX

I. OVERVIEW
 

II. NEW OFFER CONTENTS

• Features
• Differences between C for AIX Version 3.1.4 and C for AIX V5.0
• Differences between C for AIX V4.3 and C for AIX V5.0
• Differences between C for AIX V4.4 and C for AIX V5.0

III. FUNCTIONALITIES

• Language Support
• OpenMP
• Distributed Debugger
• Automatic and Explicit Loop Paralleling
• 64-Bit Support
• Unicode Support
• Performance Enhancements
• Compilation Flexibility
• Source Compatibility
• Year 2000
• Euro Currency

 

• Software
• Documentation

 

• Hardware Requirements
• Software Requirements

 

• How C for AIX is packaged
• Prerequisites Tasks and Conditions
• LUM Hardware and Software Requirements
• Installing License Use Management (for AIX 4.2)
• C V5.0 Installation
• Installation Summary

• Concurrent Nodelock License Server
• Concurrent Network license Server
• LUM V4 Configuration Questions
• LUM V4 Enablement

 

• Problem diagnose and reporting
• Known Problems

I. OVERVIEW

C for AIX, Version 5.0 extends the existing SMP support from C for AIX, Version 4.4, by supporting the OpenMP industry specification. OpenMP provides a model for parallel programming that allows a program to be portable across shared memory architectures from different vendors by using a common set of APIs.

C for AIX provides improved compile and execution performance, additional memory management debug routines, and supports the run-time dynamic linking provided by AIX Version 4.2.1, or later. C for AIX also provides improved prototyping of programs and improved cross-platform compatibility of compilers within the VisualAge family.
It offers C language features and improved optimization to protect your investment in existing C applications, including 64-bit integer data type, 128-bit floating-point data type, and run-time address checking. In addition, Version 5.0 includes a new source debugger with an enhanced GUI.
 

II. NEW OFFER CONTENTS

Features

       C for AIX, Version 5.0, offers the following features

• Supports the OpenMP industry specification in 32-bit and 64-bit
• Includes a Distributed Debugger component with an enhanced GUI
• Supports SMP through automatic and explicit paralleling
• Supports industry standards including ANSI C and Unicode
• Generates highly optimized code for all  processors
• Provides profile-directed feedback and interprocedural analysis to optimize performance of C applications
• Provides run-time address checking to detect memory errors
• Adds source code and object code compatibility with previous versions of  C

compiler for AIX

Differences between C for AIX version 3.1.4 and C for AIX V5.0
 

• New optimizations routines
• New Interprocedural Analysis Tool
• Improved memory management routines to aid debugging
• Improved cross-platform portability
• Improved fast prototyping of programs
• 64-bit enablement
• Support of License Use Management Version 4.0 (LUM V4)
• Support for Symmetric Multi-Processing (SMP) programming, including OpenMP-compliant APIs
• Support for Unicode
• Additional debugging tools

• Support  or Symmetric Multi-Processing (SMP) programming, including OpenMP-compliant APIs
• Added optimizations routines
•  Support for Unicode
• Additional debugging tools

 

• Added optimization routines
• Support of Unicode
• Support of OpenMP-compliant multi-processing programming APIs
• Additional debugging tools

 

III. FUNCTIONALITIES
 

C for AIX, Version 5.0 is designed to exploit the latest Escala hardware including the latest PowerPC technology. Applications developed with this compiler can now exploit the power of the  Escala hardware improvements.
C for AIX, Version 5.0 allows programmers to deliver high-performance, scalable 32-bit and 64-bit applications, demanded by such industries as:

 

Commercial/Enterprise

 Engineering

 Scientific

 Computational-intense

 

 
 
 
 
 
 
 
 
 

This latest C compiler provides :
 

•   Support for the OpenMP industry specification
•  A new innovative graphical source debugger
•  Support for industry standards including ANSI C and

  Unicode
•   Improved performance through new optimizations
•    including additional options

 

 
 
 
 
 
 
 

C for AIX, Version 5.0 supports the following industry standards  for compiling
C language source code:
 

  The Federal Information Processing Standard (FIPS) PUB
   160 C language.
 

   The American National Standard for Information Systems
    (ANSI) and International Organization for Standardization
    (ISO) standard ANSI/ISO-IEC 9899-1990(1992) for the
    C programming language.
 

    The ISO standard ISO/IEC 9899:1990(E) for the C
     programming language.

    Support of IBM Systems Application Architecture (SAA)
     Common Programming Interface C language definition,
     described by the document Systems Application
     Architecture Common Programming Interface C
     Reference - Level 2. SAA Level 2 is an IBM definition of
     the C language that allows programmers to develop
     applications that can be easily transported across different
      SAA environments. It specifies several features of the C
      language that the ANSI C standard designates as
      implementation-defined.
 

OpenMP is an industry specification describing a common set of APIs for multiplatform SMP programming. OpenMP is a portable, scalable programming model designed to provide SMP programmers with a simple and flexible interface for developing parallel applications for platforms ranging from the desktop to the super computer.

 C for AIX contains OpenMP pragma directives that exploit shared memory parallelism.

OpenMP pragmas fall into four general categories:

 1.  Parallel Constructs
These pragmas enable the programmer to define the  parallel regions in which work is done by threads in parallel.
Most of the OpenMP directives either statically or dynamically bind to an enclosing parallel region.
 

2. Work-sharing Constructs
This category of pragmas enables the programmer to  define how work will be distributed across the threads in a   parallel region.
 

3. Synchronization Constructs
This category enables the programmer to control synchronization among threads.
 

4.Data Visibility
This category of pragmas enables the programmer to define the private/shared context of data within a parallel region.
 
 

Distributed Debugger

• C/C++
• Fortran

interpreted Java

Automatic and explicit paralleling of countable (paralleled) loops is supported. Loops can be made parallel automatically through the use of a compiler option, or explicitly through the use of directives.
Pragma directives are used to improve on automatic paralleling performed by the compiler and fall into two general  categories:

        Informational Directives
                The first category of pragmas allow the programmer to
                provide compiler information about the characteristics of a
                specific loop. The compiler uses this information to perform
                more efficient automatic paralleling of the loop.
 
 

        Prescriptive Directives
                The second category of pragmas provides the programmer
                with explicit control over paralleling. These pragmas are
                used to force or suppress paralleling of loops, to apply
                specific paralleling algorithms to a loop, and to
                synchronize access to shared data.

64-Bit Support

C for AIX, Version 5.0 provides 64-bit pointer and 64-bit addressability support for SMP and serial codes. High optimization levels, interprocedural analysis, and SMP are supported for 64-bit code.
 

Unicode Support

C for AIX, Version 5.0 provides support for Unicode to allow application developers to develop C applications that handle all of the various languages contained within the Unicode standard in a consistent fashion. This also enables application developers to write Unicode enabled applications that will be portable across all  operating systems.

Performance Enhancements

Performance enhancements that exploit the latest hardware capabilities are made available through new options and pragmas. A new higher level of optimization is also introduced in  C for AIX, Version  5.0. Valuable information provided by new source code directives in the form of pragmas and built-in functions also increases the compiler's ability to exploit performance.
 

Compilation Flexibility

The compiler can be used to compile in either 64- or 32-bit modes.
Programs compiled in 64-bit mode can only be run on 64-bit CPUs using AIX Version 4.3, or later.
Programs compiled in 32-bit mode can be run on either 64- or 32-bit CPUs using AIX Version 4.2.1, or later.
 

C for AIX, Version 5.0 provides a high degree of binary compatibility with applications written using earlier releases of  C for AIX, Versions 3 and 4. SMP, 32-bit, and 64-bit applications can execute at the same time and can share access to files, shared memory, and inter-process communication resources.

C for AIX, Version 5.0 includes options to assist in the porting of 32-bit applications to 64-bit applications.  These options highlight specific areas where porting problems tend to occur.
 

C for AIX, Version 5.0, produces applications that run in the AIX  Version 4.2.1, or later environments and support the AIX Version 4 tools.
 

This product is Year-2000-ready. When used in accordance with its associated documentation, it is capable of correctly processing,
 providing, and/or receiving date data within and between the twentieth and twenty-first centuries, provided that all products  (for example, hardware, software, and firmware) used with the product properly exchange accurate date data with it.
 The service end date for this Year 2000 ready product is June 30,  2001.
 

Euro Currency

This program is EuroReady.
Product is considered to be EuroReady if the product, when used in accordance with its associated documentation, is capable of correctly processing monetary data in the euro denomination and of respecting the euro currency formatting conventions (including the euro sign). This assumes that all other products (i.e. hardware, software, firmware etc.) that are used with this product are also EurorReady
 

IV. DELIVERY CONTENTS

 

MI	Name
CLGG023-WA0A	C for AIX V5.0 Initial User (incl. Media)
CLGG023-PA0A	C for AIX V5.0 Additional User
CLGG024-RA10	C for AIX, Upgrade from V3 to V5.0 Initial User (incl. Media)
CLGG024-RA20	C for AIX, Upgrade from V3 to V5.0 Additionnal User
CLGG025-RA10	C for AIX, Upgrade from V4 to V5.0 Initial User (incl. Media)
CLGG025-RA20	C for AIX, Upgrade from V4 to V5.0 Additionnal User

The C for AIX Version 5.0 product information is included online in HTML format.
The online hypertext documentation for this product can be found in :

/usr/vac/html

Use a standard browser to view the online documentation by opening the following file:

file:/usr/vac/html/en_US/doc/index.html
 

The same product information is also available in Portable Document Format (PDF)
form in the file cforaix.pdf at /usr/vac/pdf.

Hardware Requirements

Processor: family of processors supported by AIX Version 4.2.1 , or later
Display: SVGA (800 x 600)
CD-ROM drive
Mouse or pointing device
Memory: 64 MB, or higher, recommended
Disk space:
                         80 MB for tool
                         10 MB for documentation
                         15 MB for search capability for HTML documents
                         35 MB for C compiler
                         64 MB swap/paging space
 
 

Software Requirements

AIX Version 4.2.1 , or later
 X11 required for the Distributed Debugger component
 Frames capable browser to access the HTML-based help
                such as: Netscape Navigator Version 3.01, or later

C for AIX, Version 5.0 produces applications that run in the AIX  Version 4.2.1, and later, environments. Note that 64-bit applications will run only on AIX Version 4.3, and later.

Compatibility: C programs written using Versions 3 or 4 of C for AIX are compatible with C for AIX, Version 5.0.

C programs written using either Version 2 or 3 of C Set ++ ® for  AIX or the XL C compiler component of AIX Version 3.2 are  source-compatible with C for AIX,
Version  5.0 with some  exceptions to detect invalid programs or areas where results are
 undefined.
 
 
 

VI.Installation Information
 
 

How C for AIX is packaged

The C for AIX, Version 5.0 LICENSED program provides:

      - native optimizing C compiler
      - memory-debugging library support
      - debugging tools
      - compile-time message catalogs
      - HTML format documentation.
      - 64-bit enablement
      - AIX Version 4.3 support
      - Symmetric Multi-Processing (SMP) programming support,
           including support for OpenMP-compliant APIs.
 
 
 

Prerequisites Tasks and Conditions

Because of the complexity of the software, not every prerequisite has been listed
in these instructions. Use the Install Preview option to verify and display requisite
software for your choice of components.
However, the following items MUST be installed on your system:

      bos.adt.include Base Application Development Include Files
      bos.adt.lib Base Application Development Libraries
      bos.adt.libm Base Application Development Math Libraries
      ifor_ls.compat License Use Management Version 4 Compatibility
      ifor_ls.base License Use Management Version 4 Base
      bos.net.ncs Base Network Computing Services

 Use the following command to determine if these items have been installed:

lslpp -h bos.adt.include bos.adt.lib bos.adt.libm bos.net.ncs ifor_ls.compat  ifor_ls.base

Refer to the AIX V4 Installation Guide if you need to install these products.

Note: ifor_ls.* are provided on this CD-ROM (C Version 5.0 for AIX)

The following optional items are prerequisites for some C for AIX, Version 5.0
components:

      X11.base.rte AIX windows Runtime Environment.
      ipfx.rte             Information Presentation Facility Runtime

      Install this if you need to:
      Use graphic License Management tools
      Run the graphical debugger (xldb)
      Use the -qipa compiler option
      Use GUI

      Use the following command to determine if these items have been installed:

lslpp -h X11.base.rte
lslpp -h ipfx.rte

Refer to the AIX V4 Installation Guide if you need to install these product.

C for AIX operates under LUM Version 4, and a LUM license certificate is required to
invoke the product. Both concurrent-network and concurrent-nodelock license
certificates are provided in /usr/vac as files cforaix_c.lic and cforaix_cn.lic, respectively.
 

LUM Hardware and Software Requirements

License Use Runtime requires no hardware other than a system that can run your version of AIX.

To install the License Use Runtime base on AIX 4.1 or 4.2, you must first install TCP/IP for AIX (bos.net.tcp).

o GUI Requirements

If you plan to install the License Use Runtime GUI filesets, you must first install IPF/X Runtime Support.
In AIX 4.2 and 4.3, this is in the package ipfx.rte that is shipped with the AIX installation media.
 

 - LUM RUNTIME FILESETS

License Use Runtime includes several filesets which are used during the installation of LUM From the various filesets, only the first two or three are mandatory as indicated below.

The following is a list of the LUM filesets:

  "ifor_ls.base" (mandatory)

    This package contains these filesets:

  ifor_ls.base.cli   - The runtime code and the command line interface
                                       for the Basic License Tool and the Configuration
                                       Tool.
  ifor_ls.base.gui   - The graphical user interface for the Basic
                                      License Tool and the Configuration Tool.

 "ifor_ls.msg.*" (mandatory)

      The LUM message catalogs associated with the various locales.

  "ifor_ls.libraries" (mandatory or optional depending on OS level)
   A replacement for the License Use Runtime libraries.  This package must
    be installed when you install License Use Runtime Version 4.5 on any
    version or level of AIX earlier than 4.3.2.
   Note : IY02209 LUM V4.5.1 REQUIRES IFOR_LS.LIBRARIES
   Required filesets for LUM on AIX 4.3.x changed between LUM
   V4.5.0 and V4.5.1.  Now fileset ifor_ls.libraries is always
   required to bring LUM libraries to a level compatible with
   the LUM executables.  This change is not documented.
 

  "ifor_ls.client" (optional)

    A dummy package that makes it impossible to install an older version of
    License Use Runtime over this version.  This package and the
     ifor_ls.base.cli fileset must be installed and uninstalled together.

   "ifor_ls.compat" (optional)

     A package required only if you run a license-enabled product that uses
     License Use Runtime Version 1.0 concurrent nodelocked licenses.  It is
     provided for backward compatibility only.  To determine whether you need
     to install it, check the documentation of the license-enabled products
     you use to see what kind of licenses they use.

  This package contains two filesets:

  ifor_ls.compat.cli - The runtime code and command-line interface for
                                        the Nodelocked Administration Tool
 ifor_ls.compat.gui - The graphical user interface for the Nodelocked
                                        Administration Tool

Installing License Use Management (for AIX 4.2)
 

The LUM Version V4 software is provided as part of the Base Operating System on AIX
Version 4.3 and may already be installed on your system. the latest version of LUM
can be obtained from:
 

http://www-opensup.bull.com/cgi-bin/misc/misc.cgi

For AIX 4.2 users, LUM Version 4 is provided on the CD-ROM for your convenience.
To install the CD-ROM Version of these images, the CD-ROM must be mounted
on you system. From the mount point, issue the following commands to install LUM
Version 4;

mount -rv cdrfs /dev/cd0 /mnt
cd /mnt

* Note that ipfx.rte is a mandatory prerequisite to install GUI filesets.

Log in with root authority

installp -acd ifor_ls.base -XFq all
installp -acd ifor_ls.compat -XFq all
installp -acd ifor_ls.msg.en_US -XFq all
 
 

  If /.profile exists, during installation of prerequisites ( iforls.*) the following message is issued:

ATTENTION:
/.profile file has been updated. You should login again so that the changes can have effect.

After installation, you should login again and check the PATH variable.
The following line is added by License Use Management installation
export PATH=$PATH:/var/ifor:/usr/opt/ifor/ls/conf

If you have no /.profile available on your system, launch the following command:
export PATH=$PATH:/var/ifor:/usr/opt/ifor/ls/conf
 

Procedure to Install C for AIX, Version 5.0 compiler product from CD_ROM

* Warnings

No C compilations should be in progress when you install the compiler or one of its
message catalogs.
 

SMIT installs files under the /usr/vac directory. There are no executables present in
/usr/bin ( cc, xlc cc_r ...). When your C for AIX, Version 5.0 software is installed, no link is specified for /usr/bin/cc. This is because of possible conflicts with other existing
C/C++ compiler product installations.
If you want this C for AIX, Version 5 to become your default C compiler, simply run the script:
/usr/vac/bin/replaceCSET This script creates appropriate links in the
/usr/bin directory. The modifications may be undone later on by running the script
/usr/vac/bin/restoreCSET.

This product will overwrite earlier versions of C for AIX. However, if you do not first
uninstall earlier versions, you may experience incorrect compiler functionality with
respect to library placements. Uninstall earlier versions of C for AIX by using root
authority to invoke the following commands:

installp -u vac
installp -u memdbg
 
 
 

C V5.0 Installation

Insert the CD-ROM software into the CD-ROM drive.
Log on as a user with root authority.
Enter the following on the AIX command line & colon.

smit install_latest

This command invokes the System Management Interface Tool (SMIT)
Enter the name of the DEVICE that contains the install images.

For example the CD-ROM drive (e.g. /dev/cd0).
SMIT will start at the following menu:
Install Software Products at Latest Level

Write all in SOFTWARE to install
Click on OK
When the installation is complete, press PF10 or choose Exit SMIT from the Exit menu to leave SMIT.

Installation Summary

Install Image                                     Version     Description

During installation, C for AIX packaging tools will determine the level of the AIX
Operating System present on your machine. Different versions of the following files may
be installed to support 32-bit or 64-bit environments, based on the level of the AIX
Operating System present.

vac.cfg          libhmd.a                      libhmu_r.a                   libhm.a                libhmd_r.a

libhu.a            libhm_r.a                    libhmu.a                       libhu_r.a             libpdf.a

libxlsmp.a    profiled/libhmd.a     profiled/libhmu_r.a    profiled/libhm.a   profiled/libhmd_r.a

profiled/libhu.a profiled/libhm_r.a  profiled/libhmu.a    profiled/libhu_r.a
 
 

VII. LUM Licenses

To invoke the C for AIX, Version 5.0 compiler, a LUM license certificate must be installed.

Concurrent-network and concurrent-nodelock certificates are provided in /usr/vac as cforaix_c.lic and cforaix_cn.lic upon completing the installation of C for AIX, Version 5.0.
This means that you do not need to call any Key Centre.
But you will have to install the LUM V4 software, configure it, and import the appropriate licenses.
LUM is automatically installed on systems running AIX Version 4.3 as a component of the Base Operating System (BOS). LUM must be installed manually on  AIX Version 4.2 systems. After installing LUM, a LUM server must be configured.
After installing the C for AIX, Version 5.0 product and prior to invoking the compiler, the LUM PRODUCT LICENSE MUST BE ENROLLED INTO A LUM LICENSE SERVER
To summarize, the following steps are required prior to using the
C for AIX, Version 5.0 product:

1)  Install LUM and C for AIX
2)  Configure LUM License Server(s)
3)  Enroll LUM product license certificate which comes with the product
 

Concurrent Nodelock License Server

A Concurrent Nodelock license server supports concurrent nodelock product
licenses.  A concurrent nodelock license is LOCAL to the node where the
LUM enabled product (e.g. C for AIX)  has been installed.  It allows a
limited number of simultaneous users to invoke the enabled licensed product
on the local system.
 

Concurrent Network License Server

A Concurrent Network license server supports concurrent network product
licenses.  A concurrent network license is a network license that can
temporarily grant a user on a client system the authority to run a LUM
enabled product.
 

LUM V4 Configuration Questions

The following are typical answers to the configuration questions of LUM V4 during its server installation (i.e. invocation of the i4cfg tool). Please note your system configuration may differ and the following is just one possibility:

Select 4 Central Registry (and/or Network and/or Nodelock) License Server on the first panel.
Answer y to Do you want this system to be a Network License Server too?
Answer y to Do you want this system to be a Nodelock License Server too?
Answer n to Do you want to disable remote administration of this Network License
Server?
Answer n to Do you want to disable remote administration of this Nodelock License
Server?
Select 2 Direct Binding only as the mechanism to locate a license server.
Answer n to Do you want to change the Network License Server ip port number?
Answer n to Do you want to change the Central Registry License Server ip port number?
Answer n Do you want to change the  Nodelock License Server  ip port number ?
Select 1 Default as the desired server(s) logging level.
Enter blank to accept the default path for the default log file(s).
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)?
Select 3 Create a new list on the direct binding list menu.
Enter the hostname, without the domain, of the system you are configuring for LUM when prompted for the Server network name(s) .
Answer n to Do you want to change the default ip port number?
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)?
Select 3 Create a new list on the direct binding list menu.
Enter the hostname, without the domain, of the system you are configuring for LUM when prompted for the Server network name(s) .
Answer n to Do you want to change the default ip port number?
Answer y to Do you want the License Server(s) to automatically start on this system at boot time?
Answer y to continue the configuration setup and write the updates to the i4ls.ini file.
Answer y o Do you want the License Server(s) to start now?
 

LUM V4 Enablement
 
 

After LUM has been installed and configured on your system, the product
license certificates can be enrolled with the LUM license server.  Two LUM
product license certificates are provided with this product:

1)  Concurrent Nodelock License Certificate

2)  Concurrent Network License Certificate

Depending on whether a Concurrent Nodelock License Server or a Concurrent
Network License Server or possibly both license servers have been configured,
the user should enroll the appropriate license certificate.

The Concurrent Nodelock license certificate is contained in the file
"/usr/vac/cforaix_cn.lic".  The Concurrent Network license certificate is
contained in the file "/usr/vac/cforaix_c.lic".

To enroll a license certificate, perform the following steps:

1)  Log in as userid "root" on the system where the license server will be
    installed.

2)  Enter "cd /var/ifor".  If this directory does not exist, then LUM has
    not been installed.(
 

3)  Invoke the LUM configuration tool by entering the LUM Basic License Tool
    command "./i4blt".

    The "i4blt" tool contains both Graphical User Interface and command Line.
    If the X11 runtime (i.e. "X11.base.rte" fileset) has been installed on your
    system, the GUI version of the tool will be invoked.  Otherwise, the
    command line version will be invoked and an error will occur since the
    appropriate command line parameters were not specified.

    The following are the instructions for both interfaces using the "i4blt"
    tool:

    a)  Enrolling using GRAPHICAL USER INTERFACE

        - Select "Products" pulldown and click on "Enroll Product" item.
        - Click on "Import" button. The "Import" panel should be displayed.
        - Enter "/usr/vac/*.lic" in the "Filter" entry prompt, and press ENTER.
            This will show the various product license files in the "Files"
             panel.  "cforaix_c.lic" (concurrent network) and "cforaix_cn.lic"
            (concurrent nodelock) should be displayed.
        - Select either "cforaix_c.lic" or "cforaix_cn.lic" by clicking on the
            entry.
        - Click on "OK" button.  The "Enroll Product" panel should be
             re-displayed with information regarding the product indicated.
        - Click on "OK" button of the "Enroll Product" panel. The "Enroll
            Licenses" panel should be displayed.
        - Fill in the information on the "Administrator Information" portion
            of the panel (optional.)
        - Fill in the number of valid purchased licenses of the product
            under "Enrolled Licenses" in the "Product information" portion of
            the panel (mandatory.)
        - Click on "OK" button of the "Enroll Licenses" panel.  The product
            should be successfully enrolled.  You may terminate the "i4blt"
             tool.

    b)  Enrolling using COMMAND LINE

        - From either the "cforaix_c.lic" or "cforaix_cn.lic" product
             license files from "/usr/vac", extract the "i4blt" command from
             the top of the file.
        - Replace "number_of_lics" from the command with the number of
            valid purchased licenses of the product (mandatory.)
        - Replace "admin_name" with the name of the administrator (optional.)
        - Invoke this command as "root" from "/var/ifor".  The product should
             be successfully enrolled.

   c) ONLY for Concurrent-Network Certificate Enrollment:

     After enrolling a concurrent-network certificate, the licenses
     MUST be "distributed" to one or more LUM license servers.  This allows
    you to distribute the load between multiple license servers.  However,
     you can distribute all licenses to a single server if desired.

      To distribute licenses, invoke "/var/ifor/i4blt" as root and perform
      the following steps:

     - Select the Product by clicking on it.
     - Select "Selected" pulldown and click on "Distribute Licenses" item.
     - Select the License Server which you would like to distribute the
         concurrent-network licenses too.
     - Select "Selected" pulldown and click on "Set Number of Licenses" item.

     - Enter the number of licenses which you would like to distribute to
         the selected license server.  This number must be equal to or less
         then the number of licenses enrolled for the product.
     - Close the "Distribute Licenses" window.  Closing the window will
          pop-up the question "Do you want to distribute the licenses?".
          Select "Yes".

NOTE:
          A simple nodelock license allows a single system to use the product
          without the requirement of a license server.  This license type
          does NOT maintain a log of the product usage and should only be used
          when the user can guarantee the usage of the product is not exceeding
          the terms and conditions of the product.
          To use a simple nodelock license, as root copy the license information
           line from the "/usr/vac/cforaix_n.lic" certificate as indicated in
          the certificate to "/var/ifor/nodelock".
 

Compiling with  the C compiler V5.0 for AIX.

Now that the product has been enrolled with LUM, the user may use the
product.  To compile a C program, invoke one of the compiler stanza's
from "/usr/vac/bin".

If you would like to make the C for AIX compiler the default C compiler,
you may invoke the command "/usr/vac/bin/replaceCSET" as "root".
 
 
 
 

VIII. MAINTAINABILITY & SUPPORT STRATEGY

Problem diagnose and reporting

Report problems in OSCAR using :

Product = C
Product Version = 05.00.00
Domain = LANGUAGES
Symkey = C

C 5.0.0.1 - C FOR AIX, V5.0 MAINTENANCE LEVEL