IBM SA41-5155-05 User Manual



iSeries

iSeries 940x RISC-to-RISC Road Map

Version 5

SA41-5155-05



iSeries

iSeries 940x RISC-to-RISC Road Map

Version 5

SA41-5155-05

Note

Before using this information and the product it supports, be sure to read the information in “Appendix D. Notices” on page 45.

Sixth Edition (May 2001)

This edition replaces SA41-5155-04. This edition applies only to reduced instruction set computer (RISC) systems.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

iSeries 940x RISC-to-RISC Road Map,

SA41–5155–05 ............v

Who Should Read This Book .........v

Conventions and Terminology Used in This Book . . v

Prerequisite and related information ......vii

OperationsNavigator..........viii

How to send your comments ........viii

Chapter 1. Overview of RISC-to-RISC

Upgrades and Data Migrations .....1

What is in this Road Map? .........1

Why Upgrade from one AS/400 or iSeries 400 Server

to Another iSeries 400 Server? ........2

What is an Upgrade? ...........2

Upgrade process flow ..........2

Hardware Investment for Upgrading ......3

How Long will the Upgrade Take? .......3

WhatisaDataMigration?..........3

Data migration process flow ........4

How Long will the Data Migration Take?.....5

Books to Use for Software Release Upgrades . . . 5

Chapter 2. Planning Your Order for

Upgrading or Data Migration ......7

Determining Your Upgrade Needs .......7

Performance Tools for Capacity Planning and

Performance Analysis ..........7

How to Gather Configuration Information . . . 8

How to Gather Performance Information ....8

Prerequisites Before Placing an Order ......9

Version 4 Software Items .........9

Other Software Related Items ........9

HardwareConsiderations.........9

System Configuration Considerations.....10

Services and Other Assistance .......10

Model-specific Considerations for Placing an Order 11

Upgrading from a 4xx, 5xx, Sxx, or 6xx to a 7xx 12

Migratingfroma5xxtoan8xx........13

Upgrading from a 6xx or 7xx to an 8xx .....14

Placing the Upgrade Order .........14

Who is Responsible for Ordering the Upgrade? 14

HowtoGetHelpwiththeOrder......15

SendingtheOrdertoIBM........15

Sending the Order to a Software Service Provider

Other Than IBM ............15

Preparing the Current System ........18

Preparing for System Assurance prior to

hardware upgrade ...........20

System Assurance Checkpoint .......23

Installing the Hardware for the RISC-to-RISC

Upgrade ...............24

Managing your new system I/O resources ....24

Performing a new system backup .......28

Chapter 4. Procedure for a Data

Migration (RISC-to-RISC) .......31

Prerequisites for data migration (RISC to RISC) . . 31 Preparing the source system for the migration . . . 31

Datamigration(RISC-to-RISC)........32

Appendix A. AS/400 Global Services . . 35

iSeries and AS/400 Data Migration Services . . . 35 LPAR Planning and Implementation Services . . . 35

iSeries Planning and Migration Services .....35

System Migration Services .........35

Related Support Services ..........36

AS/400 Solution Services ..........36

Installation Services ..........36

Performance Examinations ........36

Consulting Services...........36

Midrange Enhanced Software Service (MRESS) 37

Appendix B. Considerations and

Solutions..............39

IBM HTTP Server for AS/400 ........39

Operations Console............40

OptiConnect ..............40

Integrated Netfinity Server .........40

Clustering and Logical Partitions .......40

Lotus Notes Enhanced Integration .......40

OnDemand ..............40

SRC A900 2000 Recovery ..........40

How to Move Files That Have Been Saved with

Storage Free Specified ...........41

How to Move Freed Database Files without New

Members..............41

Appendix C. Obtain the Latest Preventive Service Planning

Information .............43

Chapter 3. Procedure for an Upgrade

(RISC-to-RISC) ...........17

Who is Responsible for Upgrading the System. . . 17

What to Do When the Hardware Arrives ....18

Appendix D. Notices .........45

Trademarks..............46

Index ...............49

iv iSeries 940x RISC-to-RISC Road Map V5R1

iSeries 940x RISC-to-RISC Road Map, SA41–5155–05

Use this book as a guide for planning and conducting an upgrade or data migration, from one iSeries 400 or AS/400 reduced instruction set computer (RISC), to another RISC model.

For information on supported releases, see http://as400service.ibm.com/supporthome.nsf/document/17623433

See “Prerequisite and related information” on page vii for a list of other required and recommended publications.

Who Should Read This Book

This road map is for anyone who is considering an upgrade for an iSeries server or is involved in migrating data from one RISC model to another RISC model. This audience includes:

v Customers

v Hardware services personnel

v Software services personnel

v Business partners

v Marketing representatives

Everyone involved in the model upgrade or data migration needs to know all of the information in this book.

Each customer should have a Customer Account Team Leader. This team leader can be a Hardware Service Representative, Software Service Representative, Business Partner, or Marketing Representative. The Availability Center usually assigns a Customer Account Team Leader.

Conventions and Terminology Used in This Book

This road map identifies activities, programs, tools, and references that you can use to upgrade the model.

As you read this book, you should be aware of the following terms:

v The terms source system and target system are used throughout this manual.

The source system is the system you are upgrading from. The target system is the system you are upgrading to.

v The term Marketing Representative can mean either an IBM Marketing

Representative,aBusiness Partner,oraServices Specialist.

v The term 1xx includes Model 150 or 170.

v The term 2xx includes Model 250 or 270.

v The term 4xx includes Model 400, 40S, or 436.

v The term 5xx includes Model 50x, 50S, 510, or 530.

v The term Sxx includes Model S10, S20, S30, S40, SB1, SB2, or SB3.

v The term 6xx includes Model 600, 620, 640, or 650.

v The term 7xx includes Model 720, 730, or 740.

v The term 8xx includes Model 820, 830, or 840.

v The term iSeries or iSeries 400 as used in this document refers to the new

generation of (previously AS/400) systems and servers positioned for e-business: e-systems and e-servers, for example Model 170.

v The term iSeries server as used in this document refers to:

– iSeries system- Models 40x, 5x0, 150 and 6x0.

– iSeries server- Models 40S, 5xS, Sxx, 170, 2xx, 7xx and 8xx.

v The term System Products Division (SPD) book-type adapter cards includes all

adapter cards that are not Peripheral Component Interconnect (PCI) adapter cards.

In this publication, the version, release, and modification levels are shown in a shortened form:

V4R4M0 Version 4 Release 4 Modification 0

V4R5M0 Version 4 Release 5 Modification 0

V5R1M0 Version 5 Release 1 Modification 0

V4R4 Version 4 Release 4 Modification (any)

V4R5 Version 4 Release 5 Modification (any)

V5R1 Version 5 Release 1 Modification (any)

Version 5 Any version 5 release, such as, V5R1M0.

Version 4 Any version 4 release, such as, V4R1M0, V4R2M0 or V4R3M0.

Attention:

Is used in this book to indicate that a step, or process may cause loss of data.

Namely: Installing incorrect versions of the operating system.

CAUTION:

Is used in this book to indicate possible damage to the system.

Namely: Static damage to component.

DANGER

Is used in this book to indicate possible damage to the users and equipment.

Namely: Electrical shock.

In any position that contains numerals, an x = any supported value, for example SFxxxxx,orVxRxMx.

Examples of displays might contain only pertinent information to a topic. So, some display examples do not show all text and lines, especially blank lines.

vi iSeries 940x RISC-to-RISC Road Map V5R1

Prerequisite and related information

Use the iSeries Information Center as your starting point for looking up iSeries and AS/400e technical information. You can access the Information Center two ways:

v From the following Web site:

http://www.ibm.com/eserver/iseries/infocenter

v From CD-ROMs that ship with your Operating System/400 order:

iSeries Information Center, SK3T-4091-00. This package also includes the PDF versions of iSeries manuals, iSeries Information Center: Supplemental Manuals, SK3T-4092-00, which replaces the Softcopy Library CD-ROM.

The iSeries Information Center contains advisors and important topics such as CL commands, system application programming interfaces (APIs), logical partitions, clustering, Java, TCP/IP, Web serving, and secured networks. It also includes links to related IBM Redbooks and Internet links to other IBM Web sites such as the Technical Studio and the IBM home page.

With every new hardware order, you receive the following CD-ROM information:

v iSeries 400 Installation and Service Library, SK3T-4096-00. This CD-ROM contains

PDF manuals needed for installation and system maintenance of an IBM ~ iSeries 400 server.

v iSeries 400 Setup and Operations CD-ROM, SK3T-4098-00. This CD-ROM contains

IBM iSeries Client Access Express for Windows and the EZ-Setup wizard. Client Access Express offers a powerful set of client and server capabilities for connecting PCs to iSeries servers. The EZ-Setup wizard automates many of the iSeries setup tasks.

Your RISC-to-RISC upgrade or data migration requires the following publications:

v This book. The online version of this book is on the iSeries Information Center

http://www.ibm.com/eserver/iseries/infocenter

under the System Planning and Installation topic.

v iSeries Information Center, SK3T-4091-00 is required for logical partition

information along with many other topics.

v Software Installation, SC41-5120-05 is required for the software upgrade. A PDF

version of this manual is available from the iSeries Information Center under

System planning and installation -> Hardware and software -> Software and licensed programs -> Install software

v Physical Planning in the iSeries Information Center under Getting Started with

iSeries -> Planning ->Physical planning for your new system.

http://www.ibm.com/eserver/iseries/infocenter

v Getting started with iSeries topic under System planning and installation in the

Information Center.

v The Backup and Recovery manual is available in PDF format from the iSeries

Information Center (under Systems Management -> Backup, recovery, and availability -> Manuals and Redbooks) and is shipped with your order.

v iSeries Model 270, 8xx, SB2, and SB3 System Installation and Upgrade, SY44-5966-01.

v iSeries 400 Model 830, 840, SB2 and SB3 Problem Analysis, Repair and Parts,

SY44-5969.

v iSeries 400 Model 270 and 820 Problem Analysis, Repair and Parts, SY44-5967.

v Operations Console Setup, SC41-5508-02.

iSeries 940x RISC-to-RISC Road Map, SA41–5155–05 vii

For information about Logical Partitioning, see the LPAR web site at:

www.as400.ibm.com/LPAR

For information about working with PTFs, see the Managing fixes topic in the Information Center under System planning and installation -> Getting started with iSeries -> Managing system operations.

For information about other AS/400 publications (except Advanced 36), see the following:

v Prior to V4R4, the Publications Reference, SC41-5003, in the AS/400 Softcopy

Library.

v The AS/400 Information Directory is a unique, multimedia interface to a

searchable database. It contains descriptions of titles available from IBM or from other selected publishers. It comes with the OS/400 operating system at no extra charge.

v iSeries Information Center: Supplemental Manuals, SK3T-4092-00.

An upgrade might require the use the following publications:

v Operations Console Setup, SC41-5508-02

v BEST/1 Capacity Planning Tool, SC41-5341-01

v LPS: OnDemand for AS/400, GC41-5079-01

v OptiConnect for OS/400, SC41-5414-02

Operations Navigator

IBM Operations Navigator is a powerful graphical interface for managing your iSeries 400 servers. Operations Navigator functionality includes system navigation, configuration, planning capabilities, and online help to guide you through your tasks. Operations Navigator makes operation and administration of the server easier and more productive and is the only user interface to the new, advanced features of the OS/400 operating system. It also includes Management Central for managing multiple servers from a central server.

For more information on Operations Navigator, see the iSeries Information Center.

How to send your comments

Your feedback is important in helping to provide the most accurate and high-quality information. If you have any comments about this book or any other iSeries documentation, fill out the readers’ comment form at the back of this book.

v If you prefer to send comments by mail, use the readers’ comment form with the

address that is printed on the back. If you are mailing a readers’ comment form from a country other than the United States, you can give the form to the local IBM branch office or IBM representative for postage-paid mailing.

v If you prefer to send comments by FAX, use either of the following numbers:

– United States, Canada, and Puerto Rico: 1-800-937-3430

– Other countries: 1-507-253-5192

v If you prefer to send comments electronically, use one of these e-mail addresses:

– Comments on books:

RCHCLERK@us.ibm.com

– Comments on the iSeries Information Center:

RCHINFOC@us.ibm.com

viii iSeries 940x RISC-to-RISC Road Map V5R1

Be sure to include the following:

v The name of the book or iSeries Information Center topic.

v The publication number of a book.

v The page number or topic of a book to which your comment applies.

iSeries 940x RISC-to-RISC Road Map, SA41–5155–05 ix

x iSeries 940x RISC-to-RISC Road Map V5R1

Chapter 1. Overview of RISC-to-RISC Upgrades and Data Migrations

The road map lists important considerations and activities that are critical to the successful model upgrade of a system. Although this road map is not designed to be an all inclusive how-to source for activities relating to upgrading your system, it covers the essentials by guiding you to the proper source. Follow all the steps in the order presented and notify your IBM into difficulties.

This road map also covers how to perform a model to model data migration. A data migration can be performed from almost any iSeries 400 model to any model. The source model must be at the same release as the new model to correctly complete the data migration. Data migration involves a new system with a new serial number.

For an overview of the RISC-to-RISC upgrades and data migration, refer to “Upgrade process flow” on page 2 and the “Data migration process flow” on page 4.

What is in this Road Map?

This road map covers the following RISC-to-RISC upgrades:

representative for assistance if you run

Note: The current system may require hardware upgrades or configuration

changes to satisfy capacity and compatibility requirements of new software and hardware.

v IBM AS/400 Model 170 to IBM AS/400 Model 170

There are no upgrades into or out of a Model 170. The Data Migration section of this book covers the procedure used to perform a data move from the source system to the new iSeries model.

v IBM ~ iSeries Model 270 to IBM ~ iSeries Model 270

There are no upgrades into or out of a Model 270. The Data Migration section of this book covers the procedure used to perform a data move from the source system to the new iSeries model.

v IBM AS/400 Models 5xx to IBM AS/400 Models 7xx

v IBM AS/400 Models 6xx to IBM AS/400 Models 7xx

v IBM AS/400 Models 7xx to IBM AS/400 Models 7xx

v IBM AS/400 Models Sxx or IBM AS/400 Models 5xx to IBM ~ iSeries

Models 8xx

There are no model upgrades into a Model 8xx from a Model 5xx, 6xx, Sxx, or SBx. However, some hardware may be moved from the 5xx into a migration I expansion unit (I/O and disk unit). The Data Migration section of this book covers the procedure used to perform a data move from the source system to the new iSeries 400 model.

v IBM AS/400 Models 6xx to IBM ~ iSeries Models 8xx

v IBM AS/400 Models 7xx to IBM ~ iSeries Models 8xx

v IBM ~ iSeries Models 8xx to IBM ~ iSeries Models 8xx

Contact your local IBM representative or authorized dealer for additional information on permitted upgrades.

For servers that do not have an upgrade path, use the data migration section of this book. This would include scenarios such as an AS/400 iSeries 400 Model 270.

Model 540 to an

Why Upgrade from one AS/400 or iSeries 400 Server to Another iSeries 400 Server?

You might ask yourself why IBM is doing this and why upgrade your server now? Most customers need to increase performance and add capacity.

What is an Upgrade?

In this book, an upgrade is any improvement made to the software or the hardware of an iSeries 400 or AS/400 model that retains the serial number of the iSeries 400 or AS/400 model. This includes moving the compatible hardware, the Licensed Internal Code, operating system, and the licensed programs to a new target system for better performance and reliability.

A data migration is the process of moving only the data from one iSeries 400 or AS/400 model to a new iSeries 400 model, with a new serial number.

Upgrade process flow

The following flow chart describes each step of an MES upgrade and lists the required outputs for each stage.

2 iSeries 940x RISC-to-RISC Road Map V5R1

Hardware Investment for Upgrading

You may choose to upgrade your existing RISC system processor, or replace it with a new iSeries 400 model. In either case, you may keep most of the current system. The process of either an upgrade of your existing system or moving parts from an existing system to a new system, are called miscellaneous equipment specification (MES). MES denotes the process steps of an upgrade. The type of MES depends on several factors:

v Your current processor model

v Costs

v Your system availability requirements

The information in this book will help to determine the right path to an upgrade. This is based on the current model and the goals of the process.

How Long will the Upgrade Take?

The upgrade process includes planning, ordering, shipping, installing and testing the system. The following table shows approximately how long an upgrade might take.

Note: You should plan at least one additional hour of down time to load the

operating system for systems not preloaded.

Order Planning - 5 to 15 Days

See “Prerequisite and related information” on page vii for required publications.

System Requirements Solution Assurance Upgrade Software Verify System

Performance Hardware and Software

Determine Services Needed

Place Order

Installation Planning and Preparation - 10 to 30 days Phase II Installation - Weekend

(1 to 3 days)

Save System

See “Prerequisite and related information” on page vii for required publications.

Preparation

Physical Planning (Site Preparation)

Phase I Installation - 5 to 20 Days

Save System Upgrade Hardware

Check History and Clean Up Messages

Save System

What is a Data Migration?

A data migration is the process of moving the OS/400®and the data from one model iSeries 400 or AS/400 to a new model iSeries 400 AS/400.

The source system must be at the same release level as the target server. This includes OS/400, all objects, and all licensed programs.

For customers ordering a new RISC iSeries 400 server with V4R4 or V4R5 to replace an existing RISC iSeries 400 or AS/400 model (″source″) and needing to migrate their data from the ″source″ model to the new server, a new feature code Feature Code (F/C) #0205, is now available. This new feature code should be ordered against the new RISC iSeries 400 server. It is valid on orders for all new servers except the Models 150 and SB1.

Chapter 1. Overview of RISC-to-RISC Upgrades and Data Migrations 3

For Feature Code #0205, the customer must have purchased a new server with enough hardware and disk unit to hold all of the data from the ″source″ model as well as any new data including any required IBM software (OS/400 and so forth). Additionally, the RISC-to-RISC Data Migration process requires that the ″source″ model must be at the same version/release of OS/400 and Licensed Program Products (LPPs) as that of the ″new″ server which has been ordered/received.

Customers with Version 3 (V3R7) on their ″source″ model must upgrade to Version

4. It is recommended that they purchase Software Subscription for AS/400. They must then order and upgrade to match the new server (V4R4 or V4R5) in order to proceed with their data migration. V3R7 cannot be directly upgraded to V4R4 or V4R5 therefore, to do this the source system will need to be upgraded to V4R2 or V4R3 before upgrading to V4R4 or V4R5. Customers with Version 4 must obtain new server release of OS/400 licenses of the LPPs, either through new orders or via Software Subscription for AS/400.

A License Addendum will be provided to allow the customer to install and use the copy of OS/400 (received with the newly ordered server) on their source model for up to 70 days. This Addendum authorizes the customers to use the new Version and Release on the source system for the sole purpose of migrating their data. The previous Version and Release must be reinstalled after the migration is completed. The V4R4 or V4R5 licenses of OS/400 and the LPPs will only allow the products to be run on one system at a time. Model 150 customers who are not at the new server release of OS/400 must purchase the BasePak Upgrade (5649-EP5 for V4R4) in addition to any upgrades for installed Optional Products in order to proceed with their data migration. Feature Code #0205 provides for minimal pre loading of the new server, inclusion of a special License Addendum.

Feature Code #0205 differs from Feature Code #0203. Feature Code #0203 SHOULD NOT be ordered for iSeries 400 or AS/400 RISC-to-RISC data migrations as it is designed exclusively for AS/400 CISC-to-RISC data migrations.

Data migration process flow

The following flow chart describes each step of a data migration and lists the required outputs for each stage.

4 iSeries 940x RISC-to-RISC Road Map V5R1

How Long will the Data Migration Take?

The data migration process includes planning, ordering, shipping, installing and testing the system. The following table shows approximately how long a data migration might take.

Note: You should plan at least one additional hour of down time to upgrade the

operating system for source systems not at the new server release level.

Order Planning - 5 to 15 Days Installation Planning and

Preparation - 10 to 30 days

See “Prerequisite and related information” on page vii for required publications.

System Requirements Solution Assurance Verify System

Performance Physical Planning (Site

Determine Services Needed Software Preparation (Upgrade

Place Order Save System

See “Prerequisite and related information” on page vii for required publications.

Preparation)

Source System Software)

Phase II Installation - Weekend (1 to 3 days)

Migrate Data

Check History and Clean Up Messages

Save System

Books to Use for Software Release Upgrades

The following table lists software release considerations, and which book to use for upgrading the operating system and licensed programs.

Chapter 1. Overview of RISC-to-RISC Upgrades and Data Migrations 5

OS/400 Release Currently Installed Book To Use For Upgrade and Software Installation

V5R1 V4R5

V4R4

If you have one of these releases installed on your system, your system already runs on the RISC architecture. Use this manual, iSeries 940x

RISC-to-RISC Road Map, SA41-5155-05, for the upgrade. Use the manual Software Installation, SC41-5120-05, to replace the installed operating system

and licensed programs. A PDF version of this manual is available from the iSeries Information Center under System planning and installation ->

Hardware and software -> Software and licensed programs -> Install software. Use the manual Backup and Recovery, SC41-5304-05, for the save

and restore requirements of these procedures. A PDF version of this manual is available from the Information Center under Systems Management ->

Backup, recovery, and availability -> Manuals and Redbooks. Note: V4R4 introduced logical partitions. Go to the iSeries Information

Center for help with setting up, upgrades to, and maintaining logical partitions.

See the Software Installation manual for other software requirements and limitations prior to the OS/400 upgrade.

6 iSeries 940x RISC-to-RISC Road Map V5R1

Chapter 2. Planning Your Order for Upgrading or Data Migration

Review this chapter as you identify a solution and again after a decision is made to verify the accuracy and completeness of the order. After you finish reviewing this chapter, you should have the following:

v Final software order

v Final hardware order

v Floor layout

v High-speed link (HSL) and system power control network (SPCN) plan

v Cable labelling of source system

v Site requirements defined

Refer to the “Upgrade process flow” on page 2 or “Data migration process flow”

on page 4, depending on your situation, to identify where Planning is in the

overall process.

Determining Your Upgrade Needs

To help determine the upgrade needs, please consider the following:

v What problems does this upgrade need to address?

v What additional applications or growth do you expect or plan for in the future?

v What new technology do you want as part of the upgrade?

v What are the requirements for the following:

– Capacity

– Capability

– Performance

– Availability

v What are your expectations for the following:

– Impact on business operations

– Cost

– Performance

v What are the financial considerations to keep in mind? For example:

– Government discounts

– Capital planning cycles

– Tax implications

– Budget

Performance Tools for Capacity Planning and Performance Analysis

The licensed program Performance Tools/400 (Program 57xx-PT1) and QSIZE400 on the iSeries 400 configurator can be used for capacity planning and performance analysis.

The BEST**/1 Capacity Planning function of the Performance Tools licensed program provides the capability to analyze how a different AS/400 or iSeries 400

configuration will perform with your current workload. The program temporary fixes (PTFs) are now available that include capacity planning information for the PowerPC processor models of the system. You can use Performance Tools to help you determine the proper configuration of the processor main storage, and disk resources that will meet your performance requirements.

Performance Tools are the best source of information for determining what configuration meets your performance requirements. You should order the PTF that updates your version of Performance Tools with the PowerPC AS processor models.

Note: If you do not have Performance Tools on your system, you should obtain

modeling information in another way, such as by using consulting services. Modeling the characteristics of your target configuration helps ensure that the configuration meets your needs.

The latest PTFs for AS/400 BEST/1 Capacity Planner are required. You can order or download these PTFs from the following Web site:

http://as400service.ibm.com

You need to register at this site. Do the following to go to the Internet PTF Facility:

1. Click Fixes, Downloads and Updates

2. Click Internet PTF Downloads (iPTF)

How to Gather Configuration Information

You and your marketing representative use the MRPD (Machine Reported Product Data) and the IBM Configurator for e-business. This process compares your current configuration with your desired configuration and creates the MES order automatically. This simplifies the work that you and the marketing representative have to do and ensures a correct MES order.

Machine Reported Product Data (MRPD)

The hardware and software inventory of a system can be transmitted to IBM and stored in databases there. Once the information has been captured, it can be accessed by the marketing representative to establish a starting point for a system upgrade. The data may also be used for problem determination by hardware and software support centers.

The data can be sent to IBM with these tools:

v Manually, with the WRKORDINF command. The WRKORDINF command sends

the information once through the Electronic Customer Support line.

v Automatically, with Service Agent and Management Central. Service Agent can

be customized to automatically transmit the data regularly on a monthly basis.

How to Gather Performance Information

Gathering performance data before installing a release gives you a base with which to compare your system’s performance after the installation is complete. Performance data is also useful when determining the correct hardware configuration for your upgrade.

To gather performance information before you install a release, see the Prepare for

software installation topic in the Information Center under System planning and installation -> Hardware and software -> Software and licensed programs.

8 iSeries 940x RISC-to-RISC Road Map V5R1

+ 46 hidden pages

IBM SA41-5155-05 User Manual

Contents

iSeries 940x RISC-to-RISC Road Map, SA41–5155–05

Who Should Read This Book

Conventions and Terminology Used in This Book

Prerequisite and related information

Operations Navigator

How to send your comments

Chapter 1. Overview of RISC-to-RISC Upgrades and Data Migrations

What is in this Road Map?

Why Upgrade from one AS/400 or iSeries 400 Server to Another iSeries 400 Server?

What is an Upgrade?

Upgrade process flow

Hardware Investment for Upgrading

How Long will the Upgrade Take?

What is a Data Migration?

Data migration process flow

How Long will the Data Migration Take?

Books to Use for Software Release Upgrades

Chapter 2. Planning Your Order for Upgrading or Data Migration

Determining Your Upgrade Needs

Performance Tools for Capacity Planning and Performance Analysis

How to Gather Configuration Information

Machine Reported Product Data (MRPD)

How to Gather Performance Information