Software Requirements

Important Changes

Note that:

Version 5 Release 18 does not support Windows 2000 Professional
Version 5 Release 18 does not support AIX 5.2
Version 5 Release 18 does not support Solaris 8
Version 5 Release 18 does not support SGI IRIX

Common Software Requirements

Version 5 runs on selected system levels of:

Windows XP
IBM AIX
Hewlett Packard HP-UX
Sun Solaris.

Refer to the Program Directory or contact your IBM Support Center, for appropriate corrective service to apply to the software described in the topics that follow.

Version 5 Release 18 prerequisites Orbix 3.3 on 32-bit OS.

Windows XP

Minimum level required: Windows XP Professional Edition with SP1 or SP2, with the following components:

A Microsoft implementation of OpenGL libraries, as delivered with Windows XP.
For recommendations related to driver levels based on tested graphic adapters, visit:

http://www.3ds.com/implementation/technology/windows/certified-workstations-list/

Regarding the localized versions of “Windows XP Professional Edition 32-Bit” (and the “Multilingual User Interface” Packs which can be installed upon the English version of Windows XP Professional Edition 32-Bit, the use of CATIA has been validated with the following versions of Windows:

Windows XP Professional 32-Bit (English) 32-Bit
Windows XP Professional 32-Bit (Japanese) 32-Bit
Windows XP Professional 32-Bit (Korean) 32-Bit
Windows XP Professional 32-Bit (Simplified Chinese) 32-Bit.

CATIA V5 64-bit on Windows XP Professional x64 Edition

Minimum level required: Windows XP Professional x64 Edition, and the following components: a Microsoft implementation of OpenGL libraries, as delivered with Windows. For recommendations related to driver levels based on tested graphic adapters, visit:

http://www.3ds.com/implementation/technology/windows/certified-workstations-list/

CATIA V5 32-bit on Windows XP Professional x64 Edition

Note: because CATIA has been ported onto 64-bit Windows XP, for customized applications related to CATIA please use 64-bit Internet Explorer. Consequently:

use 64-bit Internet Explorer 6 for 64-bit V5 on Windows XP Professional x64 Edition
use 32-bit Internet Explorer 6 for 32-bit V5 on 32-bit Windows and Windows XP Professional x64 Edition.

IBM AIX 32 or 64-bit

AIX Version 5.2 ML7, with the following components:

IBM C Set++ for AIX Application Runtime at a minimum level of 6.0.0.
IBM XL Fortran Runtime Environment for AIX at a minimum level of 8.1.1.
OpenGL and GL3.2 Runtime Environment (delivered with the operating system)
Common Desktop Environment (CDE) (delivered with the operating system)
Motif 2.1 on AIX 32-bit
JRE 1.3.1.

AIX Version 5.3 ML3 with following components:

IBM XL C/C++ for AIX Application Runtime at a minimum level of 7.0.0.
IBM XL Fortran Runtime Environment for AIX at a minimum level of 9.1.0.
OpenGL and GL3.2 Runtime Environment (delivered with the operating system)
Common Desktop Environment (CDE; delivered with the operating system)
Motif 2.1 on AIX 32-bit.

Additional Support for AIX Run time is AIX 5.3 ML03 (on 32-Bit and 64-Bit). On Power 4 and Power 5 only.

Important Notice about AIX Support

Customers currently running CATIA and ENOVIA on AIX V5.1 or 5.2 are encouraged to migrate to AIX 5.3.

HP-UX

HP 11i #Dec 2003 and HP-UX 11.i #Dec2004 with the following components:

ANSI C++ Runtime Environment (aC++, at a minimum level of 3.50, delivered with the operating system)
HP Fortran 90 Runtime Environment (delivered with the operating system)
OpenGL 3D API Runtime Environment
CDE (delivered with the operating system)

A localized version of the operating system may be required when the selected installation differs from ISO code pages.

Sun Solaris

Sun Solaris 10 with the following components:

C and C++ runtime environment (delivered with the operating system)
OpenGL runtime environment (delivered with the operating system) at level 1.3, depending on the graphic adapter
Fortran runtime environment (delivered with CATIA V5)
CDE (delivered with the operating system)
Motif 2.1

A localized version of the operating system may be required when the selected installation differs from ISO-1.

Additional Support for SOLARIS runtime on the SPARC system is Solaris 10.03/05 (on 32-bit only).

Additional Software Requirements

For Specific CATIA Products

CATIA - V4 Integration 2 (V4I) requires, on the CATIA Version 5 client, for interoperability with CATIA Version 4 CDM and ENOVIA VPM 1:

if the database server is DB2:
- on AIX, Windows, HP-UX 11.11 or Solaris: DB2 UDB Version 8.2.4
- on HP-UX 11.0: DB2 UDB Version 7.2 FP 10a
if the database server is Oracle:
- on AIX, Windows, HP-UX or Solaris: Oracle Version 9.2.0.3 or Oracle 10qR2 on SP
Note: Please contact your IBM or Oracle local representative for support and planning information on DB2 UDB or Oracle.

CATIA Version 4 CDM and ENOVIA VPM interoperability is available through CATIA - V4 Integration 2 (V4I) for the following products:

CATIA - ASSEMBLY DESIGN 2 (ASD)
DMU Kinematics Simulator 2 (KIN).

Interoperability of CATIA Version 5 on the supported Windows platforms with ENOVIA VPM through ENOVIA 3d com requires, on the client side, either (depending whether the database server is a DB2(R) or an Oracle server):

DB2 UDB Version 8.2.2 Client for Windows
Oracle Client Version 9.2.0.3 for Windows.

Math Kernel Libraries: on Intel architecture in a Windows XP environment, the use of Intel Math Kernel Libraries (MKL) can improve the performance of the following products:

CATIA - Generative Part Structural Analysis 1 (GP1)
CATIA - Generative Part Structural Analysis 2 (GPS)
CATIA - Generative Assembly Structural Analysis 2 (GAS)
CATIA - Elfini Structural Analysis 2 (EST)
CATIA - Tolerance Analysis of Deformable Assembly 3 (TAA)
CATIA - PRODUCT ENGINEERING OPTIMIZER 2 (PEO)
CATIA - Generative Dynamic Response Analysis 2 (GDY).

MKL Libraries may be obtained from:

http://developer.intel.com/software/products/mkl/

This requirement is optional. Only the latest version of Intel MKL can be found on the site. In this case, you can download it from the Intel FTP site.

Access to Online Documentation

Product information is delivered on the product CDs in HTML format. An HTML browser is required to access this documentation.

UNIX (AIX, HP-UX, Solaris)

Mozilla 1.7 with Java plug-in installed.

Windows

One of the following browsers is required:

Microsoft Internet Explorer at a minimum level of 6.0
Mozilla 1.7 with Java plug in installed.

In addition to a Java-enabled Web browser, Java Plug-in at level 1.4 is required to search online documentation.

For AIX, it is provided with the operating system or can be downloaded from:

http://www.ibm.com/developerworks/java/jdk/aix/service.html

For HP-UX, it can be downloaded from:

http://www.hp.com/products1/unix/java/java2/jpi/downloads/ index.html

For Sun Solaris, it can be downloaded from

http://java.sun.com/j2se/

For Microsoft Windows, only the 1.4 Plug-in distributed by Sun is supported. It can be downloaded from:

http://java.sun.com/j2se/

Although access to the online documentation might work on other HTML browsers, incidents specific to browsers other than those specified are not eligible for support.

Licensing

Windows workstations must have an active LAN card (Ethernet or token ring) and TCP/IP installed and properly configured, but there is no need to have the workstations connected to the network.

No additional software is required when accessing nodelock licenses.

License Use Management (LUM) is required to serve concurrent licenses across a network. A LUM configuration file (i4ls.ini) is required on clients to access concurrent licenses from these servers.

Server and nodelock licensing mechanisms are available for P1, P2 and P3, on all supported operating environments (Windows XP, AIX, HP-UX and Solaris).

IBM LUM minimum level 4.6.8 is required on all platforms.

IBM License Use Management 4.6.8 is shipped with Version 5. Other versions of LUM may be obtained, at no charge, from:

http://www.ibm.com/software/lum

IBM License Use Management High-Availability Licensing (HAL) enables you to set up an environment in which there is a very high degree of certainty that concurrent licenses will be available, even if a network license server goes down.

When you use this option, you create a cluster of network license servers. A cluster is a group of from 3 to 12 network license servers that jointly serve vendor-managed concurrent licenses that are enrolled on the cluster rather than on an individual server.

If you decide not to use HAL, when the server goes down, your Version 5 session remains active and another license is requested from another license server. If the license is granted, the total number of licenses granted is increased by one. With HAL, if the license is granted, the total numbers of licenses granted stays the same.

Consider that for HAL cluster members, it is strongly recommended to upgrade all the servers to LUM Version 4.6.8.

For more information about High-Availability Licensing, refer to the LUM documentation "Using License Use Management Runtime" for your platform.

Macro Replay Capabilities

Version 5 has built-in macro record and replay capabilities.

For UNIX, the interpreter is VB Script 3.0 from Mainsoft. Its components are included in Version 5 as shared libraries.

For Windows, the interpreter is either:

Visual Basic Script (VB Script) at minimum level 5.0. It is delivered with Microsoft Internet Explorer. VB Script libraries at level 5.0.0.3715 are delivered with Microsoft Internet Explorer 5.0 or at later levels with later versions of Microsoft Internet Explorer. Use of VB Script is recommended for developing Windows/UNIX compatible macros.
Microsoft Visual Basic for Applications (VBA) at minimum level 6.0. VBA is delivered and installed by default with Version 5.

Printer and Plotter Support

Windows

Printers and plotters are supported through the vendor's drivers for the targeted printer of plotter relative to the targeted version of the operating system. Contact the printer or plotter vendor for requirements and support.

UNIX

Version 5 provides support for the following plotter/printer languages:

CGM-ISO, ATA, CALS
Hewlett Packard HP-GL/2-RTL and HP-GL or IBM-GL subsets
OCE Graphics GPR50: VDF plotting routines
PostScript.

Batch monitoring

Using MQSeries communication tools, some batch operations can now be launched remotely. When implemented at the batch level, this optional feature requires MQSeries at minimum level 6.0.

Visit:

http://www.ibm.com/software/ts/mqseries/messaging/

for availability of client and server components on supported platforms.

MQSeries Client is required on systems where the transaction is initiated; MQSeries Server is required on systems where remote batches are executed.

Accessing more than 1.0 GB of data on AIX

This section describes necessary settings to get access to more than 1.0 GB on AIX for allocations of data within a V5 process.

Background

This behavior is only applicable to 32-bit Version 5 processes.

By default, Version 5 processes (32-bit) on AIX can allocate up to 1.0 GB. It is possible to override the default allocation capabilities up to 2.0 GB. Such a capability requires additional tunings in order to be effective :

From an operating system standpoint
From a Version 5 standpoint

Operating System required customizations

To get access to more than 1.0 GB for allocating data, the X server must be configured to use extended shared memory. To enable this support, do the following :

Modify /usr/lpp/X11/defaults/xserverrc shell script to add :
EXTSHM=ON
export EXTSHM
before execution of the X process in the shell script (for example, just before environment variable EXTENSIONS is set in the shell script).
Reboot workstation or restart the X server to take modification into account.

Version 5 required customizations

Large Memory Model

The capability to allocate more than 1.0 GB on AIX is controlled by an environment variable : V5MEM. This environment variable can take an integer value from 5 to 8 , and controls the number of 256 MB segments that Version 5 can allocate. By default, this environment variable is not set. When set, the environment variable is checked by catstart shell script, which will set the environment accordingly.

When V5MEM is not set, Version 5 will be able to allocate up to 1.0 GB (operating system customizations are not required)
When V5MEM is set, operating system customizations are required; V5MEM=5 will give access to 1.25 GB; V5MEM=8 will give access to 2.0 GB of address space for data allocated during the Version 5 session. In all cases, it is recommended to have the paging space sized accordingly.

Very Large Memory Model

Under AIX 5.2 and AIX 5.3 running the 64-bit kernel, Version 5 will be able to allocate up to 2.25 GB, but the following customization is required:

required patch : IY53656

before launching CNEXT :

export V5MEM=8

catstart -run /bin/ksh

export LDR_CNTRL=PREREAD_SHLIB@MAXDATA=0xD0000000@DSA

export MW_GMA_VADDR to 0xD8000000

export DISPLAY=<hostname>:0

export EXTSHM=ON

start CNEXT

Additional Operating System considerations

One cannot execute a Version 5 session with V5MEM set simultaneously with another Version 5 session for which V5MEM is not set. When several session need to run simultaneously on the same workstation, they should share the same V5MEM setting, or be executed with V5MEM unset.
This behavior is only applicable to 32bit Version 5 processes, those V5 Customizations should be removed for a 64-bit Version 5 process.

Accessing more than 2.0 GB of memory on HP-UX

This section describes necessary settings to get access to more than 2.0 GB of memory on HP-UX within a V5 process.

Background

By default, Version 5 processes on HP-UX can allocate up to approximately 1.9 GB of memory for storing data. The 4 GB address space offered by the operating system being split into 4 quadrants of 1 GB each; most of first 2 quadrants are reserved for private data allocations, most of last 2 quadrants are reserved for shared objects. It is possible to increase the default data allocation capabilities up to approximately 3.0 GB (1 GB remains for shared objects). Such capability requires additional settings in order to be effective :

From an operating system standpoint
From a Version 5 standpoint

Operating System settings

The maxdsiz kernel parameter, which controls the amount of private data each process can handle, should be sized to accommodate up to 3 GB of data. Therefore maxdsiz should be set to 0xC0000000 through sam or kmtune utilities.
Amount of Real memory and swap space should be sized accordingly. Increasing maxswapchunks kernel parameter may be necessary to accommodate additional swap space.
Increasing swap space and changing kernel parameters require root authority.
If running in the POSIX shell (/usr/bin/sh) make sure that ulimit data parameters is set to unlimited.

Version 5 required customizations

Since R14 the CNEXT main executable is already flagged to enable the use of the third quadrant. One can disable it by using the chatr command ( this operation requires root authority on default installation) :

Locate and make a backup copy of the main executable (say, for example, CNEXT, generally found in /usr/DassaultSystemes/B18/hpux_b/code/bin
The same pattern is applicable for ENOVIA DMU or DELMIA main executables, or other V5 main executables).
get write access on CNEXT executable :
chmod +w CNEXT
run chatr command on CNEXT, in order to enable use of third quadrant for private data
chatr +q3p disable CNEXT
Output of above command should be similar to :
...
data segment locking disabled
third quadrant private data space disabled
fourth quadrant private data space disabled
third quadrant global data space disabled
data page size: 1M
instruction page size: 1M
nulptr references disabled
shared library private mapping disabled
shared library text merging disabled
reset permissions on file to original permissions
chmod -w CNEXT

One can go back to initial behavior by restoring the original copy or enabling the use of the third quadrant :

run chatr command on CNEXT, in order to enable use of third quadrant for private data
chatr +q3p enable CNEXT
Output of above command should be similar to :
...
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
third quadrant private data space enabled
fourth quadrant private data space disabled
third quadrant global data space disabled
data page size: 1M
instruction page size: 1M
nulptr references disabled
shared library private mapping disabled
shared library text merging disabled
reset permissions on file to original permissions
chmod -w CNEXT

Accessing more than 2.0 GB of memory on Windows XP

This section describes necessary settings to get access to more than 2.0 GB of memory on Windows XP within a V5 process.

Background

By default, Version 5 processes on Windows can allocate up to 2.0 GB of memory for storing data and code. The 4 GB address space offered by the operating system being split in two areas of 2 GB each, first 2 GB for user mode, 2 other GB being reserved by the kernel. On Windows XP, it is possible to increase the default allocation capabilities up to 3.0 GB (3 GB for user mode, 1 GB reserved for kernel). Such capability requires additional tunings in order to be effective :

From an operating system standpoint
From a Version 5 standpoint

Operating System requirements

Windows XP Professional is required.
A modification of boot.ini file is needed to activate this capability at the system level. The boot.ini switch /3GB needs to be added in order to make 3 GB available for user mode applications. For example :
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB" /fastdetect /3GB
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
Notes :
- Improper modification of the boot.ini file can cause the operating system to be inoperable.
- For testing purposes of a given hardware configuration, it might be preferable to create several entries in the [operating systems] stanza, as documented in above example, as well as leave a non zero timeout, to allow user selection at boot time between regular boot and boot with the /3GB option; this can allow easy recovery in case the /3GB option causes a problem described in section Additional Operating Considerations below.
- Modification of the boot.ini file requires administrative privileges.
- Do not add the /3GB switch if running Windows 2000 Professional.
- boot.ini file can me modified using bootcfg.exe utility delivered with Windows XP (see http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q291980 for further details on bootcfg.exe utility) or by editing the file :
  1. boot.ini is generally found at the root of C: drive; in a command session (cmd.exe), make file editable :
    attrib C:\boot.ini -r -s
  2. edit, modify and save file
  3. reset file attributes :
    attrib C:\boot.ini +r +s
  4. reboot system to make the change effective
Amount of Real memory and paging space should be sized accordingly.
See the "Additional Operating System consideration" section in this page to size the number of free System Page Table Entries

Version 5 required customizations

Since R14, the Version 5 main executable is already "Large Address Space Aware", to get access to the 3GB of address space .

To disable the use of the "Large Address Space" :

Customers having access to Microsoft Visual Studio 6 development environment or Microsoft Visual .Net environment can use editbin.exe (generally found in C:\Program Files\Microsoft Visual Studio[ .Net]\VC98 [VC7]\bin), the syntax is as follows :
- edibin.exe /LARGEADDRESSAWARE:NO CNEXT.exe

To go back to the initial behavior after disabling the large address space capability, one can use :

run imagecfg.exe on CNEXT.exe
- in a command session, execute imagecfg.exe -l CNEXT.exe
- output of above command should be similar to :
  CNEXT.exe contains the following configuration information:
  Subsystem Version of 4.0
  Stack Reserve Size: 0x100000
  Stack Commit Size: 0x1000
  CNEXT.exe updated with the following configuration information:
  CNEXT.exe contains the following configuration information:
  Subsystem Version of 4.0
  Image can handle large (>2GB) addresses
  Stack Reserve Size: 0x100000
  Stack Commit Size: 0x1000
- imagecfg.exe utility can be found on the Windows 2000 Server Resource Kit Supplement One.
or editbin.exe /LARGEADDRESSAWARE CNEXT.exe

Additional Operating System considerations

Some driver may not load correctly when /3GB switch is added to boot.ini. In such case, one would need to apply Service Pack 1 on Windows XP, and tune /3GB configurations with /USERVA switch in boot.ini file. See :
Driver May Not Be Loaded with the /3GB Switch
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q319043
Microsoft recommends that the number of free PTEs must be greater than 24000 . You can monitor the PTE consumption by using the System Monitor tool or perfmon. The object to monitor is "Free System Page Table Entries." When using the /3GB option and if the value observed is less that 24,000, you should reduce this value in 64 MB steps until values larger than 24 kilobytes (KB) to 26 KB are observed . You can do that by setting the /USERVA value to 3GB - (n x 64 MB) in the boot.ini . See Microsoft article "How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB" http://support.microsoft.com/?kbid=316739 .
If you upgrade your computer to Windows XP Service Pack 1 (SP1) and you are using the /3GB switch or the /USERVA switch with the /3GB switch, Windows may not start. You may also receive an error message that states that one of the registry hives is corrupted. A supported fix is available from Microsoft through article
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328269
If you upgrade your computer to Windows XP Service Pack 2 ( SP2) and you are using the /3GB switch, CATIA may crash when using macro . KB890048 associated to the SRZ041014003627 case is correcting this problem. This fix can be provided by Microsoft on demand.

OpenGL Shaders and CgFX on Windows

OpenGL shaders are only available on Windows 32-bit (2000 or XP) and Windows 64-bit platforms.

Within Version 5 Products, certain advanced functionalities (used in the Real Time Rendering and FreeStyle applications) require the use of OpenGL shaders, and these shaders are implemented with the CgFX API (Nvidia).

These advanced visual effects (like advanced realistic materials) work on all the following graphics cards: nVIDIA, ATI, 3DLabs. (refer to the Program Directory for details graphics cards and drivers that have been certified for OpenGL shaders for Version 5).

To be able to benefit from OpenGL shaders, there is no need to download the Cg toolkit from the nVIDIA website since Cg Package Version1.5 ((C) Cg copyright 2006 Nvidia Corporation) is shipped on V5 medias.