IBM eServer iSeries Migration : (Record no. 76131)
[ view plain ]
000 -LEADER | |
---|---|
fixed length control field | 11133nam a22005053i 4500 |
001 - CONTROL NUMBER | |
control field | EBC3306370 |
003 - CONTROL NUMBER IDENTIFIER | |
control field | MiAaPQ |
005 - DATE AND TIME OF LATEST TRANSACTION | |
control field | 20240729124909.0 |
006 - FIXED-LENGTH DATA ELEMENTS--ADDITIONAL MATERIAL CHARACTERISTICS | |
fixed length control field | m o d | |
007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION | |
fixed length control field | cr cnu|||||||| |
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
fixed length control field | 240724s2003 xx o ||||0 eng d |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
International Standard Book Number | 9780738499567 |
Qualifying information | (electronic bk.) |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
Canceled/invalid ISBN | 9780738499567 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (MiAaPQ)EBC3306370 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (Au-PeEL)EBL3306370 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (CaPaEBR)ebr10112111 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (OCoLC)64550214 |
040 ## - CATALOGING SOURCE | |
Original cataloging agency | MiAaPQ |
Language of cataloging | eng |
Description conventions | rda |
-- | pn |
Transcribing agency | MiAaPQ |
Modifying agency | MiAaPQ |
050 #4 - LIBRARY OF CONGRESS CALL NUMBER | |
Classification number | QA76.9.C55 -- I36 2003eb |
100 1# - MAIN ENTRY--PERSONAL NAME | |
Personal name | Redbooks, IBM. |
245 10 - TITLE STATEMENT | |
Title | IBM eServer iSeries Migration : |
Remainder of title | System Migration and Upgrades at V5R1 and V5R2. |
250 ## - EDITION STATEMENT | |
Edition statement | 1st ed. |
264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE | |
Place of production, publication, distribution, manufacture | Durham : |
Name of producer, publisher, distributor, manufacturer | I B M, |
Date of production, publication, distribution, manufacture, or copyright notice | 2003. |
264 #4 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE | |
Date of production, publication, distribution, manufacture, or copyright notice | ©2003. |
300 ## - PHYSICAL DESCRIPTION | |
Extent | 1 online resource (534 pages) |
336 ## - CONTENT TYPE | |
Content type term | text |
Content type code | txt |
Source | rdacontent |
337 ## - MEDIA TYPE | |
Media type term | computer |
Media type code | c |
Source | rdamedia |
338 ## - CARRIER TYPE | |
Carrier type term | online resource |
Carrier type code | cr |
Source | rdacarrier |
505 0# - FORMATTED CONTENTS NOTE | |
Formatted contents note | Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. Overview of AS/400e and iSeries migration and upgrades -- Chapter 2. iSeries server hardware -- 2.1 The range of models -- 2.2 Investment leverage -- 2.3 iSeries workloads -- 2.3.1 2003 model options packages -- 2.3.2 Pre-2003 model processors and interactive features -- 2.4 iSeries 2003 models -- 2.4.1 SStar models -- 2.4.2 POWER4 Enterprise models -- 2.5 2002 iSeries models -- 2.5.1 Entry server models -- 2.5.2 Enterprise server models -- 2.6 iSeries I/O packaging -- 2.6.1 PCI-X towers -- 2.6.2 PCI expansion towers -- 2.6.3 iSeries I/O packaging: Migration towers -- 2.6.4 iSeries packaging -- 2.7 POWER4 architecture and technology -- 2.8 Support for concurrent maintenance -- Chapter 3. PCI technology, concurrent maintenance on iSeries -- 3.1 PCI internal bus concept and system unit backplanes -- 3.1.1 SPD bus and PCI bus -- 3.1.2 Backplane architecture -- 3.2 Concurrent maintenance -- 3.3 PCI tower behavior and LPAR configuration rules -- 3.3.1 IOP and IOA assignment rules -- 3.3.2 Concurrent maintenance scenarios -- Chapter 4. New model planning considerations -- 4.1 Planning fundamentals -- 4.1.1 Why upgrade -- 4.1.2 The upgrade plan -- 4.1.3 Performance measurements and criteria -- 4.1.4 Validating the installed hardware and software -- 4.2 Migration considerations -- 4.3 Memory migration to 800, 810, 825, 870, and 890 memory -- 4.3.1 Models 800 and 810 -- 4.3.2 Model 825 -- 4.3.3 Model 870 and 890 -- 4.3.4 Model 890 memory conversions -- 4.3.5 Memory migration to 820, 830, and 840 -- 4.4 Power requirements and 870 or 890 site planning -- 4.4.1 7xx to 8xx except 870 and 890 -- 4.4.2 740, 830, and 840 to 890 -- 4.4.3 System power control network (SPCN) considerations. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 4.5 Linux partition planning considerations -- 4.6 Migration and upgrade checklist -- Chapter 5. SPD upgrade planning considerations -- 5.1 SPD to PCI conversion -- 5.1.1 SPD features and towers that must be replaced -- 5.1.2 SPD and SPD/PCI features and towers that can be converted to PCI/HSL -- 5.1.3 SPD/PCI features that must be replaced when migrating to 8xx systems -- 5.1.4 SPD/PCI feature co-existence between 7xx and 8xx systems -- 5.2 Planning the SPD to PCI migration -- 5.2.1 Why you need to migrate to PCI and HSL -- 5.2.2 5065 conversion consideration -- 5.2.3 Migrating to PCI/HSL -- 5.3 Hardware upgrade path -- 5.3.1 System power control network (SPCN) considerations -- Chapter 6. Capacity on demand -- 6.1 History of capacity on demand -- 6.1.1 Capacity on demand at V4R5 (Models 830 and 840) -- 6.1.2 Capacity on demand at V5R1/V5R2 (Models 830, 840, and 890) -- 6.1.3 Capacity on demand at V5R2 (Models 825, 870, and 890) -- 6.1.4 On/Off Capacity on Demand workload considerations -- 6.2 On/Off Capacity on Demand process -- 6.2.1 Ordering an enablement feature -- 6.2.2 Applying the enablement code -- 6.2.3 Activating On/Off Capacity on Demand -- 6.3 Allocating temporary processors to partitions -- 6.3.1 Capacity Upgrade on Demand permanent activation in 2003 -- 6.3.2 Upgrade considerations for CUoD systems -- 6.3.3 Capacity planning for capacity on demand -- 6.3.4 Capacity Planning Services -- 6.3.5 Scenarios using temporary processors -- Chapter 7. HSL configuration, planning, rules -- 7.1 High-speed link architecture -- 7.2 HSL rules -- 7.2.1 HSL cable lengths -- 7.3 HSL implementation by model -- 7.3.1 HSL on the iSeries Model 800 -- 7.3.2 HSL on the iSeries Model 810 -- 7.3.3 HSL on the iSeries Model 825 -- 7.3.4 HSL on the iSeries Model 870 -- 7.3.5 HSL on iSeries Model 890 -- 7.3.6 HSL system maximums and loop maximums. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 7.4 HSL rules for the iSeries server -- 7.5 HSL cabling and loop considerations -- 7.6 HSL with Models 270, 820, 830, and 840 -- 7.7 HSL implementation by system model -- 7.7.1 HSL on the iSeries Model 270 -- 7.7.2 HSL on the iSeries Model 820 -- 7.7.3 Expansion tower placement on Model 820 -- 7.7.4 HSL on Model 830 -- 7.7.5 Towers with multiple loops -- 7.7.6 Expansion tower placement on Model 830 -- 7.7.7 HSL on Model 840 -- 7.8 SPD to HSL migration -- 7.8.1 Migration towers and HSL bus redundancy for mirroring -- 7.8.2 HSL OptiConnect at V5R1 -- 7.9 V5R1 HSL rules for the iSeries -- 7.9.1 Maximum tower and ownership rules -- 7.10 Service interface to HSL -- 7.10.1 Hardware service manager terminology for V4R5 -- 7.10.2 Hardware service manager displays -- 7.10.3 Hardware service manager displays at V5R1 and V5R2 -- 7.10.4 HSL-2 cabling -- Chapter 8. Migration examples -- 8.1 General upgrade considerations -- 8.1.1 New RAID-5 arrangement on PCI-X input/output adapters (IOAs) -- 8.1.2 Upgrading with load source migration -- 8.1.3 Upgrading with converted or relocated disks -- 8.1.4 Upgrading using unload and reload -- 8.1.5 Upgrading side-by-side -- 8.2 Upgrade examples into 810, 825, 870, and 890 -- 8.2.1 General preliminary tasks -- 8.2.2 270 to 810 mirror to RAID migration -- 8.2.3 270 to 810 RAID to RAID migration -- 8.2.4 720 to 825 migration -- 8.2.5 820 to 825 migration -- 8.2.6 740 to 890 migration -- 8.2.7 830 or 840 to an 890 migration -- 8.3 Examples of upgrading to Models 820, 830, and 840 -- 8.3.1 720 to 820 migration: Simple upgrade, disks are unprotected -- 8.3.2 720 to 820 migration: Removing the migration tower -- 8.3.3 720 to 820 migration: Disks are RAID-5 protected -- 8.3.4 720 to 820 migration with 5065 converted to 5074 -- 8.3.5 720 to 830 migration: Disks are RAID-5 protected -- 8.3.6 720 to 830 and 5065 to 5074 migration. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 8.3.7 730 to 830 migration: Disks are RAID-5 protected -- 8.3.8 730 to 830 5065 to 5074 and SPD to PCI migration -- 8.3.9 730 to 840 migration: Upgrade disks are RAID-5 protected -- 8.3.10 740 to 830 migration using the Interactive Reduction option -- 8.3.11 LPAR migration -- 8.3.12 Unsupported upgrades -- Chapter 9. Load source migration -- 9.1 820, 830, and 840 load source migration -- 9.2 No protection-to-no protection load source migration -- 9.3 No protection-to-protection load source migration -- 9.3.1 No protection-to-mirroring protection -- 9.3.2 No protection-to-RAID protection -- 9.4 Protection-to-protection load source migration -- 9.4.1 Mirroring-to-mirroring protection -- 9.4.2 Mirroring-to-RAID protection -- 9.4.3 RAID-to-RAID protection -- 9.4.4 RAID-to-mirroring protection -- 9.4.5 RAID-to-no protection -- 9.5 Valid combination for load source migration -- 9.6 Model 890 load source migration -- 9.6.1 Why use 890 load source migration -- 9.6.2 Overview of 890 upgrade process using load source migration -- 9.6.3 Load source migration process for the 890 -- Chapter 10. Disk migrate while active -- 10.1 A look at the Disk migrate while active process -- 10.1.1 Unsupported data types -- 10.1.2 An overview of the process -- 10.2 Disk migrate while active considerations -- 10.3 Starting the Disk migrate while active process -- 10.3.1 STRASPBAL command -- 10.3.2 Starting Disk migrate while active -- 10.4 Identifying disk units -- 10.4.1 System Service Tools -- 10.4.2 iSeries Navigator -- 10.4.3 System rack lists -- Chapter 11. Logical partition environment migrations -- 11.1 Order planning -- 11.1.1 LPAR configuration documentation -- 11.1.2 The LPAR Validation Tool and LPAR worksheets -- 11.2 LPAR migration concepts -- 11.2.1 Tape considerations when upgrading logical partitions -- 11.2.2 Steps for migrating LPAR configurations. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 11.3 Methods of LPAR migration -- 11.3.1 Side-by-side migration -- 11.3.2 Side-by-side example -- 11.3.3 Side-by-side primary with secondary hookup -- 11.3.4 One-step migration -- 11.3.5 Phased migration -- 11.4 Tower conversion considerations -- 11.4.1 SPD towers -- 11.4.2 PCI towers -- 11.5 Server consolidation with LPAR -- 11.5.1 Side-by-side LPAR consolidation -- 11.5.2 Phased LPAR consolidation -- 11.6 7xx LPAR migration to an iSeries server with a managing primary -- 11.6.1 Upgrade and migration tasks -- 11.7 Upgrades to Model 890 -- 11.7.1 890 LPAR upgrade scenarios -- 11.8 Multiple version support in LPAR -- 11.8.1 Basic rules -- 11.8.2 Exceptions to the rules -- 11.9 Determining LPAR functionality in a partition -- 11.10 Logical partitioning hardware functions by model -- 11.11 LPAR software functions by release -- 11.11.1 LPAR functionality in V4R5 compared to V5R1 -- 11.11.2 LPAR software enhancements with V5R2 -- 11.12 Shared processor support -- 11.12.1 Managing primary partitions -- 11.12.2 LPAR and virtual LAN connections -- 11.13 DVD-RAM drives in an LPAR environment -- Chapter 12. V5R1 and V5R2 software -- 12.1 V5R2 software -- 12.1.1 V5R2 with announcements from January 2003 -- 12.1.2 V5R2 with announcements from May 2003 -- 12.1.3 Information APAR II13365 -- 12.1.4 Information APAR II3440 -- 12.1.5 V5R2 Skip-ship and withdrawn software -- 12.1.6 V5R2 compatibility and upgrade paths -- 12.1.7 Data migration -- 12.1.8 Interoperability of releases with V5R2 -- 12.1.9 Logical partition (LPAR) software enhancements with V5R2 -- 12.1.10 Security enhancements with V5R2 -- 12.1.11 Installing system software from an image catalog -- 12.2 V5R1 software considerations -- 12.2.1 Skip-ship and withdrawn software -- 12.2.2 V5R1 compatibility and upgrade paths -- 12.2.3 Interoperability of releases with V5R1. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 12.2.4 LPAR software enhancements with V5R1. |
588 ## - SOURCE OF DESCRIPTION NOTE | |
Source of description note | Description based on publisher supplied metadata and other sources. |
590 ## - LOCAL NOTE (RLIN) | |
Local note | Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2024. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
Topical term or geographic name entry element | IBM Tivoli workload scheduler. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
Topical term or geographic name entry element | z/OS. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
Topical term or geographic name entry element | Electronic data processing -- Distributed processing. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
Topical term or geographic name entry element | Production scheduling. |
655 #4 - INDEX TERM--GENRE/FORM | |
Genre/form data or focus term | Electronic books. |
776 08 - ADDITIONAL PHYSICAL FORM ENTRY | |
Relationship information | Print version: |
Main entry heading | Redbooks, IBM |
Title | IBM eServer iSeries Migration |
Place, publisher, and date of publication | Durham : I B M,c2003 |
International Standard Book Number | 9780738499567 |
797 2# - LOCAL ADDED ENTRY--CORPORATE NAME (RLIN) | |
Corporate name or jurisdiction name as entry element | ProQuest (Firm) |
856 40 - ELECTRONIC LOCATION AND ACCESS | |
Uniform Resource Identifier | <a href="https://ebookcentral.proquest.com/lib/orpp/detail.action?docID=3306370">https://ebookcentral.proquest.com/lib/orpp/detail.action?docID=3306370</a> |
Public note | Click to View |
No items available.