IBM Frozen Dessert Maker AIX 4.3 User manual

ibm.com/redbooks

Redpaper

IBM

Front cover

AIX 4.3 to AIX 5L Migration

in a CATIA and ENOVIANOVIA

Environment

Volker Haug

Gregor Linzmeier

Exploring migration methods

Migration planning tips

Checklists included

International Technical Support Organization

AIX 4.3 to AIX 5L Migration in a CATIA and ENOVIA

Environment

December 2003

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule

Contract with IBM Corp.

First Edition (December 2003)

This edition applies to AIX 5L Version 5.1, program number 5765-E61.

Comments may be addressed to:

IBM Corporation, International Technical Support Organization

Dept. JN9B Building 003 Internal Zip 2834

11400 Burnet Road

Austin, Texas 78758-3493

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the

information in any way it believes appropriate without incurring any obligation to you.

Note: Before using this information and the product it supports, read the information in “Notices” on page v.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1. Supported hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Supported hardware for AIX 5L. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.2 Supported hardware for CATIA and ENOVIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.3 Supported software levels for CATIA and ENOVIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. Migration methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Definition of migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2 Reasons to migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3 Migration methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3.1 Migration installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3.2 New and complete overwrite installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3.3 Preservation installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.4 Migration sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.4.1 AIX and compiler CDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4.2 Network Installation Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.5 Alternate disk migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3. Planning the migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Shell scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.2 CDE or TCL/Tk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.3 Microcode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.4 IBM Sserver pSeries Customer-Managed Microcode . . . . . . . . . . . . . . . . . . . . . . . . 14

3.5 Installation preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.6 AIX and compiler runtime download Web sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.6.1 AIX fix delivery center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.6.2 FORTRAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.6.3 C++ runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4. Starting the migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1 Hardware layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2 Migration using NIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 5. Migration experiences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.1 Post-migration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.2 Migration experiences for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.2.1 Umlaute on a German language keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.2.2 Activating spaceball or spacemouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.2.3 Netscape cannot be launched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.2.4 Documentation cannot be launched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.2.5 AIX CDE login hang . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.3 Migration experiences for CATIA and ENOVIA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iv CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Appendix A. Fileset and bundle information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

AIX Version 4.3.3 ML10 filesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

AIX 5L Version 5.1 ML05 filesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

AIX 5L Version 5.1 Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Appendix B. Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Client checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Server checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult

your local IBM representative for information on the products and services currently available in your area. Any

reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,

program, or service may be used. Any functionally equivalent product, program, or service that does not

infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to

evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The

furnishing of this document does not give you any license to these patents. You can send license inquiries, in

writing, to:

IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are

inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of

express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made

to the information herein; these changes will be incorporated in new editions of the publication. IBM may make

improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time

without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any

manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the

materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring

any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published

announcements or other publicly available sources. IBM has not tested those products and cannot confirm the

accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the

capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them

as completely as possible, the examples include the names of individuals, companies, brands, and products.

All of these names are fictitious and any similarity to the names and addresses used by an actual business

enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming

techniques on various operating platforms. You may copy, modify, and distribute these sample programs in

any form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which the sample

programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,

cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and

distribute these sample programs in any form without payment to IBM for the purposes of developing, using,

marketing, or distributing application programs conforming to IBM's application programming interfaces.

vi CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,

other countries, or both:

AIX®

AIX 5L™

BladeCenter™

C Set ++®

DB2®

DFS™

™

^™

IntelliStation®

IBM®

Micro Channel®

PowerPC 604™

PowerPC®

pSeries®

POWER2™

POWER3™

POWER4™

POWER4+™

Redbooks(logo) ™

RS/6000®

SOM®

SOMobjects®

Tivoli®

TME®

VisualAge®

The following terms are trademarks of other companies:

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other

countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the

United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,

Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic

Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.

Preface

This IBM Redpaper is a guide covering the migration of the AIX operating system from AIX

Version 4.3 to AIX 5L in a CATIA or ENOVIA environment.

This document was written to guide an AIX administrator through the steps of a migration to

AIX 5L, and provides the experiences made during the migration from AIX Version 4.

Professionals wishing to acquire a better understanding of the migration process may

consider reading this document. The intended audience includes:

򐂰 Customers

򐂰 Sales and marketing professionals

򐂰 Technical support professionals

򐂰 IBM Business Partners

This publication does not replace the latest pSeries and PLM marketing materials and tools. It

is intended as an additional source of information that, together with existing sources, may be

used to enhance your knowledge of software migration. During the development of this

publication, several migrations were performed to successfully verify software migration on

different machines and configurations.

At the time of writing, Dassault Systemes AIX 5L support for CATIA and ENOVIA is only on

Version 5.1. However, since the support for AIX 5L Version 5.2 is planned for the near future,

this documentation can also be used to migrate into a AIX 5L Version 5.2 environment.

For specific information about the differences between AIX releases refer to the AIX

Differences Guide Version 5.2 Edition, SG24-5765, which describes AIX 5L Version 5.1 and

5.2 enhancements.

The team that wrote this Redpaper

This Redpaper was produced by a team of specialists from around the world working at the

International Technical Support Organization, Austin Center, and remote locations.

Volker Haug is a Certified Senior IT specialist for pSeries and RS/6000® systems in

Stuttgart, Germany. He has more than 16 years of experience in the IT industry, and holds a

degree in Business Management from the University of Cooperative Education in Stuttgart.

Volker is the worldwide pSeries technical support community leader for IBM UNIX

workstations, entry servers, and IBM Sserver BladeCenter JS20 supporting IBM sales,

Business Partners, SIs and ISVs. His areas of expertise include IBM UNIX workstations and

servers, BladeCenters, graphics, MCAD applications, and AIX® systems management.

Gregor Linzmeier is an IBM Advisory IT Specialist for RS/6000 and pSeries workstation and

entry servers as part of the Web Server Sales Organization in Mainz, Germany. Gregor is a

member of the Workstation Technology Focus Group, supporting IBM sales, Business

Partners, and customers with pre-sales consultation and implementation of client/server

environments. He has worked for more than 13 years as an infrastructure specialist for RT,

RS/6000, pSeries, and AIX in large CATIA or electronics design projects.

viii CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Thanks to the following people for their contributions to this project:

Karsten Schönberg

Bertrandt, Germany

Christian Setzer

CompuNet, Germany

Ekkehard Blauth and Matthias Hoffmann

Porsche, Germany

Rolf Simon

VW Gedas, Germany

Kenneth D. Fox and Gary Hornyak

IBM Austin

Christof Schwab

IBM Germany

Scott Vetter

IBM Austin

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with

specific products or solutions, while getting hands-on experience with leading-edge

technologies. You'll team with IBM technical professionals, Business Partners and/or

customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus,

you'll develop a network of contacts in IBM development labs, and increase your productivity

and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our papers to be as helpful as possible. Send us your comments about this

Redpaper or other Redbooks in one of the following ways:

򐂰 Use the online Contact us review redbook form found at:

ibm.com/redbooks

򐂰 Send your comments in an Internet note to:

redboo[email protected]m.com

򐂰 Mail your comments to:

IBM Corporation, International Technical Support Organization

Dept. JN9B Building 003 Internal Zip 2834

11400 Burnet Road

Austin, Texas 78758-3493

Chapter 1. Supported hardware

This chapter provides a brief description of the supported pSeries hardware models for AIX

and the hardware supported for CATIA and ENOVIA. To prevent a time-consuming analysis,

all implemented workstation and server hardware should be checked for AIX 5L Version 5.1

and AIX 5L Version 5.2 compatibility.

At the time of writing, Dassault Systemes supports AIX 4.3.3 and AIX 5L Version 5.1 for

CATIA and ENOVIA.

1

2 CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

1.1 Supported hardware for AIX 5L

AIX 5L Version 5.1 runs on most IBM IntelliStation POWER series, IBM RS/6000, and IBM

Sserver pSeries systems. These include the IntelliStation POWER 265 and 275; the pSeries

620, p640, p670, p680, p690; and all models of p610, p615, p630, and p660. The support for

AIX 5L Version 5.1 includes RS/6000 Models 150, 170, 260, 270, F50, F80, H50, H70, H80,

M80, S70, S7A, S80, and selected older models.

To find out more about supported and unsupported systems, see the Release Notes for

AIX 5L Version 5.1 or 5.2. The latest version can be obtained from the IBM Sserver pSeries

Information Center at:

http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/

The Information Center is an information portal for AIX and pSeries customers. From this site,

information can be accessed, such as AIX documentation, hardware documentation,

messages database for 7-digit error codes, links to Redbooks, and much more.

AIX 5L Version 5.1 supports various RS/6000 and pSeries models in a 32-bit and 64-bit

environment. Three unique hardware architectures are supported:

򐂰 Micro Channel Architecture (MCA)

򐂰 Power Reference Platform (PreP)

򐂰 Common Hardware Reference Platform (CHRP)

As the root user, use the bootinfo -p command to determine the architecture of the system.

Table 1-1 lists the possible results of the bootinfo - p command depending on the various

RS/6000 or pSeries models.

Table 1-1 Different hardware architectures

The 64-bit kernel requires 64-bit hardware. At the time of writing, the following RS/6000 and

pSeries models support a 64-bit kernel:

򐂰 IntelliStation POWER Model 265

򐂰 IntelliStation POWER Model 275

򐂰 RS/6000 7013 Models S70 or S7A

򐂰 RS/6000 7015 Models S70 or S7A

򐂰 RS/6000 7017 Models S70, S7A or S80

򐂰 RS/6000 7025 Models F80

򐂰 RS/6000 7026 Models H70, H80 or M80

򐂰 RS/6000 7043 Models 260, 270

򐂰 RS/6000 7044 Models 170, 270

򐂰 Sserver pSeries 610 Models 6C1 or 6E1

򐂰 Sserver pSeries 615 Models 6C3 or 6E3

Hardware architecture Output received from bootinfo -p command

Micro Channel Architecture rs6k

Power Reference Platform rspc

Common Hardware Reference Platform chrp

Chapter 1. Supported hardware 3

򐂰 Sserver pSeries 620 Models 6F0 or 6F1

򐂰 Sserver pSeries 630 Models 6C4 or 6E4

򐂰 Sserver pSeries 640 Model B80

򐂰 Sserver pSeries 650 Model 6M2

򐂰 Sserver pSeries 655 Model 651

򐂰 Sserver pSeries 660 Models 6H0, 6H1 or 6M1

򐂰 Sserver pSeries 670

򐂰 Sserver pSeries 680 Model S85

򐂰 Sserver pSeries 690

At the time of writing, Dassault Systemes AIX 5L support is only for Version 5.1. However, the

support for AIX 5L Version 5.2 is planned for the future.

1.2 Supported hardware for CATIA and ENOVIA

Dassault Systemes supports different processor architectures for RS/6000, IntelliStation

POWER series, and pSeries. These include the PowerPC 604e, POWER2, POWER3, and

POWER4.

Different graphic accelerators are supported along with the workstation hardware, such as the

GXT2000P, GXT3000P, GXT4000P, GXT4500P, GXT6000P, and GXT6500P, to name several.

Refer to the latest program directories of the various CATIA and ENOVIA products for a list of

the hardware requirements. The program directories can be obtained from:

http://techsupport.services.ibm.com/engineering/techknow?expanded=catiacfg#catia

1.3 Supported software levels for CATIA and ENOVIA

Table 1-2 lists a brief overview of the minimum required software levels for CATIA.

Table 1-2 Minimum required software levels for CATIA

Note: With AIX 5L Version 5.2 all RS/6000 models that are Micro Channel or Power

Reference Platform systems are no longer supported.

Hardware AIX level Compiler/runtime

level

Additional PTFs

IntelliStation POWER

275 (9114-275)

workstation

AIX 5L Version 5.1

ML 04 or higher

C Set ++ Runtime for

AIX 5.0 at level 6.0.0.1

XL Fortran Runtime

Environment at 7.1.1.3

IY45738 - Pointer

Markers Disappear In

CATIA

pSeries 630 Model

6E4 (7028-6E4)

workstation

AIX 5L Version 5.1

ML 03 or higher

C Set ++ Runtime for

AIX 5.0 at level 6.0.0.1

XL Fortran Runtime

Environment at 7.1.1.3

IY35110 - Shared Lib

Segment Nearly Full

Can Crash System

IY37937 -

VEOTEXTURE

Application Hangs

When Using Multiple

Textures

4 CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Table 1-3 lists the minimum required software levels for ENOVIA.

Table 1-3 Minimum required software levels for ENOVIA

Refer to the latest program directories of the various CATIA and ENOVIA products for a list of

the software requirements.

Provided are the base minimum required software levels for CATIA and ENOVIA. However,

we recommend installing the latest available AIX maintenance package as additional service.

At the time of writing, AIX 5100-05 maintenance package (IY48486) is available.

If you have dependencies with other software applications, ensure that you install at least the

minimum level.

Any other PowerPC

604e or POWER3

workstation

AIX Version 4.3.3

ML 06 or higher

or

AIX 5L Version 5.1

ML 02 or higher

C Set ++ Runtime for

AIX 4.3 at level 4.0.2

XL Fortran Runtime

Environment at 5.1.0

or 5.1.1

Hardware AIX level Compiler/runtime level

POWER4+ server AIX 5L Version 5.1

ML 04 or higher

C Set ++ Runtime for AIX 5.0 at level 6.0.0.1

XL Fortran Runtime Environment at 7.1.1.3

POWER4 server AIX 5L Version 5.1

ML 02 or higher

C Set ++ Runtime for AIX 5.0 at level 6.0.0.1

XL Fortran Runtime Environment at 7.1.1.3

Any other PowerPC 604e

or POWER3 server

AIX Version 4.3.3

ML 06 or higher

or

AIX 5L Version 5.1

ML 02 or higher

C Set ++ for AIX Application Runtime 5.0.2.7

XL Fortran Runtime Environment for AIX at

minimum level 5.1.0, 7.1.0, or 7.1.1

Hardware AIX level Compiler/runtime

level

Additional PTFs

Chapter 2. Migration methods

This chapter provides an introduction to migration and explains why customers should

migrate to AIX 5L. The following different migration methods are described in detail:

򐂰 Migration installation

򐂰 New or complete overwrite installation

򐂰 Preservation installation

This chapter also describes the various resources that can be used for a migration, such as

CD-ROM, Network Installation Management, or alternate disk.

2

6 CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

2.1 Definition of migration

The term migration is defined in the information technology field as the change of one

operating environment for another. This can involve moving to new hardware, to new

software, or both.

In the way it is used in this document, migration is defined as an upgrade of an operating

system (OS), but although the words upgrade and migration are often used interchangeably,

there is a difference:

򐂰 An

upgrade refers to an addition to an existing system. This could be the installation of a

Programming Temporary Fix (PTF) or maintenance level within a particular release of AIX.

򐂰 The term

migration for this document means to move the software of a system

environment from one AIX version or release to a different one; in our case, from AIX

Version 4.3 to AIX 5L Version 5.1.

The new OS version that is installed replaces the existing operating system, removing

software that is no longer used and installing new software that enhances the usability of

the upgraded system. The new release also provides a new revised kernel. AIX 5L

provides either 32-bit or 64-bit kernels.

The difference between a migration and a complete overwrite installation is that the root

volume group is kept with all of its file systems except /tmp, which is deleted and rebuilt while

migrating.

There is a third way to install the operating system, which is the preservation installation. It

only keeps the /home directory with the user files but overwrites the other file systems of the

root volume group.

2.2 Reasons to migrate

This section is intended to answer the first question you should ask when we try to convince

you to migrate to AIX 5L:

“This sounds like a lot of work and expense. Why should I? What’s in it for me?”

The answer has two parts:

򐂰 If your environment is stable and you do not intend to make any changes or additions

whatsoever in the future, you could stay with your current version of AIX. But, if you want

to take advantage of the new AIX 5L function, such as online backups, a migration is worth

it.

򐂰 Since AIX 4.3.3 was withdrawn from marketing (WDFM) in June 2003 and from service

(WDFS) December 31, 2003, there is a valid reason to migrate in a CATIA or ENOVIA

environment. After December 31, 2003 there is no direct method to receive defect

support.

2.3 Migration methods

The following section describes the various migration methods and their advantages and

disadvantages. To provide a complete overview about the migration methods, we also

describe the preservation installation. Based on our customer experiences, we see the

migration installation or new and complete overwrite installation as the preferred methods to

move to AIX 5L.

Chapter 2. Migration methods 7

2.3.1 Migration installation

Migration installation is the default method to move from AIX 3.2 or any release of AIX Version

4 to AIX 5L. During a migration, the installation process determines which optional software

products are installed on the existing version of the operating system. Any configuration file

that cannot be migrated will be saved in a specific directory under /tmp. System messages

will inform you of the location of the saved files. Information will also be stored in the system

installation log /var/adm/ras/devinst.log.

The migration process attempts to preserve all user configuration, while moving the operating

system to a new level of software.

The advantage of a migration installation compared to a new and complete overwrite is that

many files are preserved. This includes almost all directories, such as /home, /var, /usr, the

root volume group, logical volumes, system configurations, and previously installed software.

The only file system that will be refreshed after the migration is /tmp. You can easily avoid

losing information you have stored in this directory by copying the important information to

another directory before the migration and move it back afterwards. Additionally, after the

migration, you can import your user volume groups. It is probably the easiest way to upgrade

your system to AIX 5L while maintaining all customized information and configuration.

Another migration advantage, especially if you need to minimize the downtime of your

system, is that there are fewer reconfiguration tasks to perform when the migration process

has completed.

If an application has the requirement to use a large file system in a server environment (up to

32 TB) you must use the JFS2 file system, which was introduced with AIX 5L. By doing a

migration installation to move from AIX 4.3.3 to AIX 5L, existing JFS file systems cannot be

converted to JFS2 file systems. This is only possible for new and complete overwrite and

preservation installations. If installed graphics software support or other additional software,

selected from the installation menu during an overwrite installation, this option is not available

at migration installation time. However, after the migration is completed, you can select

additional filesets to install from various CDs or, alternatively, you can prepare software

resources over the network before migrating your system and install them after the migration

process completes.

2.3.2 New and complete overwrite installation

The new and complete overwrite installation should be used to install AIX 5L Version 5.1 on a

new system or on a system on which you do not wish to preserve the existing version of AIX,

its configuration, and possibly some of the user data. The main advantage of this method is

that your resulting AIX 5L Version 5.1 installation is cleaned of obsolete data. On the other

hand, the system will need to be reconfigured. The complexity of your installation will

determine the amount of additional work required. This work must be evaluated before

choosing such a method.

User-defined volume groups (non-root volume groups) will be preserved and will remain there

after the new installation. You should import these volume groups and mount the file systems

created on them.

Note: After a migration installation, if you want to install the next recommended

maintenance level of AIX, use the SMIT update_all fast path or the install_all_updates

command to update the filesets currently installed.

8 CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Following are some of the tasks you might perform, based on your specific environment,

when selecting a new and complete installation.

򐂰 Set the system date and time for your time zone.

򐂰 Set a root user account password to restrict access to system resources.

򐂰 Confirm or change the install device you want to use for installing additional software. The

device may be a CD-ROM, a tape drive, or a local or remote directory.

򐂰 Check the system storage and paging space needed for installing and using additional

software applications.

򐂰 Set your National Language Support (NLS) environment.

򐂰 Import user-defined volume groups.

򐂰 Create user accounts and passwords.

򐂰 Install third-party device drivers (for example, LAN printer server).

򐂰 Set your system network configuration (if applicable).

򐂰 Create local and remote terminals.

򐂰 Configure local and remote printers.

򐂰 Install and configure additional LPPs.

򐂰 Install and configure third-party software.

This method can be suitable for a stand-alone system with a simple configuration.

2.3.3 Preservation installation

Preservation installation was the default installation method of the Base Operating System

(BOS) for systems running AIX Version 3.1. Since AIX Version 3.2, the migration installation is

the default and recommended method. However, there is still the option to migrate to AIX 5L

by using the preservation installation method.

With a preservation installation, the contents of /usr, /, /var, and /tmp will be deleted. The

process will save the previous paging space and dump device, /home, and other user-created

file systems in rootvg.

User-defined volume groups (non-root volume groups) will be preserved and activated

automatically after the preservation installation completes. Before mounting the file systems

belonging to these user-defined volume groups, you need to recreate the file systems

′

mounting directories that were removed during the installation (directories under / or /usr, for

example).

Configuration files, with the exception of /etc/filesystems, will be deleted. If you want any

additional configuration files to be saved during the preservation installation, you must edit the

/etc/preserve.list file on your existing AIX system, and add the full path names of the

configuration files you want to save. There must be sufficient disk space in the /tmp file

system to store the files listed in the /etc/preserve.list file.

2.4 Migration sources

The following sections give an overview about the various sources that can be used for the

migration.

Chapter 2. Migration methods 9

2.4.1 AIX and compiler CDs

Installation CDs are required for a migration, even if used as the base installation media or

used to set up a Network Installation Management (NIM) server. All appropriate CDs are

required, including the AIX 5L base operating, compiler, and other software products.

2.4.2 Network Installation Management

Network Installation Management (NIM) is a component of the AIX operating system and is

an excellent tool for teams or companies that have a need to install, clone, or upgrade many

RS/6000 or pSeries machines with the same images at the same time.

All the migration methods discussed in the previous section (migration installation, new and

complete overwrite installation, preservation installation) can also be done through a network

by using NIM. The primary difference is that a NIM server is used instead of an installation

device (CD-ROM or tape drive).

In order to perform a migration installation using a Local Area Network (LAN), NIM must be

installed and configured on a server running AIX 5L. The installation resources, a SPOT

(shared product object tree), and the pSeries to be migrated will have to be defined as objects

on the NIM server environment.

Installation resources have to be allocated to the system objects, and then the chosen

installation method can be performed from the NIM server. A migration installation using NIM

is suitable for migrating multiple LAN-connected systems.

For more information about NIM and how to set up a NIM environment refer to the AIX 5L

Version 5.1 Network Installation Management Guide located on the AIX Documentation CD;

NIM: From A to Z in AIX 4.3, SG24-5524; or AIX Version 4.3 to 5L Migration Guide,

SG24-6924.

2.5 Alternate disk migration

An option to migrate your existing AIX Version 4.3.3 to AIX 5L with as little downtime as

possible is the alternate disk migration installation. An additional spare disk is required for this

process. The only administrative task is to prepare the NIM server with the necessary filesets

and then initiate the process of alternate disk migration by using the nimadm command. The

procedure behind this command is a mixture of cloning the rootvg and using Network

Installation Management (NIM). It is done by your server automatically and involves several

steps. AIX creates a copy of the root volume group on a free disk in your system.

Simultaneously, this disk is migrated to AIX 5L while your original AIX Version 4.3 system is

still running as normal.

An advantage is that your downtime is reduced because you migrate the system while it is still

running and functioning. A simple reboot is required to start the new system. Another

advantage is that if the migration installation on your cloned rootvg fails, the changes made

from the migration are only made to the copy of the rootvg. You can either clean up the failed

migration or redo the entire process, including making a copy of the rootvg again. The only

impact to your running production system may be a small performance decrease on your

active rootvg during the cloning due to increased disk I/O and CPU usage.

This option is suitable for a server with a spare disk, which not all workstations have available.

10 CATIA and Enova migration AIX 4.3 to AIX 5L Version 5.1

Page is loading ...

IBM Frozen Dessert Maker AIX 4.3 User manual

This manual is also suitable for

IBM Frozen Dessert Maker AIX 4.3 User manual

Related papers

Other documents