VisualAge C++ Professional Version 5.0 for AIX

I. OVERVIEW

II. HIGHLIGHTS

III. DESCRIPTION

VisualAge C++ Compilers

• ANSI/ISO Traditional Makefile-based C++ Compiler
• ANSI/ISO Incremental C++ Compiler
• Industry Standards
• Choosing the Right Compiler

Additional Enhancements

• Editor Support
• Flexible Source Control
• Better File Management Support
• Easier Transition from Makefiles
• Runtime Performance

IV. OPERATING ENVIRONMENT

• Hardware Requirements
• Software Requirements
• AIX 5L

• Software
• Documentation

• Installation Summary
• License Use-Management Overview
• Obtaining LUM
• LUM Runtime Filesets
• Installing LUM
• Configuring License Server
• LUM V4 Configuration Questions

• How to install
• Components
• Activating the LUM server
• License certificate locations
• Enrolling Product License Certificate
• Compiling with the VisualAge C++
• Security, Auditability and Control

 

• Problem diagnose and reporting
• Known Problems
• LUM Frequently Asked Questions

 

I. OVERVIEW

The VisualAge C++ Professional Version 5.0 for AIX, is a highly productive, and powerful development environment for building C and C++ applications. VisualAge C++ offers the flexibility of a set of C++ compilers supported by a suite of tools designed to offer a rich environment for object-oriented application development.

VisualAge C++ for AIX now includes a traditional, makefile-based C++ compiler.
This makefile-based compiler supports the latest 1998 ANSI/ISO C++ standard and includes a complete implementation of the ANSI Standard Template Library (STL).
Both 32-bit and 64-bit architecture and optimization technologies are supported.
Symmetric multiprocessor (SMP) architecture is also supported with the inclusion of the latest AIX C compiler, which supports the C OpenMP industry specification allowing for SMP explicit directives and automatic paralleling.
The VisualAge C++ incremental compiler can give you productivity gains through fast incremental builds and offers you easier program-understanding technology to make code development and maintenance easier than ever before.

Additional new features and enhancements in VisualAge C++ Version 5.0 for AIX, include:

• The new Distributed Debugger for local and remote debugging of 32-bit and 64-bit executables
• The performance analysis tool to help you understand and improve the performance of C and C++ applications
• Two new keyboard mappings (vi and emacs, which are popular for AIX) for the editing function within the integrated development environment (IDE)
• Support for multiple codestores within the incremental compiler allowing a large project to be implemented in separate and smaller units
• Easier transition from the incremental compiler to the traditional compiler with the ordered name lookup option, which allows the compiler to try to resolve all names to the same declarations that a traditional compiler would
• More flexible source control with the ability to check files into or out of virtually any source control system.
• Improved runtime performance with the use of a new C++ object model
• Better file management support and easier transition from makefiles.

II. HIGHLIGHTS

• Flexibility with the choice of a traditional, makefile-based C++ compiler or the  productive incremental C++ compiler
• Support for the latest ANSI 98 C++ standards in both compilers, including a complete ANSI Standard Template Library.
• Support for 32-bit and 64-bit optimization in both compilers.
• Support for SMP and OpenMP with latest C for AIX compiler (also included in the product)
• New Distributed Debugger for local and remote debugging
• New Performance Analysis tool to help analyze, understand, and tune your C and C++ applications for improved performance
• A rich set of Open Class Libraries
• Tightly integrated and configurable IDE for easy navigation and better understanding of your code (incremental compiler)
• A set of visual tools including the Visual Builder and Data Access Builder that allow you to build programs from parts
• An HTML-based online help optimized for fast access to information with a powerful full-text search engine.

III. DESCRIPTION

VisualAge C++ Compilers

ANSI/ISO Traditional Makefile-based C++ Compiler

VisualAge C++ now includes a traditional, makefile-based C++ compiler with a complete implementation of the ANSI Standard Template Library (STL). The new traditional, makefile-based compiler supports the latest 1998 ANSI/ISO C++ standard. This traditional compiler supports both 32-bit and 64-bit architecture and optimization technologies. This traditional compiler is compatible with previous C++ compilers, making migration and porting to the new compiler easy. The traditional compiler is accessible directly from the command line. The symmetric multiprocessor (SMP) architecture is supported with the inclusion of the latest AIX C compiler, which supports the C OpenMP industry specification allowing for SMP explicit directives and automatic parallelization.
 

ANSI/ISO Incremental C++ Compiler

VisualAge C++ for AIX also includes an incremental compiler with the ANSI Standard Template Library (STL). The incremental compiler also supports the latest 1998 ANSI/ISO C++ standard and both 32-bit and 64-bit architectures. With the VisualAge C++ incremental compiler, you no longer have to wait for an entire project rebuild each time you make a change. You only have to wait as long as necessary for the incremental parts of your program affected by the change to be rebuilt. Databases, or codestores of information about your program, make up the core of the VisualAge C++ incremental compiler. Because of incremental compilation, the VisualAge C++  incremental compiler can provide rapid feedback and faster error-reporting than conventional compilers. All compilation dependencies are maintained automatically in the codestore. You no longer have to worry about maintaining complex header files and makefiles.

The incremental compiler is supported by a powerful integrated development environment (IDE) that takes advantage of the codestore of program information to give you greater understanding of your program. In addition you can instantly browse the class hierarchy, modify the source code as you debug, and easily find references for a method inside a complete project as you edit, compile, and debug your code in one spot.

The VisualAge C++ incremental compiler now supports multiple codestores in a single project. This allows you to manage programs in smaller units. You can debug, browse, and build code for your executables and shared libraries at the same time.

In addition, VisualAge C++ for AIX now allows you to take advantage of the productivity gains of using the incremental compiler while maintaining code compatibility with other traditional C++ compilers. The ordered name lookup option makes the compiler try to resolve all names to the same declarations that a traditional compiler would.
 
 

Industry Standards

VisualAge C++ Version 5.0, for AIX supports the following standards:

- The C language is consistent with the International Standard C (ANSI/ISO-IEC   9899-1990[1992]). This standard has officially replaced American National standard for Information Systems-programming Language C (X3.159-1989) and is technically equivalent to the ANSI C standard. VisualAge C++ supports the changes adopted into the C Standard by ISO/IEC 9899:1990/Amendment 1:1994.

- The Systems Application Architecture (SAA) C Level 2 language definition.

- The C++ language is consistent with the International Standard for Information Systems-Programming Language C++ (ISO/IEC 14882:1998).

- The ISO/IEC 9945-1:1990/IEEE POSIX 1003-1990 standard.

- The X/Open Common Applications Environment Specifications, System Interfaces and Headers, Issue 4.
 

Choosing the Right Compiler

VisualAge C++ Version 5.0 features offers both a fully incremental compiler and a batch compiler. The Integrated Development Environment (IDE) operates with the incremental compiler. The batch compiler is run from the command line. Both compilers support ANSI/ISO C++ language standard, and the latest version 5 of the Open Class Library.

Here are some considerations to help you choose the right setup for your needs.
 
 

Features	Benefits	Incremental Compiler	Batch Compiler
Compilation	Supports the latest language standard	Uses configuration files	Uses Makefiles
Ease of Migration for makefile-based projects	Allow existing projects to take advantage of new standards and compiler technologies	Requires creation of configuration files	Little or no work required
IDE with real time updates	Assists in rapid application development, integrated editing, browsing and debugging	Yes	No
Incremental compilation	Speeds compilation, especially with larger projects	Yes	No
Visual Builder	Speeds development with visual application assembly for predefined parts and automatically generated code.	Yes	Yes
	compiles Visual Builder generated code	Yes	Yes
Data Access Builder	Speeds development with visual mapping from relational database tables into reusable parts, ready for use with The Visual Builder	Yes	Yes
	Compiles Data Access Builder generated code	Yes	Yes
Integrated debugger	Permits debugging without leaving the IDE	Yes	Yes, The IDE debugger allows you to debug programs that have been compiled with traditional debug information(TDI)
Stand-alone debugger	Allows you to debug programs running a remote machine as well as ant programs compiles with traditional debug information	Yes, Stand-alone debugging requires that you enable the export debugging information feature in your configuration file	Yes
Libraries	ANSI/ISO Standard C++ library, including the STL	Yes	Yes
Open Class Library V5.0	Compatible with STL	Yes	Yes
Performance Analysis	Examine how your  program uses system resources	Yes	Yes

Recommendations Based on Code You Have to Maintain
 
 

If you are ...	Recommendation
writing new code	incremental compiler
maintaining projects developed with VisualAge C++ Version 4.0	incremental compiler
maintaining existing code from a batch environment	batch compiler
developing applications for deployment on multiple flavors of UNIX	batch compiler
developing applications using C OpenMP support, SMP explicit directives or automatic parallelisation	batch compiler

Flexibility of VisualAge C++

The two C++ compilers offer you incredible flexibility. You can use the traditional compiler to move projects up to the ANSI/ISO 1998 C++ standard, including Standard Template Libraries (STL), with no project delays or disruptions. The new VisualAge C++ makefile-based compiler can be used to maintain existing code from a traditional environment, porting code from  a non BULL or IBM
platform or developing applications for deployment on multiple flavors of UNIX. The incremental compiler offers you the ability to move up to the new standards while taking advantage of the productivity gains from compiling only parts of the program affected by changes made since the last compile and the tight integration between the incremental compiler and the IDE. The VisualAge C++ incremental compiler gives you an opportunity to obtain significant productivity gains for new projects that you may be starting.
 

VisualAge C++ Debuggers

The Distributed Debugger's intuitive graphical user interface simplifies debugging. You can debug multi-threaded and multi-process applications by following either the parent or the child processes. You can debug multiple applications using the same user interface. Each new application becomes a new tab.

The Distributed Debugger is the common debugger that supports the C, C++, Java, and Fortran programming languages on AIX, OS/390, OS/400, and Windows NT. With the Distributed Debugger,
you will be able to reuse your debug skills across multiple languages and between application development environments.
 

Performance Analysis Tool

New to VisualAge C++ for AIX is the Performance Analysis tool, which can be used to help analyze and understand your C++ and C applications. Using this understanding of your program, you can tune your code for improved performance. The performance analyzer creates a trace file of the execution of your program. The trace file contains trace analysis data that can be examined in several views. Using these views, you can not only tune your code for increased performance but also accomplish the following:

• Diagnose program abends: When performing a function trace, the Performance Analysis tool provides a complete history of events leading up to the point where a program abends.
• Trace multithreaded Programs: After tracing a multithreaded program, you can examine the individual threads to identify their function usage and compare the execution of different threads.

• Identifying potential functions to inline
• Determining which functions of a shared library are being called
• Tracking function calls among threads
• Tracking class interaction

Visual Tools

VisualAge C++ for AIX continues to support the visual programming environments, Visual Builder and Data Access Builder, that let you build a program from parts. Using Visual Builder, you simply drag and drop, and connect visual parts. Visual Builder creates the code for you. With Data Access Builder, you can use the drag-and-drop interface to create your database mappings, and the Data Access Builder creates the source code for you. Source code generated by Visual Builder and Data Access Builder can be compiled by both the incremental and the traditional compilers.
 

Class Libraries

The Open Class Library provides advanced class libraries and frameworks to build rich and robust applications. It supports ANSI standards and you can use the ANSI Standard Template Library (STL) containers in an Open Class application.
 

Additional Enhancements

• Editor Support: The editing function within the IDE now supports 2 new keyboard mappings, vi and emacs, which are widely used editors that are common for AIX. In addition, the IDE supports an expanded selection of editors. You can launch an external editor of your choice from within the IDE.
• Flexible Source Control: It's now easy to check files into or out of any source control system which supports a command line interface.
• Better File Management Support: Now you can use the Host section of the IDE workbook to take care of file-oriented tasks without leaving the development environment; create, delete, copy or rename files and directories, and preview the contents of your files in a simple, graphical interface.
• Easier Transition from Makefiles: In the Configuration section you can now easily locate the traditional makefile-based (batch) compiler equivalents of configuration options and vice versa. You can select directives to enable or disable if you are having migration problems with a particular source file. Using the Convert Batch Options view, you can convert or display equivalent batch and incremental options. You no longer need to look through lengthy reference tables to find equivalent options. Migration help is always close at hand, thanks to the new Browse Migration button. Even when you are in the middle of the Smartguide, you can jump directly to the comprehensive Migration Guide in the online documentation.
• Improved Runtime Performance: A new C++ object model improves run-time performance. You save space with virtual bases. Virtual calls are faster when using the object model.
• A Comprehensive Help System. VisualAge C++ for AIX help is online and in HTML format, so if you've browsed the World Wide Web, you already know how to use it effectively. This online help provides you with information on every component in VisualAge C++ and includes tutorials on how to use many of the tools. It is optimized for fast access to information, and provides fuzzy and precise full-text search. Most information is also provided in Adobe Acrobat PDF format.

• C Set ++ for AIX, Version 3.1
• C and C++ Compilers, Version 3.6
• VisualAge C++ Professional for AIX, Version 4.0

Year 2000

EuroReady Products

considers an product 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 EuroReady. Hardware products that are EuroReady may or may not have an engraved euro sign key on their keyboards.

Currently, EuroReady status applies primarily to products specific to the EMU countries. Products that are not specific to these countries are deemed to be "not ready" for euro unless otherwise stated in the product's country-specific specifications.
 

IV. OPERATING ENVIRONMENT

Hardware Requirements:  VisualAge C++ Version 5.0 for AIX

• Processor:Family of processors supported by AIX Version 4.2.1, or later
• Display: SVGA 800 x 600 (1024 x 764 recommended)
• CD-ROM drive
• Mouse or pointing device
• Memory: 96 MB (128 MB or higher recommended)
• Disk space:
• Up to 750 MB
• 64 MB swap/paging space

Software Requirements:  VisualAge C++ Version 5.0 for AIX

• AIX Version 4.2.1, or later.
• On AIX Version 4.3, or later, Motif 1.2 compatibility libraries must be installed.
• X11 required for the Distributed Debugger component
• A database with the appropriate ODBC database driver, or DB2 Universal Database Version 5.0 , or later for the Data Access Class Builder tool.
• Frames capable browser to access the HTML-based help such as:
• Netscape Navigator Version 4.04, or later
• Adobe Acrobat Reader 3.0 or later, required to view and print PDF documentation.
• For more information on the Adobe Acrobat Reader, visit the Adobe Web site at:

http://www.adobe.com
On AIX 5L following levels of products are required
VisualAge C++ for AIX level 5.0.2
C for AIX level 5.0.2
XL Fortran for AIX version 7.1.0.2
XL Fortran for AIX, Version 7.1.0.2 is the fully supported version of this product. Install Version 7.1.0.2 by using your existing Version 7.1.0.0 CDs, and then apply APARs IY16228 and IY16948.

AIX 5L

Migration AIX 4.X to AIX 5L

1 - If  you order now, C/C++ or fortran compilers, you get the right supported versions to run on AIX 4.3 and AIX 5L C/C++ 5.0.2, Fortran 7.1.0.2. So, no problem of compilers versions in case of migration.

2 - If you have an older version than 5.0.0 for  C/C++compilers, You have to order the following "MIs update" C/C++  to  upgrade your C/C++ compilers at 5.0.2 level or following  "MI Upgrade" for Fortran compiler to update it at  7.1.0.2 version.

Hereafter MIs for compilers :

                                                 C COMPILER
                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

                                              C++ VisualAge V5 for AIX
  CLGG026-WA0A  VisualAge C++ Version 5.0 - Initial Licence (incl. Media & Doc)
                     CLGG026-PA0A  VisualAge C++ Version 5.0 - Additional User
 CLGG027-WA0A  Upgrade to VisualAge C++ V5.0 - Initial Licence - (incl. Media & Doc)
             CLGG027-PA0A  Upgrade to VisualAge C++ V5.0 - Additional User

                                                 FORTRAN
     FORG025-WA0A  XL Fortran V7 - Initial Licence (incl. Media & Doc and 1 user)
                     FORG025-PA0A  XL Fortran V7 – Additional User
     FORG026-WA0A  Upgrade to XL Fortran V7 - Initial Licence (incl. Media & Doc and 1user)
                    FORG026-PA1A  Upgrade to XL Fortran V7 - Additional Licence
     FORG027-WA0A  XL Fortran V7 RTE - (Licence , Media & Doc)
                      FORG028-PA1A  Upgrade to XL Fortran V7
 
 

3 - If you have C/C++ version 5.0.0  or Fortran compiler version  7.0 running on your AIX 4.2 or 4.3 system, you have to upgrade these versions to, 5.0.2 for C/C++ and 7.1.0.2 for fortran compilers, in case of migration to AIX 5L. This is mandatory to make them run on AIX 5L.

 Apply the following APARs :

APAR IY17899:  C for AIX, V5.0.2.0
APAR IY18042:  VisualAge C++ for AIX, V5.0.2.0

APARs IY16228 and IY16948. Fortran 7.1.0.2

These APARS are available on our PTFs server :
http://www-opensup.bull.com/software/languages/C/
 
 

V. DELIVERY CONTENTS

Software

Documentation

VisualAge C++ Version 5.0 provides you with extensive online documentation.
To view the online help you need to have a frames-capable browser such as Netscape Communicator Version 4.04 (or later) installed on your system.

Much of the online documentation is also available in Adobe Portable Document Format (PDF) format. You can view and print this information using the Adobe Acrobat reader. If you do not already have the Acrobat reader program installed, you can download if free form Adobe's website at
http://www.adobe.com. The Adobe PDF files are in the /usr/vacpp/pdf files after installing VisualAge C++ Version 5.0.

If you are planning to migrate existing projects to VisualAge C++ Version 5.0, we strongly recommend that you read the "Chapter 7. Prepare to Migrate to Version 5.0. Hard-copy "Getting Started" provided in the package.

Also provided as part of the help system is detailed help for  upgrading to VisualAge C++ , Version 5.0. The  Migration Guide provides information on migrating your existing  programs to VisualAge C++ Version 5.0 from any of   the following compilers:

                C Set ++® for AIX, Version 3.1
                C and C++ Compilers, Version 3.6
                VisualAge C++ Professional for AIX, Version 4.0

To start the help for VisualAge C++ Version 5 from the command line, run the following command:

  /usr/vacpp/bin/vacpphelp
 
 

VI. INSTALLATION INFORMATION

Installation Summary

http://epicentre.frec.bull.fr/software/languages/C/

click on LUM

License Use-Management Overview

This chapter describes the license management system that is used byVisualAge C++ for AIX.  This system is called License Use Management (LUM) Version 4 and is similar in features to iFOR/LS.

LUM is based on the concept of "Customer-Managed System".  This means the customer DOES NOT NEED TO CALL A KEY CENTRE for licenses.  THE LUM PRODUCT LICENSE CERTIFICATES ARE SUPPLIED WITH THE PRODUCT
(see "ENROLLING PRODUCT LICENSE CERTIFICATE" chapter).

Important:

LUM is automatically installed on systems running AIX Version 4.3 or higher 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.

To summarize, the following steps are required prior to using the VisualAge C++ for AIX, product:

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

Note

Installation and configuration of LUM is only required ONCE.
IF YOUR SYSTEM ALREADY HAS LUM INSTALLED AND CONFIGURED, YOU SKIP TO "ENROLLLING PRODUCT LICENSE CERTIFICATE" section of this document.

Although information regarding the above steps are contained in this document, it is RECOMMENDED THAT USERS READ THE "USING LICENSE USE MANAGEMENT RUNTIME FOR AIX" documentation which comes with LUM (see "OBTAINING LUM" section.)

Another reference is the "README.ARK" documentation which comes with LUM (see "OBTAINING LUM" section.)  This document contains the latest information on LUM and is very useful resource for obtaining LUM information.
 
 

Obtaining LUM

As previously indicated, LUM runtime is included with AIX Version 4.3 and higher and is automatically installed.

However, for AIX Version 4.2 systems, the customer must obtain the LUM runtime and documentation installation images and manually install them.

A version of LUM is available with this product on the CD-ROM.  Insert the CD-ROM into the CD-ROM drive.  Mount the CD-ROM as follows:

The LUM installation images are available from several sources
 On the WEB at:
http://epicentre.frec.bull.fr/software/languages/C/
click on LUM

A version of LUM is available with this product on the CD-ROM.  Insert the CD-ROM into the CD-ROM drive.  Mount the CD-ROM as follows:

    a)  As root, invoke "smit".
    b)  Select "System Storage Management (Physical & Logical Storage)",
        press the "enter" key.
    c)  Select "File Systems", press the "enter" key.
    d)  Select "Add / Change / Show / Delete File Systems", press the "enter"
        key.
    e)  Select "CDROM File Systems", press the "enter" key.
    f)  Select "Add a CDROM File System", press the "enter" key.
    g)  Enter the "DEVICE" name (e.g. "cd0").
    h)  Enter the "MOUNT POINT" where you would like to mount the CD-ROM
        (e.g. "/cdrom").
    i)  Press the "enter" key.
    j)  Exit "smit".

The LUM installp images are available in the sub-directory "lum"   indicated by the mount point of the CD-ROM (e.g. "/cdrom/lum".)
 

LUM Runtime Filesets

License Use Runtime includes several filesets which are used during the installation of LUM (see "INSTALLING LUM" section.)  From the various filesets, only the first two or three are mandatory as indicated below.
The following is a list of the LUM filesets:

1)  "ifor_ls.base" (mandatory)

    This package contains these filesets:

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

2)  "ifor_ls.msg.*" (mandatory)

    The LUM message catalogs associated with the various locales.

3)  "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.  This package is not   required on AIX 4.3.3.

4)  "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.

5)  "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:

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

Installing LUM

Installation and configuration of LUM is only required ONCE.  IF YOUR SYSTEM ALREADY HAS LUM INSTALLED AND CONFIGURED, YOU SKIP TO "ENROLLLING PRODUCT LICENSE CERTIFICATE" section of this document.

To install LUM, perform the following steps:

1)  Determine which filesets are required for your environment (see "LUM  RUNTIME FILESETS"    section.)

2)  Log in as "root".

     Enter
    "cd /var/ifor" (LUM 4.5.5 or earlier)
    or
    "cd /usr/opt/ifor/ls/os/aix/bin" (LUM 4.6.0)

    If the directory does not exist, then LUM has not been installed
    (see "INSTALLING LUM" section.)

3)  Install the filesets using either AIX's System Management Interface Tool
    ("smit") or AIX's "installp" command line tool

    a)  Using "smit"

        - Invoke "smit".
        - Select "Software Installation and Maintenance", press ENTER.
        - Select "Install and Update Software", press ENTER.
        - Select "Install and Update from ALL Available Software", press ENTER.
        - Enter the DEVICE (e.g. "/dev/cd0") or directory where the LUM
          runtime installp images reside (see "OBTAINING LUM".)
        - Select the filesets that are required for your environment as
          determined in STEP 1.

    b)  Using "installp" command line tool

        - Change directory to the location where the LUM runtime installp
          images reside (see "OBTAINING LUM".)
        - Select the filesets that are required for your environment as
          determined in STEP 1.
        - Enter the following for each fileset:
          "installp -acd <fileset_name> -XFq all" where <fileset_name>
          is the fileset you would like to install.
 

Configuring License Server

After installing the LUM runtime installation images.  One or more LUM license servers must be configured.  There are two types of license servers:

- 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. VisualAge C++ for AIX)  has been installed.  It allows a limited number of simultaneous users to invoke the enabled licensed product on the local system.
The Concurrent Nodelock licenses certificate are contained in the file "/usr/vac/cforaix_cn.lic"for C compiler, and in the file /usr/vacpp/vacpp_cn.lic for VisualAge C++ compiler.

- 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.

Either or both of the above license servers may be configured on a system.The number of concurrent users for the product is specified during the  enrollment of the product license certificate (see "ENROLLING PRODUCT LICENSE CERTIFICATE" section.)

Configuring LUM requires answering several questions on how you would like to set up the LUM environment.
It is RECOMMENDED THAT USERS READ THE "USING LICENSE USE MANAGEMENT RUNTIME FOR AIX" documentation which comes with LUM.
(see "OBTAINING LUM" section) prior to configuring LUM.
 The Concurrent Network licenses certificate are contained in the file "/usr/vac/cforaix_c.lic" for C compiler, and in the file /usr/vacpp/vacpp_c.lic for C++ compiler.
 

- Simple Nodelock License Certificate (does not require a license server) file /usr/vac/cforaix_n.lic for C compiler, file /usr/vacpp/vacpp_n.lic for VisualAgeC++ compiler.
 

To configure LUM, perform the following steps:

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

2)  Log in as "root".

     Enter
    "cd /var/ifor" (LUM 4.5.5 or earlier)
    or
    "cd /usr/opt/ifor/ls/os/aix/bin" (LUM 4.6.0)

    If the directory does not exist, then LUM has not been installed
    (see "INSTALLING LUM" section.)

3)  Invoke the LUM configuration tool by entering the command "./i4config".
    This is the command line version of the LUM configuration tool.

4)  Answer the LUM configuration questions as appropriate.
The answers to the configuration questions are dependent on the  LUM environment you wish to  create.
The following are typical answers to the configuration questions of LUM  in order to configure both Concurrent Nodelock and Concurrent Network  license servers on a single system. You may change the various answers accordingly to suit your preferred system environment.  For details  on configuring LUM, please read the "USING LICENSE USE MANAGEMENT RUNTIME  FOR AIX" documentation which comes with LUM (see "OBTAINING LUM" section).
 
 

LUM V4 Configuration Questions

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?

 Both Concurrent Nodelock and Concurrent Network license servers should  now be configured on your system.
 

VII. Installing VisualAge C++

How to install

You can install VisualAge C++ Version 5.0 in one of two ways:

- Select the individual filesets you wish to install on your machine. This allows you to control which components of VisualAge C++ are installed.

- Use _all_latest install option. This option installs all components found on the CD, giving you the most complete installation of VisualAge C++ Version 5.0 possible.

If you are upgrating an existing installation of VisualAge C++, we recommend that you uninstall your existing version of VisualAge C++ before installing VisualAge C++ Version 5.0.

Note:  If you are installing VisualAge C++ Version 5.0 on a machine running AIX Version 4.3, ensure that the Motif 1.2 compatibility fileset, X11.compat.adt.Motif12, is installed on that system.
Motif 1.2 compatibility fileset is part of the AIX Version 4.3 Base Operating System. (BOS).
It is a prerequisite for this version 5.0 of VisualAge C++.

You must have root user access to install VisualAge C++ .

To install VisualAge C++ by selecting filesets:
1. Insert the first CD into the CD-ROM device.
2. At a commamd prompt, enter smit install_latest.
3. Press FP4 or click List to display the list of devices.
4. Select the CD-ROM device, and then click OK.
5. Press PF4 or click List to select the filesets you wish to install.

Some of the VisualAge C++ filesets are specific to the AIX version and language environments on your machine. If you select filesets that do not match your version of AIX or your language environments, you will receive a failed install message. We recommend that you read the fileset descriptions closely.

Important: When fileset names differ only by the AIX version that supports them, only select fileset supported by the AIX version equal or lower than the version of AIX running on your machine. For example, if you are running AIX 4.2, and both thisfileset.aix41 and thisfileset.aix43 are available from the list of filesets, choose thisfileset.aix41

6. Follow the on-screen instructions to complete the installation.
7. If you want to install the source code for the Open Class libraries or the documentation for the japenese or Simplified Chinese language environments, repeat the above steps using the second CD.
 

To install all the components of VisualAge C++ :

1. Insert the first CD into the CD-ROM device
2. At a command prompt, enter smit install_latest.
3. Press PF4 or click List to display a list of devices.
4. Select the CD-ROM device, the click OK.
5. Click OK
6. Follow the on-screen instructions to complete the installation.

If you get a failed message see above recommendations.

Note: after install of first CD, smit ask for CD 2 to be installed.

Important :
DURING AN OPERATING SYSTEM MIGRATION, USERS REQUIRE TO PERFORM
TWO STEPS TO ENSURE VISUALAGE C++ WILL CONTINUE TO OPERATING
CORRECTLY.  THIS IS DUE TO THE LIMITATION OF THE AIX MIGRATION
PROCESS.

STEP 1:

The VisualAge C++ product contains a number of filesets specific to the operating system level which are not contained on the AIX media.  Therefore, after migrating from an earlier version of AIX to AIX 5L Version 5.1, users will be required to manually install the AIX 5L versions of the filesets from the VisualAge C++ media.Only the filesets which are required by the users need to be installed.

These filesets are:

vacpp.cmp.aix50.lib
vacpp.ioc.aix50.lib
vacpp.ioc.aix50.rte
vacpp.memdbg.aix50.lib
vatools.perf.aix50.lib
memdbg.aix50.adt

After the migration, if there exists AIX 4.2 or AIX 4.3 versions of the above filesets but are missing the AIX 5L versions, you will be required to install them.

STEP 2:

In addition, there are two filesets that require FORCE installing after the migration as they are not operating system specific but create symbolic links to operating system specific directories.

FORCE install the following filesets:

vacpp.cmp.core
vacpp.cmp.tools
 

Components

Note:  Once you have installed VisualAge C++ Version 5.0, you will need to enroll your license for the product before using it.
 

Activating the LUM server

After configuring and starting the LUM server, you can enroll product licenses. Before attempting to enroll a license, you must first ensure that the LUM daemons are active. This can be done with the following command:

# /var/ifor/i4cfg -list

Depending on the type of LUM server configured, the output will be similar to the following:
i4cfg Version 4.5.5 AIX -- LUM Configuration Tool ....
Sous-système      Groupe           PID     Etat
i4lmd                        iforls           15996   active

If no subsystem is listed as active, the start them with the following command:

# /var/ifor/i4cfg -start

The only daemon that must be active is the Nodelock License Server Subsystem (i4llmd) daemon. The other daemons that may be active depending on your configuration are as follows :
 

• License Server Subsystem (i4lmd)
• Central Registry Subsystem (i4gdb)
• Global Location Broker Data Cleaner Subsystem (i4glbcd)

 

License certificate locations

Enrolling Product License Certificate

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

1)  Concurrent Nodelock License Certificate

2)  Concurrent Network License Certificate

3)  Simple Nodelock License Certificate (does not require a license server)

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 LICENSE CERTIFICATES FOR THE VisualAge C++ for AIX PRODUCT ARE CONTAINED IN "/usr/vacpp" AFTER THE VisualAge C++ for AIX PRODUCT HAS BEEN INSTALLED (see "INSTALLING VisualAge C++ for AIX" section.)

The Concurrent Nodelock license certificate is contained in the file "/usr/vacpp/vacpp_cn.lic".  The Concurrent Network license certificate is contained in the file "/usr/vacpp/vacpp_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 (see "INSTALLING LUM" section.)

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:

    - Enrolling using GRAPHICAL USER INTERFACE

        - Select "Products" pull down and click on "Enroll Product" item.
        - Click on "Import" button. The "Import" panel should be displayed.
        - Enter "/usr/vacpp/*.lic" in the "Filter" entry prompt, and press
          ENTER.  This will show the various product license files in the
          "Files" panel.  "vacpp_c.lic" (concurrent network) and "vacpp_cn.lic"
          (concurrent nodelock) should be displayed.
        - Select either "vacpp_c.lic" or "vacpp_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.

    - Enrolling using COMMAND LINE

        - From either the "vacpp_c.lic" or "vacpp_cn.lic" product
          license files from "/usr/vacpp", 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.

4)  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".
 

Compiling with the VisualAge C++

Finding the compiler drivers

Now that the product has been enrolled with LUM, the user may use the
product.  To compile a program through the incremental compiler, invoke
"vacide" or "vacbld" from "/usr/vacpp/bin".

To compile a program through the batch compiler, invoke one of the stanza's (e.g. xlC, xlC_r,
etc.) from "/usr/vacpp/bin". Take a look on defaults options in the file /etc/vacpp.cfg.
 
 

Security, Auditability, and Control

The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
 

VIII. MAINTAINABILITY & SUPPORT STRATEGY

Problem diagnose and reporting

http://epicentre.frec.bull.fr/software/languages/C/

VisualAge C++ V5.0.2 for AIX

•      Base PTFs for VisualAge C++ V5.0.2 for AIX
•      Latest additional PTFs for VisualAge C++ V5.0.2 for AIX

C Compiler V5.0.2 for AIX

•      Base PTFs for C compiler V5.0.2 for AIX

Problem diagnose and reporting

       Product = VisualAgeC++
       Product Version = 05.00.02
       Domain = LANGUAGES
       Symkey = LANGUAGES

Known Problems

              Abstract
                   This is the May 2002 Compilers PTF for VisualAge C++ 5.0.2 for AIX

              Prerequisites
               This May 2002 PTF requires the VisualAge C++ Version 5.0 product to be at Level 5.0.2
               or later.

              Download Description
                   The following APARs were fixed in this PTF:

                   IY29489 explicit tmplt argument spec breaks member def
                   IY29384 Link error: Munch: Error reading input file
                   IY29378 int promoted to unsigned long in 64-bit mode
                   IY29299 #pragma weak causes ICE
                   IY29221 ICE when casting return type to wrong ptr type
                   IY28446 Cant use ptr to fnc as tmplt param (w exceptn)
                   IY28235 'integral constant expression' when decl array
                   IY27632 ERR msg using ptr to mbr func via ptr to class
                   IY29908 Segmentation fault in strlen with opt
                   IY29421 ICE using dynamic_cast & ->* operator
                   IY29397 signal 11 in BE when compiling with -g
                   IY28570 Opt reverses order of initialize & use
                   IY28200 ICE when using -qmaxerr=1:w
                   IY28316 Unable to declare a specialization as a friend
                   IY27682 -qinline causes seg fault at runtime
                   IY27052 Mmbr decl fails if name same as qual namspc
                   IY26294 struct copied with -O fails; passes with -g
                   IY23748 ICE when using nested conditional expr in ctor
                   IY22937 String class assumes that new throws an excptn
                   IY25371 const_mem_fun_t<> arg type should be const T*

                   The following filesets are part of this VATOOLS PTF:
                   vatools.html.help.5.0.2.1
                   vatools.loc.EN_US.lpex.editor.5.0.2.1
                   vatools.loc.JA_JP.lpex.editor.5.0.2.1
                   vatools.loc.Ja_JP.lpex.editor.5.0.2.1
                   vatools.loc.ZH_CN.lpex.editor.5.0.2.1
                   vatools.loc.zh_CN.lpex.editor.5.0.2.1
                   vatools.lpex.editor.5.0.2.1
                   vatools.msg.EN_US.lpex.editor.5.0.2.4
                   vatools.msg.EN_US.sg.5.0.2.2
                   vatools.msg.JA_JP.lpex.editor.5.0.2.4
                   vatools.msg.JA_JP.sg.5.0.2.2
                   vatools.msg.Ja_JP.lpex.editor.5.0.2.1
                   vatools.msg.ZH_CN.lpex.editor.5.0.2.4
                   vatools.msg.ZH_CN.sg.5.0.2.2
                   vatools.msg.en_US.lpex.editor.5.0.2.1
                   vatools.msg.ja_JP.lpex.editor.5.0.2.1
                   vatools.msg.zh_CN.lpex.editor.5.0.2.1

                   The following filesets are part of this Compilers PTF:
                   vac.msg.EN_US.C.5.0.2.1
                   vacpp.cmp.aix41.lib.5.0.2.5
                   vacpp.cmp.aix43.lib.5.0.2.5
                   vacpp.cmp.aix50.lib.5.0.2.5
                   vacpp.cmp.batch.5.0.2.5
                   vacpp.cmp.core.5.0.2.4
                   vacpp.cmp.extension.5.0.2.4
                   vacpp.cmp.include.5.0.2.5
                   vacpp.cmp.incremental.5.0.2.4
                   vacpp.cmp.lib.5.0.2.5
                   vacpp.cmp.tools.5.0.2.5
                   vacpp.ide.5.0.2.4
                   vacpp.ioc.aix41.lib.5.0.2.1
                   vacpp.ioc.aix41.rte.5.0.2.1
                   vacpp.ioc.aix43.lib.5.0.2.1
                   vacpp.ioc.aix43.rte.5.0.2.1
                   vacpp.ioc.aix50.lib.5.0.2.1
                   vacpp.ioc.aix50.rte.5.0.2.1
                   vacpp.ioc.include.5.0.2.1
                   vacpp.ioc.lib.5.0.2.1
                   vacpp.ioc.rte.5.0.2.1
                   vacpp.loc.Ja_JP.cmp.core.5.0.2.4
                   vacpp.loc.en_US.cmp.core.5.0.2.4
                   vacpp.loc.ja_JP.cmp.core.5.0.2.4
                   vacpp.loc.zh_CN.cmp.core.5.0.2.4
                   vacpp.memdbg.aix41.lib.5.0.2.5
                   vacpp.memdbg.aix41.rte.5.0.2.5
                   vacpp.memdbg.aix43.lib.5.0.2.5
                   vacpp.memdbg.aix43.rte.5.0.2.5
                   vacpp.memdbg.aix50.lib.5.0.2.5
                   vacpp.memdbg.aix50.rte.5.0.2.5
                   vacpp.msg.EN_US.cmp.core.5.0.2.1
                   vacpp.msg.EN_US.ioc.rte.5.0.2.1
                   vacpp.msg.JA_JP.ioc.rte.5.0.2.1
                   vacpp.msg.Ja_JP.cmp.core.5.0.2.4
                   vacpp.msg.Ja_JP.ide.5.0.2.4
                   vacpp.msg.Ja_JP.ioc.rte.5.0.2.1
                   vacpp.msg.ZH_CN.cmp.core.5.0.2.1
                   vacpp.msg.ZH_CN.ioc.rte.5.0.2.1
                   vacpp.msg.en_US.cmp.core.5.0.2.4
                   vacpp.msg.en_US.ide.5.0.2.4
                   vacpp.msg.en_US.ioc.rte.5.0.2.1
                   vacpp.msg.ja_JP.cmp.core.5.0.2.4
                   vacpp.msg.ja_JP.ide.5.0.2.4
                   vacpp.msg.ja_JP.ioc.rte.5.0.2.1
                   vacpp.msg.zh_CN.cmp.core.5.0.2.4
                   vacpp.msg.zh_CN.ide.5.0.2.4
                   vacpp.msg.zh_CN.ioc.rte.5.0.2.1
                   vacpp.samples.ansicl.5.0.2.4
                   vacpp.samples.ioc.5.0.2.1
                   vacpp.source.ioc.5.0.2.1
 
 

LUM Frequently Asked  Questions

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)  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?

A2)  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.

Q3)  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?

A3)  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 (see below)
     /etc/ncs/glb_site.txt (if used)
     /etc/ncs/glb_obj.txt

     If you are using Namespace Binding to locate the license server,
     then you do not need the "i4ls.ini" file for this configuration.

     The "glb_site.txt" file is required if the clients are not able
     to reach, via broadcast, the system where the "glbd" is running.

     The "glb_obj.txt" file is required if the license server is running
     in an alternate NCS cell.

Q4)  Occasionally, when I perform a compilation I experience a timelag in
     acquiring a LUM license.  Why?

A4)  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")

Q5)  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?

A5)  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.

Q6)  After correctly installing and configuring my license servers,
     I receive an "unable to open /var/ifor/i4ipc.out" error when
     attempting to use the product.  What is wrong?

A6)  This message is produced by LUM and is a known problem.
     Occasionally, the LUM initialization fails to create this file.
     The workaround is to create the file as root by invoking
     "/usr/bin/touch /var/ifor/i4ipc.out".

Q7)  What is the difference between "i4cfg" and "i4config"?

A7)  "i4cfg" is the GUI version of the LUM configuration tool while "i4config"
     is the command line version.  Read the "USING LICENSE USE MANAGEMENT
     RUNTIME FOR AIX" documentation which comes with LUM for details.

Q8)  What is the correlation between the product version number of LUM and
     the LUM version number in the Object Database Manager (ODM)?

A8)  4.3.0.0 indicates License Use Runtime Version 4.0, which is installed
             automatically with AIX 4.3.0
     4.3.1.0 indicates License Use Runtime Version 4.0.1, which is installed
             automatically with AIX 4.3.1
     4.3.1.1 indicates License Use Runtime Version 4.0.2
     4.3.1.2 indicates License Use Runtime Version 4.0.3
     4.3.2.0 indicates License Use Runtime Version 4.5, which is installed
             automatically with AIX 4.3.2
     4.3.2.1 indicates License Use Runtime Version 4.5.1
     4.3.2.2 indicates License Use Runtime Version 4.5.1 + APAR IX89182
     4.3.2.3 indicates License Use Runtime Version 4.5.2
     4.3.3.0 indicates License Use Runtime Version 4.5.5, which is installed
             automatically with AIX 4.3.3
Q9)  I am unable to invoke the GUI versions of the LUM tools.  What am I
     missing:

A9)  Ensure you have installed the following:

     1.  IPF/X Runtime Support.  This is in the package ipfx.rte that is
         shipped with the AIX installation media.
     2.  License Use Runtime Filesets:  ifor_ls.base.gui and
         ifor_ls.client.gui.

Q10)  I've installed LUM's documentation filesets.  How do I view the
      documentation?

A10)  The HTML documentation is available in "/usr/opt/ifor/ls/os/aix/doc".
      You may use any Web browser.

Q11)  The VisualAge C++ Professional for AIX product is licensed based on
      "Authorized Users".  However, LUM uses the term "Concurrent User."
      What is the difference?

A11)  An Authorized User is a specific user authorized to have local or
      remote access to the Program or any portion of the Program.  A separate
      authorization or Authorized User is required for each specific user
      with local or remote access to the Program or any portion of the
      Program.

      A Concurrent User based on LUM implementation is the equivalent to
      a specific userid on a specific system.

      For example:

      "Steve" is an Authorized User and "owns" three separate userids on a
      system.  "Mary" is not an Authorized User and "owns" one userid.
      In addition, "Steve" and "Mary" share a separate userid.

      Based on the license agreement for this product, "Mary" may NOT access
      the Program or any portion of the Program regardless of the userid
      including the shared userid.  "Steve" may access the Program or any
      portion of the Program by any userid, including the shared userid.

Q12)  Are there any Year-2000 (Y2K) issues with respect to LUM?

A12)  Yes, several tools originally shipped with iFOR/LS were also shipped
      with LUM to provide backwards compatibility.  A few of these tools
      (e.g. "ls_rpt", "ls_admin" and "ls_stat") incorrect display the
      year 2000 as 1900, however, THE ACTUAL LICENSING FUNCTION IS
      UNAFFECTED, AND OPERATES CORRECTLY.  LUM uses newer tools which do
      not have the problem.

      The problems can be resolved by obtaining and applying the PTFs
      for iFOR/LS APAR IX89863.  The PTFs are:

      PTF U464427 (for AIX Version 4.2)
      PTF U463932 (for AIX Version 4.3)

Q13)  When installing the compiler product, I receive an error indicating
      that ifor_ls.client.base and/or ifor_ls.client.gui filesets are
      missing.  What do I do?

A13)  ifor_ls.client.base and ifor_ls.client.gui are "dummy" filesets
      which do not contain any files.  They are used to ensure that an
      older version of LUM (or iFOR/LS) is not installed over the
      current version.  Due to the way LUM is packaged, an error may
      occur if these filesets are not installed.  To fix the product,
      install both filesets.  The filesets are available on the AIX 4.3
      CD media.  They are also shipped with this product for your
      convenience.

Q14)  What is a simple nodelock license and how do I use it?

A14)  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/vacpp/vacpp_n.lic" certificate as indicated in
      the certificate to "/var/ifor/nodelock".