Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Exploring IBM iSeries
Document related concepts
Transcript
“...indisputably the most authoritative Exploring IBM iSeries account of the ins and out of [iSeries] computing.” —Small Computer Book Club TE AM FL Y ELEVENTH EDITION The Instant Insider’s Guide to IBM’s Popular Mid-range Servers Foreword by Al Zollar, General Manager, IBM iSeries Jim Hoskins and Roger Dimmick Team-Fly® Over 80,000 copies sold! Exploring IBM ~ iSeries Eleventh Edition Other Titles of Interest From Maximum Press Exploring IBM e-Business Software: Second Edition: Young, 1-931644-00-4 Exploring IBM Technology, Products, & Services, Fifth Edition: Hoskins, 1-885068-82-4 Exploring IBM ~ pSeries, Eleventh Edition: Hoskins & Bluethman, 1-885068-81-6 Exploring IBM ~ xSeries, Twelfth Edition: Hoskins, Wilson & Winkel, 1-885068-83-2 Exploring IBM ~ zSeries and S/390 Servers, Eighth Edition: Hoskins & Frank, 1-885068-91-3 Exploring IBM Network Stations: Ho, Lloyd, & Heracleous, 1-885068-32-8 Building Intranets With Lotus Notes and Domino 5.0, Third Edition: Krantz, 1-885068-41-7 Internet Marketing for Your Tourism Business: Sweeney, 1-885068-47-6 Marketing With E-Mail, Third Edition: Kinnard, 1-885068-68-9 Business-to-Business Internet Marketing, Fourth Edition: Silverstein, 1-885068-72-7 Marketing on the Internet, Sixth Edition: Zimmerman, 1-885068-80-8 101 Internet Businesses You Can Start From Home: Sweeney, 1-885068-59-X The e-Business Formula for Success: Sweeney, 1-885068-60-3 101 Ways to Promote Your Web Site, Fourth Edition: Sweeney, 1-885068-90-5 Internet Marketing for Information Technology Companies, Second Edition: Silverstein, 1-885068-67-0 Internet Marketing for Less Than $500/Year, Second Edition: Yudkin, 1-885068-69-7 The Business Guide to Selling Through Internet Auctions: Hix, 1-885068-73-5 For more information, visit our Web site at www.maxpress.com or e-mail us at [email protected] Exploring IBM ~ iSeries Eleventh Edition The Instant Insider’s Guide to IBM’s Popular Mid-range Servers Jim Hoskins Roger Dimmick MAXIMUM PRESS 605 Silverthorn Road Gulf Breeze, FL 32561 (850) 934-0819 www.maxpress.com Publisher: Jim Hoskins Manager of Finance/Administration: Joyce Reedy Production Manager: Gina Cooke Cover Design: Lauren Smith Copyeditor: Ellen Faulk Proofreader: Jacquie Wallace Indexer: Susan Olason Printer: P.A. Hutchison This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in rendering professional services. If legal, accounting, medical, psychological, or any other expert assistance is required, the services of a competent professional person should be sought. ADAPTED FROM A DECLARATION OF PRINCIPLES OF A JOINT COMMITTEE OF THE AMERICAN BAR ASSOCIATION AND PUBLISHERS. Copyright 2003 by Maximum Press. All rights reserved. Published simultaneously in Canada. Reproduction or translation of any part of this work beyond that permitted by Section 107 or 108 of the 1976 United States Copyright Act without the permission of the copyright owner is unlawful. Requests for permission or further information should be addressed to the Permissions Department, Maximum Press. Recognizing the importance of preserving what has been written, it is a policy of Maximum Press to have books of enduring value published in the United States printed on acid-free paper, and we exert our best efforts to that end. Library of Congress Cataloging-in-Publication Data Hoskins, Jim. Exploring IBM eserver iSeries / Jim Hoskins and Roger Dimmick.— 11th ed. p. cm. Rev. ed. of: Exploring IBM eserver iSeries and AS/400e computers. 10th ed. 2001. Includes index. ISBN 1-885068-98-0 1. IBM microcomputers. I. Dimmick, Roger, 1932- II. Hoskins, Jim. Exploring IBM eserver iSeries. III. Title. QA76.8.I1015 H668 2002 004.1’45—dc21 2002151309 Acknowledgments Many “IBMers” assisted us in preparing the eleventh edition of this book despite their demanding schedules. Some provided information about their products. Others read the manuscript and provided helpful comments. To all those who assisted, we thank you. We would especially like to thank John Plansky, Dianne Moench, and Joseph McCoy for helping coordinate this edition. We would also like to thank Bill Schaffer in Boulder CO, Scott Frederick and Dick Odell in Rochester. Disclaimer The purchase of computer software or hardware is an important and costly business decision. While the author and publisher of this book have made reasonable efforts to ensure the accuracy and timeliness of the information contained herein, the author and publisher assume no liability with respect to loss or damage caused or alleged to be caused by reliance on any information contained herein and disclaim any and all warranties, expressed or implied, as to the accuracy or reliability of said information. This book is not intended to replace the manufacturer’s product documentation or personnel in determining the specifications and capabilities of the products mentioned in this book. The manufacturer’s product documentation should always be consulted, as the specifications and capabilities of computer hardware and software products are subject to frequent modification. The reader is solely responsible for the choice of computer hardware and software. All configurations and applications of computer hardware and software should be reviewed with the manufacturer’s representatives prior to choosing or using any computer hardware and software. Trademarks The words contained in this text which are believed to be trademarked, service marked, or otherwise to hold proprietary rights have been desig- nated as such by use of initial capitalization. No attempt has been made to designate as trademarked or service marked any personal computer words or terms in which proprietary rights might exist. Inclusion, exclusion, or definition of a word or term is not intended to affect, or to express judgement upon, the validity of legal status of any proprietary right which may be claimed for a specific word or term. Foreword Designing a computing system that is easy to manage, offers an extensive portfolio of industry-specific solutions and provides mainframe-class security and reliability might seem like an almost impossible task. And yet, these are the exact design points that have inspired an enduring success story in an industry where progress is often measured only by the next crank of the technology. Make no mistake about it. Technology is essential. It has put the power of yesterday’s room-sized computer into today’s laptop. But the secret behind a computing architecture based on simplicity, integration and speed of deployment goes much deeper. Its roots are found in the people who write applications for the architecture, and the customers who use it. Since I joined IBM 26 years ago as a systems engineer, I have always been in awe of the technical innovation of our IBM development team in Rochester, Minnesota. Rochester’s pioneering work with the System/38 and AS/400 included delivering an object oriented architecture before most people even knew what objects were. Rochester delivered single level storage and a virtualized machine architecture before people could imagine the possibility of their being adapted into logical partitioning and capacity on demand features that we offer on today’s iSeries servers. Rochester listened when customers asked for a simple solution— one that would allow them to spend their time managing their businesses and not their computers. They listened when iSeries business partners asked for the kind of reliability and quality that would distinguish their solutions from those of their competitors. And they listened again when customers asked them to protect their application investments, by continuing to enhance their offerings while resisting the temptation to start from scratch. The incredible ability to adopt new technology is, perhaps, what is so exciting for me about the iSeries. It’s adaptability has enabled it to take on the challenges of multiple computing generations, the latest of which we see as the era of e-business on demand. When IBM established the concept of e-business in 1996, it was clear that the global economy was on the verge of an enduring, tech- nology-led business revolution. The early phase of that e-business revolution was characterized by simple strategies such as publishing product information to the Internet and the first simple web-based transactions. The second, integrating phase of e-business adoption was marked by strategies to link internal processes end-to-end and by companies connecting across the Web to their external value nets. Today, the industry is moving into a new era of e-business, the on-demand era. Now companies are driven by the need to optimize their e-business operations, dynamically responding to the needs of customers, partners and employees. With the high pressure and fast-moving nature of today’s on-demand world, a business must be agile enough to adjust to constant change. That’s why we’ve rapidly adapted the iSeries to help customers meet the challenges of the on-demand era. iSeries is pioneering new on-demand technologies, like On/Off Capacity on Demand, and has become a multiplatform server that runs multiple operating systems simultaneously, dynamically adjusting to changing e-business requirements. Exactly what you need to thrive in today’s on demand era. Al Zollar, General Manager, IBM eServer iSeries Table of Contents ix Table of Contents Introduction .......................................................................................... xvii What This Book Is ......................................................................... xvii What This Book Is Not .................................................................. xvii How to Use This Book ................................................................. xviii Your “Members Only” Web Site .................................................... xix A Glance Backward ......................................................................... xx Chapter 1: IBM eServer iSeries 1 IBM’s e-business on demand Strategy ................................................ 1 Open Standards ......................................................................... 2 Integration ................................................................................. 2 Virtualization ............................................................................. 3 Autonomic Computing .............................................................. 3 IBM’s eServer and TotalStorage Strategy ........................................... 4 Pervasive Computing ......................................................................... 5 About IBM eServer iSeries ................................................................. 7 What Makes Up an iSeries System? ................................................... 7 Advanced Application Architecture ................................................... 9 Meet the Family ............................................................................... 12 iSeries Model Specifics ..................................................................... 16 iSeries Model 800 (i800) Specifics ............................................ 16 Model 800 Value ............................................................. 16 Model 800 Standard ........................................................ 17 Model 800 Advanced ....................................................... 18 iSeries Model 810 Specifics ...................................................... 18 iSeries Model i825 Specifics ..................................................... 21 iSeries Model i870 Specifics ..................................................... 24 iSeries Model i890 Specifics ..................................................... 28 Capacity on Demand (CoD) ............................................................ 31 iSeries Dedicated Servers for Domino ...................................... 31 iSeries for Domino Model i810D ..................................... 32 iSeries for Domino Model i825D ..................................... 34 ix x Exploring IBM ~ iSeries TE AM FL Y Performance Overview .................................................................... 34 Benchmark Testing .................................................................. 34 Server vs. Interactive Environments ......................................... 36 Typical Business Workload Performance (CPW) .............. 36 Interactive Performance ................................................... 36 iSeries for Domino Benchmarks ....................................... 37 A Closer Look ................................................................................. 38 Hardware Architecture Overview ............................................ 39 Power Microprocessors ................................................................... 44 The SStar Microprocessor ................................................ 46 The POWER4 Microprocessor ........................................ 48 Processor Core Overview ............................................ 49 Storage Hierarchy .................................................................... 51 Main Storage ........................................................................... 52 Storage Management ............................................................... 53 Auxiliary Storage ..................................................................... 54 Diskette Storage ............................................................... 55 Disk Storage ..................................................................... 55 Optical Libraries .............................................................. 58 Tape Storage .................................................................... 58 OptiConnect ............................................................................ 59 OptiMAL Connect .................................................................. 61 System Availability Functions .................................................. 62 OS/400 Subsystems and Logical Partitioning ................... 64 Multisystem Coupling ...................................................... 68 Data Resiliency and Application Resiliency ..................... 68 Continuous Availability Clustering .................................. 68 Disaster Tolerance ............................................................ 71 Upgrade Paths ......................................................................... 72 Upgrading within a Model ............................................... 72 Upgrading through a System Unit Swap .......................... 72 Upgrades between Models ............................................... 73 Packaging Technology ............................................................. 73 Fiber Optic Bus ....................................................................... 74 Chapter 2: Options and Peripherals 75 Workstations ................................................................................... 76 InfoWindow II Workstations ................................................... 77 Team-Fly® Table of Contents xi Operations Console ................................................................. 77 Personal Computer (PC) Terminal Emulation ......................... 78 Retail Workstations ................................................................. 80 Printers ............................................................................................ 81 Combined-Function I/O Processor ................................................... 84 Integrated xSeries Server .................................................................. 85 xSeries Server ........................................................................... 92 Workstation Adapters .............................................................. 93 LAN-Connected Terminals ...................................................... 94 Auxiliary Storage Options ............................................................... 94 Disk Storage Overview ............................................................ 95 Model 2105 Enterprise/Versatile Storage Server .............. 96 Disk Adapters .................................................................. 97 Tape Storage ............................................................................ 99 IBM TotalStorage Ultrascalable Tape Library #3584 .. 100 Auxiliary Storage Controllers ................................................ 103 Optical Storage Overview ..................................................... 103 The #3995 Optical Library ............................................ 104 DVD/CD-ROM ............................................................. 105 Communications Options .............................................................. 106 Local Area Networks............................................................. 107 Ethernet ......................................................................... 107 Token-Ring Local Area Networks ................................. 108 Asynchronous Transfer Mode ........................................ 109 Wide Area Networks ............................................................. 110 Modems ................................................................................. 111 Power and Packaging Options ....................................................... 112 UPS for Models 270 and 820 ................................................ 112 Packaging Expansion Features .............................................. 113 iSeries Rack-Mount Capabilities .................................... 113 Cryptographic Processors .............................................................. 113 Chapter 3: iSeries Software 115 Software Architecture Overview .................................................... 115 How the Software Layers Are Different ................................ 119 Will AS/400 and S/3X Programs Work? ................................ 121 Inside Application Compatibility ........................................... 122 Application Programs .................................................................... 123 xii Exploring IBM ~ iSeries Can Prewritten Programs Fit the Bill? ................................... 123 Cross-Industry Application Programs .................................... 124 Data Warehousing ......................................................... 124 Data Mining .................................................................. 125 Collaborative Computing .............................................. 127 Portable Application Solution Environment ................... 129 AFP PrintSuite ................................................................ 130 Advanced Print Utility (APU) .................................... 131 Page Printer Formatting Aid (PPFA) .......................... 131 AFP Toolbox .............................................................. 131 SAP R/3 AFP Print ..................................................... 132 Industry-Specific Application Programs................................. 132 Custom Application Programs ....................................... 133 Chapter 4: Operating Systems 135 Introduction to Operating System Concepts .................................. 135 OS/400—An Executive Overview .................................................. 136 A Closer Look at OS/400 .............................................................. 137 Integrated File System ............................................................ 138 Stream Files .................................................................... 141 File System Support........................................................ 142 Network File System ...................................................... 143 Remote File System ........................................................ 144 CICS Transaction Server for iSeries (5769-DFH) ........... 145 Client for Windows NT/2000 File System .................. 146 DB2 Universal DataBase (UDB) for iSeries ........................... 146 What Is a Relational Database? ..................................... 147 Records and Fields ..................................................... 147 Physical and Logical Files .......................................... 148 Concurrency and Lock Management ......................... 151 DB2 UDB Details and Components ............................... 152 DB2 Query Manager and SQL Development Kit ........... 153 DB2 Symmetric Multiprocessing (DB2 SMP) ............ 154 DB2 UDB Extenders for iSeries ................................. 155 DB2 OLAP Server ..................................................... 155 QMF for Windows for iSeries .................................... 156 DB2 Data Propagator ................................................ 156 Database Monitor ...................................................... 156 Table of Contents xiii ODBC ....................................................................... 157 iSeries ODBC Driver for Linux ................................. 157 JDBC ......................................................................... 158 Data Striping ............................................................. 158 DCE Base Services/400 .............................................. 159 Distributed Data Management .............................................. 162 Content Manager OnDemand for iSeries (5722-RD1) ........................................... 162 Communications Support ...................................................... 162 TCP/IP ........................................................................... 163 Virtual Private Networks ........................................... 168 Systems Network Management ...................................... 170 Systems Network Architecture ....................................... 171 Wireless Local Area Network ........................................ 172 S/390 Communications Support .................................... 172 iSeries Access Family (5722-XW1) ........................................ 173 iSeries Access for Windows ............................................ 181 iSeries Access for the Web .............................................. 185 XML Toolkit for iSeries (5733-XT1) ......................... 186 WebSphere Host Access Transformation Server ............. 187 iSeries Access for Wireless .............................................. 187 WebSphere Host Publisher V4 ....................................... 187 Lotus Notes Client Support ....................................... 188 Commitment Control and Journaling ............................ 188 Backup/Recovery ................................................................... 189 Tivoli Storage Manager V5.1 ......................................... 191 Backup Recovery and Media Services/400 ..................... 192 BRMS Network Feature ............................................ 194 BRMS Advanced Functions Feature ........................... 194 System-Managed Access Path Protection ....................... 195 Hierarchical Storage Management ................................. 196 Systems Management ............................................................. 197 iSeries Navigator ............................................................ 197 SystemView System Manager/400 .................................. 202 Management Central ..................................................... 203 System-Detected Software Problems .......................... 205 Management Central Methodology ............................ 205 Management Central Pervasive ...................................... 206 Enterprise Identity Mapping (EIM) ................................ 208 iSeries Performance Tools .............................................. 208 xiv Exploring IBM ~ iSeries PATROL for iSeries—Predict .................................... 209 NetFinity for iSeries ................................................... 211 WebSphere Development Studio ............................................ 212 WebSphere Studio for iSeries ......................................... 215 WebSphere Studio Workbench ................................... 216 WebSphere Studio Site Developer Advanced .............. 216 Web Services .............................................................. 216 WebSphere Development Studio Client ...................... 216 Integrated Language Environment (ILE) ........................ 219 Application Development ToolSet (ADTS) ............................ 219 Application Development Tools—Printing ..................... 220 Advanced Function Printing (AFP) ........................................ 222 Intelligent Printer Data Stream (IPDS) ........................... 222 IBM Infoprint Server for iSeries ..................................... 223 IBM Infoprint Designer for iSeries ................................. 225 The iSeries Kernel Threads .................................................... 226 Application Environments ............................................. 226 Frameworks ............................................................... 226 OpenDoc ................................................................... 230 ORB Support ............................................................. 230 Java ............................................................................ 231 Product Preview—Altered Program Objects .............. 238 Linux for iSeries ............................................................. 239 Globalization ................................................................................. 241 Unicode ................................................................................. 241 International Components for Unicode .......................... 242 Grid Computing ............................................................................ 244 Chapter 5: iSeries Communications and e-business— An Introduction 245 Computer Communications in the Office— An Introduction ......................................................................... 245 iSeries Extreme Support Personalized ............................................ 246 Universal Connection ............................................................ 247 IBM Electronic Service Agent for iSeries (Service Agent) 248 IBM Electronic Customer Support Communications............. 248 Filter Lists ...................................................................... 250 System Clustering .................................................................. 251 ObjectConnect for iSeries ...................................................... 253 Table of Contents xv IBM’s Overall Networking Blueprint ............................................. 253 Application Support Layer .................................................... 255 Multi-Vendor Application Program Interfaces ............... 255 The Common Program Interface (CPI-C) .................. 256 The Remote Procedure Call ....................................... 257 The Messaging and Queuing Interface (MQSeries) .... 257 Transport Layer Security (TLS) ............................................. 259 e-business ............................................................................... 260 Network Quality of Service (QoS) ................................. 261 Intranet .................................................................................. 263 IBM SecureWay: iSeries and the Internet ....................................... 263 Cryptographic Access Provider .............................................. 264 Digital Signatures .................................................................. 266 HTTP Server for iSeries ......................................................... 266 HTTP Server for iSeries—Powered by Apache ...................... 270 Digital Certificate Manager with SSL ............................ 272 Secure Sockets Layer (SSL) .................................................... 273 Security Wizard ..................................................................... 274 Firewalls ................................................................................ 275 iSeries and the Internet .......................................................... 276 IBM WebSphere Application Server for iSeries (WAS) ... 278 WebSphere Host Integration ...................................... 279 WebSphere Application Server—Express for iSeries ....... 279 Telephone Directory V5.1 for iSeries ......................... 281 Web Services Object Runtime Framework (WORF) .. 281 Net.Data ........................................................................ 282 WebSphere Commerce Suite .......................................... 283 Domino 5.0.5 for iSeries ........................................................ 285 Domino-Licensed Program Server Choices .................... 289 Domino-Licensed Program Client Choices ..................... 289 iNotes ........................................................................ 289 Notes ......................................................................... 290 Domino Designer ....................................................... 290 iNotes with Domino Per Server CAL......................... 290 OS/400 Directory Server ....................................................... 290 Chapter 6: iSeries and Your Business 292 What Are My Business Computing Needs? ................................... 293 Choosing the Software ................................................................... 294 xvi Exploring IBM ~ iSeries Choosing the Hardware ................................................................. 296 Small Business Environment, Manufacturing— Bob’s Gearbox Co. ............................................................ 297 Medium Business Environment—Johnson & Thornbush ...... 299 Hardware Configuration ............................................... 302 Johnson & Thornbush Software Scenario ...................... 302 Large Business Environment—Atole Enterprises ................... 304 Atole Solution Scenario .................................................. 304 Dedicated Server for Domino Web Serving Environments .... 307 Server Selection ...................................................................... 309 The Competitive View of 64-Bit Processing ........................... 310 The Business Decisions .................................................................. 311 Cost Justification ................................................................... 312 Hardware Maintenance ................................................. 312 Software Maintenance ................................................... 313 Technical Support .......................................................... 313 Facilities ......................................................................... 313 Education/Training ........................................................ 314 Communications Line Costs .......................................... 314 Environmental Costs ...................................................... 314 Enhancing Applications ................................................. 314 Benefits .................................................................................. 315 Improved Business Cycle ................................................ 315 Inventory Reduction ...................................................... 315 Improved Productivity ................................................... 315 Improved Quality ........................................................... 316 Improved Customer Service ........................................... 316 Competitive Advantage .................................................. 316 Lease or Buy? ........................................................................ 318 Education .............................................................................. 319 Security .................................................................................. 321 Loss Prevention .............................................................. 323 Theft Prevention ............................................................ 324 Service ........................................................................................... 325 Migrating from System/3X and AS/400 to iSeries .......................... 326 Software Maintenance ........................................................... 326 Sizing a Replacement iSeries .................................................. 327 Introduction xvii Introduction What This Book Is This book is dedicated to IBM’s midsize business computers—namely, the IBM eServer iSeries. Here we will help you understand the thinking behind the IBM eServer family and will then focus on the iSeries segment of that family. The iSeries family is introduced in a way that is understandable to the business user. This book will help you see how you can apply iSeries hardware and software to meet today’s business needs. Specific iSeries hardware and software configurations for typical environments are offered. Many important computer automation planning issues are also discussed. What This Book Is Not Many computer books try to be all things to all people, covering everything from checkbook balancing to the Space Shuttle’s redundant flight computer complex. This book is not a general overview of computers; it is specific to IBM’s iSeries systems (a broad enough subject for any single book). This book is neither a technical reference manual (IBM will sell you that) nor a guide to computer programming. It does, however, provide a good understanding of IBM’s iSeries systems and how to use them in the business environment. Finally, this book does not expect you to be an engineer. Business people are typically short on time and patience as far as technical matters are concerned. Although some technical discussions are necessary, we have tried to keep these as simple and concise as possible while still conveying necessary and useful information. xvii xviii Exploring IBM ~ iSeries How to Use This Book Chapter 1 introduces the IBM eServer iSeries and the thinking behind the IBM eServer family. With its proven reliability and self-managing, self-healing technology, the iSeries servers virtually run themselves, allowing the customer to regain control of Information Technology (IT) costs and deadlines. Changes in e-business are being driven at an unprecedented pace, and it is necessary that the server be able to adapt at the same rate. With logical partitioning and Capacity upgrade on Demand (CUoD), the iSeries has exceptional flexibility. Operating system flexibility enables the iSeries to adapt to all popular environments including: Linux, Windows, WebSphere, and OS/400 today and in 2004 AIX will be added. The iSeries’ on-demand operating environment includes integration, virtualization, open standards, and autonomic computing capabilities. All of the new servers support fully dynamic logical partitioning (LPAR) for OS/400 and Linux. CuoD options are available on iSeries Models i825, i870, and i890 for both temporary and permanent activation of processors. Open standards support includes Java, XML, Linux, TCP/IP, OGSA and Windows-based server management. Technologies that self-diagnose, self-configure, and self-heal much like the human anatomy are included in iSeries servers. OS/400 V5R2 includes extensive self-managed technology features automatic performance adjustment, and single sign-on with Enterprise Identity Mapping. SQE delivers self-optimizing queries tuned for the most complex business applications. After a quick overview of the iSeries line, we move in for a glance at the technology behind iSeries. A section on performance and benchmarks is included to assist in comparing the iSeries family of computers against competitive computers. Chapter 2 surveys the many hardware options available for iSeries systems, including terminals, printers, disk expansion, and communications. The section on I/O devices and adapters is provided primarily as a reference to help you identify and select the proper options for your iSeries system. Chapter 3 describes the workings of the three types of programs necessary to do productive work with iSeries computers—application programs, operating systems, and System Licensed Internal Code (SLIC)—and continues with a discussion of application programs. The question of “prewritten” versus “custom” application programs is addressed. Introduction xix Chapter 4 takes a closer look at the OS/400 operating system used on the iSeries. First, basic operating system concepts are discussed in terms of their usefulness in the business environment. Then the iSeries operating system products are described including: the integrated file system, DB2 UDB for iSeries, iSeries Navigator, iSeries Access, communications support, systems management features, advanced function printing, Management Central, WebSphere Development Studio, open standards-based interoperability, object-oriented programming languages (Java, C, C++), and Linux for OS/400. WebFacing discusses the process of moving the green-screen 5250 applications to an Internet environment as well as the tools to make that movement efficient. Emerging Internet technologies like grid computing, Unicode, and International Components of Unicode (ICU) are introduced. Chapter 5 shows how specific iSeries options and software products are used to participate in the computer communications environments commonly found in businesses. The emphasis of Chapter 5 has shifted from communications to e-business, encompassing both business-to-business and business-to-customer. Included discussions are HTTP Server Powered by Apache, WebSphere Application Services, and WebSphere Commerce Studio. The SecureWay for iSeries and Secure Sockets Layer security services are discussed. Chapter 6 discusses issues related to the selection of iSeries hardware and software for small, medium, and large businesses as well as a Dedicated Server for Domino growth scenario. Hypothetical businesses are outfitted with the appropriate iSeries configurations. Important topics such as user training, ergonomics, security, maintenance, leasing versus buying, and cost justification are then discussed. In particular, iSeries online education and security and its importance in an Internet environment have been expanded upon. Your “Members Only” Web Site The iSeries world changes every day. That’s why there is a companion Web site associated with this book. On this site you will find updates to the book and other iSeries-related resources of interest to anyone involved with the iSeries. However, you need a user ID and password to access this site. xx Exploring IBM ~ iSeries To get into the “Members Only” section of the companion Web site, go to the Maximum Press Web site located at www.maxpress.com and follow the links to the companion Web site for this book. When you try to enter, you will be asked for a user ID and password. Type in the following: • For your user ID, enter: iSeries11e • For your password, enter: Costa TE A Glance Backward AM FL Y You will then be granted full access to the “Members Only” area. Visit the site often and enjoy the updates and resources with our compliments—and thanks again for buying the book. We ask that you not share the user ID and password for this site with anyone else. On July 30, 1969, IBM executives from the entire company joined 1,200 IBMers at their plant site in Rochester, Minnesota, to announce the System/3 computer shown in Figure I.1. This system was the first computer totally developed in Rochester. Although only of historical interest today, the System/3 represented some significant advances in the technology of its time. For example, it introduced Monolithic Systems Technology, which allowed engineers to package more circuitry in a smaller space, as well as a punch card one-third normal size that held 20 percent more information. This was the first advancement in punchcard technology in over forty years. To celebrate the announcement of the System/3, Rochester IBMers held a dance featuring Ralph Marterie and his orchestra in a newly constructed building. The Rochester plant, which became a full IBM division in November of that year, was tasked to develop a “low-end” computer family. One System/3, fondly named “Old Reliable,” ran faithfully until it was shut down in September 1973. When it was finally retired, its meter showed that it had run for 15,377.97 hours, representing more run time than any other system in existence at that time. The System/32, shown in Figure I.2, was the next member of the family. It was announced in January 1975 and featured direct keyboard data entry and a display that could present up to six rows of Team-Fly® Introduction Figure I.1. IBM System/3. Figure I.2. IBM System/32. xxi xxii Exploring IBM ~ iSeries text forty characters long. The System/32 had up to 32K of memory and up to 13 MB of fixed-disk storage. The System/34 computer, announced in April 1977, was the first system truly designed to manage multiple (local and remote) workstations (i.e., terminals and printers), each located up to 5,000 feet away from the computer. This allowed it to perform tasks for up to eight local users simultaneously. The System/34, shown in Figure I.3, provided up to 256K of memory and 13 MB of fixed disk. Next came the System/38, announced in October 1978. This represented a divergence from its S/3X predecessors, offering a new architecture optimized for application development productivity. The System/38, shown in Figure I.4, could support up to 32 MB of memory, 14 GB of disk storage, and 256 local workstations. Once again, building on the architectural base of the System/34, the first System/36 was announced in May 1983 (Figure I.5). It grew to support up to 7 MB of main memory, 1.4 GB of disk storage, and 72 local workstations. Other models of the System/36 varying in processing power and capacity were announced over time. Collectively the System/3, System/32, System/34, System/36, and System/38 are known as the System/3X family of computers. Figure I.3. IBM System/34. Introduction Figure I.4. xxiii IBM System/38. The last S/36 model (the 5363) was enhanced and renamed the IBM AS/Entry system. IBM has announced its intention to no longer support the AS/Entry products. This means that they are no longer vital to IBM’s midrange product strategy. On June 20, 1988, IBM unveiled the AS/400 family of products. The AS/400 has close architectural ties with System/38, in most cases providing application program compatibility with both the System/36 and the System/38. The AS/400 Advanced/36 allowed coexistence of the System/36 SSP operating system and applications with the OS/400 operating system and applications. When coexisting, the two operating systems shared a common file system and made calls to use each other’s I/O functions. During its lifetime, the AS/400 system implemented the ApplicationCentric, Open Systems Computing, Client/Server Computing, Distribut- xxiv Exploring IBM ~ iSeries Figure I.5. IBM System/36. ed Computing Systems, and Network Computing Systems paradigms. Those computing paradigms also exist on the iSeries systems. In October of 2000, IBM introduced the IBM eServer brand under which all future servers would fall. The four lines under the IBM eServer brand became xSeries (Intel processor-based), pSeries (UNIX based and derived from the RS/6000 line), iSeries (derived from the AS/400 family), and zSeries (derived from the S/390 mainframe world). The unified IBM eServer brand reflects the fact that IBM is evolving its whole server line to meet the needs of today’s fast-changing e-business environment. IBM ~ iSeries 1 1 IBM eServer iSeries T his chapter begins with our exploration of the IBM eServer iSeries family of mid-size servers. Before we focus in on the iSeries however, let’s first pause for a quick look at some key elements in IBM’s overall vision for the future of computing. IBM’s e-business on demand Strategy IBM has been laser-focused on a concept called e-business on demand ever since their introduction in October of 2002. In many respect, you can already see the results of this focus in today’s iSeries systems (as you will see). And the $10 billion dollars IBM is committing to e-business on demand means that this strategy will increasingly manifest itself in all IBM computer hardware, software, and services over time. At it’s core, e-business on demand refers to a computing infrastructure (hardware, software, and services all working together) that can support today’s business needs and enables the migration of a business down the e-business adoption path. The term “e-business” has come to stand for the huge array of Internet-related techniques and tools a business can use to move itself forward in all areas. e-business represents the “prime mover” of today’s business world offering virtually unlim1 2 Exploring IBM ~ iSeries ited possibilities for the flexible and an inevitable death spiral for those businesses unable or unwilling to take advantage of it. While the typical computing infrastructures in use today meet today’s needs (to a varying degree), many are not prepared to support a highly dynamic, responsive, and integrated business environment—which is exactly where e-business is headed. There are four basic elements to IBM’s overall e-business on demand strategy: Open Standards The days of locking in to a specific vendor’s proprietary computing architecture are gone. Today, a computing infrastructure needs the flexibility (in vendor choice, information exchange, application integration, application selection, etc.) that only comes when the infrastructure is built around open standards defined by vendor-neutral standard bodies. Standards with names like Java, SQL, XML, and Linux. Most businesses employ more than one type of computer/operating system. Adherence to open standards will enable these different types of systems to work together or “integrate” over time at a lower cost. Other benefits resulting from the adherence to open standards include leveraging investments/skills in existing heterogenous computing infrastructures, speed of deployment for new projects, and freedom of choice. For the same reasons, adherence is also important when selecting storage devices for use in an e-business infrastructure. Integration By adhering to open standards, you will be laying the groundwork for the end-to-end integration goal of e-business. This integration of key business processes throughout the inner workings of a business, with its’ suppliers, and customers is one of the crown jewels of e-business. So businesses should not allow the construction of independent computer solutions (servers, operating systems, middleware, and applications) without giving careful thought to the ability to integrate these new solution (immediately or in the future) with the rest of the computing infrastructure. IBM ~ iSeries 3 Virtualization With virtualization, what you see is not what you get. Here we are discussing the need to accommodate change in the e-business environment. In the case of virtualization, a computer system can change the amount and type of resource and the priority a user receives in concert with the changing needs of that user. In its simplest form, virtualization allows for the dynamic allocation of processing power, storage, and other such resources to users based on need. Through this dynamic allocation, the users can get the most out of a given computer system resulting in better service and less wasted resource. Virtualization also is used to “subdivide” a single large computer system into smaller “virtual” computer systems each running possibly different operating systems (e.g. AIX or Linux) and applications. This flexibility along with the reliability afforded by protecting problems in one users “virtual computer” from disrupting the other users play right into the hands of e-business. Autonomic Computing Autonomic is a term IBM borrowed from the vernacular of the human central nervous system. The goal of autonomic computing is for the computing infrastructure to manage itself just as the central nervous system manages the human body—without our conscious effort. By making computer systems self-optimizing, self healing, self-configuring, and self-protecting, the costs associated with systems management and unscheduled down time are reduced. The more complex the computing system, the more important autonomic computing becomes. Since complexity goes up as you progress along the e-business adoption path— self-managing the complexity is a critical requirement for computing infrastructures going forward. eServer iSeries systems already have some characteristics that make them in line with the e-business on demand strategy as we will see. The ability to automatically activate a spare processor to replace a failing one along with memory error detection and correction help keep iSeries servers running. Over time, more and more elements will be incorporated in iSeries as well as the rest of the eServer families. 4 Exploring IBM ~ iSeries IBM’s eServer and TotalStorage Strategy Underlying IBM’s e-business on demand strategy is a completely revamped line of servers that make up the IBM eServer family and associated storage devices under the IBM TotalStorage brand. The IBM eServer family includes: • eServer zSeries (replacing the S/390 family) The zSeries is IBM’s family of mainframe servers offering highend capacity, performance, security, and reliability. They are designed to run mission-critical applications for an enterprise. • eServer pSeries (replacing the RS/6000 family) The pSeries is IBM’s UNIX server family designed for both traditional business applications and high-performance computing. The pSeries can scale-up in processing power both by upgrading to more powerful models and by linking (clustering) multiple pSeries systems together to achieve supercomputer performance. The pSeries systems can run AIX or Linux operating systems. • eServer iSeries (replacing the AS/400 family) The iSeries uses the OS/400 operating system, which includes many functions (Universal DB2 database, security, etc.) that often are separate add-on products for most other computers. This helps reduce the total cost of ownership and makes iSeries systems easier to manage than other computers offering similar power. The iSeries also conforms to open standards and can run both Linux and soon AIX under OS/400. • eServer xSeries (replacing the Netfinity family) The xSeries servers use from one to sixteen Intel microprocessors to deliver Windows servers with mainframe-like reliability through IBM’s x-Enterprise architecture. • eServer Clusters Clusters are not a separate product line but rather configurations of multiple eServer systems connected together through high-speed links. With clusters, you can combine the performance and capacity of multiple eServer systems while retaining the simplicity of managing them as if they were a single system. IBM ~ iSeries • 5 eServer Blades The IBM BladeCenter utilizes Intel microprocessors to make server “blades” that can be clustered together to deliver high performance in a modular and dense rack-mounted package. The IBM TotalStorage family consists of disk storage devices, tape drives, optical storage devices, and storage software. TotalStorage hardware is designed based on open standards defined by organizations like the Storage Networking Industry Association (SNIA). As with servers, storage devices that employ open standards provide more flexibility when building and evolving an e-business infrastructure over time. Specialized storage management software helps users deal with issues like information availability, backup, security, and migration of infrequently accessed information to less expensive storage media. The IBM eServer and TotalStorage product lines are both designed to reduce the total cost of owning and operating a business-critical ebusiness computing infrastructure (including the hardware purchase price, software licensing, installation, user training, upgrade requirements, maintenance, power consumption, facilities, systems management resources, etc.). According to a study of the operating e-business infrastructures of twenty-four organizations (ITG, December 2002), using IBM eServer systems in an e-business infrastructure can help to significantly reduce total cost of ownership (TCO) over a five-year period. Lower TCO translates into greater return on e-business infrastructure investments. Pervasive Computing Pervasive Computing (PvC) is characterized by the need to support a growing set of wireless devices, including PDAs, HDML-based phones, WAP phones, iMode phones, mobile companions, pagers, and so forth. This wave of e-business will provide greater mobility and convenience to users of e-business solutions. The standards for this set of devices and the protocols to be used are still in a state of flux. Pervasive Computing, then, is convenient access, through a new class of appliances, to relevant information, with the ability to take action on it when and where needed. Connectivity is one dimension that governs whether the solution is standalone or is connected in real time to a number of other services Exploring IBM ~ iSeries AM FL Y provided on the wireless network. Client models range from thin clients, where all data and application logic are managed on a central server, to a fatter client, where some of the application code is maintained on the individual mobile device. Data formats represent the various ways application content can be represented as it is transported from an application server to the client device where user interaction occurs. Protocol represents a number of other aspects of a PvC solution, including how application sessions are managed, how user authentication is performed, and how data security is managed between application server and the target client device. There are browser clients, in which case the application runs on a Web browser, not requiring an install on the device, and the logic exists solely on the server. There is also the installed client, in which case the application client is installed on the device and requires support for either Java Micro Edition or C++, sockets, and so forth. In this case the logic is split between the client and the server. The way information is encoded as it is transported to the mobile device can vary from one wireless solution to another. Current protocols include HTML, WML, and XML. Bluetooth is a wireless technology optimized for use between devices in close proximity to each other. Wireless LANs use a standard called 802.11 to enable reasonably high bandwidth (11 MB/s) connectivity between mobile devices and the network. Connectivity support is up to two miles and is often used in factory floor solutions where a number of mobile devices are used to communicate with a central server. Also in the game are the cellular telephone companies and their wireless infrastructure. The iSeries system provides many of the key building blocks required for a pervasive computing solution. The presence of JVM, Management Central Pervasive, and so forth, positions iSeries to be a significant player in pervasive computing. XML parser and XSL stylesheet runtimes as integrated components of OS/400 and the XML extenders for DB2 UDB enable two-way data interchange services between DB2 and XML. WebSphere Transcoding Publisher provides a core set of services to convert Web site content to an optimal form for a number of mobile computing devices. Additional tools are provided to simplify the task of extending existing 5250 solutions to a mobile computing model. IBM’s WebFacing tools and Host Publisher provide support for extending 5250 solutions to the Web to enable existing applications to drive a new class of mobile devices. If your pervasive computing environment is OS/400 V4R5 or V5R1, you need to use transcoding Publisher. If your pervasive environment is V5R2, use iSeries Access for Wireless (5722-XP1). TE 6 Team-Fly® IBM ~ iSeries 7 About IBM eServer iSeries The IBM eServer iSeries family of products represents IBM’s newest generation of midsize business computing systems. Like their predecessors, the AS/400 family, they are multiuser computer systems, meaning that a single computer can interact with more than one user at a time. At the same time, iSeries computers are servers, meaning that they can offer resources (e.g., disk storage, printers, shared applications, data, Web content, etc.) to other computer users over a network. The server functions of the iSeries are vital in today’s e-business environment. iSeries systems are very popular with well over 650,000 systems shipped to all corners of the globe. In developing the iSeries systems, designers drew from the ease-ofuse, advanced architecture, and productivity features of the AS/400 and then added new functions. In addition to the new application programs developed directly for execution on the iSeries family, many of the application programs developed for the System/36, System/38, and AS/400 computers can be migrated to and used on iSeries systems by applying the migration tools available. What Makes Up an iSeries System? Many users have no concept of what equipment makes up the computer systems and networks they access daily. Fortunately, it is not necessary for them to know this, just as it is not necessary to understand the inner workings of a carburetor to drive a car. However, it is helpful for our purposes to have a fundamental view of what general elements make up an iSeries system. Figure 1.1 shows the components of a very simple iSeries system configuration. The heart of the system is the system unit, which contains the “brain” that runs the computer programs and controls all activities. People interact with the computer system through terminals—or personal computers (PCs) acting as terminals—that display computer information and allow for keyboard entry. The terminal shown on the left side of the figure is the system console. The system console is a specially designated terminal used by the system operator to manage the day-to-day operations of the computer system. The other terminals are for general-purpose use. The printers shown in the figure are used to generate reports, documents, graphs, and the like. A printer can be a workstation used to fill the needs of 8 Exploring IBM ~ iSeries Terminal Terminal System Console Printer Twinaxial Cable iSeries System Unit User #1 (Personal System 2) Figure 1.1. Printer User #3 User #2 Components of a simple iSeries system. specific user(s), or it can be shared by all users. Both terminals and printers initially were attached to the system unit via twinaxial cable (or twinax), typically laid in the building’s walls or ceiling. In today’s environment, the terminals (or PCs) and printers are attached through many other media including radio communications and telephone wiring. Figure 1.2 shows the packaging used for the iSeries eServer 800. This packaging is typical of the iSeries system line in that it encompasses the primary components of the computer system, including everything necessary to compose an entry system except the terminal functions identified above. Among the elements that distinguish the system from other systems available in the midrange marketplace are the air intake scoops at the bottom and mid area of the unit’s front. The fact that all air intake is through the front cover allows the unit to be placed against walls and desks at either side. IBM ~ iSeries Figure 1.2. 9 iSeries eServer Model 800. Advanced Application Architecture The architecture of a computer is the “structural blueprint” used to guide the design of that computer system. In larger measure, it is this architecture that determines the capabilities of the computer system that implements it. The iSeries computer systems utilize the advanced application architecture which is depicted in Figure 1.3. This architecture was originally implemented on the AS/400 systems, which is one reason iSeries systems are compatible with software written for AS/400 systems. Let’s take a quick look at the seven layers in this architecture. The top layer is the client application layer. This layer provides a method for other application programs perhaps running on other computer systems (called clients) to take advantage of the iSeries server resources. Client computers can be running almost any of today’s operating systems and take advantage of iSeries resources through this top layer 10 Exploring IBM ~ iSeries CLIENT APPLICATIONS Rapid Application Development Client & Server Programming Tools S/3X ObjectUNIX OS/400 Oriented Server Server Server Applications Applications Applications OPEN APPLICATION ENVIRONMENT Open Standards Support Multiple Application Support AnyMail Multimedia Open Client Access Open Client Support Distribution Services Directories System View End-to-End System Management AnyNet DB2 Database SOM/DSOM Objects Open Networking & Database Support OPEN MIDWARE SUPPORT Technology Independent Machine Interface Object-Oriented Kernel Industrial Strength Packaging Client/Server Design Point Power PC Server IOPs Hardware Device IOPs RAID Integrated Midware Technology Independence Commercial Performance Optimization Figure 1.3.. Advanced application architecture. of the architecture. It is worth noting that along with the introduction of the iSeries came support for additional client types that are of growing importance in today’s computing environment. For example, iSeries supports Windows through the Integrated xSeries adapter, and PASE, which enables the execution of UNIX-based programs directly on the system. The iSeries also supports Linux—an emerging open system operating system. The second layer is the server layer, which supports client and server programming tools, OS/400 server applications, PC server applications, and object-oriented server applications. In general, this layer enables the distributed computing function, whereby the client application might also execute at the server in whole or in part. The fact that these server functions are equivalent to each other allows them to share data through the iSeries integrated file system, including the DB2 UDB for iSeries relational database. This, along with IBM ~ iSeries 11 Data Propagator/400, allows flat files and relational files to coexist and PC applications to readily access data, change it, and put it back again, as well as replicate it in whole or in part to a different application. Thus, legacy applications, server applications, and object-oriented applications can coexist in one iSeries computer. Implemented within the third layer as part of the integrated file system are triggers, stored procedures, declarative referential integrity, twophase commit, and long file names. These functions are available not only for the server and open systems interconnect file structures but for all of the file structures supported, improving the total function of the iSeries including legacy applications. The fourth layer is the integrated midware layer, which allows the iSeries to reduce the system management headaches associated in general both with server management and with distributed computing. The integrated midware layer reduces complexity in the following areas: • Network protocols • Database management • Security • Access to coded and noncoded data (open file system) • Enablers for advanced applications such as multimedia • Enablers for mail and directory services. The fifth layer is the technology-independent machine interface, which allows the iSeries to change major hardware and software components of the system without affecting business applications that reside above this layer. This allows the iSeries to change the functions and hardware below this interface without causing users to rewrite or recompile their application programs. Also implemented in this layer are the Logical Partitioning functions, which enable the resources of a single server to appear to be many servers. This ability to appear as many servers allows the user to consolidate multiple systems onto a single system image. The sixth layer is the System Licensed Internal Code (SLIC) and Java Virtual Machine (JVM), now designed in C++, which runs on 64bit microprocessors. This layer allows new hardware to be introduced 12 Exploring IBM ~ iSeries without affecting the applications above the machine interface layer until those applications are ready to exploit the new functions provided. The final layer, the seventh layer, is the hardware layer where the physical devices come together to make a functioning system. Now that we have seen what makes up an iSeries system and glanced at their architecture, let’s take a look at the systems themselves. Meet the Family Figure 1.4 shows the IBM eServer iSeries family. The “e” in the eServer names for these systems signifies that the systems are capable of supporting the electronic business, or e-business, environment, which means that users can do business over the Internet securely and reliably. Before discussing the characteristics of the servers in the iSeries family, let’s set the scenario for why IBM elected to replace the previous members of the iSeries family with the new models. Figure 1.4. iSeries family of eServers. IBM ~ iSeries 13 IBM anticipates that the server environment of the present and near future is an e-business on-demand environment. That on-demand environment is based on high-pressure and is fast-moving. As a result, it will be necessary for businesses participating in that environment to be flexible enough to adjust to that constant change. The IBM eServer iSeries offers a highly integrated, reliable, multiplatform server capable of running concurrently multiple operating systems, including Windows, Linux, and OS/400. The iSeries line of eServers simultaneously and dynamically adjusts to the demands imposed by the changing requirements of an e-business. This flexibility allows a business to regain control of its Information Technology through proven reliability and self-management, system-healing technology, in which iSeries servers almost run themselves. An e-business can adapt to change with the iSeries flexibility to support all the popular operating environments including Linux, Windows, WebSphere, and OS/400 today, and in the future AIX without limitations. As the demands on your business vary, iSeries eServers have the ability to respond to that demand through Capacity Upgrade on Demand (CUoD) and logical partitioning. Capacity Upgrade on Demand can be permanent or temporary. The dynamic workload manager automatically balances system performance. There can be up to 32 dynamic logical partitions per server, and a uniprocessor can have up to ten Linux or OS/400 partitions. Finally, storage can be dynamically added to active Windows servers. The new iSeries eServers offer an 80% improvement in price performance over the previous line of iSeries eServers. The Options packages provided with these systems simplify product choice, and as a rule there is unrestricted interactive 5250 CPW with the Enterprise package. The software pricing tiers have been simplified so that only a single software tier is associated with an individual processor, as opposed the having multiple tiers based on the interactive capacity defined by the interactive card purchased with a processor. New high performance I/O adapters reduce the cost of many entry-level server environments (see Chapter 2 for additional details). iSeries servers as a group offer new tools for managing e-business, application flexibility, and new technology, which offers leading-edge server performance. The iSeries system microprocessors are based on copper-interconnect and silicon-on-insulator technologies, which are innovations in the semiconductor industry. These technologies result in denser packages, lower power consumption, and higher performance. Also implemented in these systems is a memory-switching technology with switch speeds up to 36 GB per second. High-speed links 14 Exploring IBM ~ iSeries on these systems allow data transfer between I/O devices and other systems at rates up to 1 GBps (gigabyte per second). The iSeries intelligent integration of these technologies allows businesses to benefit from enterprise-class computing without the “enterprise-size” IT support staff. The iSeries architecture features a flexible operating environment that concurrently runs any combination of AS/400, ported UNIX applications, Linux, Windows, Domino, or Java applications. When that flexibility is combined with the inherent iSeries workload management capabilities, Logical Partitioning (LPAR), and the integration of IBM xSeries, the iSeries enables businesses to run several diverse application environments on one physical machine. Choices are provided with regard to whether a business should expand an existing server farm, maintain the existing server farm, or consolidate server footprints on the iSeries for simplified management, increased availability, or lower total cost of ownership. The iSeries also offers businesses the freedom to grow without disruption through Capacity Upgrade on Demand features on the Model 825, 870, and 890. These features enable a customer to activate immediate incremental processing power non-disruptively, when it is needed, and pay for it only when initiated. The activation may be made permanent if the customer perceives that the required processor power is needed on a continuous basis. The customer also has the option to use the additional processing power on a temporary basis, activating the needed processing power as required, in which case the customer pays only a daily charge (See the paragraph which follows on capacity on demand). Five basic computers form the core of the IBM iSeries family: the Model 800 server versions with two processor options and three software package options and the four server models—810, 825, 870, and 890. The dedicated Domino Server models are derived from the Models 810 and 825. The Models 810, 825, 870, and 890 no longer have any restrictions on interactive activity, i.e., the full CPW available on these models can be used for client server or interactive processing up to the limit of the processing capacity. IBM has chosen to separately classify the 800, 810, 825, 870, and 890, and the dedicated Domino servers 810D and 825D, as iSeries eServers. The “i” in iSeries stands for intelligent integration, featuring open-system functions that are built into the operating system and are pretested for reliable, turnkey function. The integrated functions include Web servers (IBM HTTP server and HTTP Server powered by Apache discussed in greater detail in Chapter 5, Web application server IBM ~ iSeries 15 (WebSphere Standard Edition), JVM (Java Virtual Machine), database (IBM DB2 Universal database for iSeries discussed in greater detail in Chapter 4), communications (TCP/IP), OS/400 PASE, e-business security, and Linux (TCP/IP and PASE are discussed in greater detail in Chapters 4 and 3 respectively). This intelligent integration enables businesses to deploy solutions faster, with greater reliability and lower cost of ownership, while providing superior performance across a wide range of e-business applications based on industry standards. Common across all of the V5R3 models are OS/400 V5R2; Webfacing, which does not require 5250 OLTP capability; Linux with up to 10 partitions per processor; Windows supports using the same Integrated xSeries Server (IXS) and Integrated xSeries Adapter (IXA) options; and common I/O support in towers (High Speed Link [HSL] attached), adapters (all PCI), and devices. The iSeries also offers businesses the freedom to grow without disruption through Capacity Upgrade on Demand features on the Models 825, 825D, 870, and 890. These features enable a user to activate immediate incremental processing power without disruption when it is needed, and to pay for it only when initiated. The iSeries Models 800 and 810 use a package similar in size to the previous Model 270, which they replaced. The Model 800 expands the performance and the I/O capabilities available in the entry-level price range offering three versions (Value, Standard, and Advanced) based on two processors with different programming package options. The Model 800 has a new higher-performance entry-point processor, and also an increased performance high-end processor. The Model 810 extends the midrange offering in performance, memory, and I/O capacity in addition to offering standard and enterprise editions for software packages. Common to the Models i800 and i810 are the use of SStar processors in either 1-way or 2-way configurations, and a limit of up to four OS/400 partitions per processor. The three server models (825, 870, and 890) provide increased server performance with no interactive workload performance limitations. Common to these models are POWER4 processors; always in N-way configurations, Capacity Upgrade on Demand, and up to 10 OS/400 partitions per processor. In addition, a processor can be licensed for only Linux. The two Domino dedicated servers, Models 810D and 825D, provide especially tuned Domino environments. The only model with interactive performance limitations is the Model 800, which offers 25 CPW on its Value and Standard configurations and 50 CPW on its Advanced configuration. 16 Exploring IBM ~ iSeries AM FL Y The capability of unlimited interactive performance available on each of the 810, 825, 870, and 890 servers allows them to support the Independent service Vendors (ISV) preload environment previously provided by the custom mixed-mode server models S20-ISV, S30-ISV, and S40ISV. Upgrades from the previous custom mixed-mode server models to the V5R3 8XX servers are supported. The custom mixed-mode software packages continue to be provided by J. D. Edwards, Software Systems Associates, Intentia International’s Movex V10.5, and International Business Systems (IBS), as well as others. iSeries Model Specifics Now let’s take a closer look at the specifics of these models. TE iSeries Model 800 (i800) Specifics The iSeries Model 800 entry processor replaces the Model 250 and Model 270. The Model i800 increases the entry-level design point beyond that previously offered by the Models 250 and 270. The Model i800 is a deskside tower–based server (Figure 1.2 on page 9). Two processor options are allowed, ranging in performance from about two times the performance of the previous Model 270 entry processor to about onethird the performance offered in the fastest AS/400e server 270 processor. The Model 800 offers three different server feature codes, two different processor feature codes, and two different programming package options. The combinations of these offerings are referred to as Value, Standard, and Advanced. All three offerings are physically packaged into a small deskside unit, which is then cabled to the necessary workstations and printers. The offerings include an HSL loop with two ports which can be attached to a single I/O expansion unit (discussed in Chapter 2 under packaging). That expansion tower can be a 5094, 5095, or 5088, or an Integrated xSeries Server. Model 800 Value The Value offering of the i800 (server feature code 0863) uses processor feature code 2463 (300 CPW client server, 25 CPW interactive) and Team-Fly® IBM ~ iSeries 17 programming feature option 7400. The processor is implemented in the SStar technology. The minimum memory offered is 256 MB, with growth supported to 8 GB by means of eight expansion cards. The Direct Access Storage Device (DASD) supported can range from a single arm at 17.5 GB up to a maximum of 4 Terabytes (TB) across 63 DASD units. A minimum of one internal DVDROM is required, with a maximum configuration of four DVDROMs. Externally it is possible to attach an additional 15 Tape/Optical/CD/DVD device in any combination up to that maximum. A maximum of 21 PCI cards are supported, 17 of which can be PCI I/O Adapters. Among the PCI cards can be 15 twinaxial controllers to attach up to 600 twinaxial devices. Also among the PCI cards can be 62 communication lines and/or 12 LAN ports. Windows integration supports a maximum of either four Integrated xSeries Servers or seven Integrated xSeries Adapters. Model 800 Standard The Standard offering of the i800 (server feature code 0864) also uses processor feature code 2463 (300 CPW client server, 25 CPW interactive) and programming feature option 7400. The processor is implemented in the SStar technology. The minimum memory offered is 512 MB, with growth supported to 8 GB by means of eight expansion cards. The DASD supported can range from a single arm at 17.5 GB up to a maximum of 4 TB across 63 DASD units. A minimum of one internal DVDROM is required, with a maximum configuration of four DVDROMs. Externally it is possible to attach an additional 15 Tape/Optical/CD/DVD device in any combination up to that maximum. A maximum of 21 PCI cards are supported, 17 of which can be PCI I/O Adapters. Among the PCI cards can be 15 Twinaxial Controllers to attach up to 600 Twinaxial Devices. Also among the PCI cards can be 62 communication lines and/or 12 LAN ports. Windows integration supports a maximum of either 4 Integrated xSeries Servers or 7 Integrated xSeries Adapters. The Programming Options Package 7400 supported by both the Value and Standard versions of the i800 provide the following functions: (1) support for multiple operating systems (OS/400 and LinuxJ), (2) Support for Web Modernization (enhanced WebFacing tool support, described in Chapter 4), (3) Support for Server Partitioning (up to four OS/400 partitions), and (4) Support for 5250 OLTP (25 CPW). Also included in Options Package 7400 is licensing for OS/400 (one processor license for each processor). 18 Exploring IBM ~ iSeries Model 800 Advanced The Advanced Edition offering of the i800 (server feature code 0865) uses processor feature code 2464 (950 CPW client server, 50 CPW interactive) and programming feature option 7408. The processor is implemented in the SStar technology. The minimum memory offered is 512 MB, with growth supported to 8 GB by means of eight expansion cards. The DASDs supported can range from two arms at 35 GB up to a maximum of 4 TB across 63 DASD units. A minimum of one internal DVDROM is required, with a maximum configuration of four DVDROMs. Externally it is possible to attach an additional 15 tape/optical/CD/DVD device in any combination up to that maximum. A maximum of 21 PCI cards are supported, 17 of which can be PCI I/O Adapters. Among the PCI cards can be 15 Twinaxial Controllers to attach up to 600 Twinaxial Devices. Also among the PCI cards can be 62 communication lines, and/or 12 LAN ports. Windows integration supports a maximum of either 4 Integrated xSeries Servers or 7 Integrated xSeries Adapters. Figure 1.5 illustrates the capacities available on the Value, Standard, and Advanced editions of the Model i800. The Programming Options Package 7408 provides the following functions: (1) support for multiple operating systems (OS/400 and LinuxJ), (2) Support for Web Modernization (enhanced WebFacing tool support, described in Chapter 4), (3) Support for Server Partitioning (up to four OS/400 partitions), and (4) Support for 5250 OLTP (50 CPW). Also included in Options Package 7408 is licensing for OS/400 (one processor license for each processor), and licensing for WebSphere Application Server–Express V5 for iSeries (one processor license for 5722-IWE). iSeries Model 810 Specifics The Model 810 is a deskside system that looks very much like the Model i800. It comes standard with one of three PowerPC SStar RISC Microprocessors #2466, #2467, or #2469 (CPW performance ratings 1020, 1470, or 2700 respectively), 512 MB of main storage, a CFIOP (Combined-Function I/O Processor), A single 17.5 GB 3½-inch disk drive, a DVD-ROM drive, a two-line PCI WAN communications adapter, and either a twinax workstation controller or a systems console on Op Con- IBM ~ iSeries Edition - Server Feature Code Processor Feature Code Processor Technology Processor CPW 5250 OLTP Main Storage DIMMs or Cards Min/Max Min Capacity (MB) Max Capacity (GB) Disk Storage (GB) Minimum Maximum Disk Arms Internal DVD/Tape External Tape/Optical/CD/DVD External HSL/HSL-2 Ports External HSL/HSL-2 Loops Max I/O Towers PCI Card Slots Maximum PCI IOA Cards 10/100 Ethernet (NC) Communications Lines LAN Ports Twinax (NC) Twinax Controllers Twinax Devices Windows Integration Integrated xSeries Servers Integrated xSeries Adapters 30 GB Tape Drive WebSphere Express (NC) Programming Tier Figure 1.5. Value Edition 0863 Standard Edition 0864 Advanced Edition 0865 2463 Uni SStar 300 25 2463 Uni SStar 300 25 2464 Uni SStar 950 50 1/8 256 8 1/8 512 8 1/8 512 8 17.5 4445 63 4 15 2 1 1 21 17 1 62 12 35 4445 63 4 15 2 1 1 21 17 1 62 12 1 15 600 35 4445 63 4 15 2 1 1 21 17 1 62 12 1 15 600 4 7 4 7 1 1 P05 4 7 1 1 P10 P05 19 Model i800 configuration/capacity chart (continued on next page). Value Edition Options Package - 7400 Function Support for Multiple Operating Systems (OS/400 and LinuxJ) Support for Web Modernization (enhanced WebFacing Tool support) Support for Server Partitioning (up to 4 OS/400 partitions) Support for 5250 OLTP (25CPW 20 Exploring IBM ~ iSeries Software Licensing for OS/400 (one processor license) Defaulted hardware/Software (can be deselected for priced alternatives) 5705 Tape/Disk Controller (Non-RAID) Minimum Configuration = 1 Disk/Tape Controller 4318 DASD (17.5 GB Drive Minimum Configuration = 1 Arm 3092 Memory (256 MB) Minimum Configuration = 256 MB 4531 DVDROM Minimum Configuration = 1DVD device 9749 Ethernet Card Minimum Configuration = 0 LAN Card Standard Edition Options Package 7400 Function Support for Multiple Operating Systems (OS/400 and LinuxJ) Support for Web Modernization (enhanced WebFacing Tool support) Support for Server Partitioning (up to 4 OS/400 partitions) Support for 5250 OLTP (25CPW Software Licensing for OS/400 (one processor license) Licensing for WebSphere Application Server - Express V5 for iSeries(5722-IWE) Defaulted hardware/Software (can be deselected for priced alternatives) 5705 Tape/Disk Controller (Non-RAID) Minimum Configuration = 1 Disk/Tape Controller 4318 DASD (2 x 17.5 GB Drive) Minimum Configuration = 2 Arm 3093 Memory (512 MB) Minimum Configuration = 1 x 512MB 4531 DVDROM Minimum Configuration = 1DVD device 9749 Ethernet Card Minimum Configuration = 0 x LAN Card 9746 Twinax Card Minimum Configuration = 0 x Twinax Card 4584 Save/Restore Device Minimum Configuration = 1 x Tape Device (30 GB or larger) Advanced Edition Options Package 7408 Function Support for Multiple Operating Systems (OS/400 and LinuxJ) Support for Web Modernization (enhanced WebFacing Tool support) Support for Server Partitioning (up to 4 OS/400 partitions) Support for 5250 OLTP (50CPW Software Licensing for OS/400 (one processor license) Licensing for WebSphere Application Server - Express V5 for iSeries (5722-IWE) Defaulted hardware/Software (can be deselected for priced alternatives) 5705 Tape/Disk Controller (Non-RAID) Minimum Configuration = 1 Disk/Tape Controller 4318 DASD (2 x 17.5 GB Drive) Minimum Configuration = 2 Arm 3093 Memory (512 MB) Minimum Configuration = 1 x 512MB 4531 DVDROM Minimum Configuration = 1DVD device 9749 Ethernet Card Minimum Configuration = 0 x LAN Card 9746 Twinax Card Minimum Configuration = 0 x Twinax Card 4584 Save/Restore Device Minimum Configuration = 1 x Tape Device (30 GB or larger) Figure 1.5 (continued). Model i800 configuration/capacity chart. IBM ~ iSeries 21 sole and an alternate IPL device. The interactive performance is achieved on the processor, without the addition of Interactive upgrade cards. At no time can the interactive performance exceed the performance rating of the selected base processor. The Model i810’s processor #2469 is a 2-way SMP implementation. The Model i810’s structure can connect up to 198 disk arms in its disk cage assemblies to achieve a maximum of 13,791 GB of disk capacity. It can also house 10 internal CD/DVD/tape devices, as well as attach 18 external tape devices or 36 external CD/DVD devices. The maximum disk and internal/external device capacities can only be achieved through the attachment of four I/O Towers using the two HSL ports and the single HSL loop. The base system unit plus the I/O Towers provides 63 PCI card slots, 50 of which can be populated with PCI I/O Adapter cards. Up to 16,384 MB of main storage can be packaged with 8 total main storage cards. The main storage expansion options used on these models attach within the processor cage so that they don’t consume expansion slots. It is also possible to attach up to 1,920 twinaxial workstations spread across 48 Twinaxial Controllers, 194 communications lines, and 36 local area network ports. (Some of the LANs may be displaced by Integrated xSeries Servers, with a maximum of thirteen allowed on a system or by Integrated xSeries Adapters with a maximum of seven allowed.) Figure 1.6 illustrates the maximum system capacities and performance capabilities for the Model i810. The model i810 can also be configured with Standard and Enterprise software offerings as well as Domino offerings. Figure 1.7 lists the contents of the Model i810 Option Packages. The Domino offerings will be discussed later in this chapter. iSeries Model i825 Specifics The Model i825 (Figure 1.8) is a deskside system unit which in general will contain multiple I/O expansion towers. The Model i825 comes standard with POWER4 RISC Microprocessors #2473 including 3 to 6 Nway processors. The fourth through sixth processors are Capacity Upgrade on Demand (CUoD) processors. This means the customer can invoke the usage of these processors as the demands of their business requires either a temporary or permanent basis. CUoD is discussed in greater detail later in this chapter. The CPW performance rating of 3,600 with the base three processors can be increased to a CPW performance 22 Exploring IBM ~ iSeries Edition - Server Feature Code Value Edition 0863 Processor Feature Code 2466 Uni Processor Technology SStar Processor CPW 1020 Software Tier P10 Main Storage DIMMs or Cards Min/Max 1/8 Min Capacity (MB) 512 Max Capacity (GB) 16 Disk Storage (GB) Minimum 17.5 Maximum 13,791 Disk Arms 198 Internal DVD/Tape 10 External Tape/Optical/CD/DVD 18/36 External HSL/HSL-2 Ports 2 External HSL/HSL-2 Loops 1 Max I/O Towers 4 PCI Card Slots 63 Maximum PCI IOA Cards 50 Communications Lines 194 LAN Ports 36 Twinax Controllers 48 Twinax Devices 1,920 Windows Integration Integrated xSeries Servers 13 Integrated xSeries Adapters 7 Figure 1.6. Standard Edition 0864 Advanced Edition 0865 2467 Uni SStar 1470 P10 2469 2-Way SStar 2700 P20 1/8 512 16 2/16 512 16 17.5 13,791 198 10 18/36 2 1 4 63 50 194 36 48 1,920 17.5 13,791 198 10 18/36 2 1 4 63 50 194 36 48 1,920 13 7 13 7 Model i810 Configuration/Capacity chart. of 6,600 through the invocation of the three CUoD processors. The minimum system includes a base main storage of 2,048 MB, a Combined-Function I/O Processor (CFIOP), a single 17.5 GB 3½-inch disk drive, a CD-ROM/DVDROM drive, four HSL ports supporting up to two HSL loops, a PCI two-line WAN communications adapter with V.90 modem, either a twinax workstation controller or a system console—on Op Console option. The Model i825 bridges the previous Models 820 and 830 to make up the low-end of the high range of the iSeries family. This provides for higher performance, more users, more communications, more storage, IBM ~ iSeries 23 Standard: <Package Function •Support for Multiple Operating Systems (OS/400 and Linux) •Support for Web Modernization (enhanced WebFacing tool support) •Support for Server Partitioning (up to 4 OS/400 partitions per processor) •Support for 5250 OLTP (5250 interactive CPW = 0) <Package Software •Licensing for OS/400 (one processor license for each processor) Enterprise: <Package Function •Support for Multiple Operating Systems (OS/400 and Linux) •Support for Web Modernization (enhanced WebFacing tool support) •Support for Server Partitioning (up to 4 OS/400 partitions per processor) •Support for 5250 OLTP (maximum 5250capacity) <Package Software •Licensing for OS/400 (one processor license for each processor) •Licensing for WebSphere - Express V5 for iSeries 5722-IWE (one processor license for each processor) •Licensing for DB2 Query Manager and SQL Developers Toolkit 5722-ST1 (one server license) •Licensing for Performance Tools - 5722-PT1 (one server license) Figure 1.7. Software Option Packages for Model i810. and greater growth capability than the previous Models 820 and most of the Model 830 at a significantly lower price performance design point. Main storage can be increased to a maximum of 48 GB through the usage of 24 total memory slots. Main storage expansion is accomplished through the addition of four matched groups of main storage expansion features. Interactive performance and client/server performance share the available CPW up to the maximum defined by the processors present. There are no Interactive cards required to achieve the maximum interactive performance. Using the HSL loops, the system unit’s capacity can be increased. Up to 18 I/O towers can be attached, providing 263 PCI card slots, which may be populated with up to 206 PCI I/O adapters. The Model 825 maximum capacities can house up to 825 disk arms to achieve 24 Exploring IBM ~ iSeries Figure 1.8. iSeries eServer Model i825. 58,216 GB of disk storage, 18 internal CD/DVD devices or 36 tape units, with equal capacities of external CD/DVD/tape devices, 135 Twinaxial Controllers can attach 5,400 twinaxial devices, 320 communications lines, and 96 LAN ports. Some of the LAN ports may displaced by up to 36 Integrated xSeries Servers or up to 18 Integrated xSeries Adapters. The system capacities and performance capabilities are summarized in Figure 1.9. The Model 825 supports the same Option Packages as the Models i870 and i890. iSeries Model i870 Specifics The Model i870 makes up the middle range of the high end of the iSeries family (Figure 1.10). It comes with a minimum eight-way Symmetrical Multiprocessor and contains an additional eight CUoD processors. All processors are POWER4 RISC (Reduced Instruction Set Computers) microprocessors. The processor feature code is #2486 (CPW performance rating 11,500, extended to a possible 20,000 if the CUoD processors are invoked). A high-speed crossbar switch connects the main IBM ~ iSeries Processor Feature Code Processor Technology Processor CPW Software Tier Main Storage DIMMs or Cards Min/Max Min Capacity (MB) Max Capacity (GB) Disk Storage (GB) Minimum Maximum Disk Arms Internal DVD/Tape External Tape/Optical/CD/DVD External HSL/HSL-2 Ports External HSL/HSL-2 Loops Max I/O Towers PCI Card Slots Maximum PCI IOA Cards Communications Lines LAN Ports Twinax Controllers Twinax Devices Windows Integration Integrated xSeries Servers Integrated xSeries Adapters Figure 1.9. 25 2473 3/6 - Way Power4 3,600-6,000 P30 4/24 2,048 48 17.5 58,216 825 18/36 18/36 4/2 2/1 18 263 206 320 96 135 5,400 36 18 Model 825 Configuration/Capacity chart. storage and I/O functions to the processor, 8,192 MB of main storage, a CFIOP, a single 17.5 GB 3½-inch disk drive, a CD/DVDROM drive, a 16port HSL card that supports eight loops, a PCI two-line WAN (Wide Area Network) communications adapter, either a twinax workstation controller or a system console on Op Console, and a logic cage that accepts PCI cards. The Model i870 bridges the capabilities of the previous Models 830 and 840. The Model 870 uses a common package with the Model 890. Both the processor unit and the I/O function tower operate from separate 240-V line sources. The I/O function tower connects to the processor unit tower by means of an interface cable called HSL, allowing a separation between any two units on a loop of up to 250 meters. AM FL Y Exploring IBM ~ iSeries Figure 1.10. TE 26 iSeries eServer Models i870/i890. No interactive cards are used in the Model i870. In any case the interactive performance value can not exceed the CPW performance value. The interactive requirements and the client server requirements share the available CPW performance capability. Eight of the processor features offer capacity on demand, capacity for ASPs (Application Service Providers), ISPs (Internet Service Providers), and dynamic growth environments. If one of these processor options is ordered, activation can be temporary, at the time of server installation and after each new activation, for a period of 14 days, and requires no Initial Program Load (IPL) activity. Activation can be permanent, in which case the activation code is both posted to the Web and mailed, and requires the entry of the activation code at the server. Capacity Upgrade on Demand standby processors are not paid for until activated. Capacity Upgrade on Demand is discussed in greater detail later in this chapter. The Model i870 in its maximum configuration with 47 I/O Towers can include up to 2,047 disk arms with a maximum capacity of 144,446 MB on 3½-inch disk drives, 26 internal CD/DVD drives or 48 tape Team-Fly® IBM ~ iSeries 27 drives, an operator panel, up to 128,000 MB of main storage, and 672 PCI cards, 528 of which can be PCI I/O adapters. The main storage expansion options used on these models attach within the processor tower so that they don’t consume I/O expansion slots. It is also possible to attach up to 7,200 twinaxial workstations using 180 twinaxial controllers, 480 communications lines, and 128 LAN ports. Up to 48 Integrated xSeries servers or 60 Integrated xSeries Adapters may be used instead of the LANs. Externally 26 CD/DVDROM or 48 tape devices can be attached. The total system capacities and performance capabilities of the Model 870 are summarized in Figure 1.11. The Model i870 supports the same standard and Enterprise Option Packages as the i825 and i890 Models. Processor Feature Code Processor Technology Processor CPW Software Tier Main Storage DIMMs or Cards Min/Max Min Capacity (GB) Max Capacity (GB) Disk Storage (GB) Minimum Maximum Disk Arms Internal DVD/Tape External Tape/Optical/CD/DVD External HSL-2 Ports External HSL-2 Loops Max I/O Towers PCI Card Slots Maximum PCI IOA Cards Communications Lines LAN Ports Twinax Controllers Twinax Devices Windows Integration Integrated xSeries Servers Integrated xSeries Adapters Figure 1.11. 2486 8/16 - Way Power4 11,500 - 20,000 P40 2/4 8 128 17.5 144, 446 2,047 26/48 26/48 16 8 47 672 528 480 128 180 7,200 48 60 Model i870 Configuration/Capacity chart. 28 Exploring IBM ~ iSeries iSeries Model i890 Specifics The Model i890 makes up the top end of the high range of the iSeries family. The Model i890 includes 24-way and 32-way versions of POWER4 microprocessors. The Model 890 uses a common package with mainframe computers, and the Model i870 which is the size of a 2.0-meter rack plus a separate I/O function tower just as in the 870 Model. Both the processor unit and the I/O function tower operate from separate 240-V line sources. The I/O function tower connects to the processor unit tower by means of an HSL, allowing a separation between any two units on a loop of up to 250 meters. The Model i890 offers two processor options. The first processor option (#2497) contains a base 16-way processor with an additional 8 capacity on demand processors and at its maximum can realize a 24way processor system. The CPW performance rating starts at 20,000 and extends to 29,300 if the capacity on demand processors are activated. Capacity on demand is discussed in the next section of this chapter. The minimum main storage capacity for this processor is 8,192 MB and the maximum main storage capacity is 192 GB. The second processor option (#2498) consists of a base 24 processors with an additional 8 capacity on demand processors, which at the maximum can realize a 32-way processor configuration. The CPW performance rating for this model starts at 29,300 and extends to 37,400 when the capacity on demand processors are activated. Main storage for this processor model starts at a minimum of 16 GB and extends to a maximum of 256 GB. Both processor options contain the following minimum configuration: a CFIOP, 17.5 GB of 3½-inch disk drives, a CD-ROM/DVDRAM drive, an eight-port HSL card supporting eight loops, a PCI two-line WAN communications adapter, either a twinax workstation controller or a system console on Op Console, and a logic cage, and battery backup units. Main storage card sizes are 4,096, 8,192 MB, 16,384 MB, and 32,768 MB. Capacity on demand standby processors are not paid for until activated. The maximum Model i890 I/O configuration can contain up to 7,200 twinaxial workstations, 480 communications lines, and 128 LANs. Up to 48 Integrated xSeries servers or 60 Integrated xSeries adapters may be used instead of the LANs. Twenty-six optical libraries/External Tape Units/CDROM/DVDRAM/Internal Tape Units can be attached unless Logical Partitioning (LPAR) is enabled, in which case the maximum is increased to 48 of each of those devices. Using the full External HSL IBM ~ iSeries 29 loop capability allows 47 I/O Towers to be added to the base I/O tower to increase the total number of 3½-inch disk drives for each unit. A maximum disk capacity of 144 TB is supported. The maximum number of PCI card slots supported is 672, including a maximum of 528 PCI I/O Adapters. The total system capacities and performance capabilities of the Model 890 are summarized in Figure 1.12. To achieve the maximum system capacities, it is necessary to attach expansion towers to each of the eight possible HSLs. HSL connection capability can be extended by the addition of three HSL Bus Adapters to achieve a maximum of 28 ports. The Model i890 supports the same Standard and Enterprise Option Packages as the Models 825 and 870. Those Option Packages are shown in Figure 1.13. Processor Feature Code Processor Technology Processor CPW Software Tier Main Storage DIMMs or Cards Min/Max Min Capacity (GB) Max Capacity (GB) Disk Storage (GB) Minimum Maximum Disk Arms Internal DVD/Tape External Tape/Optical/CD/DVD External HSL/HSL-2 Ports External HSL/HSL-2 Loops Max I/O Towers PCI Card Slots Maximum PCI IOA Cards Communications Lines LAN Ports Twinax Controllers Twinax Devices Windows Integration Integrated xSeries Servers Integrated xSeries Adapters Figure 1.12. 2497 16/24 - Way Power4 20,000 - 29,300 P50 2498 24/32 - Way Power4 29,300 - 37,400 P50 2/6 8 192 4/8 16 256 17.5 144,446 2,047 26/48 26/48 24 12 47 672 526 480 128 180 7,200 17.5 144,446 2,047 26/48 26/48 28 14 47 672 526 480 128 180 7,200 48 60 48 60 Model i890 Configuration/Capacity Chart. 30 Exploring IBM ~ iSeries Standard: Package Function Support for Multiple Operating Systems (OS/400 and Linux) Support for Web Modernization (enhanced WebFacing tool support) Support for Server Partitioning (up to 4 OS/400 partitions per processor) Support for 5250 OLTP (5250 interactive CPW = 0) Package Software Licensing for OS/400 (one processor license for each processor) Support for Capacity Upgrade on Demand (permanent and temporary) Enterprise: Package Function Support for Multiple Operating Systems (OS/400 and Linux) Support for Web Modernization (enhanced WebFacing tool support) Support for Server Partitioning (up to 4 OS/400 partitions per processor) Support for 5250 OLTP (maximum 5250 capacity) Support for Capacity Upgrade on Demand (permanent and temporary) Package Software: e-business Solution Tools Licensing for OS/400 (one processor license for each processor) Licensing for a choice of WebSphere Application Server or WebSphere - Express V5 for iSeries 5722-IWE (one processor license for each startup processor) Licensing for Lotus SameTime (100 seats) Licensing for QuickTime (100 seats) Licensing for DB2 Query Manager and SQL Developers Toolkit - 5722-ST1 (one server license) Licensing for DB2 SMP - 5722-SS1 Option 26 (one server license) Licensing for Data Propagator (one server license) Licensing for DB2 Extenders - SML and Text (one server license) Data Center Management Tools Licensing for Performance Tools - 5722-PT1 (one server license) Licensing for HA Switched Resources (one server license) Licensing for Media Storage Extensions (one server license) Licensing for BRMS (one server license) Licensing for Tivoli Monitoring - PAC for Web (one server license for each startup processor) Licensing for Tivoli Storage Manager (one server license plus five seats) Package Hardware Integrated xSeries Support (One 1.6 Ghz IXS included) One stand-by processor activated for Linux - Model 879 and 890 only Education and Services Education Credits (ILS class vouchers provided via Web registration: 1-825, 3-870, 5-890) One of three service offerings related to Windows, Linux, or WebSphere Figure 1.13. Model 825/870/890 Option Package Definitions. IBM ~ iSeries 31 The Model 890 system unit processor tower requires three-phase 240-V power. The base I/O tower must be plugged individually into standard high-voltage electrical outlets (180–260 Volts AC {VAC}). The user must rely on an external UPS (Universal Power System) to provide base utility power failure protection. Capacity on Demand (CoD) Capacity on demand (available on the Models i825, i870, and i890) allows the server to dynamically adjust to unpredictable demand without interrupting operations or applications. It is possible to activate a processor for Linux without paying for OS/400. Permanent capacity (called IBM eServer Capacity Upgrade on Demand) can comply with the planned growth of the business (payment is made when the growth is purchased, not when the system is purchased). Temporary capacity (called IBM eServer On/Off Capacity on Demand) is turned on and off dynamically by the system to meet the requirements of business peaks. There are 14 bonus days (randomly spread throughout the year) during which On/Off Capacity on Demand may be used without charge. Payment for the On/Off Capacity on Demand is made after activation. The break-even point for the use of On/Off Capacity on Demand is 30 days of activation. After that number of activations, it becomes less costly to make the On/Off Capacity on Demand into Capacity Upgrade on Demand. iSeries Dedicated Servers for Domino There are two dedicated servers for Domino offered by the iSeries product line. They include the i810D and the i825D. These servers have been tuned to match the requirements for Lotus Domino R5 workloads, including Domino Web serving, applications, and mail. Within the design point, non-Domino workloads should consume less than 10-15 percent of the available CPU CPW capability, whereas Domino workloads can consume 100 percent of that capability. No interactive processing capability is available for application use beyond the impact of the activities of a single systems administrator. When deciding whether to select a Dedicated Server for Domino model or a traditional iSeries server model, you should consider the following: Dedicated Server for Domino is best for: 32 Exploring IBM ~ iSeries • Domino Mail • Domino applications • Mixed Domino workload • Domino Web serving • Domino Web front-end to iSeries Line-of-Business (LOB) server. Traditional iSeries server is best for: • Domino and other iSeries Line-of-Business (LOB) applications on the same server • Large-enterprise user populations • DB2 database integration on the same server. Using the built-in subsystem and logical partitioning capabilities, iSeries for Domino provides a single dedicated server capable of separating mail, instant messaging, and groupware applications while automatically balancing and adjusting performance. It is no longer necessary to face the complexities of managing a server farm with an individual system for each mail function, which generally results from dedicating a single server to each mail function. Included in the iSeries for Domino support are OS/400 V5R2, Lotus Domino V6, Sametime, iNotes, and other Lotus groupware solutions. iSeries for Domino Model i810D The iSeries for Domino Model i810D is based on the previously discussed iSeries Model i810. There are three processor options offered, just as in the Model 810. The difference is the server feature codes (#0769, #0770, #0771) and the package feature codes (#7407, #7410, #7428, respectively). Also different is the interactive CPW available (0, 50, and 0, respectively). The minimum amount of main storage and DASD required to support 500 mail users on the #0769 server feature code is 1,500 MB and 105 GB, respectively. The minimum amount of main storage and DASD required to support 1,000 mail users on the #0770 IBM ~ iSeries 33 server feature code is 3,500 MB and 315 GB, respectively. The minimum amount of main storage and DASD required to support 2,000 mail users on the #0771 server feature code is 5,500 MB and 525 GB, respectively. Each iSeries for Domino Model i810D requires a single Domino license. The 0769, 0770, and 0771 servers require 100, 100, and 400 client licenses, respectively. Figure 1.14 illustrates the capacities for the iSeries for Domino Model i810D. Server Feature Code Processor Feature Code Package Feature Code (Interactive CPW) Processor Technology Processor CPW Software Tier Main Storage DIMMs or Cards Min/Max Min Memory (MB) Max Capacity (GB) Disk Storage (GB) Minimum Maximum Disk Arms Internal DVD/Tape External Tape/Optical/CD/DVD External HSL/HSL-2 Ports External HSL/HSL-2 Loops Max I/O Towers PCI Card Slots Maximum PCI IOA Cards Communications Lines LAN Ports Twinax Controllers Twinax Devices Windows Integration Integrated xSeries Servers Integrated xSeries Adapters Required Domino Licenses Server Client Figure 1.14. 0769 2466 Uni 7407 (0) SStar 1020 P10 0770 2467 Uni 7410 (50) SStar 1470 P10 0771 2469 2-Way 7428 SStar 2700 P20 1/8 1,500 16 1/8 3,500 16 2/16 5,500 16 105 13,791 198 10 18/36 2 1 4 63 50 194 36 48 1,920 315 13,791 198 10 18/36 2 1 4 63 50 194 36 48 1,920 525 13,791 198 10 18/36 2 1 4 63 50 194 36 48 1,920 13 7 13 7 13 7 1 100 1 100 1 400 Model 810D Configuration/Capacity Chart. 34 Exploring IBM ~ iSeries iSeries for Domino Model i825D The iSeries for Domino Model i825D is based on the previously discussed iSeries Model 825. There are two server configuration options offered based on the 2473 processors with capacity on demand. The server feature codes are #0772 and #0773, and the package feature code for each server is #7416. Also different is the interactive CPW available (0, and 50, respectively). The minimum amount of main storage and DASD required to support 4,000 mail users on the #0772 server feature code is 6,000 MB and 560 GB with one of the capacity on demand processors activated permanently. The minimum amount of main storage and DASD required to support 5,000 mail users on the #0773 server feature code is 12,000 MB and 945 GB, with all three capacity on demand processors activated permanently. Figure 1.15 illustrates the capacities for the iSeries for Domino Model i825D. Each of the iSeries for Domino Model i825D server offerings require a single Domino license. The #0772, and #0773 servers each require 700 client licenses. Performance Overview One important aspect of a computer system is its performance—that is, the speed at which the computer can perform work. The higher the performance, the more work the computer can do. Many things—such as the processor, main storage, disk storage, I/O bandwidth, and program design—affect the performance of a computer system. It is difficult and often misleading to predict the overall performance of a computer system by looking at selected specifications of the individual components that make up the system. Although things such as disk unit seek times and raw processor speed (often measured in millions of instructions per second, or MIPS) are important, they do not provide the whole picture in terms of overall system performance. Benchmark Testing Benchmark testing has evolved as the best way to compare the overall performance of different computers. Benchmark testing involves loading the computer system with various programs designed to simulate a workload and then measuring how the system behaves under that load. IBM ~ iSeries Server feature Code Processor Feature Code Package Feature Code (Interactive CPW) Processor Technology Processor CPW Software Tier Main Storage DIMMs or Cards Min/Max Min Memory (MB) Max Memory (GB) Disk Storage (GB) Minimum Maximum Disk Arms Internal DVD/Tape External Tape/Optical/CD/DVD External HSL/HSL-2 Ports External HSL/HSL-2 Loops Max I/O Towers PCI Card Slots Maximum PCI IOA Cards Communications Lines LAN Ports Twinax Controllers Twinax Devices Windows Integration Integrated xSeries Servers Integrated xSeries Adapters Required Domino Licenses Server Client Estimated Users/CUoD activations Figure 1.15. 35 0772 2473 3/6 - Way 7416 (0) Power4 3,600-6,000 P30 0773 2473 3/6 - Way 7416 (50) Power4 3,600-6,000 P30 4/24 6,000 48 4/24 6,000 48 560 58,216 825 18/36 18/36 4/2 2/1 18 263 206 320 96 135 5,400 945 58,216 825 18/36 18/36 4/2 2/1 18 263 206 320 96 135 5,400 36 18 36 18 1 700 3,000/1 processor 1 700 5,000/3 processors Model 825D Configuration/Capacity Chart. Through this benchmark testing, all elements of the computer system come into play, and the overall performance of selected computer systems can be meaningfully compared. To perform benchmark testing, the test group must make assumptions about the kind of work being done and the behavior of the users 36 Exploring IBM ~ iSeries accessing it. For this reason, the performance measurements derived from a benchmark may vary significantly from what users will get if their business environment does not match the set of test assumptions. However, because all assumptions are the same for all computers included in a benchmark test, it is possible to get a good idea of the relative performance of tested computer systems. Server vs. Interactive Environments TE AM FL Y Performance must be considered in relation to the environment in which the computer system is executing. An iSeries system may operate in a general-purpose interactive environment (supporting multiple users and a batch-processing workload) or in the role of a server (offering resources to other computers and their users over a network). What makes a computer function well in one of these environments may be an inhibitor in the other environment. As a result, different methodologies are needed to measure computer performance in those different environments. Typical Business Workload Performance (CPW) IBM has conducted benchmark testing on iSeries systems using the CPW benchmark, which is designed to simulate a typical interactive business workload (e.g., order entry, accounts payable, and accounts receivable). When IBM’s iSeries group benchmarks a system, the benchmark is used against criteria that measures how that system is intended to be used. Figure 1.16 shows the interactive CPW performance ratings of the V5R3 RISC-based models of the iSeries systems. Additional information on other benchmark results on the iSeries and other vendors’ generalpurpose commercial processing systems’ performance may be obtained from the Transaction Performance Council (TPC, www.tpc.org), which publishes CPW test results on a wide variety of systems. Interactive Performance Interactive performance is only limited on the Model i800. The Model i800 Value, Standard, and Advanced editions provide 25, 25, and 50 CPW support for 5250 OLTP applications. All other models limit interactive performance only by the CPW capability of the processors present in those models if the models also include the Enterprise Options Package. In other words, 5250 OLTP applications which have Team-Fly® IBM ~ iSeries 37 40000 35000 CPW 30000 25000 20000 15000 10000 5000 0 2466 2469 6-way 16-way 24-way Standard 2467 3-way 8-way 16-way Advanced Value 32Way Processor Figure 1.16. Model i800 Model i810 Model i870 Model i890 Model i825 V5R3 Processor interactive CPW by model. been webfaced using WebSphere WebFacing Tool and run under WebSphere Application Server (WAS) or WebSphere Express require zero 5250 interactive capacity. iSeries for Domino Benchmarks A new performance metric has evolved for Domino. In the past, Simple Mail Users (SMU) was used as a benchmark. To arrive at a measure of Typical Mail Users for Domino, a measurement was made of Simple Mail Users, and that result was divided by three. The new performance metric, Mail and Calendar Users (MCU), evolved because the previous Notesbench Mail benchmark is no longer representative of the more complex environment for Domino R5 and after users. Domino R5 includes calendaring and scheduling, a 60 percent heavier workload with 30 KB more traffic per hour. To arrive at Typical Mail Users using the MCU benchmark, which is closer to the Typical Mail Users environment, the rule of thumb is to divide by two. Typical Mail Users values allow the comparison of older AS/400 servers with new servers, as Typical 38 Exploring IBM ~ iSeries Mail Users represents a constant metric. Figure 1.17 illustrates the CPW benchmark values for the Dedicated Server for Domino models. The five iSeries for Domino configurations supported can all upgrade to the Models i870 and i890, as well as to the higher performing models/processors within those configurations. A Closer Look Many elements provide the functions and performance of IBM iSeries computers. The remainder of this chapter provides a closer look at the following aspects of the IBM iSeries systems: • Hardware architecture • PowerPC AS microprocessors • Storage hierarchy • Main and auxiliary storage 7000 6000 CPW 5000 4000 3000 2000 1000 0 2466 2467 2469 772/2473 Domino Performance by Processor Model 810D Figure 1.17. Domino Model Performance. Model 825D 773/2473 IBM ~ iSeries • OptiConnect • System availability functions • O/S 400 Subsystems and logical partitioning • Upgrade paths • Packaging • Fiber optic bus. 39 Hardware Architecture Overview The underlying arrangement and interconnection of a computer system’s electrical components is called its hardware architecture. This architecture is the fundamental structure upon which all system functions are built and has the largest effect on how the computer system will behave. A basic understanding of the iSeries system architecture (Figure 1.18) makes it possible to compare iSeries computers with other systems and to understand important aspects of system performance and capacity. The core of the iSeries computer (as in all computers) is the system processor (shown across the top of the figure). The system processor is the circuitry that actually executes a computer program’s instructions and does all the mathematical calculations. The smallest piece of information (data) in the computer is called a bit. Bits are grouped into bytes (eight bits), half words (sixteen bits), full words (thirty-two bits), and double words (sixty-four bits) inside the computer. These groupings form the computer’s representation of numbers, letters of the alphabet, and instructions in a program. Processors for iSeries systems move information around one double word (sixty-four bits) at a time. Since much of a computer’s time is spent moving information around, the double-word organization helps improve overall system performance. Other bits inside the system processor are used to uniquely identify or address storage and I/O devices (e.g., a disk unit) within the computer system. iSeries system processors group sixty-four bits together to form a unique address. This sixty-four bit addressing provides 18,446,744 trillion (264) unique addresses. This is more than enough addresses for today’s midsize computer environment (and even for the foreseeable future). In fact, the largest iSeries systems and servers today have just iden- Exploring IBM ~ iSeries 6 processors 2.0 GB/s 2.0 GB/s 2.0 GB/s I/O Hub 6 processors 6 processors 2.0 GB/s 2.0 GB/s 2.0 GB/s 6 processors 2.0 GB/s 2.0 GB/s 36 GB/sec High Speed Switch 2.0 GB/s 2.0 GB/s Memory Control 1.0 GB/s 1.0 GB/s 1.0 GB/s 1.0 GB/s Memory Memory Memory I/O I/O I/O I/O 40 Balanced Systems = High Performance Figure 1.18. Memory 24 500 MHz Processors 96 GB Memory 14 Buses Crossbar Switch iSeries Model 840 architecture. tified the capability to use 144+ trillion of those addresses. This shows the kind of growth potential inherent in the iSeries architecture. The “memory,” or main storage (shown at the bottom of the figure), provides a work space for the system processor. Since much of a computer’s time is spent moving information to and from main storage, the speed of main storage can be a limiting factor to the overall performance of any computer system. The speed of storage is measured by the time it takes to respond to a request to store or recall information (the cycle time). The main storage cycle time for iSeries computers varies depending on the model. The shorter the cycle time, the better the system performance. The largest iSeries computers can have up to 256,000 MB of main storage. The main storage in all iSeries systems provides error detection and error correction. This main storage error detection and correction works to protect the all-important integrity of user information in the computer system. IBM ~ iSeries 41 All iSeries system processors also use cache memory to help increase the effective cycle time of main storage. A cache is a small and very high-speed memory area that sits between the processor and main storage. The idea is to keep the information most likely to be needed next in cache to avoid the time delay associated with main storage. Data and instruction caches on the processors of iSeries systems accelerate performance when accessing information or program instructions (respectively). Another important part of the iSeries architecture is the System Licensed Internal Code (SLIC). SLIC is a set of extremely simple instructions (never seen by the computer programmer or user) that are directly performed by the electronic circuits within the system processor. All user program instructions are automatically converted into a series of these SLIC instructions, which are then executed by the system processor. For more information on SLIC instructions, see Chapter 3. In the iSeries Models i825, i870, and i890, the separation of main storage and I/O is possible because of a high-speed switch. The highspeed switch makes possible the independent 128-bit data buses between the processors, I/O controllers, and the switch network. As shown in the figure, the processors are distributed uniformly across the data buses, with the one data bus dedicated to the I/O controllers. A single sixty-four-bit address bus connects all of the processors plus the I/O controllers with the switch. Although the address bus is heavily loaded and physically traverses the system board to connect the processor cards, the bus utilization and latency were kept sufficiently low by configuring the system bus arbiter located within the switch to allow only one address for every two data cycles. The I/O is driven from an HSL bus (the HSL bus is an ultra high speed serial interface), either a copper bus limited to fifteen feet in length for a single segment and having a bandwidth of 10 GB/sec, or an optical bus limited to 250 feet in length for a single segment and having a bandwidth of 10 GB/sec. With the exception of the Model i825, the copper bus connects to at least one I/O tower, which can be populated with disk units, tape units, and I/O interface cards. The main storage bus is partitioned into multiple buses, each of which is supported by a separate storage control chip (STG/CTL) that manages the main storage accesses and up to 512 MB of L3 cache. This multiple-memory bus architecture helps improve the performance of these systems. For these three models, the high-speed switch is embedded on the POWER4 chips (discussed later in this chapter). 42 Exploring IBM ~ iSeries The I/O processors (shown at the bottom of the figure) are responsible for managing any devices attached to the iSeries system. Each of these specialized processors has independent responsibilities and performs tasks in coordination with the system processor. A computer that has multiple processors working together with the system processor like this has a multiprocessor architecture. The advantage of having multiple processors performing work simultaneously is simply that more work can be done in a given period of time. For example, the workstation I/O processor manages the detailed processing associated with the multiple terminals and printers attached to the system, allowing the system processor to concentrate on doing more productive work for the user. The same is true of the other specialized I/O processors such as the storage I/O processor, which manages disk, diskette, and tape devices attached to the iSeries system. The I/O processors communicate with the system processor over an I/O bus (called the PCI bus), a group of wires that carry information very quickly from one area to another inside the computer system. As indicated in the figure, some iSeries systems have a single I/O bus, whereas others have multiple I/O buses. Because only one information transfer can occur on any one bus at any one time, systems with multiple buses have the advantage of allowing overlapping transfers between I/O processors and the system processor or main storage. Therefore, multiple buses contribute to the overall system performance advantages of larger iSeries systems. The PCI I/O buses in the 8XX models provide an I/O bandwidth of greater than 10 GB for the movement of data and instructions between the I/O devices and the processor/memory complex. Various controllers and adapters plug into physical slots in each of the packages used to provide electrical connections to the bus. In addition to I/O processors, a service processor is built into every system. It is responsible for starting the system and constantly monitoring the health of the entire computer. It interacts with the system operator through the control panel and helps with such things as system fault isolation, error detection, and error reporting. It is the equivalent of having a built-in service person who watches over things with relentless consistency. All iSeries systems employ a multiprocessor architecture in that they have a system processor and multiple specialized processors (e.g., workstation and I/O processors) to handle specific tasks. However, at some processor level, all models (e.g., models i810, i825, i870, and 890) employ multiple system processors to cooperatively execute a single copy of the operating system (OS/400), thus appearing to be a single large processor. This multiple system processor architecture is called IBM ~ iSeries 43 the N-way multiprocessor architecture (where N is replaced by the number of processors), also referred to as the Symmetric Multi-Processor (SMP) architecture. Figure 1.19 shows how N-way models are organized. (Note: All system processors share the same I/O buses, I/O processors, and main storage.) Symmetric Multi-Processors process in parallel, sharing a task list. Each processor in an SMP set has its own data and instruction cache and its own virtual storage view of the system. In the case of a query, each processor in the SMP group will process in parallel against a segment of disk storage to resolve the query. With SMP, the performance rating increases with each new processor added. For example, if you compare a single processor system to an SMP system with two processors of identical power, you get a performance increase of about 70 percent. You don’t get a 100 percent improvement because the two system processors must spend some of their processing power coordinating activities with one another. They must 6XX Bus @ 83 MHz 4-Way PU Card Add in Pairs 4-Way PU Card L2 L2 L2 L2 PU PU PU PU 16B Main Storage SCIL Bus 0 SCIL Bus 1 SCIL Bus 2 SCIL Bus 3 SCIL Bus Gen. SCIL /ABS Bus Conv BCAEX Optic Bus 1419 Main Storage Storage Controller SCIL Bus SCIL /ABS Bus Conv BCAL Optic Bus 27 SCIL /ABS Bus Conv Spd Bus BCAEX BCAEX BCAEX Optic Bus 813 BCAEX BCAEX BCAEX MFIOP IOP IOP LAN CRYPTO DASD Tape Comm Figure 1.19. N-Way hardware architecture block diagram. 44 Exploring IBM ~ iSeries also share the same main storage, I/O bus (or buses), disk storage, and so on. For these reasons, adding a second system processor does not double the performance of the system; however, SMP configurations do allow significant performance improvements. Figure 1.20 shows the performance advantage afforded by the use of two-way processors in the Model 810, three-way and six-way in the Model i825 along with eight-way (#0158) and sixteen-way (#0159) processors in the Model 870 SMP configurations as well as the twenty-four-way (#0197) and thirty-two-way (#0198) processors offered in the Model 890 SMP configurations. POWER Microprocessors A microprocessor is a computer chip containing millions of microscopic transistors that work together to form the “brain” of a computer sys40000 35000 30000 25000 20000 15000 10000 5000 0 8-way 3-way 2-way Figure 1.20. 6-way 16-way 24-way 16-way N-Way Processor Performance Model i810 Model i825 Model i870 Model i890 Performance characteristics of N-way architecture. 32-way IBM ~ iSeries 45 tem. The internal structure of a microprocessor is called its architecture, and many different architectures are in use today. Current iSeries systems (and other computers, such as the IBM eServer pSeries) use one or more POWER microprocessors as the basis for their computing engines. These microprocessors are a special implementation of the POWER architecture, which is based on the Reduced Instruction Set Computer (RISC) concept. The idea behind RISC (pronounced “risk”) is to gain a performance advantage by utilizing a simple set of instructions executed very quickly to do all work. The POWER architecture enables high levels of performance through its superscalar design, using pipelining, hardwired operations, new op codes, and formats for optimal decoding and branch prediction to improve superscalar scheduling and cycle times. The op code is the portion of the instruction that tells the microprocessor what operations to perform on the data to be manipulated by the instruction. Superscalar means that more than one instruction can be executed in a single cycle of the processor. Pipelining allows instructions to be processed as if they were on an assembly line. Optimal decoding adds a structure to the instruction layout that makes interpretation (within the microprocessor) faster. Branch prediction means that (during the compiling activity) potential jumps from one section of a program to another have been inspected to predict if they will be taken, in order to minimize the delay caused by the need to empty the pipeline if the branch requirements are met. Many compiler optimization techniques have been implemented to minimize design bottlenecks while maximizing parallelism. The POWER microprocessors used on iSeries systems have on-chip cache memory. These very high-speed memory areas serve as temporary storage and reduce the amount of time the microprocessor spends waiting for information to be pulled in from main storage, where access speed may be as much as thirty-five times slower. There are separate instruction and data cache areas to help streamline information flow through the microprocessor. Commercial computing workloads have different characteristics than engineering/scientific computing workloads (a traditional strength of RISC). The commercial environment typically has an increased number of concurrent users, longer instruction path lengths in both application code and the operating system, decreased predictability in branches, mostly fixed-point arithmetic functions, and randomly organized I/O activity. These differences are illustrated in Figure 1.21. Exploring IBM ~ iSeries Commercial Workloads Scientific/Engineering Workloads Many concurrent users Longer path length over larger set of instructions More execution time in operating system code Fewer loop iterations—more branches Extensive manipulation of data structures through integer arithmetic and strong operations Random I/O activity Few concurrent users Smaller instruction working sets Sequential I/O activity AM FL Y Figure 1.21. More execution time spent in application work Tight loops Extensive use of floating point arithmetic Commercial vs. scientific/engineering workloads. The RISC POWER AS systems also have a wider I/O bandwidth, allowing for iSeries systems with more I/O buses. This makes for iSeries systems with greater I/O capacity, which is necessary to maintain balance with the higher levels of performance enabled by the RISC Power microprocessors. The POWER microprocessors used in current iSeries systems are the SStar Microprocessor and the POWER4 Microprocessor. In low-end and midsize iSeries servers (Figure 1.22), the microprocessor is connected to main storage through a storage control chip, and to the I/O interfaces through a bus control adapter logic (BCAL) chip. The BCAL chip creates an intermediate interface from which other chips create a PCI bus interface. The base system unit in these systems always contains a PCI bus interface. In the high-end Symmetrical Multiprocessor System Units, the main storage is again managed through storage control chips, but the storage cards are arranged in either two or four banks and the I/O interface is driven across a high-speed serial/parallel interface bus referred to as an HSL (High-Speed Link) bus. The implementation of the HSL bus allows the I/O devices to be packaged in a separate unit from the System Processor/Memory unit. The E-Server Models i870 and i890 uses the separation to package the I/O in a separate tower. TE 46 The SStar Microprocessor The SStar microprocessor is a fully scalable sixty-four-bit POWER Symmetric Multiprocessor implementation. SStar-based systems are Team-Fly® IBM ~ iSeries A10 INT BUS BCAL BCAEX I/O BUS BUS EXTENSION L2 CACHE 0.5 MB L2 CACHE 0.5 MB STGCTL MAIN STORAGE 47 STGCTL MAIN STORAGE Figure 1.22. Microprocessor I/O and main storage interconnect for low-end and mid-range processors. targeted at the high-performance computing graphics, commercial workstation, and entry-level server markets. To meet the requirements of compute-intensive environments, the SStar design contains a highly superscalar core that comprises eight execution units, fed by a highbandwidth memory interface supporting four floating-point operations per cycle. There are two L1 cache functions implemented on the SStar processor; instruction cache of 32 KB supports two outstanding misses, and data cache of 64 KB supports up to four misses. All caches are nonblocking. Designed for high bandwidth, the SStar processor has a separate, independent sixteen-byte memory bus and a thirty-two-byte L2 bus, each with separate address, data, and control lines, enabling the achievement of 6.4 GBps throughput to the L2 cache. Sequential instruction and data access detection algorithms are implemented in hardware, permitting prefetch of cache lines to closer levels of the memory hierarchy, reducing the negative performance impact of increasing memory latencies. 48 Exploring IBM ~ iSeries The SStar design has 23 million transistors and uses copper CMOS 7s 0.22-micron technology. The SStar microprocessors run at up to 750 MHz. The POWER4 Microprocessor The POWER4 microprocessor runs at clock rates up to 1.3 GHz. The design goal for the development of the POWER4 microprocessor was optimization for Symmetrical Multi-Processor (SMP) designs and total system performance (memory and I/O interfaces), and binary compatibility with 32-bit and 64-bit PowerPC applications. Each POWER4 chip has two microprocessors, each with an L1 data and instruction cache and sharing a unified L2 cache structure through a crossbar switch (CIU). The L1 instruction cache is a 64 KB directmapped cache capable of either one thirty-two-byte read or write each cycle, which is indexed by the effective address of the instruction cache line. The L1 data cache is a 32 KB two-way set associative cache with an FIFO replacement policy, capable of two eight-byte reads and one eight-byte write per cycle. The data cache implements a store through design, meaning that updates to the L1 data cache are immediately stored through to the L2 cache to maintain synchronization between the two caches. Figure 1.23 illustrates the main components of the POWER4 chip. The L2 cache is physically divided into three equal parts, each with an L2 cache controller. Logically part of the L2 cache, each processor has an associated non-cacheable unit responsible for handling instruction-serialization functions and performing any non-cacheable operations in the storage hierarchy. To minimize the latency to memory, the directory for the L3 cache and its controller are located on the POWER4 chip. (The actual L3 arrays are located on the MLD module.) I/O device communication is implemented using the gigaprocessor series bus and the two associated four-byte wide GX buses, one on chip, and one off chip. The POWER4 chip also contains a fabric controller that controls the network of buses, which connect the on chip L2 and L3 controllers and other POWER4 chips and POWER4 modules. The fabric controller directs a point-to-point network between each of the four chips on the Multichip Module (MCM) as well as the buses to the NCU and GX controller. Additional functions on the chip include trace and debug facilities, built-in self-test facilities, performance monitoring, an interface to the service processor used to control the overall system, power-on reset sequencing logic, and error detection and logging circuitry. IBM ~ iSeries Core Processor 1 Trace & Debug Ifetch BIST Engines Store Core Processor Loads Ifetch Store Loads SP Controller Error Detect & logging Cache L2 Cache L2 Cache L2 Core 1 NC Unit Chip-Chip Fabric (2:1) Core 2 NC Unit Chip-Chip Fabric (2:1) Fabric Controller MCM-MCM (2:1) Figure 1.23. JTAG POR Sequencer CUI Switch Perf Monitor GX Bus (N:1) 49 GX Controller L3 Directory MCM-MCM (2:1) L3 Controller Mem Controller Bus L3/Mem (3:1) POWER4 chip architecture. Processor Core Overview Figure 1.24 illustrates the functions of each processor core. The processor core is a speculative superscalar microprocessor with out-of-order instruction execution capabilities. Eight independent execution units are capable of executing instructions in parallel, providing a performance attribute known as superscalar execution. The execution units include two identical floating-point units capable of completing a multiply/add instruction each cycle (for a total of four floating-point operations per cycle), two load-store units, two fixed-point units, a branch unit, and a unit to perform logical operations on the condition register. To keep these execution units busy, each processor can fetch up to eight instructions per cycle and dispatch and complete instructions at a rate of up to five per cycle. Each processor can have more than 200 instruc- 50 Exploring IBM ~ iSeries IFAR I-Cache BR Scan Instr Buffer Decode, Crack & Group Formation BR Predict GCT BR/CR Issue Q BR Exec Unit CR Exec Unit FX/LD 1 Issue Q FX1 Exec Unit FX/LD 2 Issue Q LD1 Exec Unit LD2 Exec Unit FX2 Exec Unit FP Issue Q FP Issue Q FP1 Exec Unit FP2 Exec Unit StQ D - Cache Figure 1.24. Block diagram of POWER4 processor core function. tions in various states of execution concurrently. Instructions may be issued and executed out of order but are tracked to complete in program order. This out-of-order instruction capability allows the processor to continue executing instructions while it waits for load instructions to retrieve data from the storage hierarchy located beyond the L1 data cache. Eight requests per processor can be outstanding to reload data into the L1 cache. Instructions execute speculatively. Speculative execution potentially enhances performance by eliminating stalls associated with waiting for a condition associated with a branch to be resolved. If an instruction IBM ~ iSeries 51 contains a conditional branch instruction, the conditional test associated with that branch directs the flow of execution either to take the branch or to continue execution at the next sequential instruction. All such conditional branches are predicted and instructions are fetched and executed speculatively based on that prediction. In order to make accurate predictions about the outcome of a conditional branch instruction, the processor tracks two different prediction methodologies simultaneously, and also tracks which method is more effective in predicting a particular branch so it may use the more successful prediction method for a given branch. There is also target address prediction logic for predicting the target of branch-to-link and branch-to-count instructions, which often have repeating targets. Storage Hierarchy In addition to the instruction and data L1 cache functions discussed earlier, each POWER4 chip includes an L2 cache that’s managed by three L2 controllers. Cache lines are hashed across the three controllers. Cache line replacement is implemented as a binary-tree psuedo-LRU (least recently used) algorithm. The L2 is a unified cache for instructions, data, and page table entries, and is shared by both processors on the chip. Memory coherency in the system is primarily enforced at the L2 cache level by the cache controllers utilizing command queues known as coherency processors. All transactions in the system are observed by snoop processors in the controllers which provide responses or deliver cache lines as the situation merits. The basic building block for the POWER4 Symmetrical Multiprocessor environment is a Multi-Chip Module (MCM). The POWER4 MCM includes four processor chips, for a total of eight processors per MCM. Symmetrical multiprocessors can be configured with sixteen, twenty-four, and thirty-two processors. Figure 1.25 illustrates the content and interconnection to the POWER4 MCM. The L3 cache is an eight-way set-associative cache organized in 512byte blocks but with coherence still maintained in the system cache line size of 128 bytes. The POWER4 chips are connected to memory through the L3 cache. In general, the L3 cache deals with data that comes from the memory port to which it is attached. The L3 cache is designed to be combined with other L3 caches on the same processor module in pairs or quadruplets to create a larger address-interleaved L3 cache. The L3 cache MLD chip contains 16 MB of L3 cache. Two chips are packaged 52 Exploring IBM ~ iSeries M MEM Ctrl E GX Bus L3 M X1 Ghz Core X1 Ghz Core Shared L2 Chip-Chip comm. L3 MEM Ctrl M GX Bus E M O O R R Y MEM Ctrl GX Bus Figure 1.25. L3 L3 MEM Ctrl Y GX Bus Block diagram of the POWER4 Multi-Chip Module (MCM). on a module. There is one module per processor chip on the MCM, making for a total L3 cache size of 128 MB. This grouping increases the cache size and the bandwidth available to any processor. Main Storage The “memory,” or main storage, is the set of electronic circuits within an iSeries system that provides a “workspace” for the system processor. Data and programming instructions are moved from disk storage to main storage for the programs and the processing of data. After execution or processing, modified data are moved back to main storage and are kept there until no longer needed. At that point, the data typically are written back to disk storage for safekeeping. iSeries systems spend much time moving information between the system processor and main storage. There are two major reasons that this is so. First, all programs currently being executed by the system processor reside in main storage. Therefore, the system processor must (at some point) retrieve every instruction from main storage. Second, main storage holds the data to be acted on by the system processor. Since the information traffic between the system processor and main storage is heavy, the speed of main storage is important to overall sys- IBM ~ iSeries 53 tem performance. That is why high-speed cache memory, which increases the effective speed of main storage, is included in the system design. As we have seen, every main storage location in iSeries main storage consists of sixty-four pieces of information, or bits. All information in main storage is encoded using these 64-bit groupings, called double words. In addition to the sixty-four bits of information, each word in main storage has several additional bits (called check bits) that are generated based on the value of that particular sixty-four-bit word. In the event that one or two bits of the sixty-four-bit words is somehow corrupted, the check bits notify the iSeries computer that the error exists. If only one bit of the sixty-four bits is corrupted, as is usually the case, the check bits actually restore the corrupted bit and correct the error. This main storage error detection and correction works to protect the allimportant integrity of user information in the computer system. Storage Management The methods used within a computer system to manage main storage and disk storage, called the computer’s storage management, are fundamental to the capabilities of the computer. Understanding the basics of storage management provides insight into one of the unique features of iSeries computers compared with traditional computer systems. Figure 1.26 shows conceptually what the storage in iSeries computers looks like. All programs and information currently being used by the computer system must be contained in main storage, which resides inside the computer’s system unit. Main storage is relatively expensive and responds at very high speeds (compared to disk storage) when called on to provide or store information. Because main storage loses all information when the computer system is turned off, it is called volatile storage. Main Memory Figure 1.26. Disk Storage iSeries main storage and fixed disk storage. 54 Exploring IBM ~ iSeries Disk storage is less expensive but cannot provide or store information as quickly as main storage. Disk storage is said to be nonvolatile because it does not lose its information when the power is turned off (or lost due to a power failure). As a result of this nonvolatility and relatively low cost, disk storage is commonly used to hold all information that must be readily available to the computer. Disk storage may reside either inside the system unit or inside a separate box cabled to the system unit (as depicted in the figure). Disk storage can be internal or external. When external on iSeries eServers, that storage is connected using fiber channel. (See the discussion on Storage Area Networks [SAN] in Chapter 2.) When the iSeries computer is first turned on, information vital to an orderly startup and smooth operation is automatically copied from the disk to main storage. Once normal system operation is established, users can begin to do their work. During the course of this work, users will start various computer programs. As each program is started, it is copied from the disk to main storage and then executed. Depending on the work being done, the computer programs manipulate various sets of data that are also loaded from the disk as needed. It does not take long to realize that the main storage in a computer can quickly become filled up with programs and data as the system is called upon to do more and more work. In the earlier days of computing, the main storage size limited the amount of work a computer could manage at any one time. This limitation capped the size of programs, the number of programs that could be run concurrently, the number of users who could share the system, and so on. In modern computers a technique called: virtual storage (discussed more fully in Chapter 4) alleviates the need to squeeze all active programs and data into main storage. In computers that support virtual storage, the computer basically “fakes out” the computer programs and appears to have much more main storage than it actually has. (The iSeries allows a virtual storage size of 144+ million terabytes.) Virtual storage therefore allows more programs, data, and users to be simultaneously active on the system than could be supported in real main storage. Auxiliary Storage Auxiliary storage, commonly used to keep data and program information in all computers, is an inexpensive way to retain and later access information. Information kept on auxiliary storage can easily be modified or kept unchanged over long periods of time as an archive. Because IBM ~ iSeries 55 all auxiliary storage is nonvolatile, the information remains intact whether the computer is turned on or off. The iSeries systems use four types of auxiliary storage: diskette, disk, optical libraries, and tape. Diskette Storage Diskettes are a portable magnetic storage medium that can be used to record and later retrieve computer information via a diskette unit. The diskettes consist of a flexible disk with a magnetic surface permanently enclosed in a square, protective outer jacket, as shown in Figure 1.27. One of the primary functions of diskettes is to provide portable storage, allowing for the transfer of programs and data between computers. To this end, all similarly configured iSeries computer systems can freely exchange programs and data via diskettes. Also, information on System/3X diskettes can be freely exchanged with a properly configured iSeries computer. Disk Storage Earlier in the chapter we introduced another kind of auxiliary storage used with iSeries systems called disk storage units, or Direct Access Storage Devices (DASDs). These are high-capacity magnetic storage devices commonly used in all types of computers from PCs to large mainframe computer systems. The basic anatomy of a disk unit is shown in Figure 1.28. Disks consist of a drive mechanism with permanently installed metallic disks, often called platters (because they are shaped like a din- Figure 1.27. Diskette used with application servers. Exploring IBM ~ iSeries AM FL Y ner plate). These platters have a magnetic surface that can store information. Disk units are described in greater detail in the following paragraphs and in Chapter 2. Disk unit performance is important to the overall performance of a computer system in most applications. This is particularly true in virtual storage and multiuser environments, in which there is heavy transfer of information between disk storage and main storage. The performance of a disk unit refers to the rate at which information can be located and transferred between the disk unit and the main storage. The speed at which a disk unit can position the read/write head over the proper region of the platter is the average seek time, usually expressed in milliseconds (1/1,000 of a second). After the read/write head is properly positioned, the system must wait as the platter spins until the needed data begin to pass under the read/write head. The average time it takes for the platter to rotate to the proper position is called the average latency (also expressed in milliseconds). Finally, once the read/write head is positioned and the data begin to pass by on the spinning platter, the information is transferred from the disk unit to the computer system. The speed at which this is done is called the data-transfer rate and is usually expressed in millions of bytes per second (MBps). The shorter the average seek time and the average latency, and the higher the transfer rate, the better the performance of the disk storage subsystem and the overall computer system. Figure 1.29 shows the average seek times, average latency, and data transfer rates for some internal disk units that are provided as standard equipment on iSeries systems. TE 56 Head Disk Assembly Armature Read/Write Head Platter Figure 1.28. The anatomy of a disk unit. Team-Fly® IBM ~ iSeries 57 In addition to the disk unit specifications, there are other performance considerations when configuring the disk storage subsystem of an iSeries system. Some disk units have multiple actuators, whereas others only have one. (The actuator is the accessing mechanism of the disk unit, which carries the read/write head and flies over the surface of the disk detecting or imprinting the magnetic bits.) Often, each actuator in a disk unit can perform independently, so the more actuators you have for a given amount of disk storage, the better the performance. In fact, choosing disk storage configurations that have more actuators for a given amount of storage can result in higher performance than selecting disk units with faster specifications but fewer actuators. This is particularly true with iSeries systems because single-level storage tends to spread information over many areas of the disk units. This spreading of information produces more efficient operation because the actuators can all share the load, but it does emphasize the need to follow proper backup procedures. Computer System Standard Configuration Disk Size Average Seek Time Data Transfer Rate Rotation Speed (rpm) Number of Acuators/ Drives 150 720,730 740,170 150,170, 720,730, 740, 250, 270, 820, 830,840 150,170, 720,730, 740, 250, 270, 820, 830,840 270,820 830,840 270,820 4194 MB 4194 MB 3.5 inch 3.5 inch 8.6 8.6 20 40 7200 7200 1 1 8580 MB 3.5 inch 8.6 40 7200 1 17500 MB 3.5 inch 8.6 40 7200 1 8580 MB 3.5 inch 8.6 40 10000 1 17500 MB 3.5 inch 8.6 40 10000 1 Figure 1.29. Performance characteristics of internal fixed disks provided as standard in iSeries servers. 58 Exploring IBM ~ iSeries Optical Libraries Optical libraries consist of arrays of optical disks associated with one or more optical disk read/write units. In some cases, the optical storage read/write units also have one or more conventional magnetic disk storage units associated with them to improve the write performance from a system perspective. The optical disks may be CD-ROM, WORM, or WMRM technology, each of which imposes different requirements upon the read/write unit and upon the controller within the system. CDROM is an abbreviation for Compact Disk–Read Only Memory, and the technology presents digital data in a continuous serpentine path across the surface of the optical disk. WORM is an abbreviation for Write Once, Read Many. This technology presents data in circumferential paths across the surface of the optical disk. Because the data will only be written once, this technology generally has the header embedded on the raw media, and a sector corresponds to the data content that can fit in the shortest circumferential track. WMRM, sometimes referred to as erasable optical disk technology, is an abbreviation for Write Many, Read Many and also presents data in circumferential paths across the surface of the optical disk. But because the data written at one time must be erased before new data may be written to replace it, WMRM must follow the sectoring, header, trailer, and error-correction rules of magnetic disk technology, including bad track recovery and directory management. DVD-ROM is similar to CD-ROM in that the data may be written once and read as frequently as needed. The major difference is in the capacity of the media. DVD-ROM has a capacity of 4.7 GB versus the capacity of a CD-ROM at 640 MB. DVD-RAM is rewritable DVD media, again similar to the WMRM media described above for CD based technology. Again, the capacity is the major difference in the same proportion as described above for DVD-ROM. Tape Storage The last type of auxiliary storage to be covered is magnetic tape, or simply “tape.” One primary purpose of tape is to provide a backup storage medium for information on the computer’s disk storage. The low cost and high recording densities inherent in tape make it ideal for archiving information. Tape is also very useful in distributing programs and transferring information from one computer system to another. IBM ~ iSeries 59 Diskettes can be used for these same functions, but the higher storage capacity of tapes is preferred if you are dealing with a large amount of information. Tape storage consists of a long, flexible strip coated with magnetic material and rolled on a reel or into a cartridge. Tape is discussed in more detail in Chapter 2. OptiConnect OptiConnect is the system-to-system interconnection fabric that allows distributed functions and applications to operate at high speed. It can be used to form a high-performance, multisystem cluster (group of computer systems working together). There are two primary uses for the OptiConnect technology. Horizontal growth is the traditional and most popular use. Separating database operations from applications workload allows multiple systems to operate as a cluster to grow computing power beyond what a single system can provide. It is important to understand that not all applications are conducive to this type of workload distribution. The horizontal growth/scalability is dependent on the database I/O intensity. The best implementation is the separation of the interactive application from the corresponding data while maintaining the batch application on the same system as the batch data. Techniques are available that transparently manage the batch job submission to the database server system. The second use for OptiConnect technology is high availability. When used in conjunction with business partner applications such as those offered by Lakeview Technology and Vision Solutions, efficient, highavailability solutions can be achieved. The OptiConnect technology provides the most efficient use of CPU resources to allow fast replication of data between systems. Perhaps the most critical clustering function is heartbeat monitoring, which constantly checks communications between the nodes in a cluster. If communication between two nodes is lost, heartbeat monitoring attempts to reestablish communications; if a node fails, heartbeat monitoring reports the node failure to the rest of the cluster. Although the HABPs (High Availability Business Partners) can implement a form of heartbeat monitoring, IBM’s system-level implementation of heartbeat monitoring consumes fewer resources and provides a more accurate view of node status. Heartbeat monitoring, in conjunction with other integrated cluster services, ensures that all nodes have a consistent view of the cluster. 60 Exploring IBM ~ iSeries Two things differentiate OptiConnect from traditional communications-based distributed operations. The first is a system bus connection between multiple systems using high-speed fiber optic technology. The second is an I/O driver embedded in the operating system that streamlines the application access to data on a remote system. To accomplish this, OptiConnect provides a shared bus on which systems communicate using a peer-to-peer protocol. Once OptiConnect establishes system connections on the shared bus, much of the APPC (Advanced Peer-to-Peer Communication) protocol stack is bypassed. The OptiConnect fast-path connection for database transactions provides DDM (Distributed Data Management) access to databases anywhere in the OptiConnect cluster at a fraction of the standard communications code path. Data warehouse, DRDA, and data propagation functions can use this technology. Traditional communication protocol overhead is too impractical for heavy-workload-distributed applications. To minimize latency, or the time it takes to send a message and receive a response, the protocol chosen must be efficient in the number of code steps required. To maximize bandwidth, or the amount of data that can be transferred in a unit of time, high-performance hardware must be used. The OptiConnect channel is very efficient and is the best solution for both latency and bandwidth. The length of the cable affects how low latency can get. As distance increases, the speed of light becomes a limiting factor for a given bandwidth. The OptiConnect for OS/400 software provides a streamlined communications path across the dedicated system buses. Together with the hardware, the following functions can utilize the high-speed systembus-level connections between iSeries systems: • All Distributed Data Management (DDM) operations for supported object types can run across OptiConnect, including data files, data areas, and data queues. • All Structured Query Language (SQL) support provided by DRDA will run across OptiConnect, including distributed unit of work and remote unit of work. • DB2 Multisystem with its DB2/400 support for multinode files will run across OptiConnect, providing data warehouse functions of Query for iSeries support and two-phase commit. IBM ~ iSeries 61 • ObjectConnect/400 will operate over OptiConnect to provide high-speed system-to-system save/restore functions. • Standard APPC conversations are available over OptiConnect with an OptiConnect communication controller. This allows for System Network Architecture Distribution Services (SNADS), display station passthrough, network printer passthrough, and other functions. • OptiConnect has an Application Program Interface (API) to which business partner software packages can code. OptiMover for OS/400 is a special, low-cost PRPQ (Programming Request per Quote) version of OptiConnect for OS/400 software. It enables non-DDM functions to utilize the OptiConnect high-speed link, allowing system-bus-level connections between iSeries systems. Business-partner packages written to these APIs allow users to take advantage of this lower-priced option. OptiMAL Connect The iSeries 8XX models support a high-performance optical bus connection called HSL OptiConnect. HSL OptiConnect is a system area network that provides high-speed server- to-server connectivity using HSL Loop technology, which is a replacement for the SPD bus. HSL OptiConnect provides a 1 GB/second transfer rate. Through this connection, iSeries servers can be connected together and cooperate (exchange programs and data) without suffering the performance degradation typically associated with system interconnection via other methods (e.g., TCP/IP, Ethernet, or token-ring networks). OptiMAL Connect is supported on all V5R1 and later models. HSL OptiConnect communication between systems requires V5R1 and the optional feature OptiConnect for OS/400 software on each system. Switchable Independent Application Storage Pools (IASPs) use the HSL OptiConnect loop and require an optional feature, HA Switchable Resources for OS/400 software. OptiConnect for OS/400 is not a requirement for switching I/O towers. OptiConnect intersystem communications can use either HSL OptiConnect hardware, 1 GBps Ethernet, or SPD optical via a Migration Tower, and OptiConnect intersystem 62 Exploring IBM ~ iSeries communications is required software, but HA Switchable resources are not required. OptiMAL Connect loop maximums are as follow: • Two servers per HSL OptiConnect loop • Max external towers (I/O and IXS) are model dependent (see Figure 1.30) • Three external I/O towers per loop segment (section between two systems) • Migration towers are not supported on an HSL OptiConnect loop • HSL OptiConnect is limited to 250 meters An HSL OptiConnect cluster can consist of up to fifteen systems with full system-to-system connectivity if all systems in the cluster were Model 890 systems and each loop from any system included at least one I/O tower. Up to thirty-two systems can be interconnected in more complex structures where all satellite systems must communicate with one hub systems. Figure 1.31 illustrates the clustering of three systems. System Availability Functions Since their inception, the AS/400 systems and their iSeries follow-ons have had high availability as a target. The average single AS/400 system in 1997 had an availability of greater than 99.9 percent, with average Model i800 Model i810 Model i825 Model i870 Model 890 Figure 1.30. I/O Towers System Maximum HSL Loop Maximum I/O Towers and IXS’s/HSL Loop 1 4 18 47 47 1 1 3 (1st loop max is 1) 8 (1st loop max is 5) 14 (1st loop max is 5) 1 13 36 48 48 Maximum external Netfinity or IXS units or I/O Towers. IBM ~ iSeries iSeries System C 9406 Model 320 Optical Bus from System C Optical Bus from System A iSeries System A 9406 Model 320 Bus Expansion Unit Optical Bus from System B iSeries System B 9406 Model 310 Figure 1.31. Three-system cluster with one bus given up in each system to connect to the expansion tower. 63 64 Exploring IBM ~ iSeries unplanned outages of less than nine hours per year. Daily reports are accumulated on greater than 87,000 AS/400 and iSeries systems in the United States. These reports show that on systems shipped since January 1996, the average interval between hardware problems is sixty-one months. These results were accomplished through a combination of hardware and software actions. The hardware and software items described next identify the actions taken by the iSeries to achieve that availability. The five items described after the hardware and software actions are what take the iSeries beyond the AS/400 to an availability of 99.99 percent. On the hardware side, things like battery backup and continuously powered main storage protect against utility failures and the loss of data that could result from those failures. Redundant bulk power supplies and independent redundant local voltage regulators protect against power system failures. RAID-5, mirroring, and redundant write cache protect against data loss from disk unit failures, whereas concurrent maintenance allows the repair of those failures without loss of the system to your users. System Power Control Network (SPCN) turns the system and its remote components on and off at the same time and monitors the remote units to enable maintenance actions before they cause a catastrophic system failure. From the software side, items like commitment control and journaling, auxiliary storage pools, system-managed access paths, savewhile-active, S/R parallelism, hierarchical storage management, and BRMS (combined with the pretesting of the integrated operating system and applications code) reduce the duration of the recovery actions needed if an outage does occur. Figure 1.32 describes the hierarchy of actions needed to achieve 100 percent availability. The following paragraphs describe the options offered as well as the choices a user must make to increase the iSeries availability. Included in the choices are capabilities such as logical partitioning, multisystem coupling, data and application resiliency, clustering of systems, and disaster tolerance. OS/400 Subsystems and Logical Partitioning Logical partitioning is the creation of several independently functioning systems within the covers of a single system. Initially, N-way Symmetrical Multi-Processors (SMP) (where N is replaced by the number of processors) and sufficient main storage were both required. With the V5R1 announcement, this is no longer required. The primary partition re- IBM ~ iSeries 100% 65 Disaster Tolerance Remote Cluster Nodes High Speed WAN Clustering Integrated Cluster Resource Services HABP Cluster Management Data Resiliency & Application Resiliency High Availability Business Partners Cluster-enabled ISVs, Check Point Restart Multi-System Coupling DDM, DRDA, Journaling, DB2 Multisystem, High Speed Opticonnect OS/400 Subsystems and Logical Partitioning Subsystem Isolation, Automatic Restart, Multiple, Independent OS/400 Copies, Partitioned IPL 99.9% Software 45 Million Lines of Pre-tested, Integrated Code, Commitmen Control, Auxiliary Storage Pools, System Managed Access path, Save-while-active, S/R parallelism, HSM, BRMS, ADS Hardware RAID-5, Mirroring, Battery Backup, Redundant Write Cache, Continuously Powered Main Store, Concurrent Maintenance Figure 1.32. iSeries availability solutions. quires one-quarter of a processor and 256 MB of main storage. Creating and managing secondary partitions is done from the primary partition. Each secondary partition requires a minimum of one-tenth of a processor, 64 MB of memory, an I/O processor with disk resources, and its own console device. The maximum number of partitions has been extended from twelve to thirty-two with the V5R1 announcement. It is possible to have OS/400 V4R4 running in one partition while OS/400 V5R2 is running in another partition. Support has been added for an external stand-alone CD-ROM that can be switched between partitions to simplify the loading of software. There can be multiple secondary partitions, each with its own I/O resources assigned from the list of total system resources. Processors can be shared between partitions. An installation of a secondary partition does not impact other partitions, but an IPL of the primary partition requires an IPL of all secondary partitions. Figure 1.33 illustrates how logical partitioning might appear on a single system. Resources can be dynamically moved between partitions as required without requiring a re-IPL. OS/400 OS/400 Each partition runs a logical independent version of OS/400 within the same physical system • Footprint consolidation • Mixed test environments • Departmental systems • Integrated cluster • Constrained systems • Firewall • Granular switchover OS/400 OS/400 Exploring IBM ~ iSeries Hypervisor SMP IOP IOP IOP AM FL Y IOP V4R4 Manual configuration at IPL Figure 1.33. iSeries logical partitioning. TE 66 New processor and memory resources can be allocated to a secondary partition by an IPL of that partition, not the entire system. Available I/O resources (e.g., disk, tape, and CD-ROM) can then be allocated to that secondary partition without an IPL. Tape, I/O processors, and CDROM devices can be switched between partitions and can also be dedicated to individual partitions. I/O processors become the switchable entity for IASPs between partitions. A dynamic virtual and High-Speed Link connects each partition to its I/O. Adequate communications resources such as LAN adapters should be dedicated to each partition. OS/400 is licensed once for the entire system by its normal processor group, independent of the number of partitions. V4R4 of OS/400 is the initial enabling release for logical partitioning and can be installed on each partition. Pre-V4R4 releases are not supported for logical partitioning. License management has been improved to manage system licenses across the entire system rather than at the partition level. An internal virtual bus provides the option to use OptiConnect for high-performance communications between partitions. OptiConnect allows applications on one partition to access the database of another partition using DDM remote SQL, although disk resources are not physically shared. So although logical partitions can be operated independently, the high-speed internal bus connection between partitions enables Team-Fly® IBM ~ iSeries 67 applications having a need for multiple iSeries application servers to access a single database server. A virtual LAN is supported to provide multiple communications paths between partitions (OS/400 to OS/400, OS/400 to Linux, Linux to Linux) without required additional hardware resources. This allows the sharing of I/O functions between partitions. The partition sharing the resources is called the Host. The Host can be a primary partition, but it does not have to be. A single partition can be the Host for multiple Linux partitions. The shared resources are under OS/400 management (e.g., disk space is allocated from OS/400 disk drives for Linux use.) Included are OS/400 data-protection methodologies such as RAID and backup/restore facilities for the Linux environment. Up to sixteen highspeed virtual LAN, TCP/IP connections can exist per partition. The virtual LAN provides selective communication paths between partitions utilizing the iSeries memory bus to emulate 1 GB Ethernet Adapters. System values for each partition are set independently. Each partition has a different system name and can use a different primary/secondary national language, or can even be operated in different time zones. Multinational companies can centralize multicountry operations in a single location while retaining the national characteristics of each system. For Logical Partitioning, a minimum of V4R4 must be installed on each partition. AS/400 6XX, 7XX, and Sx0 systems can support V4R4, V4R5, and V5R1 operating systems in their partitions, but the restriction of each partition requiring a single non-shared processor apply. These systems also do not support a Linux partition. The iSeries 8XX systems cannot support V4R4 because the PCI I/O adapters were not supported in that release. The increased scalability of the iSeries provides the opportunity for companies to consolidate multiple iSeries systems into fewer, more manageable systems. Logical Partitioning (LPAR) in OS/400 enhances the role of the iSeries as a consolidated server. Logical partitioning provides both the power and flexibility to address multiple systems requirements in a single machine. Logical partitioning needs to be considered for environments requiring server consolidation, business unit consolidation, mixed production and test environments, and integrated clusters. The Model i800 can support up to 4 Linux partitions. For all other models (i810, i825, i870, i890) the limit is 10 partitions per processor up to a maximum of 32 partitions per system. Dynamic logical partitioning enables cost containment through the consolidation of server farms onto a single iSeries system. The partitions can be executing OS/400, Linux, AIX, or Windows operating systems. The management 68 Exploring IBM ~ iSeries headaches of a server farm can be reduced to the management of a single system all controlled through the primary OS/400 partition. (AIX has been announced as a 2004 target operating system for iSeries.) Multisystem Coupling Multiple iSeries systems can be coupled using the OS/400 resources associated with Distributed Data Management (DDM), Distributed Relational Database Architecture (DRDA), Journaling, DB2 Multisystem support for Symmetrical Multi-Processors, Switchable DASD towers, and high-speed OptiConnect. Data Resiliency and Application Resiliency Data resiliency and application resiliency are provided by the IBM highavailability business partners DataMirror, Vision Solutions, and Lakeview Technology. Checkpoint restart is a capability included within the software provided by these business partners. Also included within the business partner-provided software are cluster management, data replication, and application availability tools. Two types of cluster resource groups are supported, one for data resiliency and one for application resiliency. Data resiliency provides the capability to switch the point of access for a set of data over to a backup node that is maintaining an exact replica of that data. Resilient resources are object replicated to one or more nodes of a cluster. Application resiliency provides the capability to switch an IP address (representing the application server) to a backup node and to restart the application in the event of a primary node failure. Continuous Availability Clustering Continuous availability cluster solutions are designed for those users who require access to their data and systems 365 days a year, 24 hours each and every day. The continuous availability cluster solutions can use a pair of iSeries systems consisting of any iSeries system or server. The systems are connected together using a high-performance data path, either optical or ATM. Also, the systems are connected to either a LAN or a WAN containing either terminals or personal computers. Figure 1.34 illustrates the system interconnection for continuous availability. Figure 1.35 illustrates the supported cluster topologies including a re- IBM ~ iSeries CRG CRG CRG Primary Server Any AS/400 System Applications File update/OLTP CRG CRG LAN/WAN Secondary Server HA Server Applications: Save to tape Batch Hot backup Routine Maintenance 170, 720, 730, 740 server 365-day X 24-hour operations Operations may be used to: 1. Selectively reduce interactive activity 2. Naturally fit server Figure 1.34. System interconnect for high availability. 270 270 840 830 890 Hub Tower Hub Tower 840 ATM WAN 270 820 270 830 LPAR Switch 270 270 Figure 1.35. 270 Cluster topologies supported for iSeries. 820 69 70 Exploring IBM ~ iSeries mote cluster node connected by a high-speed WAN through a switch. Switched-disk clustering increases protection against unscheduled outages and improves the available options for scheduled data center server maintenance and upgrades. Cluster resource services within the OS/400 operating system reduce the complexity of managing iSeries clustered systems. OS/400 keeps track of data and applications for those systems. Cluster-management and data-resilience applications (provided by high-availability business partners) protect users’ businesses from unplanned and planned outages as well as site loss disasters. Cluster resource services contain an open set of APIs providing cluster facilities available to iSeries application providers and users to enhance application availability. These APIs allow the creation, configuration, and administration of the cluster. Systems are defined into the cluster as cluster nodes. Communication interface addresses are defined to form the cluster node interconnection links. Cluster resource services also provide low-level facilities such as heartbeat monitoring, reliable message delivery, switch-over administration, and distributed activities. The services are built on cluster topology and messaging functions, which keep track of each node in the cluster and ensure that all nodes have consistent information about the state of cluster resources. Heartbeat monitoring ensures the active state of each node. If the heartbeat for a node fails, the condition is reported and the cluster can automatically fail-over to the resilient resources on the backup node. The iSeries clusters support up to 128 nodes (instances of OS/400), using any combination of the existing OptiConnect, HSL, WAN, and LAN connectivity options to build the cluster. A single workstation (containing the continuous-availability business partner cluster management application) manages all systems in the cluster. OptiConnect hardware is a connectivity method for high- and midrange models. ATM provides a high-performance connection to remote systems in a cluster. Ethernet and Token-Ring LANs can be used to connect low-end iSeries models into a cluster. Data resilience support for modern applications has been enhanced with the introduction of Byte Stream File (BSF) replication. Business partner solutions provide real-time recording of changes to BSF data replication to remote systems. Transfer of changes using remote journaling protects in-flight data at the point of failure. V5R1 introduces Resilient Cluster Devices which consist of a hardware resource represented by a configuration object that can be switched 71 IBM ~ iSeries between systems in the event of a system outage. Initially this only includes Independent Application Storage Pools (IASPs), but will be expanded eventually to include removable media and communications devices. To support resilient cluster devices, two new cluster constructs are needed; device domain and resilient device common resource grouping (CRG). The device domain consists of a subset of cluster nodes across which a set of resilient devices can possibly be shared, which prevents conflicts that would cause resilient device switching to fail. Cluster resources negotiated across a device domain include IASP number assignments, DASD Unit number assignments, and virtual addresses. New cluster interfaces can add or remove device domain entries and list domain information. CRG failover order is device, data, then application. New cluster interfaces manage device CRG and add/remove resilient device list entry. These concepts are illustrated in Figure 1.36. Disaster Tolerance Disaster tolerance is provided by the support of remote cluster nodes as replication points for resilient data. The remote cluster nodes can be off Model Number System Maximums HSL Loops Optical HSL Loops I/O Towers Integrated Adapters for xSeries I/O Towers and Integrated Adapters xSeries HSL OptiConnect Loops HSL Loop Maximums I/O Towers Integrated Adapters for xSeries I/O Towers and Integrated Adapters xSeries HSL OptiConnect Loop - 2 Systems I/O Towers and Integrated Adapters xSeries HSL OptiConnect Loop - 3 Systems I/O Towers and Integrated Adapters xSeries 800 810 825 870 890 1 0 1 4 5 1 1 0 4 13 17 1 4 1 18 36 36 2 8 2 47* 48 47 4 14 12 47* 48 47* 14 1 2 3 5 4 9 6 5 9 6 5 9 6 5 9 4 4 4 4 4 N/A N/A 0 0 0 *The primary I/O Tower is not included in this total as it is defined as part of the Model 840 or 890 Figure 1.36. Maximum connections on HSL Loops. 72 Exploring IBM ~ iSeries the user site, and may even use facilities of other businesses like IBM or Application Service Providers to provide recovery mechanisms. HighSpeed WAN facilities like ATM are used to support the remote cluster nodes. Disaster environments include hurricanes, tornadoes, and floods, wherein the business becomes unable to utilize its local facilities for a period of time. A 1998 Gartner Group study compared the availability of various systems. The only systems that ranked higher than the iSeries were clustered systems. The average Windows NT server outages were forty times worse than the iSeries servers. Upgrade Paths There are two methods available for upgrading within the iSeries product line: upgrading within a model and upgrading through a system unit swap. Upgrading within a Model This method is used if the need is for more performance or I/O device functionality and the current system is not using the maximum performance features available within the specific iSeries model. These could be the processor, interactive processor feature, main storage size, attachable I/O device capability, or disk storage size. In this situation, performance can be upgraded within a model by swapping processors, adding additional main storage, or adding disk storage or additional IOPs without having to swap system units. In general, the system should be upgraded within the model until those maximums are reached. This method of growth is referred to as horizontal growth. Upgrading through a System Unit Swap Another way to upgrade within the iSeries family is to replace the current iSeries system unit with a more powerful model (e.g., you upgrade a Model 825 to a Model 870 or 890 by changing the system unit). This method is used if the current system is at its processor and storage maximums, or if the number of users has increased beyond the capabilities of the current model. This method would also be used if there is a need for application programs that run on newer RISC-based iSeries models IBM ~ iSeries 73 only, or if you are upgrading from an older AS/400 model. This method of growth is referred to as vertical growth. Upgrades between Models No upgrades between models 6XX/SXX/7XX and 8XX servers may be accomplished without exchanging the system unit. You can continue to use all the same workstations, modems, and so forth. Upgrades of CPUs from a Model 150, Model 170, Dedicated Server for Domino 170D, SB1, 4XX/5XX, or CISC to 8XX models are not supported. Upgrades from these models will get a new serial number. Packaging Technology Most of the circuitry in iSeries systems was built using IBM’s version of Very Large Scale Integration (VLSI) technology called Complementary Metal Oxide Semiconductor (CMOS). This packaging technology builds circuits with 0.18 micron sized elements, allowing millions of high-speed transistors in a single chip. Main storage is implemented using IBM’s 16 MB and 64 MB (16 and 64 million bit) memory chip technology. Sixteenmegabit chips are used on all except the largest-capacity memory cards, which use 64 MB chips to achieve an improved packaging density. Three basic mechanical designs are used in iSeries computer system units. The sizes range from the deskside tower of the Model 800 to the dual tall-tower racks that house the models 870 and 890. The system unit package contains the system processor, main storage, tape, disk units, a CD-ROM, and some number of I/O controllers. The main storage for models 800/810 is packaged on standard DIMM form factor cards. Main storage for the microprocessor-based processors for Models i825, i870 and 890 is contained on separate 9x11inch cards that are plugged into an internal card chassis (called a cage), allowing for electrical connections to the bus. All iSeries systems use the cable-thru wiring scheme. Cable-thru allows multiple displays or printers (i.e., workstations) to be attached together in a daisy-chain fashion, as shown in Figure 1.37. With cable-thru, it is not necessary to run a separate cable from the computer to each workstation. Instead, a single cable from the computer can be used to attach up to seven workstations over a distance of up to 5,000 feet. 74 Exploring IBM ~ iSeries Single twinaxial cable ... Printer Display Personal Computer (PC) Figure 1.37. workstations. All applications use the cable-thru approach to attach to local Fiber Optic Bus The fiber optic bus design continued from the AS/400 predecessors permits the larger iSeries systems to support additional I/O buses. This allows the system to accommodate more I/O devices without loading down existing I/O buses. The fiber optic cable that attaches these additional I/O buses (i.e., system unit expansion features) uses laser light rather than electrical signals to exchange information with the rest of the iSeries system. Using light allows the additional I/O buses to operate at full speed over greater distances and eliminates the electrical interference inherent in electrical cables carrying high-speed signals. The fiber optic cables can carry light signals at a rate of 1,063 MBps. With these optical cables, the various towers of an iSeries system can be located up to 250 meters apart rather than within the twelve-foot limit imposed by earlier electrical I/O bus cables. Options and Peripherals 75 2 Options and Peripherals T he iSeries servers are likely to be found in many diverse environments—from fish markets to insurance companies. The activities performed by people in these environments vary widely, and so do their computing needs. By selecting the appropriate optional equipment, iSeries servers can be customized to many environments. This includes feature cards, internal options, and peripherals. Feature cards are circuit boards containing electronics that provide some additional capacity or function(s) to iSeries servers. They can be installed in one of the I/O expansion slots provided in all iSeries eServer computers. Peripherals are devices that attach to iSeries servers, usually via a cable, and perform functions under the computer’s control. This chapter covers: • Workstations • Auxiliary storage options • Communications options • Power and packaging options • Cryptographic processors. 75 76 Exploring IBM ~ iSeries Although this chapter does not provide comprehensive coverage of all the optional equipment that can be used with iSeries servers, it does introduce the reader to many devices that are representative of those most commonly used in the business environment. Workstations TE AM FL Y The devices used to interact with iSeries servers are known as workstations, which can be either terminals or printers. A computer terminal (also called a display station) is the TV-like device that converts the computer’s electrical signals into light images that convey information to the user. Terminals also come equipped with a keyboard that allows the user to send information back to the computer. Printers are electromechanical devices that print the computer’s electronically encoded information onto paper. If a workstation is near the computer system—for example, in the same building—it can be locally attached to the computer system via a cable. If the workstation is not near the computer—for example, in another state—it can be remotely attached over communications lines. Either way, the function provided to the workstation user is the same. Some type of workstation is required to allow the user to interact with the iSeries server. Many types of workstations can be used with iSeries eServer, including the following: • InfoWindow II Workstations • Operations console • Personal computer (PC) terminal emulation • Retail workstations • Printers, both impact and nonimpact • Combined-function I/O processor (CFIOP) • Workstation adapters. Team-Fly® Options and Peripherals 77 InfoWindow II Workstations InFoWindow II workstations are nonintelligent workstations consisting of a display and keyboard at the minimum, but they may also include a mouse as well as other features. The table shown in Figure 2.1 summarizes the more popular InfoWindow II workstation characteristics. Operations Console The iSeries Operations Console allows PC workstations with Windows 32-bit operating systems to locally or remotely perform iSeries system operations and services via an iSeries System Console Session. To allow the System Console Session, iSeries Access for Windows must also be installed. The Operations Console is a follow-on to the Client/Access PC5250 Console function. Operations Console can be used as a System Console Session when connected to iSeries systems running a recent version of OS/400. Operations Console connects to the Combined-Function I/O Processor (CFIOP) through a special cable, which may be ordered with the iSeries hardware, at rates up to 115,200 bps (depending on the attached model). Operations Console also provides the ability to remotely perform system console and control panel functions. To use the remote-console capability, called Remote Controlling System (RCS), a Local Controlling System (LCS) must initially be set up. This requires a Windows NT 4.0 desktop to be directly attached to the iSeries and running the operations console functions. The remote console also includes a graphical Information Window # Text Only/ Graphics 3486 3487 Text Only 14" Text Only 14"/15" Size 3488/3489 Text Only Variable Figure 2.1. Monochrome/ Color Printer Graphical Special Support Characters Features Monochrome Color/Mono Y Y Y Y Color Y Y InfoWindow workstation characteristics. Barcode/ Badge Reader Lite Pen 78 Exploring IBM ~ iSeries control panel application that allows a PC user to select iSeries Control Panel functions from the desktop. All control panel functions are supported, including system power on, except for those reserved for onsite CE use. To use this program, another special cable, which may be ordered with the iSeries hardware, must be connected to the iSeries Control Panel. This program can be used with iSeries systems running OS/400 V4R1 or later. The operations console is an install option of iSeries Access and is packaged both with iSeries Access for Windows and with EZ Setup (see Chapter 4) on the iSeries Navigator CD-ROM. Navigator can be enabled from the operations console if a help desk is present. This centralizes the system-management functions through a single ASYNC connection to the iSeries system. Developers can use iSeries Control Panel sockets API to write Windows applications to do iSeries Control Panel functions. It is possible to remotely connect a Local Controlling System for Operations Console using the ECS modem and TCP/IP dial-up. It is also possible to replicate the control panel function on a remote console and provide control of the iSeries system from that console. Personal Computer (PC) Terminal Emulation With the proper feature card and software (e.g., iSeries Access Family for Windows or iSeries Access Family), a Personal Computer (Figure 2.2) can also be used as a terminal for an iSeries server. In this case, the PC is said to be acting like (i.e. emulating) a terminal. In the simplest case, the PC appears to the iSeries server to be like any other terminal with no special capabilities. The user can then interact with the iSeries server just as with any other terminal discussed. Further, a printer attached to the PC can be used both as a printer for PC application programs and as a system printer for the iSeries application programs. Hitting a simple keystroke combination temporarily suspends terminal emulation, and the PC is changed back into a normal PC able to run the many PC programs available today. Because the PC is a computer, not just a terminal, it has its own intelligence. It is therefore called an intelligent workstation. This intelligence can be used to run PC programs independent of the iSeries servers, or it can be used to work with the iSeries servers, and it provides for Options and Peripherals Type: Color/text and graphics Features: Local intelligence, advanced graphics Options: Various models, connection type 79 Figure 2.2. Properly configured personal computers can be used as workstations for application systems. the direct interaction between PC programs and those running on iSeries servers. This type of interaction can be done without user intervention to perform functions ranging from simply transferring a file between the PC and the iSeries servers to more complex program-to-program communications (e.g., cooperative processing). You can also concurrently interact with multiple iSeries servers using a single PC or sign on to a single system as more than one terminal. If you have an existing PC system that you desire to attach to an iSeries system with an appropriate twinaxial, ASCII, or local area network (LAN) interface, but do not have the proper level of software, the iSeries system will detect this and automatically download the current level of iSeries Access Family, providing you with the selection of either the Windows 95/98/ME/NT/2000/XP support or Windows 3.1/OS2/ DOS support. V5R2 is the last release of OS/400 that will provide iSeries Access support for Windows95/98/ME/NT4. 80 Exploring IBM ~ iSeries Retail Workstations Retail workstations are basically PCs with a cash drawer and with some unique characteristics added to interface with customers and sales items. Those characteristics include the ability to print receipts on a rolling tape and acknowledge receipt of checks, the ability to present to the customer and the operator the price of what is being checked out, and an interface to at least one and sometimes several forms of UPC (Universal Product Code) barcode reader. With the advent of token-ring and Ethernet LANs on both the PC and the iSeries systems, a method for direct connection of those workstations now exists. An illustration of a retail workstation is shown in Figure 2.3. Of course, in some situations the retail workstation is connected via wireless methods. Figure 2.3. A typical retail workstation. Options and Peripherals 81 Printers Printing technologies have exploded, providing dramatically expanded choices in speed, resolution, connectivity, color, and paper-handling function. The technology is important, but printing requirements (and with e-business applications, presentation requirements) still drive printer decisions. Some of those key requirements are: • Document characteristics: Electronic-output documents, where the application composes the entire output page (as opposed to only variable data with preprinted forms), have greatly increased the use of electronic forms, bar coding, image and graphics, typographic fonts, and color. Preprinted forms remain a major requirement in many environments, particularly where carbon copies must be produced. • Printing applications: Where does the application reside (system, client, network)? What output datastream is created? Where will it be printed or delivered? • Printer location: Where will the printer be located (in the extended iSeries network)? How will it communicate? What systems and applications will be supported? • Printer function: Combining print, copy, scan, and fax in a single footprint is now an option. These are called Multifunction Printers, or MFP for short. • Relative importance: Where is the printing application, on a scale from convenience or personal up to mission-critical? The characteristics and management required for mission-critical printing normally are significantly different from printing to a convenience printer. • Print volume: Printing at speeds of sixty pages per minute and higher is generally considered production printing. Individual printers printing over 1,000 pages per minute are now directly supported on iSeries (i.e., InfoPrint 4000 Advanced Printing System). 82 Exploring IBM ~ iSeries • Print window: Usually related to print volume, the print window refers to the time duration available for a given print application. For example, a month-end statement run may need to be done within a three-day print window. • Printing costs: The costs of placing a printer, both acquisition and operational costs. • Other factors: Other factors such as special forms or environmental considerations. Special forms can include heavier paper stock or even plastic (i.e., credit or membership cards). There are some printers (for example, the InfoPrint 62) that can handle these kinds of forms. • e-Output requirements: Does the document or report need to be distributed electronically in addition to (or in lieu of) printing? Changes in document characteristics represent one big change in iSeries printer requirements. iSeries printing traditionally has meant printing simple lines of text on twinax-connected impact printers. Printer decisions were primarily based on speed. With electronic documents, anything can be printed anywhere on the page. This means that the document can become part of the organizational workflow. For example: • Bar-coded labels are scanned during order picking to automatically update shipped quantities. • Documents with zip codes encoded in Postnet bar code are automatically routed by scanning equipment, which results in significantly lower mailing costs. • Checks printed with MICR encoding are automatically processed. • Payment coupons with the invoice number and invoice amount encoded in barcode can be scanned upon receipt, instead of being re-keyed. • Scanned documents, such as checks or freight bills, can become part of the customer statement. Options and Peripherals 83 The change to an iSeries-generated fully electronic document enables the transformation from the traditional hardcopy output model to an e-business output model, or “e-Output.” Simply put, e-Output means the ability to create fully electronic pages of communications— such as statements, invoices, barcoded labels, reports—and deliver those pages to the required destination in the appropriate format. That could mean printing the pages and distributing in hardcopy format. It could also mean producing the pages in electronic format (i.e., AFP or PDF) and delivering them electronically via such methods as browser access, e-mail, fax, and archive systems. See the software sections for more on e-business output, particularly Infoprint Server for iSeries. Generally, iSeries printed output comes from three types of applications, each with different print data streams, or print languages: • Line-at-a-time mode printing in SCS (SNA Character Set) format • Page-mode printing in AFP (Advanced Function Printing) format • Line- or page-mode printing in ASCII formats (i.e., HP-PCL, Postscript, other printer-specific formats). AFP applications create sophisticated electronic output, generally print full pages instead of lines, and utilize external print resources (i.e., electronic forms, fonts, image, graphics, and bar codes). AFP is the standard, integrated page architecture of the iSeries. AFP is output-independent. For printing, AFP documents and reports are converted into a printer-specific data stream. This is normally the IPDS (Intelligent Printer Data Stream) format. IPDS is “intelligent” because it is a two-way printing process with full error recovery by page. IPDS printing is, in essence, a client/server application between the iSeries (specifically, Print Services Facility/400, or PSF/400) and the printer. Refer to Chapter 4 for more details on AFP and PSF/400. Other print data streams include PCL (using Host Print Transform, part of OS/400) or PDF (using Infoprint Server for iSeries—5722-IP1). Client, LAN, or network applications can create either line-mode or page-mode output, although most now tend to be full pages using either PCL, Adobe Postscript, or PDF print datastreams. The iSeries natively supports only AFP, SCS, IPDS, and line data formats. ASCII print formats are handled either through transparency (i.e., sent as is) 84 Exploring IBM ~ iSeries or through print transforms. The iSeries spooled files (or network spooled files sent via NetServer) can be transformed to iSeries format (AFP/IPDS) by using the Postscript, PDF, and PCL transforms that come with Infoprint Server for iSeries. Given this print application environment, the location of the printer becomes important. Traditionally, iSeries printers have been twinaxconnected directly to the system. The predominant connection today is network connection, enabling a printer to be shared across clients, applications, and systems. In addition, the standard network communication protocol has become TCP/IP. Attaching a printer using an IP (Internet Protocol) address provides flexibility. However, the standard TCP/IP support for printing (remote output queue on the iSeries side) is limited, in both document function and print management. In this environment, IPDS acts as a bridge to provide full application and print-management function. See the discussion on IPDS earlier in this section for additional details. Today’s printers break down into two technology categories, impact and nonimpact. Within each of those categories are many different subcategories. Impact printers include wire matrix technology and band matrix technology. Nonimpact printers include thermal, inkjet, and laser technologies. Figures 2.4 through 2.8 summarize the characteristics of the printers available to the iSeries. Combined-Function I/O Processor A Combined-Function I/O Processor (CFIOP) is provided with every iSeries system and fills the role of disk adapter for the disk unit(s) that comes as standard equipment (and for up to nineteen additional disk units). On the models i800, i810, i825, i870 and 890, a 32 MB version of the CFIOP is embedded on the backplane. The #5095 PCI Expansion Tower also has a 32 MB version of the CFIOP embedded on the backplane. The CFIOP replaces the multi-function IOP by combining the functions of a Converged Service Processor and the functions of an I/O controller into a single entity. The PCI base CFIOP supports up to four I/O Adapters (IOAs). The PCI embedded CFIOP and the #2842 PCI IOP have a storage capability and a performance capability of 100 and support the IOAs listed in Figure 2.9. The figure also lists the storage and performance requirements imposed by those IOAs. Similar rules apply to the IOPs and IOAs Options and Peripherals Type Technology Throughput: characters per sec (cps), lines per min (lpm), and pgs per min (ppm) Graphics resolution Paper handling Data stream support Interface Desktop/floor Figure 2.4. 85 IBM 4230 Matrix Printer IBM 4247 Matrix Printer IBM 6400 Line Matrix Printer Near letter quality 9-wire dot matrix Near letter quality 18-wire dot matrix Near letter quality Band matrix 375-600 cps 200-700 cps 1-10 ppm 4-14 ppm 500-2000 lpm 15-55 ppm 144 pels vertical x240 pels horiz. Continous forms to 13.2" IPDS/SCS/ASCII 144 x 144 pels 144 x 144 pels Continuous forms to 13.2" + cutsheet IPDS/SCS/ASCII Continuous forms Twinax, parallel or serial Twinax, Token Ring, Twinax, Token Ethernet, parallel Ring, Ethernet, or serial parallel or serial Desktop Floor Desktop IPDS/SCS/ASCII iSeries impact printer summary. assigned to Linux partitions. The IOA feature cards are renumbered, but the rules are the same for the particular cards. Figure 2.10 identifies the utilization of the PCI-based IOPs and systems and towers where those IOPs are used. Integrated xSeries Server The Integrated xSeries Server (previously called the Integrated PC Server—IPCS, or the Integrated Netfinity Server), along with supporting OS/400 software, provides a high-performance file server function for a local area network. That is, it enables personal computers (running Windows or DOS) to freely and efficiently access iSeries disk storage. The same file system can also be accessed by iSeries host application programs and can provide LAN communications to iSeries application programs using TCP/IP and APPN. Windows Network Neighborhood is used by xSeries users to connect to the iSeries servers. Team-Fly® PCL, Postscript Data streams available Figure 2.5. Footprint Interface Cut sheet Cut sheet Letter quality Laser 40 Infoprint 1140 Letter quality Laser 45 Infoprint 1145 IPDS, PCL, Postscript, PDF Ethernet, Token Ring, Parallel, USB, Twinax Desktop or Floor Cutsheet 1200 dpi IPDS, PCL, Postscript, PDF Ethernet, Token Ring, Parallel, USB, Twinax Desktop or Floor Cutsheet 1200 dpi AM FL Y IPDS, PCL, Postscript, PDF Ethernet, Token Ring, Parallel, USB, Twinax Desktop or Floor Cut sheet 1200 dpi TE Letter quality Laser 30 Infoprint 1130 iSeries nonimpact workgroup printer summary. IPDS, PCL, Postscript, PDF Ethernet, Ethernet, Parallel, USB Token Ring, Parallel, USB, Twinax Desktop Desktop 1200 dpi 1200 dpi Letter quality Letter quality Laser Laser 16 20, 25 Infoprint 1120, 1125 Type Technology Throughput in impressions per min (IPM) inches per second Graphics resolutions Paper handling Infoprint 1116 Desktop Ethernet, Twinax, Parallel 203 dpi 300 dpi Continuous forms IPDS, IGP, Code V Letter quality Thermal Laser 6-10 IBM 4400 Thermal 86 Exploring IBM ~ iSeries Options and Peripherals Type Technology Throughput in impressions per min (IPM) Graphics resolutions Paper handling Figure 2.6. Figure 2.7. Infoprint 2105 Infoprint 2000 Letter quality Laser 70 Letter quality Laser 85 Letter quality Laser 105 Letter quality Laser 110 600 dpi 600 dpi 600 dpi 600 dpi Cutsheet, with reproduction and finishing IPDS, PCL, PDF, Postscript Token Ring, Ethernet Cutsheet, with finishing IPDS, PCL, Postscript Ethernet, Parallel Floor Floor iSeries production cutsheet printer summary. Type Technology Throughput impressions per min (IPM) Graphics resolutions Paper handling Footprint Infoprint 2085 Cutsheet, with reproduction and finishing IPDS, PCL, PS IPDS, PCL, PDF, Postscript Token Ring, Token Ring, Ethernet, Serial Ethernet or Parallel Floor Floor Footprint Data stream available Interface Infoprint 70 Cutsheet, with finishing Data stream available Interface 87 Infoprint 62 Infoprint 3000 Infoprint 4000 Infoprint 4100 Letter quality Laser 62 Letter quality Laser 112-344 Letter quality Laser 150-1002 Letter quality Laser Up to 1522 240, 300 dpi 600 dpi Continuous forms IPDS Continuous forms IPDS 240, 300, 480, 600 dpi Continuous forms IPDS, Postscript Token Ring, Ethernet Floor Token Ring, Ethernet Floor Token Ring, Ethernet Floor 240, 300, 480, 600 dpi Continuous forms IPDS, Postscript Token Ring, Ethernet Floor iSeries production continuous forms printer summary. 88 Exploring IBM ~ iSeries Infoprint Color 1220 Type Letter quality Technology Color laser Throughput in 20 impressions per min (IPM) Graphics 2400 dpi resolutions Paper Cut sheet handling Data stream Postscript, available PCL, IPDS Interface Ethernet, Token Ring, Parallel, USB, Twinax Infoprint 4000 Hilite Color 1228 Infoprint Color Infoprint Color 100 Infoprint Color Plus Letter quality Color laser 28 Letter quality Color laser 150 to 944 Letter quality Color laser 105 Letter quality Color laser 138 2400 dpi 240, 300 dpi 600 dpi 600 dpi Cut sheet Continuous Continuous Continuous forms forms forms Postscript, IPDS Postscript Postscript, PCL, IPDS IPDS, PDF Ethernet, Attaches to Token Ring, Ethernet, Token Ring, production Ethernet Gigabit Parallel, USB, monochrome Ethernet, Twinax (i.e. Infoprint ESCON, 4000) FICON, FDDI Desktop/ Floor Floor Floor Floor Footprint Desktop/ Floor Figure 2.8. iSeries nonimpact color printer summary. The fastest area of expansion is the successful marriage of the iSeries and Windows NT/Windows 2000 on the Integrated xSeries Server. In this case, the user purchases Microsoft-certified Windows NT/Windows 2000 and service for the software package through a Microsoft reseller. Up to forty-eight separate Windows NT/Windows 2000 servers can exist on a single iSeries server 870. Each of the Windows NT/Windows 2000 servers is independent of the others, but they can share the iSeries disk, tape, and CD-ROM facilities. The operations that support the Windows NT/Windows 2000 environment use integrated iSeries operations and user administration. Windows NT/Windows 2000 messages can be sent to iSeries operators. The client storage space drive lettering matches the Windows NT/Windows 2000 drive numbering. Windows NT reliability is improved through the iSeries’s ability to mirror the NT event log to an iSeries message queue or job. During the Windows NT/Windows 2000 install process, it is possible to specify the type of Options and Peripherals Storage Requirement Performance Card in all systems Requirement Type IOA Disk Unit / Magnetic Media IOAs #2749 PCI Ultra Mag Media Controller #2763/#9763 PCI RAID Disk Unit Ctrlr #2765 PCI Fibre Channel Tape Ctrlr #2766 PCI Fibre Channel DASD Ctrlr Notes 25 29 36 dedicated IOP 22 25 21 50 dedicated IOP 25 A B E E 29 29 29 29 29 30 21 21 25 21 G G B A A 13 14 5, 8 5, 8 5, 8 2 25 35 26 36 36 H E E 25 2 25 35 35 35 25 36 26 12 47 47 47 36 A F A A A A A 1 3 3, 4, 8, 10, 12 3 1 15 15 15 15 25 25 22 11 2 15 14 14 14 14 7 7 7 18 26 14 C A D A 15 14 C #2768 PCI Magnetic Media Ctrlr #5702 PCI-X Ultra Tape Controller #5705 PCI-X Tape/DASD Controller #2757/#9757 PCI RAID Disk Unit Ctrlr #2782/#9782 PCI RAID Disk Unit Ctrlr #4748/#9748 PCI RAID Disk Unit Ctrlr #4778/#9778 PCI RAID Disk Unit Ctrlr #9767 PCI Disk Unit Controller LAN IOAs #2743/#2760 PCI Ethernet/IEEE 802.3 Adpt #2744 PCI 100/16/4 MB Token Ring Adpt #2817 PCI 155MBps MMF ATM #2849 PCI 100/10 Ethernet Adpt #5700/#5701 PCI Ethernet/IEEE 802.3 Adpt #4723 PCI Ethernet/IEEE 802.3 Adpt #4815 PCI 155MBps UTP OC3 ATM #4816 PCI 155MBps MMF ATM #4818 PCI 155MBps SMF OC3 ATM #4838 PCI 100/10MBps Ethernet IOA WAN IOAs #2742 PCI Two Line WAN IOA #2772/#2773 PCI Dual WAN/Modem IOA #2805/#2806 PCI Quad WAN/Modem IOA #4745 PCI Node WAN IOA #4750 PCI ISDN BRI U #4751 PCI ISDN BRI S/T #4761 Integrated Modem (8 port) #4801 PCI Crypto Coprocessor #4805 PCI Crypto Coprocessor #9771 Base PCI 2-Line WAN w/Modem #2793/# 2794/#9793/#9794 2-Line WAN w/Modem Figure 2.9. 89 5, 8 9 9 A B A A A PCI IOAs and plugging rules. (continued on next page) 3, 4, 8 3, 4, 8 3, 4, 8 3 7 7 7 6 6, 15 90 Exploring IBM ~ iSeries Workstation IOAs #4746 PCI Twinax Workstation IOA 10 Imbedded IOAs CCIN288E PCI 100/10 Ethernet IOA 25 6 A 36 n/a on 52M Notes: Card Types: A-PCI, 32 bit, 33MHz, Universal voltage, short (Universal means will work in either 3V or 5V slots) B-PCI, 32 bit, 33MHz, Universal voltage, long C-PCI, 32 bit, 66MHz, 3 Volt, short D-PCI, 32 bit, 66MHz, 3 Volt, long E-PCI, 64 bit, 66MHz, Universal voltage, short F-PCI, 64 bit, 133MHz, 3 Volt, short G-PCI, 64 bit, 133MHz, 3 Volt, long H-PCI, 64 bit, 66MHz, 3 Volt, short 1. #2743/#2760/#5700/#5701 has the following plugging rules: • must not be placed in a 5 Volt PCI card slot • must be placed in a 64 bit slot in CECs and I/O Towers • will be placed in 32 bit slots in 52L and 52Me CECs • must be limited to one per EADS address boundary. (This rule does not apply when under an Integrated Server). • may only be combined with a maximum of one other IOA 2. Cards must be plugged into slots based on their length and voltage level (3V, 5V, or Universal) as indicated in the Card Type column above and the backplane layouts below. 3. Mot more than two total LAN adapters allowed per IOP. 4. Not more than one ATM adapter allowed per IOP. 5. Not more than 3, total, of this group (indicated by the same number) per IOP. 6. #4801/#4805 are not allowed to be plugged under the Model 52L and 52Me CEC imbedded IOPs or the base IOP of the models 52M and 52H. 7. Not more than one total of this group per IOP. 8. Not more than one PCI RAID Controller is allowed per IOP when that IOP is also driving any ATM IOAs. 9. Maximum of 2 #2765/#2766s in any combination per EADS boundary. 270, 52L, 820, 52M #5095 #5075 830/840 #5074/#0578/ 52Me, CEC CEC tower tower# base I/O 5078/#0588/#5088/ enclosure #5079/5294/ #8079/#8094 Maximum 2 4 3 4 5 6 #2765/#2766s Preferred 64 bit slot placement, but not hard rule. Max 32 LUNS of disk units supported per #2766. 10. This feature is a 64-bit card, but is allowed to plug into any 32-bit or 64-bit card slot. 11. The #2766 requires a dedicated IOP. 12. A maximum of one #2757/9757 is allowed per IOP and are mutually exclusive with a PCI RAID controller on a given IOP. 13. A maximum of two #2782/9782 are allowed per IOP and is mutually exclusive with a PCI RAID controller on a given IOP. 14. A Maximum of two 4805s are allowed per IOP. 15. The #5705 PCI-X Tape/DASD Controller can attach 6 disk (non-RAID) devices and/or 1 tape device (800/810 only). 16. The #5702 PCI-X Ultra Tape Controller can attach 1 or 2 external tape drives. Figure 2.9 (continued). PCI IOAs and plugging rules. Options and Peripherals 91 IOP Storage Performance 800 Capability Capability 810 825 870 890 Note1 5094 5095 Imbedded 32 MB PCI Node IOP #2842 PCI Node IOP #2843/#9943 PCI Node IOP #2844/#9844 100 100 X X X X 52L52Me 1 1 100 100 2 211 100 4 4 4 211 100 5 5 5 2 52L52Me Notes: 1. A maximum of 2 #2844 features in the model 52L and 52Me CECs. A maximum of 3 #2844 features (and one #9844)in the model 52M CEC. A maximum of 4 #2844 features (and one #9844)in the model 52H CEC. A maximum of 6 #2844 features in the #5088/#0588 PCI Expansion Tower. 2. IOPs cannot be placed in consecutive slots. 3. A maximum of 4 IOAs may be placed under an IOP. 4. The #2844/#9844 must not be placed in a 5V slot. 5. PCI IXA/NetFinity features are considered an IOP. 6. All LAN features attaching to Integrated Netfinity Servers do not enter into storage and/or performance capability calculations for any other IOP. Figure 2.10. PCI IOPs capability and usage rules. Windows NT/Windows 2000 log entries to be sent to an iSeries message queue. The administrator can specify the drive sizes for the Windows NT/Windows 2000 operating system. The iSeries administrator can submit Windows NT/Windows 2000 commands directly to the Windows NT IXA from the iSeries with output returned to a job log, IFS, or spool file. The administrator need not switch back and forth between the two systems. Tape backup utilities written for Windows NT/Windows 2000 can back up data to the iSeries tape drive. The IXA usage as a file server for generating local area networks is expected to decrease in proportion to the volume of IXA-based networks used for supporting Windows NT/Windows 2000. The iSeries NetServer is preloaded as part of OS/400 at no additional charge, and OS/400 provides a single point of software maintenance. There is no NT server license, installation, configuration, or maintenance involved. NetServer uses the iSeries processor, disk, and LAN adapters, and user data is protected by iSeries RAID-5 and mirroring. NetServer is managed with iSeries Navigator, providing simple, 92 Exploring IBM ~ iSeries consistent graphical administration and operations. Users connect to NetServer via Windows Network Neighborhood using standard iSeries user profiles and security. With NetServer, users do not require iSeries Access to perform native file and print sharing for PC clients. Automatic translation from ASCII to EBCDIC and back is performed. The maximum number of Integrated xSeries Adapters that may be installed on the iSeries is sixty on an iSeries system 890, but if the system maximum number of LANs is less than four, the maximum number of Integrated xSeries Adapters is that lower number. The maximum is the aggregate number of all LANs. A two-port Integrated xSeries Adapter counts as two LANs against the system maximum. Each IXA is a personal computer built on an adapter that can be installed inside an iSeries system unit. It includes a microprocessor, main memory slots (affording up to 4 GB of main storage), and two or three communications adapter slots into which can be plugged either Ethernet or token-ring adapters. xSeries Server The xSeries server is a standalone unit containing up to sixteen of the xSeries server functions equivalent in performance to the #2790/#2890 server devices. These standalone units connect to the host processors through an HSL link to provide high-speed DASD support for the xSeries function. Figure 2.11 identifies the number of xSeries servers allowed on each iSeries model. The iSeries DASD support for the xSeries servers can be organized as a Storage Area Network (SAN) in an Independent Auxiliary Storage Pool (IASP). Figure 2.11. iSeries Model Number of xSeries servers 800 810 825 870 890 4 13 36 48 48 Integrated xSeries servers allowed by iSeries model. Options and Peripherals 93 Figure 2.12 identifies the characteristics of the available Integrated xSeries Servers. A display must be connected to the IXS to support Windows. The xSeries Server is hot pluggable on selected iSeries servers. It is possible to direct attach N-way xSeries servers to iSeries models 8XX and 270 while retaining iSeries storage consolidation and systems management. The direct attachment is accomplished through the high-speed link. Workstation Adapters To attach any local workstation to an iSeries computer system, the proper workstation adapter must be installed in the computer’s system unit or an expansion unit. (Note: Remote workstations are attached through communications lines, not through a workstation adapter.) The workstation adapter is a microprocessor-controlled intermediary between the workstation and the iSeries processor. The adapter receives keystrokes Processor Clock Rate (GHz) Mainstorage Max. (GB) Mainstorage Elements (MB) Memory Slots Max No. of LAN Features PCI Card Slots Pre-requisite 2790/2890 2791/2891 2792/2892 2799/2899 0.7 0.85 1.6 1.0 4.096 4.096 4.096 4096 128/256/1028 128/256/1028 512/1028 128/256/1028 4 3 3/2 V4R5 4 3 3 V4R5w/CUM 4 3 2 V5R2 4 3/2 3 V5R1 Notes: 1. #28XX features are supported only in the model 270 CEC, and in the 5075/5095 PCI Expansion Tower when it is attached to the model 270. 2. Supported LAN IOAs are the following: #2743 PCI 1 GPS Ethernet IOA. #2744 PCI 100 Mbps Token-Ring IOA. #2760 PCI 1 GPS Ethernet UTP IOA. #4838 PCI 100/10 Mbps Token-Ring IOA. 3. Native iSeries functions are not supported. 4. External Host LAN is not supported. 5. #2890/#2891/#2892/#2899 Require 3 PCI card slots when in an Expansion Tower. Figure 2.12. Integrated xSeries server characteristics. 94 Exploring IBM ~ iSeries from the workstation and, in combination with the IOP, formulates the screens and sends back formatted views of screens for display on the workstation terminal. Managing the workstation traffic (e.g., keystrokes) leaves the system processor in the iSeries server free to run user application programs. The result of this multiprocessor architecture, as was discussed in Chapter 1, is that the iSeries system is able to do more work in a given amount of time. Only twinax workstation controllers are supported on the iSeries systems. The twinaxial support provides for up to forty active local workstations (any mix of terminals and printers) daisy-chained over eight ports (up to seven workstations per port). For all iSeries twinaxial workstation connections, a twenty-foot cable is attached between the controller and an external box that provides the eight port connectors. This external box is designed to be mounted on the floor, wall, or tabletop. From 1 to 180 twinaxial workstation adapters can be installed in a single iSeries system for attaching those workstations. LAN-Connected Terminals Additional workstations may be attached to the LANs supported by these systems. These terminals must be intelligent terminals, including personal computers, network stations, or retail terminals. Each LAN can support up to 256 terminal addresses. Auxiliary Storage Options As was discussed in Chapter 1, there are four basic types of auxiliary storage devices used with iSeries servers. That storage can consist of both internal and external disk and tape units as well as internal and external optical storage devices. External disk and tape units are attached to the iSeries via the Fiber Channel adapter. Multiple devices may be attached using a single Fiber Channel adapter. See Figure 2.9 for a listing of adapters. • Disk units • Tapes Options and Peripherals • Optical libraries • CD-ROM. 95 Let us now look at the specific auxiliary storage options available for the iSeries servers. Disk Storage Overview Disk storage provides the nonvolatile (not erased when power is turned off) long-term storage for the programs and data used on a regular basis. It comprises the second level in the hierarchy of storage of iSeries systems (main storage is the first). The function of disk storage is to hold information that must be readily available to the computer system yet preserved when power is turned off. It is used to store the operating system, application programs, and data. Disk storage is provided by disk storage units (also called Direct Access Storage Devices, or DASD) that store information on the surface of one or more platters (metal disks shaped like a dinner plate). The platters spin at a very high constant speed while the built-in read/write head records or detects information on the platter’s surface. The arm that positions the read/write head is called the actuator. The read/write heads in disk units never actually touch the platter’s magnetic surface, but are positioned extremely close to that surface. All iSeries systems support many different disk unit configurations. Disk unit performance is very important to the overall performance of a computer system. Each disk unit attaches to the computer through control circuitry contained within the units of the system. This function might be provided by the Combined-Function Input Output Processor (CFIOP) provided with the iSeries systems or an optional disk adapter card that often is necessary to support disk storage beyond that provided as standard with the iSeries system. Figure 2.13 lists the various disk units used with iSeries systems. The following paragraphs describe the following disk storage expansion options for the iSeries: • Integrated hardware disk compression • Model 2105 Enterprise/Versatile Storage DataServer Exploring IBM ~ iSeries Size—GB SCSI Type 4308 4.19 Ultra-2 4314 4317 4318 4319 4323 4324 4326 4327 8.58 8.58 17.54 35.16 35.16 17.54 35.16 70.56 Ultra-2 Ultra-3 Ultra-3 Ultra-3 Ultra-3 Ultra-2 Ultra-4 Ultra-4 IOA 2757, 2782, 2763, 4748, 4778, 9757, 9763, 9767, 9778, 9782 " " " " " " " " AM FL Y Feature # RPM Mirror (1) RAID(2) 7.2K 1 A 7.2K 10K 10K 10K 15K 7.2K 15K 15K 2 2 3 4 4 3 4 5 B B C D D C D E Notes: (1) Disk Unit Features with the same “Number” in this column can be mirrored to each other. (2) Disk Unit Features with the same “Letter” in this column can be put into the same RAID array. Figure 2.13. • Disk unit table for V5R2 systems. TE 96 Disk adapters. The new RAID disk controllers and adapters no longer offer disk compression. The reasoning behind this change from offering disk compression IOPs and IOAs is that with the larger capacities of the disk drives and the significant performance gains provided by both the new drives and controllers/adapters, disk compression can only mitigate against those gains. Model 2105 Enterprise/Versatile Storage Server The TotalStorage Model 2105 Enterprise/Versatile Storage Server is a Storage Area Network (SAN) device designed for use in e-business, enterprise resource planning, business intelligence, service consolidation, high availability, and other mission-critical applications. Heterogeneous attachment is provided to all major server platforms including iSeries, AS/400, S390, Windows NT/Windows 2000, and many varieties of UNIX. The Enterprise Storage Server incorporates the capabilities of supporting a wide variety of Windows NT, iSeries, and UNIX servers and Novell Netware, and providing remote management through a secure intranet connection and the StorWatch Storage Specialist. Team-Fly® Options and Peripherals 97 The Model 2105 Enterprise Storage DataServer is intended as an enabler for server consolidation. The Model 2105 can be concurrently attached to up to sixteen separate systems, with its 11 TB of data space partitioned dynamically among those systems. The capacity and performance can be scaled to meet requirements from 400 GB to 11 TB through sixteen standard configurations. The Ultra SCSI differential interface allows data to be moved both to and from the 2105 at up to 40 MB/sec. The interface can also support Fast and Wide SCSI at a reduced performance of 20 MB/sec. The 2105 internally is fully redundant if fewer than eight different systems are interfacing to it, and can use both RAID-5 and mirroring to protect against a disk failure causing a loss of data. Internally there are cross connections to send operations to either of the redundant systems or SSA ports. Dynamic sparing is provided to allow the using systems to continue operating until a convenient maintenance period occurs. The storage space can be partitioned into logical volumes of various sizes that can be defined at installation time and are independent of the operating systems using the partitions. The partitioning scheme supports the concurrent attachment of heterogeneous platforms such as Hewlett-Packard, Sun, Compaq, and the IBM RS/6000, Integrated xSeries Adapters, or iSeries. Access to a partition may be shared among similar servers (e.g., NT to NT, AIX to AIX, etc.), providing a single database for multiple servers. In the case of data consolidation, the data integrity must be provided by the use of lock-management functions within the database manager or application. The systems administrator is provided with an RS/232 modem interface into the 2105, which allows dynamic repartitioning of the space among the systems attached, as needed. The data stored is not sharable between iSeries systems because the partitioning schemes supported are incompatible with the iSeries singlelevel store concepts. The 2105 device is slower than the internal disk units. One area of interest for iSeries is the large cache available (512 MB to 6 GB), which can make certain operations requiring fast read-access viable. Additional information on the Enterprise Storage Server and 7133 Serial Storage Subsystem can be found at http://www.storage.ibm.com. Disk Adapters Disk adapters provide the circuitry necessary to transfer information between any attached disk units and the iSeries main storage. These 98 Exploring IBM ~ iSeries disk adapters (also called Input/Output Processors, or IOPs) have their own computing power used to lessen the burden on the iSeries’ main processor(s) when it comes to moving information to and from disk units. Many of these adapters support RAID-5, compression, and multiple interfaces. Figure 2.14 identifies the maximum number of disk controllers allowed per system model. Figure 2.15 summarizes the characteristics of the available disk adapters on iSeries systems. A minimum of four drives of the same capacity are needed for a valid RAID-5 array, with a maximum of four arrays per controller. The new RAID disk controllers and adapters no longer offer disk compression. The reasoning behind this change from offering disk compression IOPs and IOAs is that with the larger capacities of the disk drives and the significant performance gains provided by both the new drives and controllers/adapters, disk compression can only mitigate against those gains. #2957 or #2782 Figure 2.14. Adapter # Model 800 Model 810 Model 825 Model 870 Model 890 4 16 42 144 5-144 Maximum number of disk controllers allowed per model. Systems supported 2748/4748 800 9748 2748/4748 810, 825, 870, 890 9748 Expansion Towers 9767 800, 810 2763 270, 820, 5075 2782 2757 800, 810, 825, 5095 800,810,825, 870, 890 Figure 2.15. OS/400 Version supports CDROM/TAPE other support V4R4 and later Yes maximum of eighteen drives, -maximum fifteen drives V4R4 and later V4R4 and later V5R2 V5R2 Yes maximum 6 drives Yes maximum 12 drives, Ultra-2 only maximum 12 drives maximum 18 drives Yes Yes Disk adapter characteristics for iSeries computers. Options and Peripherals 99 The 2782 PCI-X RAID I/O Adapter used on the Models i800, i810, and i825 and the 5095 I/O Tower only supports a minimum of 3 drives and a maximum of 12 drives in a RAID configuration. The 2757 PCI-X Ultra RAID Disk Controller has a 320 MBps SCSI bus bandwidth, and can drive up to 4 SCSI buses, while supporting a maximum PCI burst rate of 1,064 MBps. RAID arrays attached to this controller can have a minimum of 3 drives and a maximum of 18 drives. This controller also supports SCSI bus-tagged command queuing and array parity checking and data scrubbing, creating arrays that are more flexible than was available under any previous controller. The 2757 PCI-X Ultra RAID Disk Controller can be used on any V5R2-supported system unit. Tape Storage Computer systems are woven deeply into today’s businesses and usually become the core of day-to-day operations. The information stored on the computer is itself a valuable asset and must be protected like any other asset. Magnetic tape storage provides a cost-effective and efficient means of backing up the information on the disk units of computer systems. Magnetic tape storage is the third tier of hierarchical storage in an iSeries system and is used for long-term storage of information. In general, the frequency of access to information on tape storage is significantly reduced when compared to the access frequency for information stored on disk. A tape unit reads and writes information on the tape much as a cassette recorder records and plays music on audiocassette tapes, but the recording quality is much higher and the format employed is very different. In either case, the tape unit runs the tape across the read/write head, which is in contact with the tape surface. Electrical impulses in the read/write head are used to transfer information to and from the tape surface. Tape storage units are able to store very large amounts of data in a relatively small area. Data stored on a tape storage unit are somewhat immune from damage by external effects, but because the writing and reading methodology involves small magnetic fields, large magnetic fields in the vicinity of the tape storage will destroy the data. Tape storage is the slowest performing of the auxiliary storage methods, but with compression techniques holds the most data at the lowest cost. The following tables provide a summary of the internal and external tape units used with iSeries systems. The tape units are connected to 100 Exploring IBM ~ iSeries iSeries systems through control circuitry located on tape I/O processors. The 5702 PCI-X Ultra Tape Controller can attach either one or two external tape drives. The 5705 PCI-X Tape/DASD Controller can attach six disk drives and/or one tape drive, and can be used only on the Models i800 and i810. Figure 2.16 lists the internal tape units supported on iSeries computers. Figure 2.17 lists the internal tape formats supported with the capacity and performance to be expected from each. Figure 2.18 lists some external tape units commonly used with iSeries systems and provides some basic information about each. The table of contents on the Members Only Web site offers links to more detailed descriptions of the devices listed in the table. IBM TotalStorage Ultrascalable Tape Library #3584 The IBM TotalStorage Ultrascalable Tape Library #3584 is a tape library storage solution designed for the large, unattended storage requirements of mid-range systems as well as high-end network servers. Designed to optimize access to data and reliability, the 3584 library can contain IBM LTO Ultrium Tape Drives. These are compact storage devices designed to support the intensive read and write operations required by network servers. Tape Library 3584 supports the use of both the LTO Ultrium 2 tape drives and the LTO Ultrium 1 tape drives in the same library. The Ultrium 2 Tape drive has a native data transfer rate of 35 MB/second. Data rates for the library can aggregate to 18 TB/Hour (with 2:1 compression) for a fully configured 3584 library. Tape cartridge capacity is 200 GB native capacity (400 GB with 2:1 compression) The 3584 Tape Library can contain up to 496 TB (992 TB with compression) by using up to 72 Ultrium 2 tape drives in up to six 3584 library frames. Other features of the Ultrium 2 Tape Drives include: speed matching to the host data rate, power management to either totally off or low-power modes, and Channel Calibration to allow for customization of each read/write data channel for optimum performance. It is possible to write multiple filemarks separately into a separate data set. The cartridge is compatible with the Ultrium 1 cartridge, but with improved transfer rates. Data Access times, Rewind, and Load times are faster (respectively 46 seconds, 80 seconds, and 10 seconds). The Model L32 base frame has 141 to 281 cartridge slots and supports up to 12 tape drives. Up to twelve logical libraries and/or up to Options and Peripherals 4482/4582 4483/4583 4486/4586 Capacity Native Capacity Compression Bytes SCSI Type Data Rate Native Data Rate Compression 4 GB 16 GB 25 GB 8 GB (1500') 32 GB (1500') 50 GB (1500') 1 2 2 Fast Fast Fast 380 KB/s 1.5 MB/s 2.0 MB/s 760 KB/s 3.0 MB/s 4.0 MB/s Figure 2.16. Media Type SLR100-50 GB SLR100-5 GB SLR 60-30 GB MLR3-25 GB MLR1-16 GB MLR1-2 GB SLR5-4 GB DC9250 DC9120 DC6525 DC6150 101 Internal tape unit supported on iSeries systems. Media Capacity and Data Rate 50 GB 5.0 MB/s 50 GB 5.0 MB/s 30 GB 4.0 MB/s 25 GB 2.0 MB/s 16 GB 1.5 MB/s 2 GB 1.5 MB/s 4 GB .36 MB/s 2.5 GB .3 MB/s 1.2 GB .3 MB/s 525 MB .2 MB/s 120 MB .12 MB/s Feature Code FJELD-3 4 GB (.4 MB/s) SLR60 30 GB (4 MB/s) MLR1-S FJORD-2 16 GB 25 GB (1.5 MB/s) (2 MB/s) SLR100 50 GB (5MB/s) NO NO NO NO R/W NO NO NO NO R/W NO R/W NO NO R/W NO R/W NO R/W R/W NO R/W R/W R/W R NO R/W R/W R/W R R/W R R R R R/W R R R NO R/W NO NO NO NO R/W NO NO NO NO R/W NO NO NO NO 4482/ 4484/ 4483/ 4486/ 4487/ 4582/4682 4584/4684 4583/4683 4586/4686 4587/4687 R=Read Capability W=Write Capability R/W=Read and Write Capability NO= No read or write capability Figure 2.17. Internal tape formats supported on iSeries systems. 102 Exploring IBM ~ iSeries Model 810 Tape Subsystem Group A 8mm Cart 7208 External (2) 8 mm Library - 9427 1/2-Inch Reel - 2440 - 9348 System Maximum for Group A Tape Subsystem Group B 1/2-Inch Reel - 9437 System Maximum for Group B Tape Subsystem Group C 1/2-Inch Cart - 3570, 358XHXX/LXX/DXX, 3590(1), 3480, 3490, 3490E-AXX, BXX, C10, DXX, 3490E others, 3575 (3) 1/2-Inch Reel - 3422/3430 1/4-Inch Cart. - 7207-122 System Maximum for Group C Tape Subsystem Group D 1/4-Inch Cart - 5032 System Max/LPAR Max Model 825 Model 870 Model 800 Model 890 10 18 0 18 18 18 18 0 18 18 26 48 48 48 48 4 15 0 15 15 26 48 48 48 48 0 0 0 0 0 0 0 0 0 0 18 18 26 15 26 0 0 0 0 48 18 0 18 18 18 0 18 18 48 0 48 48 15 15 15 48 0 48 48 0 18 0 18 0 48 0 15 0 48 Notes: (1) 3490E CXA, F1A and 3590 B1A can be placed into a 3494 Library. The CXA, F1A, and B1A are counted toward the tape subsystem maximums while the 3494 library is not. (2) For each 7208-002, 012, 222, 232, 234, and 342, count the number of #0021s tied to these units as the number of 7208 tape drives. (3) 3570-XXX can be placed into a 3570 library. The 3570-XXX is counted toward the tape subsystem maximum while the 3575 library is not. Figure 2.18. External tape units maximum/system. twelve SCSI control paths can be configured for each frame. Each Model L32 library has a standard ten-slot cartridge input/output station for importing or exporting cartridges from the library without requiring a re-inventory. For bulk loading of tape cartridges the library door can be opened. Each time the library door is closed a bar code reader scans the cartridge labels enabling a re-inventory of the cartridges in less than sixty seconds. Options and Peripherals 103 The Model D32 frame supports up to 440 storage slots and up to 12 tape drives. There is an incremental reduction of storage slots for each set of four tape drives added. A fully configured 3584 tape library, with one L32 frame and five D32 frames will support up to 72 tape drives or up to 2841 storage slots. Each frame can have up to twelve logical libraries or twelve control paths. The heterogeneous sharing provided by the multi-path feature of the 3584 Tape Library provides a sharing of the library robotics. This is accomplished by partitioning the library into as many as seventy-two logical libraries (up to the number of tape drives installed), and providing each logical library its own separate and distinct drive(s), storage slots, and control paths. The I/O slots are shared on a first come first served basis. The cartridges under library control are not shared and can not be moved between logical libraries. Auxiliary Storage Controllers Tape adapters provide the circuitry necessary to transfer information between any attached tape units and the iSeries main storage. These tape adapters (also called Input/Output Processors, or IOPs) have their own computing power used to lessen the burden on the iSeries main processor(s) when it comes to moving information to and from tape units. The #2749 PCI Ultra Magnetic Media Controller provides Ultra SCSI attachment capability for an external tape device or an external optical device. The #2768 provides an Ultra SCSI attachment capability for an external tape or external CD-ROM device requiring a singleended SCSI interface. Optical Storage Overview For large volumes of information that is not needed frequently but must be immediately available when it is needed, optical disk storage should be considered. Unlike magnetic disks, which record information with magnetic fields, optical disks use plastic disks coated with a thin reflective alloy material and housed in a cartridge case. Information is stored on the plastic disk either by burning holes into the reflective surface with a laser beam (ablative) or by using the laser to heat the reflective 104 Exploring IBM ~ iSeries alloy layer to a liquid state and then changing its reflective properties by means of a magnet (magneto-optic). This type of storage provides for extremely high data recording densities, which makes for relatively inexpensive storage. However, today’s optical disk technology is slower than magnetic disk storage. Optical libraries are devices that consist of arrays of optical disks associated with one or more optical disk read/write units. In some cases, the optical disk read/write units also have one or more conventional magnetic disk storage units associated with them to improve the write performance of the library system. The optical disks used may employ CD-ROM, WORM, or WMRM technologies. DVD-RXM is a higher capacity format for CD-type device disks. When the last three letters are ROM, the disk can be written once. When the last three letters are RAM, the disk can be written more than once. The DVD format is the same format that is used for writing movies on CD. Capacities of greater than 5 GB can be achieved. The #3995 Optical Library The #3995 Optical Library family of products can be used to store large volumes of information using optical storage technology. These devices are in a self-contained box that rests on the floor near the computer system. There are five models of the #3995 that can be directly attached to an iSeries system to provide storage capacity ranging from 104 to 1,342 GB (unformatted capacity). There are also #3995 models that attach directly to LANs and can be used with iSeries systems in a LAN environment. Figure 2.19 lists the internal CD-ROM, DVD-ROM, and DVD-RAM units which may be used with iSeries models. Figure 2.20 lists the external direct-attached optical libraries, identifying the allowed maximums/system. Each optical disk cartridge used in a #3995 library can hold from 650 million to 5,200 million bytes of information depending on the cartridge type. Magneto-optic WMRM and both ablative and continuous composite WORM recording technologies are supported in a single optical library. The #3995 attaches to an iSeries system through the Removable Media Device Attachment feature (#2621) or the PCI Magnetic Media Controller (#2729). Options and Peripherals 105 Feature Code Device Type IOA Media 4425/4525/4625 CD-ROM Read only - CD-ROM/CD-R 640 MB 4430/4530/4630 DVD-RAM 2748, 2757, 2763, 2782, 4748, 4778, 9757, 9767, 9778 2748, 2757, 2763, 2782, 4748, 4778, 9757, 9767, 9778 4531/4631 DVD-ROM Figure 2.19. Internal CD-ROM, DVD-ROM, DVD-RAM units. Optical libraries #3995 - All Models Figure 2.20. 2748, 2757, 2763, 2782, 4748, 4778, 9757, 9767, 9778 Read - CD-ROM/CD-R 640 MB Read DVD-ROM Read - DVD-RAM 2.6/4.7/5.2/9.4 GB Write - DVD-RAM 2.6/4.7/5.2/9.4 GB Read only - CD-ROM/CD-R 640 MB DVD-R DVD-ROM 4.7/8.5/9.4 GB DVD-RAM 2.6/4.7 GB Model 800 Model 810 Model 825 Model 870 Model 890 15 18 18 26 26 Maximum external optical libraries allowed per system model. DVD/CD-ROM CD-ROM drives are auxiliary storage devices that store and read information on the surface of an optical disk using laser light. This technique allows a large amount of data to be stored in a small physical space. Performance of the CD-ROM devices is faster than 4 mm and 8 mm tape storage but slower than disk storage or 1/4-inch and half-inch tape storage. In addition, the data is less subject to damage due to outside influences such as magnetic fields and temperature extremes than is data stored on these other devices. 106 Exploring IBM ~ iSeries AM FL Y A CD device is included in all iSeries models. The CD device is used for distribution of OS/400 and other licensed program products. It can also be used as an alternate IPL (Initial Program Load) device. It attaches to the Combined-Function I/O Processor (CFIOP) provided with every iSeries system. CD-ROMs are also used for the distribution of software by many independent software vendors and for use by application programs directly through the HFS API (which is a native OS/400 application programming interface). Communications Options TE With the emergence of the Internet and the intranets driven by local area networks, businesses are placing increasing emphasis on computer communications. The full range of communications options is supported by iSeries servers. Connections to the Internet are established using Wide Area Network (WAN) protocols and controllers/adapters with modem connections to the pervasive telephone network and finally to an Internet service provider. Wide area networks are also used to connect computers together for different branches of the same business corporate entity. (One example is that IBM, like many other companies, has divisions located in many states that are connected together by WANs.) WAN controllers also serve the function of connecting remote workstations, and the adapters connect the system console in some user-defined system configurations. Intranet connections are established using LAN protocols and controllers/adapters to an appropriately wired network of personal computers or network computers and specially adapted network stations such as shared network printers. An intranet is a name for a LANconnected system grouping that has, in addition, an external connection to the Internet. Not all LANs are intranets. The number of communications lines and LANs supported by the iSeries eServer is identified in the system specifics for each particular model. The following paragraphs are a communications tutorial. Though this chapter does not provide a total list of all available communication options, it does discuss representative options that fit the most common business needs. (in Chapters 4 and 5, you will learn more about the communications software structures supported on the iSeries family). Since configuration limitations govern which and how communications Team-Fly® Options and Peripherals 107 options can be used together in a single system, before configuring your system you should be sure to seek the assistance of IBM or an authorized dealer. Figure 2.9 (on pages 89 and 90) summarizes the communications adapters available. Local Area Networks A Local Area Network (LAN) consists of a group of computers connected to a high-speed communications system that spans a confined region (i.e., a single building or campus). Computers of all sizes (personal computers to mainframes) can participate in a single LAN. The computers participating in a LAN can exchange information (programs and data) and share resources (for instance, disk storage and printers). The iSeries systems can fully participate in several types of LANs including Ethernet, token-ring, FDDI, and wireless. In fact, a single iSeries system can participate in several different LANs at the same time (see Figure 2.21 for system maximums). The iSeries server models have been optimized to offer (or “serve”) resources to other computers in a LAN environment. There is also an Integrated xSeries Server (IXS) that makes the iSeries an efficient server in a PC LAN environment. Ethernet Probably the most popular local area network is the Ethernet LAN (IEEE 802.3). Ethernet adapters are available at 10, 100, and 1000 MBps data rates. With Ethernet, each computer is attached as a tap-off of a common cable or bus. For this reason, Ethernet is called a bus-wired network. Thus, an Ethernet LAN is a party line on which all computers can transmit a message for all other computers to hear. Every computer has equal access to the cable and can send a message at any time with- Maximum LANs Maximum Integrated Netfinity Servers Model 800 Model 810 Model 825 Model 870 Model 890 12 4 36 13 96 36 128 48 128 48 Figure 2.21. Maximum number of LAN adapers/Netfinity servers per system. 108 Exploring IBM ~ iSeries out warning. To ensure that only one computer transmits at a time, there is a protocol called Carrier Sense Multiple Access–Collision Detect (CSMA-CD) that each connection or node follows to transmit a message. This is the same protocol used in telephone conversations where, for instance, only one person can speak at a time or neither is clearly understood. One party waits for the other to finish before beginning to speak. Thus, the phone line only carries one party’s voice at a time, and the message is clear. This is the “CSMA” part of CSMA-CD. The “CD” part of the protocol handles the times when two nodes start transmission simultaneously. To understand this part of the protocol, think of what happens during a telephone conversation when two people begin talking at the same time. Typically, both stop talking and begin again a few moments later, hoping that this time one begins sooner than the other. This is equivalent to what CSMA-CD does. If two (or more) nodes begin transmitting at the same time, the messages “collide” on the network. Each communicating node monitors for such a collision, and when one is detected all nodes stop transmitting and begin again after a pause of random length. Usually, one node will begin its retransmission before the other(s), thus gaining control of the network. Ethernet adapters are available with a PCI bus interface. Token-Ring Local Area Networks The token ring is an IBM-developed local area network able to move information at speeds of either 4, 16, or 100 MBps, depending on the version. The participating computers (called nodes) are connected through a ring-shaped wiring scheme depicted in Figure 2.22. In addition to the token-ring methodology described, a faster, more flexible technology of token ring-based LAN communications, called ATM (Asynchronous Transfer Mode), exists. The protocol used by the token-ring local area network is called the token-passing protocol. With this protocol, packets of information are passed around the ring from node to node in a continuous circle. These packets are called message frames (see Figure 2.23). A unique frame (called a token frame) controls access to the ring. When a node receives a frame, the node checks to see if it is a message or a token frame. If it is a message frame, the node examines the destination address to see if the message is intended for that node. If the message is not intended for that node, the message frame is passed on unchanged to the next node in the ring. If the frame received by a node is a token frame, the node knows Options and Peripherals 109 Personal Computer System/390 Message frame System/36 AS/400 Personal Computer Token Frame Control info Figure 2.22. Destination Source address address Message Trailer symbol Token symbol Trailer symbol The basic structure of a token-ring network. that the network is idle and that it may send a message frame if it has information to transfer. After it sends a message frame, the node then sends a token frame to indicate that the ring is again inactive and ready to carry information. All iSeries systems can participate in a token-ring network if an appropriate token-ring network adapter is added. Asynchronous Transfer Mode Asynchronous Transfer Mode (ATM) brings 155 MBps performance to local area networks. IBM is dropping support for ATM after V5R2. 110 Exploring IBM ~ iSeries Personal Computer System/390 Message frame System/36 AS/400 Personal Computer Token Frame Control info Figure 2.23. Destination Source address address Message Trailer symbol Token symbol Trailer symbol Token passing protocol used on IBM token-ring networks. Wide Area Networks A Wide Area Network (WAN) is a group of computers connected to a communications system. It is called a “wide area” network to indicate that the computers participating in the network need not be geographically confined to a particular building or campus (as is the case with a LAN). WANs can provide a connection between two computers located Options and Peripherals 111 across town from one another or among hundreds of computers across global distances. To participate in a WAN, the iSeries system must have the proper programming (which is included in the OS/400 operating system) and be equipped with the proper electrical interface. The term interface refers collectively to the connector, electrical voltage levels, connector pin functions, and so on, that are provided for the physical attachment to a communications line. Just as there are different rules of grammar and punctuation in English, French, and other languages, there are different rules for various types of computer communications. In computer communications, a set of rules is called a communications protocol. The protocols of most interest for our purposes are Async, Bisync, SDLC, X.25, IDLC, and Frame Relay. Each of these different protocols is supported by OS/400 and has the same basic goal of moving information from one place to another efficiently and reliably. And each has advantages and disadvantages. The one you use will depend on your requirements in the areas of transmission speed, cost, and compatibility with the other devices in the network. At all times, however, each device using a given communications line must be using the same protocol. Some popular electrical interfaces used with WANs are RS-232, V.24, V.35, V.36, X.21, and ISDN interfaces. Although it is not necessary to understand exactly what these cryptic names mean, it is important to understand that there are different types of interfaces necessary to support different types of WANs. A separate adapter card working with a communications controller card may provide the interface, or it may be built onto the same card with the communications controller circuitry. Modems A modem converts computer information into communications signals and transmits them over telephone lines (i.e., it modulates the computer information). A modem at the receiving end then converts the telephone line signals back into computer information (i.e., it demodulates the telephone line signal). The term modem, then, derives from the terms modulate and demodulate. In performing this action, the modem changes the computer digital signals to voice or analog signals to pass over pub- 112 Exploring IBM ~ iSeries lic switch networks. Computers need modems because telephone lines were originally designed to carry electronically encoded voice messages from one point to another. The telephone converts the speaker’s voice into electronic signals suitable for phone line transmission. Although the information in a computer is already electronically encoded, it is not in a form that can be transmitted over standard phone lines. For this reason, a device is needed to convert the electronically encoded computer information into electronic signals suitable for telephone line transmission. A modem can be thought of as a telephone for a computer. Just as both parties need their own telephones to hold a conversation, both computers must have their own modems to transfer information over the phone lines. Modems are often used in the construction of wide area networks. Power and Packaging Options The following paragraphs list the power and packaging features for the various iSeries systems and identify which of the systems accept the particular feature and the function performed by the feature on that particular system. UPS for Models 270 and 820 An Uninterruptible Power Supply (UPS) significantly improves system uptime by minimizing the impact from power fluctuations and outages. The models 270 and 820 support an external UPS (#9910). UPSs are available in three capacities—1,000 VA, 3.0 KVA, and 6.0 KVA. The UPS offers continuous no-break power, a keypad and digital display with fifteen programmable operation functions and alarm set points, and brownout boost to save battery run time. The 3.0 KVA and 6.0 KVA units can be expanded with a 3.0 KVA add-on. Additional external battery and battery enclosure are available for these units for the users who require additional shutdown time. External UPS units are recommended for the models 830, 840, and 890. IBM does not specify or recommend a vendor for these units. Options and Peripherals Feature # Function-base, other Interface 5094 PCI Expansion Tower HSL 5088 5095 PCI Expansion Unit PCI Expansion Tower, redundant power option Figure 2.24. HSL HSL, SPCN Models 800, 810, 825, 870, 890 800, 810, 825, 870, 890 113 Internal IOAs Internal media supported disks devices 14 45 14 7 12 2 Packaging options for iSeries systems. Packaging Expansion Features The packaging expansion options are shown in Figure 2.24. The table identifies the models with which the expansion feature is applicable, the expansion functions supported, and redundancy options available. iSeries Rack-Mount Capabilities The iSeries rack-mounting options are designed for industry standard EIA mounting. These offerings provide solutions for Applications Service Providers (ASPs), large users, multiples, etc., who wish to reduce the floor space consumed by the system footprint. Cryptographic Processors Cryptographic processors help improve the security of an iSeries system by encoding information using cryptographic techniques (ANSI Data Encryption Standard [DES]). That is, iSeries-resident information can be scrambled via encryption keys, making it meaningless to anyone except those who have the key. This capability is particularly beneficial where valuable iSeries information might be exposed to unauthorized access via a communications network like the Internet. Data encryption is required to support many financial institutions, to support e-business transactions on the Internet, and to securely ex- 114 Exploring IBM ~ iSeries change data on a worldwide basis. A maximum of three cryptographic functions are supported on any single system. The #4754 Security Interface Unit (SIU) is an optional device that attaches to the cryptographic processor and allows the user to enter cryptography keys by sliding a personal security card through a reader. iSeries Software 115 3 iSeries Software T he previous chapters closely examined the system hardware optional equipment of the iSeries systems. This chapter begins the discussion of how that hardware is put to work—namely, the all-important software. It is the software that harnesses the iSeries systems’ computational power and allows you to perform many diverse and useful tasks. The chapter begins by introducing you to the software structure used by the iSeries and continues with a discussion of the kinds of software used to actually perform useful work. Then, iSeries’ compatibility with software written for System/3X computers is covered. Software Architecture Overview The model of software that constitutes the programs that execute on the iSeries systems is divided into three segments—application programs, operating system programs, and SLIC programs. Figure 3.1 illustrates the layered-structure relationship of the three segments. The arrows at the top of the figure illustrate the user’s view of iSeries servers. That is, the user sees mostly the application programs that are being executed, with barely a glimpse at the operating system functioning behind the 115 Exploring IBM ~ iSeries User's View of System Application Program Operating System Main Storage SLIC System Hardware AM FL Y Hardware Figure 3.1. Conceptual software model of the iSeries system’s basic software structure. The three layers of the software model work together (and with the hardware) to perform useful work for the user. TE 116 scenes. (What the user perceives is governed by the methodology provided by the operating system.) Application programs (the shaded area in Figure 3.2) constitute the work that is desired to be performed on the computer. These range from a relatively straightforward function such as payroll (an individual’s hours worked are multiplied by a pay rate, appropriate taxes are subtracted and retained, and finally a check is printed out for the individual) to what may be very complicated e-business applications (which allow a user to conduct business over the Internet). The operating systems layer in our model is shown shaded in Figure 3.3 directly below the application programming layer. The operating systems layer interfaces directly to the application programs and performs tasks for the application under control of the application. Application programs rely on the operating system to perform many of the detailed housekeeping tasks associated with the internal workings of the computer. The operating system provides the environment in which applications execute. Operating systems accept commands directly from the user to do such things as copy files and change passwords. The Team-Fly® iSeries Software 117 User's View of System Application Program Operating System Main Storage SLIC Hardware System Hardware Figure 3.2. The application program software layer of the model. The application program defines the particular tasks the computer is performing for the user. User's View of System Application Program Operating System Main Storage SLIC Hardware System Hardware Figure 3.3. The operating system software layer of the model. The operating system provides the environment in which the application program(s) run. 118 Exploring IBM ~ iSeries operating system must also manage the system variables used for tailoring the major types of objects supported by the system, such as programs, files, and communication protocols, and provides national language support. Operating systems are discussed in greater detail in Chapter 4, which is devoted to the topic. The integrated nature and the rich set of functions of the iSeries operating system (OS/400) are among the things that make the iSeries systems different from other midrange computers. The third and final layer of software in the software model (the shaded area in Figure 3.4) is called the System-Licensed Internal Code (SLIC) layer. SLIC is a set of extremely simple instructions (never seen by the computer programmer or user) that are directly performed by the electronic circuits within the system processor. All user program instructions are automatically converted into a series of these SLIC instructions, which are then executed by the system processor. SLIC in many ways is considered as part of the hardware because it instructs the hardware directly what to do for the software. Unlike application programs or operating systems, users never interact with the SLIC layer. It exists only to help application programs and the operating system per- User's View of System Application Program Operating System Main Storage SLIC Hardware System Hardware Figure 3.4. The SLIC software layer of the model. SLIC directly controls the hardware elements of the application systems and shields application programs and the operating system from hardware details. iSeries Software 119 form their tasks. SLIC instructions help hide the hardware specifics from the application programs, making application program compatibility possible across a wide range of hardware. SLIC and some of its interfaces to the hardware and operating system are part of the Technology Independent Machine Interface, which has enabled the iSeries systems to continuously improve the hardware and operating system while maintaining compatibility with application programs. It is the particularly rich SLIC layer in an iSeries system that helps set its architecture apart from those of more conventional computers. The built-in database, single-level storage, object-oriented architecture, and other iSeries features described in “Hardware Architecture Overview” in Chapter 1 are all designed into the SLIC layer of iSeries, making them part of the machine itself. This results in highly efficient, consistent, and easy-touse implementations of these functions. Because there are more SLIC instructions than can fit in the Instruction Cache (I-cache), some must reside in the slower main storage area. All SLIC instructions in the I-cache will execute in one I-cache cycle time (the time it takes the I-cache to respond to the system processor’s request for the SLIC instruction). Because all actions of the system processor are dictated by SLIC instructions, the system processor runs in lockstep with the I-cache cycles. When the needed SLIC instructions are in the slower main storage, the system processor is delayed, reducing the overall system performance. A larger I-cache area provided in the iSeries computers holds more of the SLIC instructions, thus contributing to higher system performance. How the Software Layers Are Different One of the basic differences between iSeries and traditional computer systems can be seen by examining the software layers. Figure 3.5 shows the three software layers of our model (application, operating system, and SLIC) in a little more detail. The figure shows the traditional software layers side by side with those of the iSeries. The first thing to notice is the difference between where the various software functions reside in the layers. In the traditional system, functions such as security, database, and communications reside in the operating system layer (which is usually made up of a collection of separately purchased operating system products). With this traditional approach, each operating system product must be installed and maintained separately. This is why 120 Exploring IBM ~ iSeries Traditional Systems Application Programs Application Programs Base OS functions Single Security product operating Communication product system Database product components Other OS products Lowest level available to programmers Microcode Machine instructions and hardware Processor, memory, etc. iSeries System Application Programs Single operating system SLIC and hardware Application program interface (API) Application Programs Base OS functions Communications database security (integrated) Machine instructions Processor, memory, etc. IOPs Lowest level available to programmers MI (machine interface) I/O file system Novell UNIX NT Notes Workflow Figure 3.5. The iSeries software architecture differs from that of more traditional systems. Implementing more function in the SLIC layer and providing a one-piece operating system results in improved efficiency, consistency, and simplicity. a highly skilled individual called a systems programmer is needed to support this kind of system. With the iSeries approach, much of the basic database, security, and other functions are built into the SLIC layer. Because SLIC implementations are in general more efficient (by nature of their “closeness” to the hardware), overall system performance is improved. The operating system for the iSeries (OS/400) provides all of its functions in a single product. This eliminates the need for the operator to install, tailor, and manage the multiple operating system components in traditional operating systems and to make sure that each works with the others as new versions are shipped at different times. The price you pay for this simplicity is that you get all OS/400 functions whether you need them or not, whereas the user of traditional systems can select only the traditional operating iSeries Software 121 system components needed at a given time. (Of course, in traditional operating systems, the user is responsible for ensuring that the selected components work properly together.) Another basic difference lies in the way a programmer properly “sees” the systems. With the traditional system, system function such as database management or security resides in the operating system and therefore can be modified by a systems programmer. This gives the systems programmer more flexibility in customizing the computer system at the expense of more complexity. In a traditional operating system environment, the database functions are not part of the operating system but are purchased as a separate component, such as DB2, Oracle, Sybase, or Informix. With the iSeries, ease of use and efficiency are gained at the price of some flexibility. For example, because the database functions are built into the SLIC instructions, they cannot be modified. If programmers want to change how the database is managed, there are some things they simply cannot do. Thus, there’s a choice with other systems that is not available in OS/400. Will AS/400 and S/3X Programs Work? Before the introduction of the iSeries servers, the AS/400 and the preceding System/3X computer families were the most widely used business computing systems in the world. As a result, a wide variety of application programs had been developed for those computers. The flexibility afforded by virtue of this large and diverse software base allowed these earlier families to fill many different needs. Of course, this tremendous choice of available programs did not exist when these earlier computers were first announced. It took the independent efforts of many people over many years to develop the large software base that exists today for AS/400 and System/3X. To capitalize on that software base, software compatibility was a primary objective in the design of iSeries computers. That is, most programs written for the AS/400 or System/3X family can easily be migrated to iSeries computers. It is important to understand that of the three software layers in our software model, compatibility with programs in the application program layer is the most important. Why? First, application programs typically represent the largest share of a user’s investment. Being forced to abandon an application program because of incompatibilities may also make a user throw away the data and training or experience accu- 122 Exploring IBM ~ iSeries mulated with the application program—which can be substantial. Some users have developed custom application programs at considerable cost in development time and money. Incompatibility at the application program level would render these programs virtually useless. Also, and perhaps most important, application layer compatibility allows iSeries users access to the thousands of application programs that have been developed for AS/400 and System/3X computers. What about the operating system and SLIC layers? Maintaining compatibility with earlier AS/400 or System/3X operating systems software is not as important for several reasons. Operating systems typically represent only a small fraction of a user’s software investment. Further, a new operating system is usually necessary to allow users access to the new features of the computer system not considered by the programmers of the old operating system. Of course, the user is automatically supplied with a new SLIC layer that fully supports the hardware with every iSeries system. Inside Application Compatibility To understand iSeries application compatibility, you must understand something about how software is typically written. First, a programmer writes a program’s instructions (code) using a programming language (e.g., COBOL or RPG), which is basically a library of computer instructions from which a programmer may choose to write programs. The list of programming language instructions is called source code. For a program to be run on a computer, the source code instructions must be converted into instructions a computer can understand. This conversion process is called compiling the program. When source code is compiled, the result, called object code, can be directly executed by the computer hardware. In addition to programming languages, the programmer can use predefined lists of operating system commands to do things like start programs and present menus. These predefined lists are called procedures. With this background, let us look at how the iSeries provides compatibility with System/3X programs. Programs written for System/38 computers, in general, are object code compatible with iSeries systems. That is, you can take the object code for a program written for a System/38, load it onto an iSeries system, and run the program. This is possible because of the System/38 environment, which makes the iSeries system look like a System/38 to iSeries Software 123 the application program. Furthermore, most of the operating system commands used on the System/38 are the same as those used on the iSeries. For this reason, System/38 procedures will also run with little or no change. SLIC has an emulation that looks at every instruction from the S/36— operating system, utilities, compilers, and applications—and executes the correct sequence of iSeries instructions. Application Programs The software architecture overview described how three basic software layers in an iSeries server cooperate to perform useful work for a user. A layered model was used to illustrate the software architecture. This section concentrates on the top layer of the model—application programs. It is the application programs that “apply” the iSeries server’s computational power to a particular business task. Some businesses use application programs designed, written, and sold by other companies. These are called prewritten application programs. Compatible programs include those written by IBM, by IBM Business Partners, and by general software vendors. Some prewritten application programs are discussed, but by no means does this chapter provide a complete consumers’ guide to all prewritten software for the iSeries. Comprehensive coverage of the many business application program products available today would fill many books, which would be obsolete by the time they were published. Instead, the discussions that follow will help you make more informed purchasing decisions; they give examples of the kinds of things available from prewritten application programs. Many businesses choose to design and write their own custom application programs or use a combination of prewritten and custom application programs. In the last part of the chapter, we briefly look at custom software alternatives. Can Prewritten Programs Fit the Bill? Today’s prewritten application programs range from simple programs that concentrate on a very specific task to powerful and very complex groups of programs designed to work together. They perform many 124 Exploring IBM ~ iSeries functions as diverse as the environments in which computers are found today. Many prewritten application programs are useful in most business environments (for example, word processing and accounting). These are known as cross-industry application programs because they are not specific to any particular industry segment. Other prewritten applications address the specialized needs of a particular industry (e.g., manufacturing or utilities). These are called industry-specific application programs. As a rule, the application programs written by IBM fit into a cross-industry category as opposed to an industry-specific category. Cross-Industry Application Programs Let’s take a quick look at some examples of cross-industry application programs for iSeries systems. Data Warehousing Data warehousing consists of a set of hardware and software components that analyze the massive amounts of data that companies are storing to improve business decisions. The data used to operate the business includes a wealth of knowledge and may be a partially wasted asset. Data warehousing applied properly can make it possible to do the following: • Understand business trends • Improve forecasting decisions • Bring better and more timely products to market • Analyze daily sales information • Speed decisions that can affect a company’s performance. On-Line Analytical Processing (OLAP) products are multidimensional analysis tools that store data using these data structures. Data marts contain informational data that is departmentalized, tailored to the needs of specific departmental work groups, and characterized by small size, generally less than 10 GB. Metadata is information about iSeries Software 125 the data warehouse and the data contained in that data warehouse, and is composed of two parts—technical data and business data. Technical data contains descriptions of the operational database and the data warehouse. The warehouse administrator uses technical data to maintain the warehouse so as to know where all of the data is coming from. Business data helps locate information in the data warehouse without knowing the base implementation of the database. Business data information is presented in business terms instead of the terms the programmer used when the database was built and provides information about how recent the data is, which operational database the information came from, and how reliable the data is. Data Mining Data mining is the search for relationships and segmentation in the data in the data warehouse. Discovery-driven data mining is the finding of new relationships and segmentation that are totally unexpected. IBM’s newest product in this area, Intelligent Miner (5733-IM1), provides a framework for using all of IBM’s current and emerging data-mining techniques. Intelligent Miner is scalable, flexible, and open—integrating components and extracting data from many environments, including all DB2 for iSeries relational database family products. It provides client support for Windows, Windows NT, and AIX. Intelligent Miner is designed for business users, not data analysts, offering the derivation of new, comprehensible information through predictive modeling, database segmentation, link analysis, and deviation detection using data-mining techniques. Figure 3.6 illustrates the functions and layers of the construct for data mining. What makes the iSeries with its OS/400 operating system a good server on which to perform data warehousing and data mining? The five requirements of a data warehouse server are performance, capacity, scalability, open interfaces, and multiple data structures. Intelligent Miner has increased its functionality through support for a full range of statistical functions including correlations, factor analysis, linear regression, univariate curves, and bivariate statistics. The existing mining techniques have been optimized, and one mining technique, net value prediction, has been added. The database server must be capable of supporting the user’s performance expectations during analysis. Many warehouses contain over 100 GB of data, with very complex analysis tasks being executed against the Exploring IBM ~ iSeries Symbolic Natural Induction Networks Fraud Detection Claims Cellular Telephony Text Mining Abstract Search Patent Data Search Internet Database Link Analysis Deviation Detection AM FL Y Predictive Modeling Radial Basis Functions Symbolic Association Visual- Statistical Segmenta- & Sequence ization Analysis tion Discovery Data mining constructs. TE Figure 3.6. Customer Segmentation Customer Retention Targeted Mailing Cross Selling Customer Vulnerability Analysis Database Segmentation & Summarization Data Mining Operations Applications Market Basket Analysis Promotional Effectiveness Subscriber Analysis Demand Forcasting Data Mining Tech niques 126 database. Parallel computing technologies become quite important when dealing with this large a size. The iSeries at the single-system level supports parallel computing, using its DASD I/O processors on the DB2 for iSeries database and Symmetrical MultiProcessing (SMP), which can apply the resources of up to thirty-two processors cooperatively for a single job or query. In addition, with Opticonnect, up to 128 nodes (a node is an instance of OS/400) can be connected in a loosely coupled relationship. The power of all 128 nodes can be brought to bear both in containing the warehouse size and in performing the analysis required. DB2 Multisystem must be installed to support the loosely coupled technology. Intelligent Miner supports your analysis needs in the areas of: • Capacity • Scalability • Open interfaces • Multiple data structures. Team-Fly® iSeries Software 127 Intelligent Miner has been extended to include text-analysis tools (clustering, classification, feature extraction) by using an advanced search engine and providing Web access tools. One example of how data mining can help a business was the discovery of an unexpected relationship between young men with small children who enjoyed football, beer, Thursday nights, and diapers. If these young men went to the store on Thursday night during football season to buy diapers for their young children, they would also stop at the beer display and pick up some beer to drink during that weekend’s games. If a particular brand of diapers was located on the same aisle, the young men would pick up whatever brand of diapers it was, regardless of price. Needless to say, the retailers located the most profitable brand of diapers on the same aisle as the beer. Collaborative Computing Collaborative computing is an environment in which many users require the coordination of multiple actions toward the accomplishment of a common goal. Programs that enable the achievement of that coordination are known collectively as groupware. Groupware applications help organizations communicate, collaborate, and coordinate strategic business processes both within and beyond the boundaries of the business to achieve improved business results. Examples of groupware are Lotus Notes and Domino. Lotus Notes supports the client functions, and Domino supports server functions. Domino for iSeries is described in Chapter 5 with regard to its use for e-commerce and network computing capabilities. Lotus Notes client functions support: • Advanced client/server e-mail • Direct Web browsing, Web agents, and off-line access to Web pages • Calendaring and scheduling for personal calendaring, task management, and group scheduling • Support for mobile workers • Bundling and integration with Netscape Navigator and Microsoft Internet Explorer 128 Exploring IBM ~ iSeries • Optional, high-performance Lotus components. Domino Server Powered by Notes provides: • HTTP Web server accessed using a standard Web browser • Calendaring and scheduling with free-time search and interoperability • SMTP–MTA (Simple Mail Transfer Protocol–Message Transfer Agent) providing mail coexistence with Notes Mail • Support for Internet standards, including SMTP/MIME, X.400, JAVA, Netscape plug-ins, ActiveX, POP3, HTTP, HTML, MAPI, SNMP, SSL, and CGI • Integration with corporate data, including iSeries data via DataPropagator/400 (5716-DP1). IBM offers two iSeries integration packs for Lotus Notes. The iSeries Integration BasePak for Lotus Notes allows the IXA to act as a LAN adapter, providing software to install Notes on the server. It also includes one copy each of Lotus Notes R4 server and a full applicationdevelopment client license. The iSeries Integration BasePak for Lotus Notes also includes server administration, the ability to add Notes users via the iSeries, the ability to exchange mail with Notes Mail, and shadowing of the iSeries SDD (System Distribution Directory) to the Notes Name and Address book. With the availability within Notes of SMTP-MTA (Message Transfer Agent) and POP3, iSeries Notes users can communicate with a wide variety of other mail clients. Even nonprogrammable terminals have interoperability, as they will receive the text and attachments as storable, forwardable PC files. The IXA supports existing Notes database functions, including replication and compression. DB2 UDB for iSeries data can be imported to Notes databases. Options are available for shadowing DB2 UDB for iSeries data into Notes as either a full or an incremental refresh. An optional user exit program allows Notes updates to DB2 UDB for iSeries. Web Navigator allows Notes clients to simply click wherever they want to go. Web Publisher, a separate Lotus product, allows for batch conversions of Notes-created documents to HTML. iSeries Software 129 Portable Application Solution Environment The Portable Application Solution Environment (iSeries PASE) provides an integrated OS/400 runtime for porting UNIX applications. PASE uses a subset of AIX libraries to provide that runtime environment. PASE is not an operating system and is not an emulator. It takes advantage of the fact that the iSeries and the RS/6000 are using a common processor technology (the RISC PowerPC) that includes both the RS/6000 and the iSeries runtime environments. Given that environment, the iSeries processor directly switches runtime modes from iSeries to RS/6000 and back again as required to support the applications. Figure 3.7 illustrates the positioning of the runtime code for the PASE function. The result is not only that the UNIX applications port to the iSeries in hours, but they also have access to OS/400 services like DB2 UDB for iSeries database, file system, sockets, and so on. The UNIX applications can also call JAVA and iSeries ILE applications and can exploit all aspects of OS/400 operations and administration. The general process is that PowerPC code development is done on an RS/6000 workstation using AIX Application Development tools (editors, iSeries ILE Applications iSeries PASE Applications OS/400 OS/400 Services AIX (TM) Shared Libraries Technology Independent Machine Interface Syscall OS/400 SLIC Kernel PowerPC AS 64-Bit AS/400e Server (8/97 or Later) Figure 3.7. iSeries PASE software positioning. PowerPC 64/32-Bit 130 Exploring IBM ~ iSeries compilers, linkers, debuggers). The binaries are then copied to the iSeries and placed in a stream file in the Integrated File System. The iSeries PASE codes (binaries) are then invoked by calling the new OS/400 API. The AIX runtime base is 32-bit and 64-bit AIX version 4.3.3 libraries, providing kernel support for over 200 AIX syscalls. The AIX runtime provides a more complete AIX syscall and API support than previous UNIX support offered; includes Euro support and utilities for locales; supports Bourne, Korn, and C shells; updates C, C++, and Fortran language runtimes; and offers X Window System (client) and Motif runtime libraries. Support is provided to build OS/400 PASE programs without compiling on a separate AIX system. Application development utilities such as make, Ld (linker), and As(assembler) are included. System Openness contains header files for OS/400 PASE C and C++ programs. OS/400 PASE applications are supported for debugging by the iSeries System Debugger. Many open source tools compiled for AIX PowerPC can be run on OS/400 PASE. The application environment includes support for PTY/TTY device drivers, making it easier to port applications requiring terminal support. OS/400 PASE programs support launching the iSeries integrated JVM as well as support for the integrated JVM to run native methods implemented as procedures in an OS/400 PASE executable. This makes it easier to port AIX applications that use a combination of Java and C/C++ code to OS/400 PASE. OS/400 PASE includes Linux library support based on AIX 5L. Most Linux applications that can be ported to AIX 5L can be ported to OS/400 PASE, at the most requiring a recompile. This provides a more integrated and scalable solution. Documentation is provided for runtime, shells, and utilities in the IBM InfoCenter. The user needs an AIX system to prepare application binaries. There is no graphics adapter (use X-Windows server). There is no support for kernel extensions, and there is no JVM. AFP PrintSuite AFP PrintSuite for OS/400 is a family of print-enabling applications for transforming traditional line-mode printing to full-page documents and reports—output that blends application data with a variety of fonts, electronic forms, images, text, graphics, and bar coding. While the standard interface to AFP document function is with DDS and external printer files, there are situations where a different approach is required. iSeries Software 131 For example, you may want to change the format of your invoice without making changes to the line-of-business invoicing program. The AFP PrintSuite products (with the exception of AFP Toolbox) enable application-independent document formatting. AFP PrintSuite for OS/400 is composed of four separate document formatting applications. Advanced Print Utility (APU) Advanced Print Utility (APU) is an interactive end-user application that transforms existing application output into advanced electronic documents. No application changes are required, since APU works off the output spool file created by the application. Through a standard iSeries interface, a new document is designed. The new document can incorporate electronic forms, image, fonts, bar codes, text, and other elements. The existing output data is brought up visually, and placement of each element on the page can easily be changed. Additionally, application data can be tested to determine page layout and types of copies produced. Once the document design is complete, the new application can be put into production using the APU Monitor. The APU Monitor includes the ability to control where output, including copies, is printed as well as providing multiple user exits in order to further customize the document design or print flow. Page Printer Formatting Aid (PPFA) Page Printer Formatting Aid (PPFA) is a compiler that converts AFP print formatting resources—page definitions and form definitions—from source format to object format. Page and form definitions are standard AFP resources that control how line-mode application output (called line data) is mapped to a page. Once these definitions are created and specified in the printer file, existing application output is dynamically changed. When the application is run the next time, it creates full recommended replacement for PPFA. AFP Toolbox AFP Toolbox is a developer set of tools that provides for full control of the AFP print data stream. Composed of high-function C and C++ objects, the AFP Toolbox enables the formatting of complex documents. For example, you may need to create customer statements where each 132 Exploring IBM ~ iSeries page is dynamically designed based on a customer profile and transaction data. Or you may have a document where a scanned image must be imbedded on the fly. Or you may need to create a standard AFP “print driver” for a series of applications. The AFP Toolbox APIs enable a developer to code these document characteristics at a high level and have the appropriate AFP structure fields automatically created. SAP R/3 AFP Print SAP R/3 AFP Print provides AFP print support for SAP R/3 applications. Basic support enables R/3 reports to be printed on IPDS printers. Extended support enables you to enhance existing R/3 output (for example, an invoice) with electronic forms, typographic fonts, and image. SAP R/3 AFP Print is built into R/3 print processing for maximum efficiency. Industry-Specific Application Programs The cross-industry application programs discussed up to this point are of a highly general nature, able to fill the common needs found in even the most diverse business environments. They were designed to be as general as possible to cover the largest market possible—sort of the “all things to all people” approach. In most cases, however, a business also has some needs that are more specialized to its particular industry. Therefore, another type of prewritten application program, called an industry-specific application program, may be desirable. As the term industry-specific implies, this type of application program is specially designed to address the needs of a well-defined business category. A real estate office has application program needs that differ from those of a dental practice. Each would benefit by an appropriate prewritten yet highly specialized industry-specific application program. Many software companies have put a great deal of effort into developing industry-specific programs for the System/3X computers. Since iSeries systems can run many of these programs as well as those specially written for the iSeries, highly specific business/professional environments can be addressed. There are industry-specific applications designed for manufacturing companies, insurance companies, real estate offices, medical practices, construction companies, law practices, churches, and so on. These programs are often modular, meaning that iSeries Software 133 they are really several different programs designed to work closely together. Each program or module can be used individually or share information with the others. Modular programs allow you to select only the modules you need, reducing costs for those not needing “the works.” Hundreds of software companies have written thousands of industry-specific application programs, and new application programs are appearing almost daily. Before custom software, discussed next, is purchased, industry-specific software should be carefully considered. Custom Application Programs Prewritten application programs fit many needs. They are comparably inexpensive, flexible, and convenient tools. In some cases, however, users may find that the fit of their application program to the way the business operates needs to be that of a tight glove. This is especially true in environments in which the iSeries servers are needed to perform highly unusual and specific tasks or there is a need to conform to existing company procedures. In these cases, it’s better to develop custom application programs written to the user’s exact specifications. Custom application programs are designed and written by programmers employed by the company or by consultants contracted for just that purpose. In either case, the basic development steps are the same. First, a software specification is developed that describes the actions of each program, and the specific interface is projected for the input and output of the program. Then a preliminary version of the program is written that demonstrates the final program. The user evaluates this preliminary version, and the specification is altered to reflect any needed changes. Last, the final program and user manuals are written and put in place at the user’s location. Typically, the developer will provide user training and any problems will be ironed out. Once the user accepts the program, the software has to be supported. Users will need a place to go when they have questions not addressed by the manuals. Support also includes making necessary changes to the application program, which the changing business environment often may require. This kind of ongoing support is critical to the success of any computer automation project. Most of the time, developing custom application programs is more expensive and time-consuming than going with the prewritten application program approach. In many environments, however, this additional expense and time can be recovered by the increased return on invest- 134 Exploring IBM ~ iSeries ment that can result from custom applications that precisely fit the needs of the environment. An additional benefit of custom application programs is their ability to change as a company changes. Getting major modifications to prewritten application programs may be difficult or impossible. The iSeries functions and programming tools including the basic architecture of iSeries systems make for a very productive programdevelopment environment. The built-in database and single-level storage provide high-level structures and consistency. Operating Systems 135 4 Operating Systems F ew areas in information processing create more confusion and apprehension than the operating system. This chapter is designed to help remove some of the mystery associated with the iSeries operating system and related system software. Introduction to Operating System Concepts The operating system used by all iSeries computers is OS/400. Before we take a look at OS/400, let’s cover a few basic concepts. The operating system provides the necessary interface that allows a user and the application programs to interact with computers. The user interacts directly with the operating system’s user interface to manage files on a disk, start application programs, print files, and so on. The operating system performs the tasks that all applications must perform, providing a uniform, consistent method for accomplishing those tasks. The operating system also performs tasks directly under the control of application programs without any user assistance. The application program initiates tasks by directly interacting with the operating system through the Application Program Interface (API). 135 136 Exploring IBM ~ iSeries TE AM FL Y The API is simply a set of operating system commands that can be issued directly by the application program. OS/400 recognizes commands written in Control Language (CL). The API simplifies the job of the application programmer because it is not necessary to become involved with the details of hardware interaction. Further, when an application uses the API, it is shielded from changes in the computer hardware as new computers are developed. The operating system can be changed to support new computer hardware while preserving the API unchanged, allowing application programs to run on the new computer. The iSeries uses an integrated operating system called OS/400. With more traditional computer systems, the operating system must be “assembled” from individually selected components which must be integrated and tested by a systems programmer. With iSeries systems, the OS/400 operating system comes pre-packaged as one integrated product. That is, IBM has already assembled and tested all OS/400 components to make sure they operate properly. The disadvantages of this approach are that the user must take OS/400 as a package, and it is not possible to “pickand-choose” only the operating system functions you want. OS/400—An Executive Overview Operating System/400, commonly called OS/400, is a multiuser (serves more than one user at a time) operating system used with all iSeries computer systems. It works closely with the System Licensed Internal Code (SLIC) instructions in iSeries systems to implement database, security, single-level storage, and many other functions that are basic to the iSeries architecture. OS/400 is a pre-packaged and pre-tested set of programs that perform housekeeping tasks based on requests from both users and application programs. Any iSeries user can load and switch between multiple batch or interactive tasks, each protected from disruption by other tasks or users. Although OS/400 offers users complex and sophisticated features, much has been done to make OS/400 easy to use. One of the ease-of-use enhancements is the uniting of the OS/400 and the Windows desktop to provide a new graphical interface for users who are familiar with the Windows interface. Other OS/400 items that directly address ease of use include automatic configuration of devices and table-driven customization. Team-Fly® Operating Systems 137 Extensive help and online (computer-based) documentation are provided to reduce the need to consult reference manuals when a user needs more information. Online education using CD-ROMs is built into OS/400, allowing users to learn how to use the system while sitting in front of their workstation. In addition to performing tasks under the direct control of the user, OS/400 performs tasks under direct control of an application program, which issues commands to OS/400 through the OS/400 application program interface (API). The API provides a defined protocol for passing information directly between the application program and OS/400 with no user interaction required. Often, OS/400 subsequently calls on the routines of the underlying SLIC instructions to effect the desired action. OS/400 provides multiple APIs to maintain compatibility with programs originally written for System/36, System/38, and AS/400 predecessors of the iSeries. The newer iSeries API provides some additional capabilities not found in earlier operating systems, such as the structured query language method of dealing with databases. If a user gets stuck on some operating system screen, pressing the “Help” key causes some help text to appear on the screen. The particular help text shown depends on where the cursor was on the screen when the Help key was pressed; that is, the text will address the particular item at which the cursor was positioned. This is called contextual help. Extensive database and communications support in OS/400 allows iSeries to manage large amounts of information and participate in many communications configurations. Available application development tools improve the productivity of programmers for those writing their own custom application programs. For current users of System/38 systems, the iSeries will run System/38 object code. It is important to note that the Linux operating system can also be used on iSeries systems (as a secondary operating system to OS/400). Linux is emerging as a very important industry-standard operating system which is fully embraced by iSeries and the rest of the IBM eServer lines. Later in this chapter we will explore Linux further. A Closer Look at OS/400 Even though OS/400 is fairly easy to use, it has many complex features and functions. A complete description of these features would 138 Exploring IBM ~ iSeries require a separate book. However, the remainder of this chapter looks briefly at some of the most important topics and the impact on those topics as a result of the evolution of computing to the e-business environment of today: • Integrated file system • DB2 UDB for iSeries • Communications support • Systems management features • Advanced-function printing • Management Central • WebSphere Development Studio • Open standards-based interoperability • Object-oriented programming languages (Java, C, C++) • Linux for OS/400 • Globalization. Integrated File System The integrated file system of OS/400 provides a consistent structure for manipulating all the types of information (i.e., file types) stored in an iSeries system (see Figure 4.1). That is, it provides a consistent structure and interface (for users and application programs) for accessing traditional database files, libraries, folders, documents, and so on, as well as increasingly important information types such as images, audio, and video. Support is provided for: • Stream files, which can contain long continuous strings of data (for example, the text of a document or the long string of data representing a scanned image). Operating Systems 139 Integrated File System Libraries Database Files Figure 4.1. Directories Stream Files Folders Document Objects OS/400 integrated file system structure. • The Network File System (NFS) and the Remote File System (RFS), which are popular in UNIX environments. • CICS files, which are popular on the IBM S/390 computer family. • A hierarchical directory structure (similar to that of UNIX) that allows objects to be organized like fruit on the branches of a tree. An object is accessed by specifying the path through the directories to the object. • A common interface that allows users and application programs to access all information—not only the stream files, but also database files, documents, and other objects stored in the iSeries system. The integrated file system enhances the data-management capabilities of OS/400 to better support emerging and future forms of information processing (e.g., client/server, open systems, and multimedia). The benefits provided by the integrated file system include: • Fast access to iSeries data, especially for applications using the PC file server (shared folder) facilities. 140 Exploring IBM ~ iSeries • More efficient handling of the increasingly important types of stream data, such as images, audio, and video. • A file system and directory base for supporting UNIX-based open system standards such as POSIX and XPG. This file and directory structure also provides a familiar environment for users of UNIX and PC operating systems such as DOS and Windows. • The ability to handle information (such as record-oriented database files, UNIX-based stream files, and file serving) through separate file systems or to manage it through a common interface, depending on user needs. • Better graphical user interface for PC users. For example, Windows users can use the Windows graphical tools to operate on iSeries stream files and other objects in the same way that they operate on files stored on their PCs. • Continuity of object names and associated object information across national languages. This support ensures that individual characters remain the same when switching from the code page of one language to the code page of another language. OS/400 contains a file system that connects the iSeries to a Windows NT/Windows 2000/Windows XP domain as a client. That file system is named QNTC and uses standard POSIX APIs to provide access from the integrated file system. The transport mechanisms to the new file system use industry-standard protocols NetBios and TCP/IP. Messaging protocols between the integrated file system and QNTC are the industry-standard CIFS and SMB. Through its access to data stored within the Windows domain, the iSeries becomes a mechanism for distribution of applications and data. Any iSeries application that can use data as formatted on the Windows server can use the file system, such as Java applications. Access is allowed to data on both standalone Windows servers and the iSeries Windows application processor. Support is provided for Windows NT/2000. The total number of active Application Storage Pools (ASPs) supported has been increased from sixteen to sixty-four. Operating Systems 141 Stream Files To better understand stream files, it is useful to compare them with iSeries database files. A database file is record-oriented: It has predefined subdivisions consisting of one or more fields that have specific characteristics, such as length and data type. A stream file is simply a file containing a continuous stream of data. Documents stored in iSeries folders are stream files. Other examples of stream files are PC files and the files in UNIX systems. Figure 4.2 illustrates the difference between record-oriented database files and stream files. The different structure of record-oriented files and stream files affects how an application is written to interact with them and where each type of file is best used in an application. A record-oriented file, for example, is well suited for storing customer statistics (such as name, address, and account balance) because these predefined fields can be individually accessed and ma- Access Services (HTTP, IIOP) Browsers PCs Pervasive Devices WebSphere Application Server Web Server Runtime Services ORB e-business Applications J2EE, Web Services Java Servlet, EJB Connection Services Relational Databases Figure 4.2. Legacy Systems ERP Systems Other Application Servers Stream file structure vs. record-oriented file structure. 142 Exploring IBM ~ iSeries nipulated using the extensive programming facilities of the iSeries. A stream file is better suited for storing information such as a customer’s picture, which is composed of a continuous string of bits representing variations in color. Stream files are particularly well suited for storing strings of data such as the text of a document, images, audio, and video. File System Support From the perspective of structures and rules, the OS/400 support for accessing database files and various other object types through libraries can be thought of as a file system called QSYS.LIB. Similarly, the OS/400 support for accessing stream files is a separate file system, called QDLS. Other file systems supported under the integrated file system include the following: • Root: The root file system is designed to take full advantage of the stream file support and hierarchical directory structure of the integrated file system, and it has the characteristics of the DOS and OS2 file systems. • QOPENSYS: The open system file system is designed to be compatible with UNIX-based open system standards, such as POSIX and XPG. It is stream file-oriented and supports case-sensitive object names. • QLANSrv: The LAN server file system provides access to the same directories and files as are accessed through the OS/2 Warp Server licensed program. It allows users of the PC file server (shared folders) and iSeries applications to use the same data as OS/2 Warp Server (5769-XZ1) clients. OS/2 Warp Server will run applications that do not require graphical user interface interaction. OS/2 Warp Server increases save/restore performance and provides printer-serving capability and TCP/IP support including NetBIOS over TCP/IP, and LAN-to-LAN print capability. Users and application programs can interact with any of the file systems through a common integrated file system interface. This interface is optimized for input/output of stream data in contrast to the record input/output provided through the data-management interfaces. A set Operating Systems 143 of user facilities (commands, menus, and displays) and application program interfaces is provided for interacting with the file systems through this common interface. Triggers, stored procedures, declarative referential integrity, two-phase commit, and long field names are supported under all file forms and therefore improve DB2 UDB for iSeries as well as CICS/400. The integrated file system can support a large address space up to 72 terabytes, which can be used for heap storage, shared memory, and memory mapped files. In addition to the large address space, the IFS can support stream files up to 256 GB in size in the root (/), qOpenSys, and user-defined file systems. Threadsafe integrated file system API interfaces can access objects in the following file systems in a multithreaded job: • QSYS.LIB • QOPT • QLANSrv. A new directory implementation provides better directory performance, scalability, robustness, and recoverability. Combining the foregoing with journaling and improved caching techniques results in a faster, safer, more reliable file system. Network File System The internal structure of the integrated file system is shown in Figure 4.3. There are five components to that file system structure. The QOPT PFS (Physical File System) supports both CD-ROM and optical libraries. The user-defined physical file system supports long-named objects, as well as allows the user to identify specific groupings of hardware to belong to particular auxiliary storage pools. The Network File System (NFS) Server and NFS Client PFSs are UNIX specific and are discussed further in the following paragraphs. QNetWare Client PFS supports the needs of an Internet set of clients. The NFS Server and NFS Client communicate using Remote Program Calls (RPCs). The NFS Client is a physical file system that implements the iSeries Virtual File System architecture. The NFS Client provides seamless access to remote files for local applications. The remote files could be 144 Exploring IBM ~ iSeries Applications/Generic Commands FMS Non-POSIX APIs POSIX APIs PC File Server (shared folders) Logical File System NFS Server vnode interface QDLS PFS Qsys.lib PFS Root PFS QOPT PFS QOpenSys PFS NFS Client PFS User-Defined PFS QFileSvr.400 Client PFS QLANSrv Client PFS QNetWare Client PFS F S I O P Legend Added in 1996 Integrated File System Base OS/400 Base Figure 4.3. Integrated file system internal structure. on a remote UNIX machine, the AIX IOP, or any machine that is running an NFS Server. The network file system contains both a lock manager and a system monitor. The design of the system between the server and the client is a stateless design (one in which after completion of the current activity it is impossible to go back to a previous activity, because there is no coherent tracking of separate activities), so changes made at the client cannot be acquired at the server until the data stream is received at the server. Therefore, the server locks all data that has been sent to the client until received back from the client. The server monitor keeps track of the state of the systems in the network. Remote File System The iSeries Remote File System allows users to share access to devices such as optical libraries or integrated NetFinity Servers among iSeries systems, manage a network from a single iSeries, share data in a homogeneous iSeries network, and get data from multiple iSeries systems with one connection from a PC. The remote file system allows an iSeries computer to act as a client to other iSeries computers to allow access— Operating Systems 145 using the integrated file system commands—to any object on those iSeries systems. It can only talk to other iSeries systems, and iSeries Access can use this connection to access data on those other iSeries systems. It is possible to chain system connections this way, but you must pay a propagation delay penalty. The connections can be across TCP/IP, APPC, or both. Functions not supported across these connections include multiple entities such as authorization lists and group profiles, extended attributes and byte locking, and save/restore functions. Also, all users share the same connection to the remote system, and symbolic links can be traversed but not created. CICS Transaction Server for iSeries (5769-DFH) Previously referred to as CICS/400, CICS Transaction Server for iSeries comes packaged with two other products—CICS Universal Clients and CICS Transaction Gateway. The grouping of these products allows entry into e-business. Using application programs (prewritten or custom) to access and manipulate information in an iSeries database, businesses can combine all of the methods of accessing information to provide an environment that is tailored to their particular needs. These application programs may, unknown to the users, employ one or more of the previously discussed database-access methods, depending on the specific need. Using the CICS Transaction Server for iSeries extension to OS/400, programmers can run CICS application programs (COBOL) on an iSeries and access data on the iSeries or some other computer (e.g., an S/390 or OS/2 computer) running CICS. Application programs that use CICS are very common in the IBM S/390 user community. CICS Transaction Server for iSeries allows programmers to migrate S/390-based CICS application programs to the iSeries or use their CICS experience to write new CICS application programs specifically for the iSeries. The communications functions provided by the CICS environment provide another way for iSeries programmers to write/migrate application programs that give users access to information stored in the iSeries and other computer systems. The CICS Translation Server for iSeries functions have been extended to include client/server support, two-phase commit, and C applicationlanguage support. Programs written for the CICS Clients and the CICS Transaction Gateway can access CICS transactions on iSeries over a TCP/IP or an SNA network. This allows host-based applications to be enabled for 146 Exploring IBM ~ iSeries client environments. The CICS Transaction Gateway enables these same applications to be used in Web-serving environments. Client for Windows NT/2000 File System AM FL Y The Client for Windows NT/2000 File System provides the iSeries access to the NT/2000 files in the Windows NT/2000 File System via the iSeries Integrated File System. TCP/IP transports are used to communicate with any NT/2000 server in the domain. Connections can be made to NT/2000 on the Integrated xSeries Servers (IXS) and standalone NT/2000 servers. The iSeries can be used as a management control point for distributing applications. Any iSeries application that can use data formatted on the NT/2000 server has access to that data. If NT/2000 data needs backup, NT/2000 Backup must be used. TE DB2 Universal DataBase (UDB) for iSeries To efficiently interact with large amounts of information, it is necessary to organize that information in some uniform way. For example, the information in a telephone book is organized into an alphabetical list of names, addresses, and telephone numbers. Computers also provide a tool for storing information in an organized software structure called a database. Almost any kind of information (e.g., a department store’s inventory, a library’s books, personnel records, digitized sound effects, medical records, scanned images of houses, etc.) can be stored within a computer database. All iSeries systems come with built-in database functions, called DB2 Universal DataBase (UDB) for iSeries, as part of OS/400. DB2 Universal Database (UDB) for iSeries is a member of IBM’s DB2 UDB family optimized for the iSeries platform and operating system. Over 35,000 commercially available iSeries application solutions take advantage of the power, flexibility, and ease of use of the DB2 UDB for iSeries database manager. These applications are written for a wide range of industries and users, ranging from small businesses with basic accounting needs to large corporations with complex computing environments. The fact that DB2 UDB is built into the operating system means that the database functions are preloaded, fully integrated with the rest of the system components, and thoroughly tested. This integration also means that each enhancement to the operating system enriches the database environment. Team-Fly® Operating Systems 147 What Is a Relational Database? The DB2 UDB for iSeries is a relational database structure. In a relational database, each piece of information is related to the others using a simple tabular structure. This provides great flexibility when defining the database and using the information it contains. Inside the iSeries database, information is stored as records and fields. Do not be intimidated by the words. This is exactly how the information in a phone book is structured. Figure 4.4 shows an example of a telephone book listing and the corresponding relational database structure found in an iSeries computer. The phone book itself is analogous to a set of information or a database. Records and Fields The information about one person in the phone book would be analogous to a record (or row). The record contains the information for a given entry, and all other records contain similar information about their respective entries. (An employee’s record contains all of the pertinent information about that employee regardless of the number of fields needed.) In the case of a telephone book, a record contains the name, address, and phone number of the person. Each one of these three items is analogous to a field (or column). For example, in a relational database, the address part of a phone book entry is called the address field. Manually looking up information in a phone book is time-consuming and quickly becomes fatiguing. The same is true for manually manipulating any large body of information. Once information is entered Information organized in a telephone book Telephone book (Name) (Address) (Phone #) Packar J. C. 1012 SE 45 St----654-8499 Packer O. R. 244 W 13th St----878-2443 Pagano B. R. 667 NW 83rd St---655-0097 Information organized by a database application program Computer "database" file "Name" field "Address" field 1012 SE 45 St Record #1 Packar J. C. Record #2 Packer O. R. 244 W 13th St Record #3 Pagano B. R. 667 NW 83rd St "Phone No." field 654-8499 878-2443 655-0097 Figure 4.4. Information in a database is organized much like the information in a telephone book. 148 Exploring IBM ~ iSeries into a database, its retrieval by the computer is quick and easy. What does the built-in database capability of the iSeries have to offer? In iSeries computers the database structure is defined independently from user programs. The data in the database is available to all user programs for analysis, report generation, update, and so on, but the database definition does not reside in the users’ programs. The data is therefore said to be externally described, meaning that no single user’s program on the system describes the structure or content of the database. Instead, the definition lives inside the iSeries’ built-in database system and in that respect is independent from any one program. This is an important point, because it improves the consistency and thus the maintainability of application programs. Now the programmer has one source for all information pertaining to the database structure and how application programs use the database. Externally described data contribute to improved programmer productivity because the database will fit itself to the application program rather than the application program fitting itself to the database. Physical and Logical Files Another important feature of iSeries database support is the support for logical files. The telephone book example deals with real, or physical, database files, which are groupings of information inside a computer. The concept of logical files allows a system administrator to change the appearance of the physical database to better suit individual needs. For example, suppose there is a personnel database on an iSeries computer for a fictitious company named Atole Enterprises. The organization of the personnel information is shown in Figure 4.5. This physical database file contains all personnel information and was described externally to any user programs. A clerk (Jim) has the job of keeping an up-to-date mailing list of all employees for the company magazine, but to protect employees’ privacy, Jim must not have access to the wage information that is part of the physical database file. To meet these needs, a logical database file is defined that contains no information but only a view of the physical database that meets Jim’s needs. The logical database file restricts Jim’s view of the physical database file to only the information he needs. Furthermore, since Jim looks up employees by name, this is the key field defined in his logical database file. He is able to access the information by alphabetical order of Operating Systems Name Address Phone Wages SS# 149 Date of Hire Marital Status Record 1 Record 2 Record 3 Record 4 Record 5 Record 6 Record 7 Record 8 Record X Figure 4.5. Physical database containing personnel information. employee name (his key field) rather than by the order in which the names actually appear in the physical database file. Jim’s database file structure is shown in Figure 4.6. Another logical database file for a different clerk (Nancy) exists using the same physical data. Nancy tracks employee anniversaries. Her logical database file structure is shown in Figure 4.7. Nancy looks up employees by their date of hire, so this is the key field in her logical database file. Only the fields needed to do her job are made available to Nancy. As the needs of Atole change, many logical database files can be defined to meet the different employees’ needs without affecting any other user or the physical database file. The restrictions provided by unique views for different users or user groups inherently guarantee data security and data integrity. Also, within any particular view, fields may be further identified as read only for additional data integrity. Users are allowed to view and change data contained in only the fields for which they have authorization to make changes. This example illustrates how multiple users can use a single copy of a physical database to do completely different jobs. Without logical files, multiple physical databases would have to be kept in the computer system, wasting space. The Atole Enterprises example is extended in the next section to illustrate the problems of data concurrency and lock management across multiple physical databases containing redundant data. 150 Exploring IBM ~ iSeries Jim’s Logical Database (Key) Name Address Name Address Phone Wages SS# Hire date Marital status Record 1 Record 2 Record 3 Record 4 Record 5 Record 6 Record 7 Record 8 Record X Figure 4.6. Jim’s logical database provides a “view” of the physical database needed to perform his job. Nancy’s Logical Database (Key) Jim’s Logical Database (Key) Name Name Address Address Name Phone Wages Address SS# Date of hire Hire date Marital status Record 1 Record 2 Record 3 Record 4 Record 5 Berger 123 W 7th St 1234567 750.00 12345 7/1/81 Record 6 Record 7 Record 8 Record X Figure 4.7. Multiple logical databases can be constructed, providing different views of the same physical database. Operating Systems 151 Concurrency and Lock Management Figure 4.8 illustrates a situation at fictitious Atole Enterprises that can occur when multiple databases contain redundant information. The figure shows three different databases (one for Jim, one for Nancy, and one for payroll), each of which contains name and address fields for Atole employees. In addition to wasting space because of the redundancy, other problems are associated with having multiple physical databases. For example, one morning Jim receives notice that an employee (Mr. Berger) has a new mailing address and Jim promptly updates the database. Later that same morning, Nancy searches for that month’s service anniversaries and finds that the month is Mr. Berger’s seventh anniversary with the company. She checks his address and sends him an anniversary card. Without the logical-file approach, in which Jim and Nancy share one physical copy of the data, Mr. Berger’s card would be sent to the old address. With the logical database of the iSeries computers, as soon as Jim updates Mr. Berger’s address, it is available to Nancy and Mr. Berger gets his card on time. The problem solved by the single physical file with multiple logical views is one of concurrency (synchronization). Without this, when multiple physical files exist with redundant data defined across those physical files, an update to a redundant field in one Jim’s Database Name Address Nancy’s Database Name Address Hire Date Name Berger 333 E 7th St Berger 333 E 7th St Physical Database #1 7/1/81 Physical Database #2 Address Payroll Database Phone Wages SS Hire Date Berger 333 E 7th St 1234567 750.00 23422 7/1/81 Physical Database #3 Figure 4.8. Without logical database views, multiple physical databases would be necessary, wasting space, compromising data integrity, and complicating processing. 152 Exploring IBM ~ iSeries of those files makes it different from the identical field in the other physical files. An alternative solution is to maintain a cross reference file that identifies all of the redundant fields of each of the physical files and an application program that updates the redundant fields of the other physical files when any of the fields receives a change. A second problem that arises from the concurrency problem is lock management. Lock management becomes a problem because once the computer knows that a redundant field has received a change, the computer must prohibit processing with those fields of the physical files containing old data because either this will cause erroneous results or, as in our example, the information will be sent to the wrong location. To prevent that erroneous processing, the computer system locks those fields until update processing has completed. If a program has started that uses a locked field, the program must be backed out of the computing system or be put into a suspended state. The illustration selected is a simple one because the data that changed was entered by an individual, but consider the problem when the redundant field is changed under control of an application program, with other application programs referencing that field for processing information. With multiple physical files with redundant fields, situations have arisen in which the entire computing system became deadlocked because the total resources of the computer were tied up and the update program could not gain access to the resources to resolve the lock situations. Lock-management programs are very complex programs. Lock management is also a problem when redundancy occurs over distributed databases on distributed systems. There are ways to keep multiple copies of information up-to-date on computer systems without logical files, but if our example is extended to a real business environment with many different clerks, many different programs undergoing changes, and many different types of databases, managing the problem becomes time-consuming and difficult. With the logical-file approach, there is no data-redundancy problem to manage. This example illustrates one method of using logical database files to provide a user with the information needed in the way that it is needed. DB2 UDB Details and Components DB2 UDB for iSeries is a relational database that performs all the functions described in the examples used to introduce relational data- Operating Systems 153 base concepts: multiple physical databases within a single database structure, each of which contains records, fields, and some relationship; and multiple views for each physical database within the structure. In addition, the iSeries supports more recent database technology such as triggers, stored procedures, declarative referential integrity, and check constraints for both physical files and SQL tables. The DB2 UDB for iSeries capability provides support for the following industry standards: • ANSI X3.135.1992, ISO 9075-1992, and FIPS 127-2 • Structured Query Language (SQL) • Open Group Distributed Relational Database Architecture (DRDA) • Microsoft’s Open Database Connection (ODBC) • Java DataBase Connection (JDBC). The DB2 database-manager function is integrated into OS/400 software and iSeries hardware and includes all the support necessary for applications and queries that use SQL to run on the iSeries. Some of the functions needed for the development of SQL high-level applications are packaged optionally in the DB2 Query Manager and SQL Development Kit product. DB2 Query Manager and SQL Development Kit The DB2 Query Manager and SQL Development Kit for iSeries provides an interactive query and report writing interface as well as precompilers and tools to assist in writing Structured Query Language (SQL) application programs in high-level programming languages. By conforming to industry-standard structured query language, the SQL implementation for OS/400 allows the definition, manipulation, query, and control of access to iSeries data, working with both iSeries files and SQL tables. Once created, the applications and queries can be restored and run on other systems that do not have this product installed. An SQL Development Kit for relational database uses programming languages such as C, C++, and REXX. 154 Exploring IBM ~ iSeries Another part of the SQL Development Kit is Interactive SQL (STRSQL), which provides a prompt-driven interface that allows programmers to test and run SQL statements. The interactive query interface, Query Manager, enables users to generate queries and reports. The user can specify page headings and footings; the order, width, and indenting for any column; page breaks; and column summary information. DB2 UDB for iSeries has been enabled for Internet application serving, which allows immediate use of existing data on the Internet to or from a terminal no matter where in the world the terminal is located, provided the usage meets the security requirements to use the Web server and has an appropriate Web browser. The results of a query are returned to your Web browser as an HTML document. Figure 4.9 illustrates how the Internet connection to DB2 UDB for iSeries parallels the iSeries generalized support for client/server computing. DB2 Symmetric Multiprocessing (DB2 SMP) DB2 SMP expands on the parallel capabilities of the iSeries hardware. With DB2 SMP for iSeries, a single database operation can run on mul- Distributed Presentation Distributed Presentation Distributed Logic Remote Data Management Distributed Database Data Management Data Management Data Management Data Management Data Management Logic Logic Logic Internet Presentation Internet Access Point 5250 3270 VT100 HTML Presentation Presentation Telnet Web Browser HTML HTML Data Management Logic Logic Logic Presentation Presentation Presentation Java Style Presentation FTP Figure 4.9. DB2 for iSeries Internet-style application development environment. Operating Systems 155 tiple processors at the same time or, in other words, in parallel. This additional processing power allows some operations to run dramatically faster. These operations that can be done in parallel include the creation of keyed logical files and indexes as well as index maintenance. DB2 UDB Extenders for iSeries The DB2 XML Extender provides new data types that allow the storage of XML documents in the DB2 database, and new functions that assist in working with these structured documents. XML represents a fundamental change in computing away from proprietary file and data formats to a world of open interchange through portable data. DB2 provides stability, scalability, and security to the XML environment. The logical structure of an XML document is based on a tree-like hierarchy, uses start and end tags, and must have only a single root element. To enable DB2 to handle XML documents, a Document Type Definition (DTD) Repository was added. When the database is enabled for XML, a DTD reference table must be created. Each row of the DTD reference table represents a DTD. DTDs are used to validate XML documents. A Location Path is a sequence of XML tags that identify an XML element or attribute. The attribute or element must be mapped to a DB2 column. There are two access and storage method XML columns, and XML collection. An XML column is used to store and retrieve entire XML documents as DB2 column data, and XML data is represented by an XML column. XML collection can compose or decompose an XML document into a collection of relational tables. Both SQL and Relational Database (RDB) mapping are supported. The DB2 Text Extender is a linguistic search technology. The Text Extender is designed to perform sophisticated, high-speed searches through any character field in the database and even text documents stored in IFS. DB2 OLAP Server DB2 OLAP Server for iSeries provides a fast path to turn your business data into business insight. DB2 OLAP Server employs the widely accepted Essbase OLAP (OnLine Analytical Processing) technology supported by over 350 business partners and over 50 tools and applications. Create “speed of thought” database queries with the DB2 OLAP Utility. The latest version of DB2 OLAP allows a choice of data storage for the server by application, offers advanced attribute analysis as a Exploring IBM ~ iSeries built-in function to achieve economical storage usage, supports larger outlines for enhanced performance and scalability, and offers analytics support for a Query Designer featuring linear regression, exponential smoothing, etc. QMF for Windows for iSeries AM FL Y QMF for Windows is a graphical, multipurpose query environment for business reporting and data sharing. QMF eliminates the requirement for installing middleware on the end user’s PC by utilizing a direct database connection to the iSeries. In addition, QMF for Windows for iSeries also provides a conversion utility to convert your existing green-screen Query/400 and Query Manager reports. DB2 Data Propagator The Data Propagator Relational Capture and Apply for iSeries products enables easy management of DB2 family distributed databases containing local copies of master databases by providing automatic update support for the shadow copies and the capability to replicate entire copies of a file. Data Propagator Relational Capture and Apply can update source tables and replicated tables, and can take advantage of the remote journal function to run the capture process at the remote journal location. This off-loads the capture process overhead from the production system. The apply process performs differential refresh using the locally resident staging tables. TE 156 Database Monitor A database monitor has been added to DB2 UDB for iSeries. The database monitor provides information about what the database is doing, such as how many temporary indexes have been created, which information people are using the most, how many queries have exceeded a specified time limit, and which queries are using the most system resources. The data from the monitor is collected at the job or system level. Here is some of the information that the monitor provides: • System and job name • SQL statement and subselect number Team-Fly® Operating Systems • Start and end time stamp • Estimated processing time • Total rows in table queried • Number of rows selected • Estimated number of rows selected • Estimated number of joined rows • Key fields for advised index • Total optimization time. 157 ODBC ODBC is a Microsoft-provided application program interface specification for database access, whose objective is to provide interoperability between applications and databases without writing database-specific code in the application. This definition sounds very similar to the program-independence objective identified for the relational database in Telephone Book. DB2 UDB for iSeries supports ODBC. As a result, programmers can use popular programming languages such as Visual Basic or Visual C++ to access iSeries data. The SQL Call Level Interface (CLI) is compatible with ODBC, allowing an application to be written on a PC using ODBC and then be ported to run on the iSeries directly. ODBC is also supported by iSeries Access Family for Windows and Access Family. The Windows 95/NT client can access iSeries database information over any supported connectivity by means of the Microsoft ODBC 3.0 Driver Manager. New client/server applications can take advantage of the new functions provided by the Microsoft ODBC specification, yet old applications do not require rewrite. iSeries ODBC Driver for Linux The iSeries ODBC Driver for Linux provides access to data stored in DB2 UDB for iSeries for Linux programs written to the ODBC inter- 158 Exploring IBM ~ iSeries face. This ODBC driver is based on the ODBC driver in the iSeries Access for Windows product. The driver has the ability to store and process Unicode data. Versions exist for both Linux running in iSeries LPAR and Intel-based Linux workstations. OS/400 must be V4R5 or later. JDBC Similar to ODBC, JDBC provides data access interfaces for Java applications. Since JDBC is SQL-based, it is able to leverage and use the latest DB2 UDB features such as Triggers, Stored Procedures, and UserDefined Functions. The iSeries JDBC support is based on JDBC 3.0 and includes support for the Java Transaction API (JTA). Support also exists for storing persistent Java objects as well as for binary large objects and structured types. Increased performance and scaling of systems have resulted from synchronization, exception handling, method calls, generated code loop handling, field access in objects, and garbage collection. DB2 UDB for iSeries includes many self-managing concepts in compliance with IBM’s Project eLiza. Included are automatic spreading of data and index balancing, system-managed access path protection, and system-managed journal options. In addition, a new Index Adviser in iSeries Navigator’s Visual Explain function automatically provides suggestions on how to improve performance using information gathered during application execution. The iSeries Navigator’s Database Navigator displays more complex data models with the inclusion of triggers. The iseries Navigator also includes support for management of DRDA connections, SQL packages, transactions and SQL Explain. A new wizard called SQL Assist simplifies the process of creating complex SQL queries. Data Striping Data striping is a technique used to improve the performance of reads and writes to the database. A database file consists of many blocks of information. These blocks are randomly spread (or striped) across multiple storage devices. A single storage device can store multiple blocks from a single file. Most likely the multiple blocks for a file on a device are not logically contiguous. This spreading across multiple DASD devices allows the data to be accessed in parallel. Significant performance Operating Systems 159 improvement results because data can be brought into main storage in parallel, instead of serially. This is made possible because the multiple I/O processors (IOPs), supporting disk units on the iSeries system, preprocess the data on writes and reads to improve access time. DCE Base Services/400 Distributed Compute Environment (DCE) Base Services/400 is based on the Open Software Foundation (OSF) DCE Version 1.2.2. The code provided by OSF for DCE has been enhanced to provide the look and feel of iSeries with support for iSeries messages, menus, prompts, and help text. DCE code is consistent with other iSeries products in the areas of reliability, availability, and serviceability. DCE uses Remote Procedure Call (RPC) as a model for implementing communications between a client and a server, in which the client side runs on one machine and makes a request for service, and the server side runs on another machine in the network and fulfills the service request. RPC extends the model of the local procedure call into the open environment and the distributed-computing environment. The RPC facility includes an application development tool and a run-time library. When developing a DCE application, an application developer defines an RPC interface between the client application and the server application. DCE uses the DCE Interface Definition Language (IDL) to define this interface. The application development tool contains an IDL compiler that compiles the customer’s interface definitions into portable C-language source code. The IDL-generated source code can be compiled with the customer’s application code using the ILE-C compiler and can be linked to the DCE run-time library to form the distributed application. RPC helps hide the complexities of the distributed environment from the application programmer and the user. RPC is integrated with the DCE cell directory service and the DCE security service, enabling the client application to transparently find the location of the server and have secure communications. The DCE cell directory services act as a centralized location for storing information about the resources in the distributed system. The name of an object can be looked up and information can be retrieved about the object. Distributed systems objects include the users, the systems, and the resources associated with the systems. 160 Exploring IBM ~ iSeries A single distributed directory service is created. The directory service provides a logically centralized physically distributed place to store information. The directory can accommodate all the distributed resources in an enterprise, is scalable to any size, and can grow as the distributed system grows. The cell directory service manages a database of information about the resources in a group of systems that work together, called a DCE cell. Users can define the size and content of a DCE cell to best suit their needs. An application uses the cell directory client function to query the directory when information is needed about the location of a resource with which the application needs to communicate. With the directory structure in place, a remote procedure is referred to by a unique identifier, such as its name, by an application programmer. When it is queried, the directory returns the address location of that remote procedure to the application. A cell directory server must be configured in the cell to use the DCE cell directory client function. This directory server can reside on any system that implements the OSF DCE cell directory server, such as RS/6000, System/390, iSeries, or Windows NT/Windows 2000. DCE security service ensures that clients and servers are trusted by each other by supporting an authentication service in the open distributed environment. Authentication of clients and servers by the DCE security service prevents unauthorized use of distributed resources by supporting an access control facility. The DCE security service ensures data integrity and data privacy. The authentication mechanism used by the DCE security service is based on the Massachusetts Institute of Technology (MIT) Kerberos authentication technology. The client and server are authenticated or securely identified to each other by a third-party security server. As a result: • Users no longer need to be explicitly defined to every physical system that they need to access in the distributed environment, eliminating administrative overhead because a user or resource need only be defined to the security server once. Only one password needs to be remembered per user. • DCE security protects the server from clients that are imposters and protects the clients from servers that are imposters, as opposed to security systems that protect the intelligence at only the host or server end. Operating Systems 161 • Like directory services, security has a logically central, physically distributed database for users; because of the single logical structure, changes need be made in only one place. • A user can access all the DCE resources of the distributed system by once logging on to a DCE system. Server applications within OS/400 allow OS/400 itself to act as a Kerberos client, improving interoperability with Microsoft and other Kerberos-based authentication systems. Once a protected session between a client and a server is established, the client can access the resources of the server using security policies to control that access. Different security policies can be set up between each client/server pair. Data-integrity verification is based on a checksum generated by DCE security to ensure that data was not tampered with during transmission. The Data Encryption Standard (DES) algorithm is used by the DCE security service to protect data privacy. The data-privacy facilities are offered as DCE DES library routines. U.S. government import/export laws and regulations regarding full DES products affect this product because it enables encryption. Once a DCE security server is configured in a cell, the DCE security client function can be used. The security server can be configured on any system that implements the OSF DCE security server. Distributed Time Services periodically synchronize the clocks on the different nodes in a distributed network and keep the distributed time in each node synchronized with coordinated universal time (UTC). The synchronization is needed because many distributed applications need to ascertain the order of events, compute the interval between events, and schedule events independent of where the events occurred. The DCE time server must be configured in the DCE cell and can reside on any system that implements OSF DCE time services. DCE Base Services/400 implements the distributed-time clerk function. DCE isolates the application programmer from the communications code required for distributed applications, enabling the development of higher-quality, more functional distributed applications. Directory and security functions are automatically invoked as part of RPC. Distributed application client and server routines, written for a target operating system, are more easily ported to another operating system because OSF DCE APIs are the same among operating systems that support the DCE standard. 162 Exploring IBM ~ iSeries Distributed Data Management In a networked system environment, the Distributed Data Management (DDM) function of OS/400 allows an iSeries user to access data on a remote iSeries server as if the data were located on the local iSeries system. With DDM, the user need not know which computer system has the needed data. If the needed database resides on a different iSeries system located elsewhere in the communications network, DDM will automatically get the information for the user. Distributed data management has always allowed distributed database activity with remote iSeries systems, but there was no support for interacting with any compatible databases on other computer systems (e.g., IBM’s ES/9000 line of computers). Enhancements in the DDM function of OS/400 include full support of the Distributed Relational Database Algorithm (DRDA). DRDA’s remote unit of work allows iSeries application programs to include compatible System Query Language (SQL) statements that interact with data residing on another compatible database on a distant computer system. That is, users now have access to the data stored on other computer systems (e.g., an IBM ES/9000 computer system with a SQL/DS database). A user can interact with multiple remote databases during a single database transaction. Content Manager OnDemand for iSeries (5722-RD1) Content Manager OnDemand for iSeries provides automatic loading of nonspooled data in the Integrated File System, such as PC files. This frees the end user from manual intervention of loading PC files into OnDemand Common Server environment. Text search is enabled for AFPDS documents in Common Server environment. OnDemand commands take advantage of OS/400 spooled file attributes. The sample programs provided have been improved for both Common Server and Spool File Archive environments. Communications Support Communications facilities included in OS/400 allow a properly equipped iSeries computer to communicate with different computing equipment in a variety of ways. First, OS/400 provides support for remote workstations, allowing terminals and printers to be located far away (e.g., Operating Systems 163 across the country) from the iSeries computer system itself. This allows remote offices to perform all the functions available to those users located in the same building as the iSeries. Further, OS/400 provides the programming support for communications with other computer systems (both IBM and non-IBM) such as eServer or zSeries systems, personal computers, UNIX workstations, and other iSeries systems. OS/400 includes support for the following protocols, the first four of which are used in wide area networks (including the Internet), the last four of which are used in local area networks: • Async • Bisync • SDLC • X.25 • TCP/IP • IEEE 802.5 (IBM token-ring networks) • IEEE 802.3 (Ethernet networks) • ISO 9314 (FDDI networks) • Wireless local area networks. In addition, the ATM protocols and devices may be used to increase the information flow rate between networks and systems using those protocols and devices. The point is that OS/400 comes with the programming required to support many different types of communications environments. Now let’s take a look at some of the more important communications protocols in use these days. TCP/IP TCP/IP Communications Utilities (#5738-TCl) allow iSeries servers to participate in communications networks that use the Transmission Con- 164 Exploring IBM ~ iSeries trol Protocol/Internet Protocol (TCP/IP). TCP/IP is commonly used over a Local Area Network (LAN) (e.g., Ethernet) as well as over the Internet, environments in which computer systems (e.g., UNIX-based systems) of different brands communicate with one another. The IBM TCP/IP Server Support/400 product (#5798-RWY) gives clients access to iSeries database files and folder files via Sun Microsystems’ Network File System (NFS), which is commonly used in TCP/IP environments. The TCP/IP protocol has become increasingly significant as the client/server environment has moved into a networked environment including both intranets and the Internet. Standards supported by iSeries TCP/IP include Dynamic Host Configuration Protocol (DHCP) and Domain Name Server (DNS). DHCP support allows the iSeries to dynamically assign Internet Protocol (IP) addresses when new hosts are added to the network, such as when a network station or PC is turned on in an intranet. DNS converts the text names as used in URLs to the 32-bit codes used for network routing. As an example, it converts www.as400.ibm.com to 205.217.130.11. Dynamic DNS provides interoperability with Windows 2000 and supports secure and nonsecure updates of the DNS, DHCP is enabled to the updated DNS, and a Java GUI with wizards is provided to simplify configuration functions. Other functions supported are TCP/IP dial-in via point-to-point and ISDN as well as full TCP/IP routing. The iSeries Navigator provides a Windows-like graphical interface to the TCP/IP configuration function. TCP/IP can be configured to start automatically at IPL time. In the case where a retransmission is necessary, it is possible to reconfigure parameters to attain better control of sockets by identifying a value to a time unit timeout. This provides an adjustable timer for a socket pair timeout after a connection is closed. It also allows the customer to configure values that TCP uses during the retransmission processing to determine when to change to a new route or abort a connection. Remote service is supported over TCP/IP for either a DSL (Digital Subscriber Line) connection or a Dial-up client. The remote iSeries VPN client secures the VPN connection across the Internet to Nortel VPN Security Gateway, enabling direct access to iSeries eService Servers. The iSeries supports point-to-point (PPP) over Ethernet to exploit DSL for Internet access. Point-to-point includes Radius Client support, DHCP proxy client support, support for consolidated spoolfile output, and Communications Trace and Trace connections information to improve manageability. Operating Systems 165 It should be noted here that iSeries supports the IPv6 platform. IPv6 is a re-architected base infrastructure for the Internet. IPv6 allows a customer to build, test, and debug applications for the next generation of the Internet based on IPv6 using ILE and OS/400 PASE programs. Support includes Key Sockets APIs and iSeries Navigator changes to allow application and middleware providers to be ready for rapidly approaching TCP/IP changes coming with IPv6. Filtering of the IP packets can be based on the remote system’s IP address and applications, choosing to allow or deny for the remote access to filter. Network Address Translation (NAT) and filtering activities can be journaled. The entries will be added each time IP packets are examined, IP addresses are translated, or rules are updated. The user can choose to start the journal or not. As discussed in Chapter 5 under firewall, users have the opportunity to change IP addresses of IP packets going out from the net so that the internal addresses are not shown to the external hosts. This secures the internal network. Wizards have been added to iSeries Navigator to allow the most common filtering configurations to be accomplished by novice-level network administrators. Configuring of the required IP filtering rules in support of VPN is eliminated in the majority of cases, including the implicit IKE rules that allow IKE (UDP 500) traffic without explicitly coding the required filter rules and no need to explicitly code IPSec policy filters. NAT provides a technology called IP masquerading, which allows multiple users to share a single public IP address. NAT translates the internal IP addresses to a single specific IP address using the unique port numbers assigned to the internal IP addresses. Virtual IP Addressing (VIPA) provides network load balancing and fault tolerance between multiple IP interfaces (adapters). Outgoing balancing and incoming balancing work differently. Outgoing balancing is done through the routing configuration. Incoming balancing needs an external router capable of distributing IP packets to multiple interfaces. The distribution information is provided to the routers by the RIP protocol. Using routers, the load balancing enables multiple redundant paths from the server to the network, providing horizontal bandwidth growth and high-availability tolerance for link or router failures. Figure 4.10 provides an example of TCP/IP-enabled dial-on-demand networking. In Figure 4.10 a switched point-to-point connection is established only when demanded by either the central site or one of the remote sites. The types of connections can be mixed and matched to the available connection capabilities—analog lines up to 33.6 KB, switched Exploring IBM ~ iSeries Central Site Chicago Remote Office Portland AM FL Y Remote Office Boston Remote Office Dallas Figure 4.10. Remote Office Atlanta Example of iSeries dial-on-demand networking. TE 166 digital up to 56 KB, and ISDN at up to 128 KB. Figure 4.11 shows an integrated TCP/IP load-balancing connection for a high-volume e-business server to either an intranet or the Internet. File Transport Protocol (FTP) graphical client support includes the UNIX list command. Directories other than database libraries can be used as the initial working directory, and files larger than 2 GB can be transferred. Options are added to create new database files. FTP supports the ability to transfer files larger than 2 GB in all file systems that support the large file sizes. Database files containing null field data can also be transferred. Transport Layer Security (TLS)/Secure Sockets Layer (SSL) support for server authentication exists on the native FTP client, allowing secure sessions with compatible servers. This support allows the specification of whether FTP session data, including the login ID and password used for authentication, is encrypted. SSL can also be used for secure transmission of files. The administrator is allowed to limit some or all FTP functions by user profile without requiring writing an exit program. The performance has been improved when transferring large files over high-speed links. Team-Fly® Operating Systems 167 Router Intranet High-volume e-business server Router Figure 4.11. iSeries integrated TCP/IP load balancing for a high volume e-business server. SMTP scalability has been improved by extending the number of inbound and outbound connections from sixteen to unlimited and by changing the Domain Name Server (DNS) resolver to support large ISPs; as a result, the SMTP client processes all mail exchange records returned by a domain name server query. An option exists to track delivery status and mail statistics using journaling. There is an option that forces all mail received by the iSeries SMTP to be processed by the iSeries Mail Services Framework (MSF). A dial-up mail retrieval capability has been added to support ISP mail handling. Multiple domain support is available for servicing mail for domains the iSeries is not a part of. Blacklist support has been improved. SMTP client has been added to meet the Kerberos interoperability requirement of time synchronization. Kerberos is an encryption security standard. Telnet Server provides native support for SSL, and the interactive capacity of TCP/IP-attached workstations has been increased. Client authentication support provides a mechanism to authenticate a client before providing an iSeries screen. Telnet Server also supports long passwords up to 128 characters. To support fault tolerance and high availability, the iSeries allows the definition of a Virtual IP address on the same network as defined on other, physical interfaces. Given this configuration, the iSeries responds to Address Resolution Protocol (ARP) requests for virtual interfaces, eliminating the need to define static routes or run a dynamic routing protocol such as Routing Information Protocol (RIP). This is referred to as Proxy ARP Routing. 168 Exploring IBM ~ iSeries Virtual Private Networks Virtual Private Networks (VPN) evolved from the need to ensure secure communications between networked computers. At considerable expense, companies established private networks. Firewall technology enabled these private networks to connect into the public networks (including the Internet) with some hope of protection against hackers. As the trend of network computing and e-business continues to evolve, secure communications need to be extended within the enterprise while allowing the public networks to be utilized. Standards are evolving to allow a uniform VPN solution across vendors. The iSeries VPN solution addresses four environments: • Intranets—secure connections within an intranet • Extranets or ValuNets—secure connections between intranets of different companies • Remote office/branch office—secure connections between intranets of the same company • Mobile Worker—secure connections from a mobile worker, using different ISPs to an intranet. There are security exposures at every point along an end-to-end path: on the Dial-up link, in an ISP’s access box, on the Internet, in the firewall or router, and in the corporate intranet. To be effective, VPNs must address the following requirements: • Data origin authentication to verify that each datagram was originated by the claimed sender • Data integrity to verify that the contents of a datagram were not changed in transit, either deliberately or due to random errors • Data confidentiality to conceal the clear text of a message by using encryption • Replay protection to ensure that an attacker cannot intercept a datagram and play it back at a later time Operating Systems 169 • Key management to ensure that your VPN policy can be implemented throughout the extended network with little or no manual configuration • Performance and availability to ensure that the VPN does not hinder your business operations, but grows as your business grows • Interoperability to ensure that your VPN uses standards-based technologies to maintain interoperability with other VPN vendors. UDP-encapsulated IPSec is a standards-based protocol that solves the problem of end-to-end security for networks and firewalls using Network Address Translation (NAT) when using the IPSec protocol. This reduces the risk associated with doing business on the Internet when using end-to-end IPSec security on a Virtually Private Network. The IPSec protocols have three main components—an authentication header which provides data origin authentication, data integrity, and replay protection using hashed message authentication codes based on shared secrets, and does not encrypt datagram content; an Encapsulating Security Payload (ESP) which provides data confidentiality by encrypting the payload of IP packets by using cryptographic keys; and the Internet Key Exchange (IKE) protocol which dynamically generates the cryptographic keys providing rekeying while VPN is running, using a two phase approach to protect keys and data. The keys themselves are never entered or communicated between servers, but are derived using agreed inputs and algorithms by each of the key servers. The IP Payload Compression protocol (IPComp) is intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. This can result in an increase of overall performance over slow or congested links. The IPComp function must be performed before any IP security processing, and before any fragmentation of datagram for an outbound IP datagram. On the inbound IP datagram, the decompression must be performed after the packet reassembly and completion of all IP security processing. Encryption support includes, in addition to DES, RC4 and RC5. RC4 is the most widely used stream cipher. It is used for file encryption and SSL and is faster than DES. RC5 is a fast-block cipher. Both RC4 and RC5 are optional IPSec ESP transforms. The iSeries Navigator provides three VPN diagnostic tools consisting of a connection manager job log, a VPN Key manager job log, and a service-trace capability. The VPN GUI can also make use of the Java Trace facility in iSeries Access. 170 Exploring IBM ~ iSeries TCP/IP Remote Access Extensions The remote-access dial-up solution for mobile users’ Virtual Private Network is used to support dial-in access to a corporate network whose users are all company employees. The standards group defined a tunneling protocol called Layer 2 Tunnel Protocol (L2TP) which extends the span of a point-to-point (PPP) connection. Instead of beginning at the remote host and ending at a local ISP’s point of presence (PoP), the “virtual PPP” link now extends from the remote host all the way back to the corporate gateway. The remote host appears to be on the same subnet as the corporate gateway. When used in conjunction with IPSec, L2TP provides a cost-effective and secure remote access for mobile users. Systems Network Management Having iSeries systems participate in a communications network is one thing, but managing that communications network is something else. Systems network management tasks include such things as problem determination, problem tracking, making network configuration changes, and distributing necessary changes. In addition to the management tasks, the iSeries provides operations monitoring, automated operations, problem management, software distribution, change management, backup and recovery, media management, security, performance management, and capacity planning—not only for the iSeries systems in your network, but also for the attached clients. The user is not involved in the following activities because the system performs them automatically: problem data collection and logging; hardware problem prediction and logging; automated configuration and resource data logging; performance data capture and logging; alert generation, logging, and reporting; and Electronic Customer Support (ECS), which provides automated problem reporting, electronic PTF selection/distribution, automated service dispatching, and an electronic interface to the IBM information/database. This automation allows a reduction in staff. The iSeries will do the distribution automatically, take care of the security related to the software, detect the problems that occur on the clients whether those clients are from IBM or other vendors, and provide backup and recovery for those clients as required. The distribution of the functions that accomplish these tasks within the iSeries is accomplished under a set of programs named Systems Manager/400 within OS/400. The next section shows how this might work between an iSeries system and a System/390 computer. Operating Systems 171 The necessary systems network management functions vary depending on the type of communications network involved. For example, in a simple token-ring network, OS/400 can automatically notify the network operator of any problems that develop in the token-ring adapter or cable and can record the error to help in problem determination. In more complex communications environments, OS/400 has other functions that help manage the enterprise. Suppose an iSeries in Pittsburgh is part of a network managed from a central System/390 computer located in San Francisco. The network operator in San Francisco uses a System/390 program called NetView to manage the entire network. Now a problem develops in the communications link between the iSeries in Pittsburgh and the System/390 in San Francisco. OS/400 automatically notifies the network operator in San Francisco that a network problem has been detected. This is done through an alert message that is automatically sent by OS/400 to the computer in San Francisco. Once an alert notifies the network operator of the problem, several OS/400 functions help identify and correct the problem. First, the Network Remote Facilities (NRF) program allows the network operator to interact with the iSeries as if the System/390 terminal in San Francisco were actually a remote iSeries workstation in Pittsburgh. Using another OS/400 network management feature called the NetView/Remote Manager (NV/RM), the network operator can also issue network commands to test the health of network elements (e.g., modems). Once the cause of the problem is determined, the necessary fix can be put into place. To exchange files between the S/390 host (running MVS/ESA) in San Francisco and the iSeries in Pittsburgh, the NetView File Transfer program (5730-082) can be used. Thus, the San Francisco-based network operator can use his or her expertise to analyze and fix the problem without having to travel to Pittsburgh. This kind of network-management environment makes for speedy problem determination and correction, resulting in reduced system downtime. Systems Network Architecture OS/400 supports IBM’s Systems Network Architecture (SNA). This is a published set of rules governing various aspects of computer communications from protocols (e.g., SDLC) to document formats (e.g., Document Content Architecture, or DCA) and electronic mail (e.g., SNA Distribution Services, or SNADS). It is SNA that provides the common ground on which different types of computer equipment can efficiently 172 Exploring IBM ~ iSeries exchange information. OS/400’s Advanced Peer-to-Peer Network (APPN) architecture has been adopted as part of SNA. Further, APPN support has been expanded (APPN end-node support) to allow more-direct interaction with traditional SNA networks. Wireless Local Area Network The IBM Wireless Connection for iSeries (5798-TBW) is a networking software program for the OS/400 operating system based on the TCP/IP sockets program connecting real-time 5250 mobile devices with the iSeries. A separate feature allows multiple instances of the wireless connection program to run on the same iSeries, allowing large users to consolidate smaller iSeries systems into one or more larger iSeries data centers. The system administrator can name PTC device sessions, change the PTC configuration without first ending Wireless Connection for iSeries, remap the PTC keyboard, and reformat the PTC screen to display existing applications. This networking software product uses Internet Protocol (IP) and TCP/IP sockets to support wireless networks through locally attached Ethernet and token-ring LANs and at remote locations through routers, allowing easy integration between wireless networks and installed LANs. An existing LAN wiring infrastructure can be used for this connection by dropping an Ethernet or token-ring access point from the existing wiring. This combination of remote access and support for multiple instances of the program allows the management of the 5250 devices anywhere in the world. S/390 Communications Support The iSeries Communications Utilities (5738-CM1) software product complements the communications function of OS/400 for interacting with System/390 computers and eServer zSeries systems. This set of programs augments OS/400 communications functions in the area of interchanging electronic mail and files with various System/390 computer environments over an SNA communications network. For example, iSeries Communications Utilities allows iSeries Office users to exchange information with users of the OfficeVision/VM and OfficeVision/MVS. These programs run on the System/390, providing those users with functions (e.g., electronic mail and calendaring) that are now available on the Domino for iSeries product grouping. The other basic function provided by iSeries Communications Utilities is called the Remote Job En- Operating Systems 173 try Facility (RJE). RJE allows an iSeries system to emulate an RJE workstation used to submit batch jobs to or receive output from System/390 computers. Figure 4.12 illustrates one method for connecting an iSeries system to a System/390 computer. iSeries Access Family (5722-XW1) Client Access for iSeries is now called iSeries Access. Many of the Access components are included with the Operating System. The Access family of products provides iSeries-to-PC connectivity and function. Access has been divided into two server components, iSeries Access for Windows (5769-XW1) and iSeries Access (5769-XY1). Access supports the full 32-bit version of Advanced Function Print (AFP) Workbench Viewer. The viewer can be used to display, on the PC, information stored in iSeries spooled files (AFP and SCS). Full-page documents are completely rendered on both Windows and OS/2. Image files (such as those stored in GIF, TIFF, or JPEG) can be viewed on a PC. There are three client functions included in iSeries Access Family for Windows. The client functions are: Application(s) OS/400 Comm. Utilities SLIC iSeries 7861 Modem * Remote Location 7861 Modem System/390 Computer Central Location * Line used for Electronic Customer Support Figure 4.12. Example of a communications configuration used to attach an iSeries to an S/390 computer. 174 Exploring IBM ~ iSeries • iSeries Access for Windows client (5769-XE1) • iSeries Access for Windows 95/NT client (5763-XD1) • iSeries Access Enhanced for Windows 3.1 client (5763-XK1). The key functions included in iSeries Access are: • 5250 display emulation used for working with iSeries programs (e.g., RPG applications, OS/400 screens, using the command line, etc.) • 5250 print emulation so iSeries output can be directed and printed on PC printers • Uploads of PC data to the iSeries database • Downloads of iSeries database information to a PC file • The ability to print PC output on iSeries printers • The ability to save and share PC files in the iSeries Integrated File System • An ODBC driver provides for iSeries database access from PC programs • Support for other middleware such as remote commands, data queues, etc. • iSeries Navigator for working with OS/400 resources (only in XE1 and XD1). Business processes have been extended beyond printed output to archiving, indexing, retrieval, customer service viewing, reprint, and fax. The iSeries Access for Windows (5769-XE1) has been added to allow a client-access environment that does not require SNA, operates entirely in a TCP/IP environment, and is included with the iSeries Access Family for Windows product along with the other client members. Figure 4.13 Figure 4.13. x x x x(3*) x x x x x x x x x x x x x x x x x x x x x x x x(2*) x x(2*) x(2*) x x x x x x x x x x x x x x x x x x DOS Ext x OS/2 x Optimized OS/2 Windows 3.1 Windows 95 x x x x x DOS iSeries access detailed function chart vs. supported PC operating systems. (continued on next page) See Notes, page 190 License Management Enhanced Security Check Expired Password Password Encrypted Network Password Management 5250 Display Emulation RUMBA/400 (SBCS/DBCS) PC5250 (SBCS/DBCS) WSF (SBCS) AS/400 PC Console RUMBA/400 PC5250 5250 Print Emulation RUMBA/400 PC5250 WSF GUI Interfaces Graphical Access System Object Access AFP Workbench Subset Graphical Operations Multimedia Enablers Ultimedia System Facility Function Operating Systems 175 Team-Fly® Figure 4.13. x x x x x x x x(7*) x(9*) x x7*) x(9*) x TE x x x x x x x Windows 3.1 x x x x x x x(8*) x x x(8*) x x x x x Windows 95 x x x(9*) x x (1*) x x x (1*) x x x (1*) (1*) x x x (1*) x x x x OS/2 AM FL Y x x x x x x x x x Optimized OS/2 x x x(6*) x x x x x x x x x DOS Ext x x x x x x x x DOS iSeries access detailed function chart vs. supported PC operating systems. (continued on next page) See Notes, page 190 File/Database Functions Integrated File System Transfer Function Database Access GUI ODBC Version 2 Level 2 ODBC Version 1 Level 2 ODBC Version 1 Level 1 Remote SQL APIs Remote SQL Extensions Supports DRDA 1 Architecture Supports DRDA 2 Architecture Checkin/Checkout SNA Networks Twinax Asynchronous X.25 SDLC Token-Ring Ethernet ISDN API’s Supported EHNAPPC CPI-C 2.0 Sockets Function 176 Exploring IBM ~ iSeries Figure 4.13. x x x x x(9) x x x(9) x x x(9) x(5*) x Optimized OS/2 x x x(10*) x(5*) x x Windows 3.1 x x x(10*) x x x(10*) x(9*) x x x Windows 95 x(5*) x x OS/2 x(5*) x DOS Ext x(5*) x DOS iSeries access detailed function chart vs. supported PC operating systems. (continued on next page) See Notes, page 190 Communications Programs Included Subset of CM/2 NetSoft Router (32-bit) NS/Windows Router DOS Router (APPC) Communications Programs Supported NetWare for SAA 2.0 Microsoft SNA Server LAN Drivers MSDLC (32-bit) LAN Support Program (V1.38) included NTS/2 included TCP/IP Networks (native) Token-Ring Ethernet Asynchronous (SLIP) TCP/IP Networks (AnyNet) Token-Ring Ethernet Asynchronous (SLIP) APIs Supported EHNAPPC (via AnyNet) CPI-C (via AnyNet) - Sockets Sockets Function Operating Systems 177 Figure 4.13. x x x x(8*) x x x x x x x x(4*) Windows 3.1 x x(11*) x x x x x x Windows 95 x x x x x x x(5*) Optimized OS/2 x x x x OS/2 x x x x DOS Ext x x x DOS iSeries access detailed function chart vs. supported PC operating systems. (continued on next page) See Notes, page 190 TCP/IP Stacks Supported IBM DOS (included) FTP OnNet 1.1 (Windows) Microsoft WFW (32-bit) Novell (V4.2) WRQ V4.01 (Windows) NetManage Chameleon (Windows V4.01) Microsoft Windows 95 (32-bit) IBM OS/2 (included) Client Management SNMP Client Management Desktop Management (DMI) PC Update Central Administration Function Migration Utility Node Operation Facility (NOF) Mail/Office Functions MAPI (to POP3 server) MAPI (to OV/400 only) PC Text Assistant (OV/400, SBCS)x Application Command Level APIs Data Queues Function 178 Exploring IBM ~ iSeries Figure 4.13. x x x x(12*) x x x x x x x x x x x(8*) x Windows 95 x x x x x x x x x x x x x x x x Optimized OS/2 x x x x x x x Windows 3.1 x x x x x x x x x x OS/2 x x x x x x x x x x x x DOS x x x x x x x DOS Ext iSeries access detailed function chart vs. supported PC operating systems. (continued on next page) See Notes, page 190 Application Command Level (continued) Submit Remote Command Distributed Program Call OLE Enablers (APIs) Custom Controls Automation Command Level APIs on AS/400 Start PC Command (STRPCCMD) Run Remote Command (RUNRMTCMD) Copy to PC Document (CPYTOPCD) Copy from PC Document (CPYFRMPCD) Print Serving AS/400 Printers PC Network Printers AFP Printer Driver Integrated w/FAX/400 Programmer Tools PC Tools Folder (QIWSTOOL) CA/400 Toolkit Shipped with client PC Code Installable From PC Diskettes From PC CD-ROM From PC Server/FSIOA Onto PC Server Function Operating Systems 179 Figure 4.13. iSeries access detailed function chart vs. supported PC operating systems. (continued from previous page) (1) Stand-alone Communications Manager/2 (CM/2) can provide this connectivity. AS/400 Client Access can also be used in conjunction with this CM/2. (2) DBCS is Japanese only. (3) Not supported on native TCP/IP networks. Is supported on TCP/IP networks when using AnyNet. (4) Applications (such as TELNET) are not provided with the stack. Supports English only SBCS (DBCS data transmission supported). (5) Supports English SBCS/DBCS. (6) Supports SBCS only. (7) Windows 3.1 Client NS/Windows Router supports CPI-C Version 2.0 + optional classes for Data Conversion, Queue Level Non-Blocking, Full Duplex and Callback functions. Windows 95 Client NetSoft Router supports CPI-C Version 2.0 + optional classes for Data Conversion only. (8) Windows 95 Client provides 32-bit APIs. The Windows 95 Client also supports the Windows 3.1 Client APIs, so applications written to those 16-bit APIs can also be run over SNA/APPC networks or TCP/IP networks (with AnyNet). (9) Works with Client Access but is not included in Client Access package. (10) OS/400 provides SLIP dial-in support for TCP/IP networks in V3R2 and V3R7. For PC users connecting to V3R1/V3R6 systems, PPP can be used to dial into a gateway, then connect to AS/400 via TRN or Ethernet. TCP/IP stack being used in PC must also support dial-up in order to use this capability. (11) POP3 server provided in OS/400 V3R2 and V3R7 only. (12) Limited support; client administration restrictions (for example, cannot customize functions available to individual users). Notes: 180 Exploring IBM ~ iSeries Operating Systems 181 demonstrates how the various Access functions support different operating systems. Support for Client Access for Windows 95/NT and Client Access Enhanced for Windows 3.1 has been discontinued since July 2002. iSeries Access for Windows The iSeries Access for Windows (5769-XE1), which was previously known as Client Access Express for Windows, is a 32-bit client program that does not require the presence of Systems Network Architecture (SNA) and uses only TCP/IP for its connectivity protocol. The TCP/IP program used is the standard TCP/IP program shipped with the Microsoft 32-bit operating systems. (Other Winsock-compatible stacks can also be used.) This client does not support routers and does not contain any screen scrapers. The iSeries server must include OS/400 Version 4 Release 2 or later. Access runs on PCs installed with Microsoft Windows 98, 2000, XP, and NT 4.0 (workstation or server) operating systems. Included with the Microsoft NT environment is support for Terminal Server Edition (TSE), which enables the NT server to be used as a gateway between end users and the iSeries. Also included is the Microsoft Internet Information Server (IIS) environment with a version called Peer Web Services that provides iSeries database access from Web pages. The ODBC and OLE DB components are ported to run natively on 64-bit Windows (on Intel Itanium hardware). Most other components run in 32-bit mode on 64-bit hardware. (Print drivers and SSL support do not run with 64bit applications.) Users of Windows 2000 PCs configured for NTFS can now write to most files, enabling traces, diagnostic information writes, and Data Transfer requests. Highlights of the Access client content are: • Supports TCP/IP connectivity • Uses iSeries NetServer for PC file serving and network print support • Contains 32-bit client/server application enablers for iSeries (e.g., OLE DB provider, ODBC driver, ActiveX Automation Objects, Remote command, and Data Queues) 182 Exploring IBM ~ iSeries • Delivers GUI for iSeries OS/400 functions through its iSeries Navigator function • Improves administration for PC users from a central iSeries system through improvements to Microsoft System Policy support and Navigator Application Administration. Secure Sockets Layer (SSL) is provided for client functions to improve TCP/IP security. The user ID and password sent between the desktop and the iSeries is encrypted. The user has the choice to select what is encrypted. Server authentication is used to ensure connection to the intended iSeries, diminishing the possibility of spoofing in an Internet environment. Access for Windows also supports the use of a Kerberos server for authentication to an iSeries with Kerberos tickets sent to the iSeries in place of user ID/password and 128-bit encryption. A full-function AFP Workbench is included. The viewer can display on the PC information stored in iSeries spooled files (AFP or SCS) as well as image files (files stored in GIF, TIFF, or JPEG formats). Local and remote-console access are included through Operations Console. Microsoft technologies are exploited through the inclusion of 32-bit client/server application enablers, OLE DB Data Provider and Active X, ODBC driver, Remote Command, and Data Queues. The iSeries Access for Windows client includes the PC 5250 Operations console function, enabling PC workstations to locally or remotely perform iSeries system operations and services from PC 5250 emulation via an iSeries System Console Session, including the graphical control panel application. PC 5250 support includes Personal Communications 5250 V5.5 emulator, a bypass sign-on that can be used in conjunction with Kerberos tickets to avoid a sign-on screen, Hindi and Japanese code page 1390/1391, wrap-pasted text that allows copy/paste of text across fields and lines without breaking a word or ending a line with an invalid word, movement of +/– sign before the number when copying/pasting, and improved error messages. PC5250 emulation options allow the user to save changes when exiting the session, and a connection dialog allows the user to specify a default user ID to be used. Policies can be used by administrators to limit the capabilities of end users. VBScript has been upgraded to Version 5 to make it consistent with Internet Explorer V5. Toolbox for Java provides a generic framework and consistent programming interface for working with various iSeries objects and lists. Text can be converted in bidirectional languages, such as Arabic and Operating Systems 183 Hebrew, between iSeries and Java formats. A pool of iSeries objects can be managed to share and manage connections to your server, including JDBC connections. Faster string conversions are provided as a result of Toolbox for Java’s incorporating its own conversion tables. Data transfer provides an array of GUIs for both desktop users and programming enablers for application programmers to retrieve data from an iSeries database or to store PC file data in the iSeries database. Thirty-two iSeries files can be selected and data transferred with a single request to a desktop display, a PC printer, a PC file, or an HTML file, or directly into an Excel spreadsheet. When transferring a spreadsheet formula cell, Data Transfer determines the numeric value of the cell. Specified records or fields of records can be selected and transferred. Wizards can create, modify, and run transfer requests or save them for later use. Batch transfers are also supported. A transfer can be auto-run or be part of a start-up session. Wizards can be used to create a new iSeries database file definition for PC file upload requests. When working with PC files, Data Transfer has an option to retain trailing spaces from character data when writing to a Tab Delimited Text file, reducing the confusion caused by not knowing whether the field value was null or simply all spaces. An option has been added to ASCII text file details to allow numeric fields to be padded with leading zeros instead of spaces. Database information can be inserted directly into a section of an existing HTML file, enabling the update of part of a Web page while leaving the remainder intact. Datalink commands for linking to HTML tables are supported. All functions of the Express client, with the exception of the functions of PC 5250 Display and the functions of Print Emulation and Data Transfer, can be used without acquiring a license for iSeries Access for Windows product. The handling of CCSID data has been improved by the addition of an option to the File Details panel, allowing users to manually set the CCSID of their data. ActiveX automation objects can be used to programmatically run Data Transfers. The automation objects can configure, load, save, and run transfer requests with few lines of code. These automation objects can be used by many development languages including Visual Basic, VBA, C++, and Lotus Script. Other iSeries database Access improvements include: • The ODBC driver capabilities include enhancements to the setup GUI, Microsoft Transaction Server (MTS) via XOPEN/XA interfaces, Wide API set, Unicode SQL statements, static cursors, 184 Exploring IBM ~ iSeries data compression direct conversion of data to the column CCSID for parameter markers in SQL statements, and support for 8-byte integers (BIGINT). (MTS is a component-based transaction processing system for developing, deploying, and managing high-performing scalable, and robust enterprise, Internet, and intranet server applications.) • ODBC and OLE DB supports the ROWID function, 64K SQL statements, and additional descriptor information. • OLE DB can support updatable cursors for the SQL dialect. • The ODBC and OLE DB are thread safe. • Support for 8-byte integers (BIGINT). • Data can be transferred to/from float and double fields in database files. • Data can be accessed from multiple IASPs. • Data transfer supports for Web serving: – The default autosize for HTML downloads is 128 KB, but the value can be changed. – The HTML details panel includes support for writing to a UTF-8 file, allowing Web pages to contain characters from many different character sets. – More than 256 columns of data can be uploaded to a database file. – Lotus 1-2-3 V9 file formats are offered. Migration to iSeries Access for Windows is supported from: • Client Access Enhanced for Windows 3.1, and Client Access for Windows 95/NT • Client Access for Windows 95/Windows NT (V3R2 only). Operating Systems 185 iSeries Access for the Web The iSeries Access for the Web product is intended for casual iSeries users wanting simple-to-use browser access and includes support for Linux and Network Station. Support is also provided for users wanting brief Internet access to their iSeries system and for loosely connected intranet users who need casual access. The iSeries Access for the Web (5722-XH1) runs on WebSphere Application Server V4 and on Apache Software Foundations Jakarta Tomcat. This version can also be configured to run on more than one Web application server concurrently. • iSeries Access for Web contains its own 5250 interface and no longer uses the WebSphere Host Publisher XML Gateway when starting 5250 sessions. Many additional capabilities are included in the 5250 interface, examples of which are: – Workstation ID (device ID) can be configured and provides wildcard support similar to the PC 5250 emulator in iSeries Access for Windows. – Two switchable views: Web view and traditional view, each fully customizable. – Function keys and page up and page down support (requires JavaScript, and works with IE 5 and later browsers. • Jobs support: Users can view jobs submitted, and server jobs working on their behalf. Commands used for managing these jobs include hold, release, delete, and view job log. • Batch commands can be saved and retrieved later. Searches for these commands can be performed by name or description. • Database results returned from an SQL statement can be in PDF. Users can configure functions such as page size, orientation, margins, table header and footer, column heading, table style, and alignment, or upload or download .XML, so that data can be interchanged with other XML-enabled applications. • File System functions are copy file, rename file and directory mail file, delete file and directory, and create directory. Exploring IBM ~ iSeries Users can e-mail the results of a database, CL or file command, or PDF view of print information to other users. This provides a one-step method of distributing information across a network even to non-iSeries users. • The Personal Folder Container resides on the Web server and can be accessed only by the owner. This can be combined with the mail function to notify users when new items are placed in a folder, providing an easy way to avoid sending large attachments, and can be used to improve workflow. • Access for Web can deliver AFP print output to the AFP viewer plug-in, and the user can select the spooled file from a list and click on a link that would result in the spooled file being delivered to the browser. • Web Access utilizes the PDF services of Infoprint Server for iSeries (5722-IP1). From the Web Access browser, customers can select output files and display or print them. The delivery mechanism employed by Web Access passes the selected spooled file to the PDF subsystem, gets back the PDF file, then passes the PDF to Acrobat which automatically opens the file in the Web Access browser. GIF viewing is improved with 300 dpi resolution and more printer-friendly views. • IBM WebSphere Application Server (WAS) - Express or iSeries • WAS V5 for iSeries • WAS V4 plus latest PTFs Advanced Edition (AE) for iSeries • WAS V4 Advanced Edition Single Server (Aes) for iSeries • Apache Software Foundation’s Jakarta Tomcat (included with the IBM HTTP Server) AM FL Y • TE 186 XML Toolkit for iSeries (5733-XT1) The XML language has been identified as a solution to the problem of information exchange between applications and within business-to-busi- Team-Fly® Operating Systems 187 ness environments. It is simple, extensible, and non-proprietary. XML parsers’ APIs assist in the creation, navigation, or modification of the content of an XML document. The XML Toolkit for iSeries assists in the general industry movement toward XML by providing an interface to an XML parser for procedural language use, such as RPG, C, or COBOL. This refresh of the XML Toolkit provides support for V4 and V5. The XML parsers for C++ and the procedural languages are based on cross-platform, Apache open-source code compliant with W3C XML industry standards. The latest refresh is consistent with the Apache Software Foundation’s Xerces-C 2.1. WebSphere Host Access Transformation Server WebSphere Host Access Transformation Server is a Web-to-host program that extends host applications such as HTML to Web browsers and converts green screens to GUIs. This software, by presenting users with a familiar point-and-click interface, reduces end-user training costs and improves productivity. The rules-based transformation engine converts host screens to GUIs in real time and requires no changes to the host application. The implementation speed can extend legacy 5250 applications to the Web within a few hours of loading the software. iSeries Access for Wireless iSeries Access for Wireless provides access to iSeries administrative functions and development tools intended for wireless devices such as personal digital assistants and Internet-enabled phones. This product is delivered with OS/400. WebSphere Host Publisher V4 WebSphere Host Publisher V4 is compatible with WebSphere Application Server V4 (WAS-V4) and requires that WAS-V4 be installed. WebSphere Host Publisher is a business-to-business application connector offering a development environment on a PC using task-oriented GUIs, which generates fully customizable Web pages. WebSphere Host Publisher uses an HTML/JSP editor and business logic creation tools to create reusable Host Integration Objects that encapsulate host interactions and data retrieval. Host Publishers runtime environment provides session management, license monitoring, run-time administration, load 188 Exploring IBM ~ iSeries balancing, and log and trace management. The environment supports SSL encryption and DES-encrypted passwords, and supports integration with other IBM connectors. Host Publisher V4 supports WAS-V4 plus the latest PTFs, Advanced Edition (AE), and Advanced Edition Single Server (AES) for iSeries. Included in Host Publisher V4 are applications that comply to J2EE, an industry-standard architecture intended to reduce the cost and complexity of developing enterprise applications. The pages produced are at JSP 1.1 level, and the applications built are at the EJB 1.1 specification level. Migration tools are available to support movement from earlier versions of the above elements of Host Publisher. Host Publisher Integration Objects and EJB Access Beans are enabled to become Web services. Host Publisher supports multiple languages. If the IBM Support Center becomes involved, a Software Maintenance Utility product can help in the application of software fixes. This command line tool scans the product and creates a package containing documentation and files for the support team to use in troubleshooting. Lotus Notes Client Support The Lotus Notes client can be used on all desktops running either the Express client or the Windows 95/Windows NT client. Lotus Notes can be used with Lotus Domino for iSeries. Lotus Notes supports Internet SMPT/MIME mail standards and can be used as a client to the post office services (POP3) built into OS/400. Lotus Notes client supports e-mail, calendaring, Web browsing, and information-management features. The iSeries Navigator function is also packaged with iSeries Access for Windows. Access for Windows client uses SSL for Client Encryption. Client Encryption includes an SSL for Windows 95/Windows NT and an SSL for Java. The 5769-CE1 provides 40-bit encryption; 5769-CE2 provides 56-bit encryption; and 5769-CE3 provides 128-bit encryption for the United States and Canada only. Commitment Control and Journaling Two other functions of OS/400 are commitment control and journaling. Commitment control allows an application program to be designed so that a user must complete all changes related to a database transaction before the transaction is permanently reflected in the database. This helps ensure the data integrity of the database in the event of a system Operating Systems 189 failure in the middle of a transaction. It also allows a transaction to be canceled in process if the user feels the transaction is erroneous. Journaling is a task performed by OS/400 in which every database transaction, in addition to changing the database, is stored in a separate file of transactions. This journaling works in conjunction with normal backup procedures to allow for recovery of database information in the event of information loss—for example, if the information in an iSeries database becomes corrupted through a user error or hardware failure. The recovery process would involve loading a previously made backup tape and restoring the database through a simple restore command. However, none of the database transactions made since the backup tape was made would be reflected in the newly restored database. Thus, the database has been recovered only to the point at which the last backup copy was made. Thousands of transactions may have been made since the last backup, and these will have to be reapplied to the restored database. This is where journaling comes in. Because all transactions performed since the last backup are stored in the separate journal area, these transactions can automatically be applied to the newly restored database to bring it to the point immediately before it was corrupted. Without journaling, every transaction performed since the last backup would have to be manually reentered, which can be a very time-consuming process. Remote journaling allows database changes to be sent immediately to another system for high-availability applications to help off-load central processing unit consumption from the source machine so that it can achieve more throughput by capturing and transmitting journal images between source and target systems. This can significantly reduce the time and effort required to reconcile source and target databases following a system failure, because database changes are transported immediately to the remote system, ensuring no loss of transactions. Backup/Recovery As users begin to use the iSeries system, the disk storage begins to accumulate business information that often is vital to the day-to-day operations of the business. This information becomes an asset to the business and should be protected as such. OS/400 provides several functions that protect against loss of information from user errors, hardware failures, intentional corruptions, and so forth. These include backup/recovery 190 Exploring IBM ~ iSeries (BRMS/400), commitment control and journaling, Tivoli Storage Manager V5.1, iSeries Navigator, disk-failure recovery, utility-failure recovery, and SMAPP. First, the system’s operator can make backup copies of the information on disk storage to magnetic tape. With OS/400 these backup copies can be made while users are actively using the systems. This feature is called save while active. Before the save while active function was provided, the systems operator had to regularly reserve a block of time and dedicate the iSeries system to backup operations, making it unavailable to the users. Now the backup operations occur while users are still performing useful work. If the information on the iSeries disk storage is lost, the backup tapes can be used to restore the iSeries disk storage to the state at which the last backup was made. With the additional journaling function and the Tivoli Storage Manager V5.1 plus BRMS/400 functions of OS/400, not only can all transactions subsequent to the backup but prior to the failure be posted to the restored information, but recovery of the lost data can be accomplished without the users being aware of its occurrence. This typically completes the recovery procedure, and the information on the iSeries system is restored to the point just before the failure occurred. Support on save commands for generic library names and omit options provide flexibility in defining which libraries and objects to save and allow usage of multiple tape drives to reduce the time required for a save operation. Multiple concurrent restore operations using two or more tape units can be used to restore objects to a single library or to restore document library objects to a single auxiliary storage pool. Most save and restore commands support using multiple tape devices or multiple resources in a tape library in parallel. This reduces the amount of time required to save and restore very large objects. The previous save rate was limited to the throughput capabilities of a single tape; by using multiple tapes in parallel, the maximum throughput can be increased. Save menu option defaults have been added to simplify unattended save operations. The defaults include save entire system, save system data only, and save all user data. The operations console makes it possible to provide remote console support equivalent to a full-function 5250 system console session. When the systems and operations staff are in separate locations, either can initiate remote backup/recovery operations. Transferring programs between systems in a network has been simplified by means of the capability to use recovery-program methodol- Operating Systems 191 ogy to a different system than the backup was performed on. A restore menu option was added to all unattended restores and restores to a different system. Tivoli Storage Manager V5.1 IBM’s Tivoli Storage Manager (TSM), using offline storage facilities, safeguards the organization’s data from hardware failures and other errors. TSM is able to scale itself to protect hundreds of computers ranging from laptops to mainframes running a dozen operating systems. Those computers may be connected together via the Internet, WANs, or LANs. TSM minimizes the administration costs of data protection and the impact to both computers and networks by centralizing the cooperative activity of the Web-based management, smart-data-move and store techniques, and comprehensive policy-based automation. Business-critical applications running 24x365 use optional modules to utilize TSM’s centralized data protection with no interruption to their service. Incremental backups affect only backup files that have changes since the last backup. TSM utilizes the disks and tapes in its storage hierarchy. The option exists for TSM to combine with BRMS to provide a single centralized backup and recovery solution to your entire storage server environment. The core functions of TSM include: • Data backup and restore. Backups consist of copies of your active online data stored on offline storage. If any online storage device fails, or a data error occurs, or someone accidentally deletes a file, the offline copy of that data can be restored to online active storage. • Managed data archive and retrieve. The copies of active or inactive online data retained on offline storage are referred to as data archives. Archives serve two functions: the maintenance of point-in-time copies of important data for regulatory or bookkeeping requirements, and the movement of inactive data from expensive online storage to less-expensive offline storage. TSM manages the data archives for a defined lifetime through the policy-automation engine, just like backed-up data. When required, TSM is capable of rapidly restoring the archived data, extending your data storage capabilities without the need for additional online storage. 192 Exploring IBM ~ iSeries • Protection for 24x365 business-critical applications. Applications remain available during backups with online, nondisruptive image backups. Image backups complement progressive incremental backups and can be used for faster recovery of large amounts of data in file systems with large numbers of files. • Support for small tape libraries (two drives and forty tape slots). Backup Recovery and Media Services/400 Backup Recovery and Media Services/400 (BRMS/400) is a systemsmanagement tool for managing backup, archiving, and recovery environments for one or more iSeries systems at a single site or across a network where the principal data exchange is by tape. BRMS/400 is designed to perform complex backups easily. The definitions of a backup and changes to those definitions are easy. Full error checking is performed, and messages are provided to the operators to ensure that errors do not go unnoticed. BRMS includes “EXITs” to allow processing of user commands or programs during the backup procedures. BRMS performs full, incremental, or noncumulative incremental saves; saves to save files; and save while active. BRMS/400 offers a step-by-step recovery in the form of a report printed after the nightly backups are complete. Recovery includes full and detailed feedback during the recovery process by means of an autorefresh screen, updated as each library is restored. The BRMS System Recovery Report steps include setting up standalone or media library devices for recovery, initializing BRMS functional authority information, updating system name in BRMS media information, configuring auxiliary storage pool devices, verifying auxiliary storage pool device names, and recovering Linux servers in a logical partition. BRMS/400 archives data from direct access storage devices (DASDs) to tape and tracks information about objects that have been archived. Locating data in the archives is easy because the restore can be triggered from a work-with screen. Dynamic retrieval for database files is possible, and archived files can be restored upon access with the user application. No changes to the user application are needed to initiate the restore. BRMS/400 provides a comprehensive inventory-management system for all tapes, cataloging and managing an entire tape library, as well as outputting reports as instructions to operators about required actions. Operating Systems 193 BRMS/400 provides for policy-driven backup, recovery, tape media management, and archive services for tape devices. This means there is an automatic recall of archived database files from tape devices to DASDs when required, which relieves the user from having to become involved. BRMS/400 is intended for the system environment with over fifty tapes and therefore may introduce excess complexity in the operation of a smaller system. TSM operations have a media policy limited to a maximum of sixty-four characters for passwords, the maximum allowed by TSM servers. The BRMS TSM client supports the PASSWORDACCESS GENERATE client option when used with the Tivoli Storage Manager OS/400 Client API, V4R2.1. The iSeries Navigator is intended to provide the backup/restore functions for this less-complex environment. In addition to these functions, BRMS can back up or archive lowvolume iSeries user data server including another iSeries, RS/6000, or S/390, or on the 3466 Network Storage Manager. BRMS provides the ability to back up a single library, or single library object, in parallel across any number of tape devices. Parallel backup enables a user to shorten the window of time required to perform backup by using more tape devices in the backup process. Using parallel backup with an automated tape library device allows a large library to be saved to all currently available resources. This reduces the administration involved in setting up a backup strategy by eliminating the need to design the strategy based on the current number of drives and the current objects. BRMS interfaces can be controlled, allowing administrators to secure the setup and functionality of BRMS from users not skilled in the administration and usage of BRMS. The BRMS functional-usage model can secure the following types of function from specific users, and each user can be allowed to use one function and not others (e.g., allow an operator backup functionality, but not the ability to recover objects): • Backup • Archive • Recovery • Retrieval • Migration. 194 Exploring IBM ~ iSeries The functional usage model allows the administrator to control specific setups such as a control group or policy. Users could use and view a policy but not be allowed to change the contents of the policy. Not supported by the base product are archive, dynamic retrieval, automated migration operations, or shared media. BRMS Network Feature The BRMS Network Feature enables a BRMS system to be connected to other BRMS network systems using a network. Networked BRMS systems can share the inventory and policies associated with media managed by a central BRMS system. An attribute has been added to the network Group that indicates whether the system is enabled for TCP/IP communications. If set to yes, BRMS communicates to other systems in the BRMS Network using TCP/IP. BRMS Advanced Functions Feature The BRMS Advanced Functions Feature enables BRMS advanced functions such as Hierarchical Storage Management (HSM) archive with HSM dynamic retrieval and automated Application Storage Pool (ASP) object migration. Parallel Backup also works with the advanced functions, allowing for parallel archive and parallel dynamic retrieval of a single object. Parallelism used in the dynamic retrieval of a large database file reduces the required time for the retrieval process. The Advanced Functions Feature can initiate archiving of database files, stream files, and documents based on frequency of usage. The frequency-of-use rule is based on the number of days used and is calculated based on a one-month period. The user can specify the value into the archive control group driving the archive operation. New commands provide object detail for duplicated media, initialization of BRMS functional authorities, renaming of the owner of the BRMS media information and history information before recovering to a system or logical partition with a name different from when the information was saved, and the reorganization of the BRMS databases. BRMS provides a plug-in to iSeries Navigator. The BRMS plug-in includes a move policy wizard and move policy properties to help create and maintain move policies and create new locations. Media functions and tasks enable the action and verification of media movement operations. Backup policy properties allow the specification of media libraries and save files and TSM servers as backup devices with options to enable and define parallel device backups. Operating Systems 195 It is possible to: • Specify the days of the week when running commands before and after the backup or add special actions (exits) to be performed during backups • Define the type of incremental backup to use • Specify what subsystems should be ended and restarted • Specify what job queues are to be held or released • Specify whether backup items are to be saved using save-whileactive. The backup policies folder can contain functions that allow the creation, update, and management of backup lists and the saving of backups to save files. Locations can be created, updated, and managed through the move policies folder. A media pools folder within the media folder enables the creation update and maintenance of media pools (classes). The backup history can be filtered based on expiration date, saved system, and disk pool name or number. The volumes-include panel can filter the volumes based on location, container, owning system, and volumes marked for duplication, duplicated volumes, or secured volumes. Specific maintenance functions can be selected when running maintenance and cleanup options. One or more BRMS reports of various types can be selected for printing on the iSeries server. Global properties in the plug-in allow the specification of TCP/IP to be used for BRMS network operations; also allowed are the specification of notification controls, sign-off exception, and IPL controls. The restore wizard allows the performance of point-in-time recoveries of objects saved using online incremental Lotus server backups and the restoration of objects saved to TSM servers, objects saved to parallel devices, or objects saved to save files. System-Managed Access Path Protection A function called System-Managed Access Path Protection (SMAPP), which automatically records the access path information according to a mathematical algorithm set by the user, has been added to the systemsmanagement function. Users tell the system manager how long they are Exploring IBM ~ iSeries AM FL Y willing to wait for recovery to take place after a long utility outage, and the system manager ensures that the access paths will be journaled frequently enough to achieve that recovery period. The recovery period may be identified to be either system-wide or by Application Storage Pool (ASP). An ASP is a grouping of files related to a common set of applications. The file grouping is generally both logically and physically related. In the case of a utility outage on a system with internal battery backup or a UPS power system, when the main storage data has been dumped to disk and the system then powered down, the access paths to the data dumped to disk have been lost if SMAPP has not been enabled. Before the main storage contents can be reloaded and processing resumed, the access paths to the data resident in main storage must be rebuilt. This can take many hours of interaction with the system administrator, or SMAPP can journal the access path information, and recovery time can be reduced to the identified time interval in SMAPP. Hierarchical Storage Management TE 196 Hierarchical Storage Management (HSM) interface support provides data management within a storage hierarchy consisting of high-performance disks, compressed disks, and tape devices. With HSM implementation, users can migrate data as it ages from fast disk devices to compressed disk devices, to optical devices, and then to tape devices. Data stored on tape devices is accessed just like data residing on disk. BRMS/400 is the application program providing the foundation for the HSM customer interface. BRMS/400 defines a new set of policies under which a user can determine when the different object types can be moved or migrated to the different levels of storage. OS/400 enablers include a new API (FREESTG) to support archiving one object at a time (which also eliminates the temporary copy on disk). The utility (WRKASP) handles the movement of data between the different levels of storage hierarchy. Using BRMS/400, the hierarchical storage management enables the migration of user libraries, folders, and spooled files between Application Storage Pools (ASPs), simplifying the archiving of database files, database members, and documents. Stream files can be migrated from disk to tape, or from a high-performance disk to a compressed disk. Dynamic retrieval provides files on demand for application access. HSM operates automatically and is policy based, requiring no application changes to implement and minimal maintenance support. The fast access, high ca- Team-Fly® Operating Systems 197 pacity, and high data transfer rate make the IBM Magstar MP3570 and 3575 tape subsystems excellent HSM tape-storage alternatives. Systems Management iSeries Navigator The iSeries is designed for office environments in which technical skills are usually limited. Systems-management tasks are simplified by iSeries Navigator. This product allows an iSeries system administrator to perform systems-management tasks through a familiar Windows-based Graphical User Interface (GUI). The new function emphasis is on pictures, not just icons. Wizards are used to perform many common tasks with a high degree of integration, not just standalone utilities. This makes it easier for users unfamiliar with iSeries systems to perform OS/400 tasks. Previously referred to as Operations Navigator, iSeries Navigator will be referred to simply as Navigator in the remainder of this book. Navigator supplies many iSeries functions used by system administrators and users on a daily basis, including job manipulation, message handling, printer management, printer-output handling, user and group administration, database administration, file systems, security functions, authorization lists, security and auditing policies, backup support, and hardware and software inventory. These functions may be accessed for a particular system from either a local or a remote system workstation. For example, a large company may have one iSeries system at the headquarters location and multiple iSeries systems distributed in other locations throughout the country or around the world. Rather than provide iSeries and OS/400 personnel at each of the locations, it often is desirable to have a centralized staff of experts who can support all of the iSeries systems throughout the company (a central help desk). That help desk can then coordinate all outside resources (e.g., IBM’s customer support structure or an application software company’s support system) as the single point of contact for the whole company. Management Central is an optional subcomponent of Navigator. Work management, as performed by Navigator: • Groups active jobs by subsystem and allows the customization of the active job lists including sort, include, columns, and short- 198 Exploring IBM ~ iSeries cut functions. Menu options added include Call Stack, Locked Objects, Open Files, and Library List. • Lists job queues allocated to active subsystems; lists all job queues defined on the system; allows jobs to be moved within and between queues using drag and drop; and provides menu options to work with jobs, hold, release, clear, or list the properties of the jobs in the job queues. • Lists all subsystems that have been started and provides the following menu options related to those subsystems: work with jobs, job queues, start, stop, and properties of the jobs on the job queues. The Database Navigator provides a pictorial view of database objects which includes tables, views, journals, indexes, keys, and constraints. Object menus are available to work on items in the pictorial view, and SQL statements can be generated from the existing DB objects. As part of Project eLiza, Navigator has some new work management functions. Those functions include: • System status • Seeing threads for a job and taking actions on threads • More job lists for jobs using IFS objects • Tape devices • Disk pools • TCP/IP connection jobs • Lock holders for objects, members, and rows • Locked objects lists include: – Lock space objects – System objects Operating Systems – 199 More • View the last SQL statement that ran • Improvement to viewing job logs (sort, print, and find). Also added are: • Output queue support to see output queues and their contents and to take actions on output queues. • Fix support for group fixes. The compare and update fixes wizard is more robust with: – Improved supersede recognition – Continuing when fixes are not available – Performing an update without doing a compare. • Support for standalone tape device and tape library, which includes actions to vary on/off devices and format, duplicate, display, and print tapes and cartridges; see the cartridges and tape resources in a tape library; and also insert and eject cartridges. • Disk management support to see parity sets and take actions on the parity sets such as start or stop parity, resynchronize parity, and change parity optimization. Additional disk pool support to create independent disk pools and disk pool groups that support libraries and databases. A graphics view option allows the user to view all or by disk pools, locations, etc., enabling the user to see units across all towers. The user can right-click on a disk unit to get a menu of options for that unit. This includes the administration of Windows Server (xSeries) disks as well as Windows users and groups. • Network support for IP Version 6 (IPv6); new wizards to create IPv6 and IPv4 configuration, interfaces, and routes; new communication lines folder; and the ability to create user-defined servers that will appear in the server jobs list; more Quality of 200 Exploring IBM ~ iSeries Service (QoS) support such as inbound connection rate control; and more packet rules and VPN support. • Windows Administration support to run a Windows command on an integrated IBM eServer xSeries; support to install the latest version and service pack, and to create a new open source disk file system for guest operating system logical partitions such as Linux. • Other new items such as verifying the central system connection, menu streamlining, basic system time synchronization, and auto-refresh support on all folders. Navigator includes support for TCP/IP configuration, including DHCP and DNS. This support is simplified by the use of wizards and GUIs. Servers can be configured to start automatically when TCP/IP is started and the status of the servers can be monitored. Navigator integrates the administration of Domino for iSeries, iSeries NetServer software, and the iSeries system’s Internet capability by launching a Web browser interface to configure HTTP Server for iSeries, Firewall, and IBM Network Station. Plug-in Application Program Interfaces (APIs) are provided for use by other applications to integrate into the iSeries Navigator program’s interface. From the Navigator window it is possible to drag and drop printer output to various printers and to the desktop, to set the Navigator windows so that Windows can refresh their content automatically, to open separate windows to monitor specific items of interest, to create desktop shortcuts to items within Navigator, and to find text within Navigator lists. PC users can view and end iSeries messages. Navigator graphical interfaces provide capabilities for improving operation and administration of the iSeries by means of the following: • Security Configuration Wizard • Real-time graphical performance monitor • iSeries DCE server setup and management • TCP/IP security setup for Network Address Translation (NAT) and IP packet filtering Operating Systems 201 • Network File System (NFS) server management • Viewing iSeries NetServer (SMB) server statistics • Managing remote journals and aliases, updating iSeries database table contents, and copying/moving capabilities between system database tables. An LPAR GUI makes it easy to view LPAR configuration and status. The LPAR GUI includes an LPAR configuration wizard. The iSeries Navigator is used to work with iSeries resources and for administering and operating iSeries systems. New graphical interfaces are added to iSeries Navigator for working with the following iSeries functions: • Folders in the integrated file system can be created, deleted, and renamed. Objects in the file system can be cut, copied, and pasted, or dragged and dropped between iSeries systems and PCs. • Database improvements include SQL performance monitor, SQL scripts, SQL indexes, stored procedures, LOBs, DataLink data types, and user-defined functions. • Virtual Private Networks (VPN) and application and network security have been added to TCP/IP for secure connections across a public network. Other TCP/IP functions include the ability to have multiple user IDs while using a single copy of Access. Each user ID can be using a different application. • The GUI interfaces that work with output queues and spooled files have been expanded and include ad hoc access to PDF and e-mail functions. These functions are active when iSeries Navigator detects that Infoprint Server (5722-IP1) is installed. One or more spooled files can be selected, PDF and e-mail parameters can be specified, and the PDF and e-mail operations may be interactively invoked. • Management central system group functions have been added to the hierarchy for object packaging and distribution, remote operations, PTF management, inventory, and job scheduler. 202 Exploring IBM ~ iSeries • Application administration of third party plug-ins is offered. • Microsoft policies are also supported. A maximum of 150 different policies can be enforced. Policy restrictions can be enforced on a per-user or per-PC basis. It is possible to selectively install only the needed Navigator functions, and system administrators can select which functions are available to specific users. Plug-in support allows anyone to add his or her own applications to Navigator. The plug-ins can be written in Java or Visual Basic. The application is distributed using iSeries Access Install. SystemView System Manager/400 The SystemView System Manager/400 (#5769-SM1) provides facilities that allow a central iSeries system/site staff to perform systemsmanagement tasks for a network of remote iSeries systems. It addresses the following systems-management needs: problem management, change management, Access/400 client inventory, problem tracking for those clients, and PC software management. System Manager/400 provides a GUI, session-management support, and support for a roving user—one who needs to use multiple workstations, but only one at a time. The user can move from one workstation to another and maintain the same capabilities and interface characteristics used on the prior workstation. In the area of problem management, System Manager/400 provides a way to maintain an electronic problem log. That problem log is managed automatically and includes the clients attached via iSeries Access. As users or the iSeries system itself reports a problem, that problem is automatically noted in the problem log. The problems are prioritized, and notes are kept on the activities associated with each problem. If IBM’s customer service needs to get involved, the problem, with all of its notes, is sent electronically to IBM’s support network. If the central support site has an S/390 computer system, System Manager/400 cooperates with the S/390, allowing all support activity to be performed from that system. In the area of hardware/software inventory and software management, SystemView System Manager/400 automatically detects what hardware is connected on the LAN networks and downloads the operating system required for Windows, OS/2, and so on. Operating Systems 203 OS/400 can provide automated tracking and management of co-requisite PTFs within co-requisite PTFs as a group. The risks and complexity in managing co-requisite relationships are reduced as a result of this cooperative effort. These PTFs can be downloaded across the Internet. Customers with a network of iSeries systems can use software intended for use on a remote system without having to install that software on the central site system. This saves DASD space and installation time. Management Central Management Central provides a way to do things to multiple systems with a single request, manages long-running tasks from a GUI asynchronously, and schedules tasks. Instead of connecting to each system individually, requests are sent to a system designated as the “Central System.” The iSeries servers connected to the central system are referred to as endpoints. Endpoints can be collected into system groups for convenience. Requests flow outward to the endpoints, and status and results flow back from the endpoints to the central server. Tasks can be long-running or scheduled. The Navigator PC obtains information from the central server, while passing requests to the central server. System performance monitors are integrated with jobs, allowing a graphic history function for seven days of history. Using Management Central technology, Navigator contains a compare and update menu option for system values on System and Endpoint pop-up menus. Management Central provides immediate and up-to-the-minute information about the systems being managed, making it possible for system administrators or operators with multiple systems and networks to gather, analyze, and react to system information. Systems can be grouped to allow the control and monitoring of multiple iSeries systems in a network from a central iSeries server. It is possible to monitor: • CPU utilization (average, interactive) • Interactive response time • Batch logical I/O • Transaction rates 204 Exploring IBM ~ iSeries • Utilization of disk space • Communications IOPs • Communications lines • Local area networks • Disk IOPs • Disk arm utilization • Machine pool faulting rates (maximum only) • Base user pool faulting rates • CPU utilization Lite (average only). With the capability of real-time graphical monitoring, it is possible to monitor multiple systems or groups, establish thresholds for each monitor, automatically execute programs/actions on threshold events, and view threshold events. TCP/IP security can be set up to include network address translation and IP packet filtering to accept or reject IP packets based on criteria. The latter capability provides one method for eliminating unwanted e-mail. The system can also be set up to manage an iSeries Network File System (NFS) server, including the exports and netgroups for that server. If NetServer is operating on an Integrated NetFinity Server, it is possible to view server statistics with optional automatic refreshing, shared objects being used by a session, and sessions using a shared object. Within a database, Management Central enables table contents to be updated, remote journals to be managed, aliases to be managed, and tables to be copied and moved between systems. In a Distributed Computing Environment (DCE), it is possible to set up and manage iSeries DCE services. For Lightweight Directory Access Protocols (LDAP), it is possible to set up and manage an iSeries Directory Server and publish user information to an LDAP directory. Operating Systems 205 System-Detected Software Problems When an error occurs, the OS/400 licensed program automatically creates symptom strings. The use of symptom strings eases the management of problems in the system and makes recovery faster by improving the customer’s rate of discovery of appropriate fixes. Problem resolution time is decreased when failure data is collected at the time of occurrence and the necessity to re-create failures is reduced. Management Central Methodology Management Central provides a methodology for managing multiple systems, system groups, and system group functions. Management Central includes performance monitors, support for remote operations, inventory collection, packaged-object distribution, management of software fixes, performance-collection services, and job scheduling. The primary components of Management Central include the following: • Collection Services is a tool for data collection which replaces the performance monitor with an emphasis on capturing data with minimum system impact. The data is not processed until needed. Flexibility is provided in what data is collected and how that data is managed. Collected data is written into a management-collection object. Management-collection objects may be created and destroyed automatically or retained indefinitely based on user-defined parameters. A performance monitor database is created based on the data in the management-collection object. The creation of the database can be deferred until a later time than the data collection or even on a different system. Also, only data of interest need be processed, and only over time intervals of interest. Multiple database views may be created from the same management-collection object. • Object Packaging and Distribution Graphical Interface provides a way to send objects from any file system to one or more iSeries in a network. It also includes features for restoring objects, taking snapshots of objects, versioning packages of objects, and posting execution of commands against objects. The functions Exploring IBM ~ iSeries can be performed on a group or network of iSeries eServers and can be scheduled for a convenient time. PTF Management Wizards for a distributed environment walks the user through comparing the PTF levels of multiple iSeries systems to a model system on which a proven set of PTFs have been installed. The wizard then performs the distribution and installation of any missing PTFs on the remote iSeries by identifying the system or group of systems to be updated. • Inventory for Multiple Systems can be performed using a graphical interface that enables the scheduling of regular inventory collections of hardware, software, and PTF information. The inventory collection can be for a group or network of iSeries systems. Using the data collected, it is possible to search for a specific piece of information and export that information to a PC application for analysis, or just compare information for multiple systems. AM FL Y • TE 206 Management Central Pervasive Management Central Pervasive extends a subset of Management Central capabilities to the wireless environment. This enables the management of multiple systems from tier-0 devices such as PDAs and cellular phones. Management Central Pervasive will also run in a workstation Web browser. With Management Central Pervasive it is possible to: • Watch system status of iSeries systems • Monitor performance on multiple systems including: – View real-time performance metrics – See if thresholds have been reached/exceeded – View the top twenty jobs or other related detail contributing to each metric – Start/stop metrics Team-Fly® Operating Systems • • Monitor specific jobs and servers on multiple systems, enabling the operator to: – View job-level and summary-level metrics in real time – See if monitors have triggered – Start/stop monitors Monitor message queues on multiple systems, making it possible to: – View job-level and summary-level metrics in real-time – See if monitors have triggered – View message details – Reply to messages – Delete messages – Start/stop monitors • Hold, release, or end a job on any Endpoint System • Run commands on any group of systems, allowing you to: • 207 – Choose from your predefined list of Management Central commands – Enter the command from the wireless device – View the distributed task status Manage Integrated xSeries Servers (IXS) through the ability to view the status of IXS servers, start up/shut down servers, run NT commands, and monitor IXS events that are routed to an iSeries message queue. 208 Exploring IBM ~ iSeries Enterprise Identity Mapping (EIM) Enterprise Identity Mapping is a Project eLiza initiative. Project eLiza is IBM’s approach to creating a self-managing, autonomic computing environment. Project eLiza is intended to help companies deal effectively with increased complexity, allowing for faster reaction to changing circumstances, permitting the realization of cost efficiencies, and enabling a focus on business needs. Project eLiza is a blueprint for self-managing systems aimed at creating an intelligent IT infrastructure capable of responding to unexpected capacity demands or system failures. EIM provides a technology that maps a user identity on one system to the user’s identity on another system. The operating system and applications can equate jsmith on iSeries to janesmith on an eServer zSeries system. The resulting single sign-on capability reduces the threat of password theft, reduces user identity management across the network, and simplifies the authentication processor for users. iSeries Performance Tools The IBM iSeries Performance Tools accesses system load information automatically logged by the system. With these tools, the performance of the system can be tuned and future performance requirements projected. The tools provide performance reports that can be as high level or as detailed as needed. System use, response time, and number of transactions are statistically treated. The expert systems-based advisor function assists the systems manager in interpreting performance analysis and often recommends specific actions. The iSeries Performance Tools helps the systems manager determine where the system is and where it is going in terms of capacity and performance. For smaller systems or those not requiring the function of iSeries Performance Tools, the Performance Tools/400 (5763-PT1) provides basic performance-planning tools. Also, the Performance Investigator/400 (PRPQ #5799-PRG) runs on a PC under DOS/Windows and graphs in real time (fifteen-second samples) items such as CPU use, response time, and so on. One PC can monitor up to sixteen iSeries systems. The iSeries Navigator can create and view summary reports and graphs. Instrumentation for performance supplies a wide variety of performance tools with information to help customers solve their performance problems, predict when they will need system upgrades, and monitor the current performance of their systems. Operating Systems 209 Performance Collection Services makes it easier for applications to plug in programs that enable application performance statistics to be collected and stored in the system performance database. The collection of performance information occurs on a continual basis, including much clearer and efficient reduction and analysis. This makes it easier and faster to identify which function in the system is contributing to a bottleneck so appropriate steps can be taken to expedite the problem’s repair. This collection is the first step in a multistage plan to better instrument and enable the system for continual measurement and analysis. LDAP-based directories provide integration for e-business. LDAP is being expanded beyond Apache, WebSphere Application Server, and WebSphere Commerce Suite to include Enterprise Identity Mapping and other solutions. The HTTP performance data is contained in the HTTP data-collection category for Collection Services. This performance data can be queried for analysis of HTTP server activity to achieve an understanding of what types of HTTP transactions are being processed by the iSeries. Examples of data types include static files, CGI, and Java Servlets. Performance Tools for iSeries generates reports based on the HTTP performance data with regard to transactions processed by HTTP server jobs. Performance Explorer (PEX) analyzes application performance and identifies performance bottlenecks. Performance Explorer has been improved as part of Project eLiza to include additional functions that are instrumented with user-defined events addressing specific server jobs used by e-business applications. This results in improvement in the ability to optimize and tune the server jobs and the applications that use them. The amount of time it takes to end a PEX collection has been decreased, as well as the overhead of PEX, enabling it to run longer and make it easier to find performance bottlenecks in the software being analyzed. PATROL for iSeries—Predict PATROL for iSeries—Predict (5620-FIF) uses existing performance data from Collection Services to provide comprehensive response-time analysis and predictive modeling capabilities. A “what-if” analyzer reveals the impact of changes such as load, configuration, and users across the iSeries environment. Users can prevent performance, service, and response-time problems before their occurrence and ensure ongoing success by providing the right hardware upgrades, at the right time. 210 Exploring IBM ~ iSeries The graphical planning capabilities provided by PATROL for iSeries—Predict consist of two components: • Create model functions for identifying OS/400 jobs and assigning work to workloads based upon user ID, job name, OS/400 subsystem, and other categories. Performance Monitor database files more recent than V4R2 are supported for input to creating the model. • A Windows PC GUI active on a workstation is used for validating the model and performing capacity planning scenarios. The capacity planning components provide the following functions: • CPU, disk, ASP (logical volume) capacity planning • Interactive feature utilization, variable interactive CPW for LPAR partition • Percentage growth per time period • HTML-based graphical displays for reports and bar charts. The available reports are divided into seven groups: • Validate model (predicted compared to model) • Multiple CPUs that can coexist in a single model • Task pads for status messages • Icons to indicate warning (threshold reached) • Guideline reached per resource • Ability to process performance data from multiple releases • Allows for “what-if” scenarios by changing the system configuration or workloads. Operating Systems 211 BEST/1 users should be aware of the following limitations in the first release of Patrol for iSeries: • No explicit modeling for IOPs and IOAs • No explicit modeling of separate memory storage pools • Limited Raid modeling detail • No batch job modeling • No release level or application-type performance adjustments • No configuration recomendations • No individual communications object modeling. NetFinity for iSeries NetFinity for iSeries (5716-SVA) enables the movement of systems-management tasks from end users to more-experienced system administrators. NetFinity contains an inventory server that collects hardware and software inventory information from the clients being managed and stores it in DB2 UDB for iSeries databases on the iSeries server. This information is used to perform management tasks such as software distribution, distributed monitoring, and remote control. NetFinity enables the system administrator to perform remote control of the PC clients, allowing the identification and correction of potential problems before they impact business. NetFinity also provides a graphical interface to software distribution by defining custom reports for querying the hardware and software database, runs the reports and displays results, generates a node list for distributing software, and distributes the PC software. Other NetFinity capabilities include critical file monitoring, workstation discovery, performance monitoring, activity scheduling, enhanced security, user profile data collection, alert management and processing, and problem analysis and correction. NetFinity for iSeries has two components: NetFinity Server for iSeries (5716-SVA) is the server component, installed on the iSeries servers and the central site system. NetFinity iSeries Manager (5716-SVD) is the 212 Exploring IBM ~ iSeries manager component, installed on a PC connected to an iSeries server in its workgroup. NetFinity Services for iSeries (5716-SVE) contains the PC client code supporting NetFinity for iSeries; this is what you order to obtain the code for remote PCs. All the PCs to be managed within the enterprise must include this code, which performs the responses directed by the NetFinity Manager and NetFinity for iSeries software. NetFinity Server for iSeries includes an easy-to-use GUI for setting up proactive resource monitors and alert conditions on the clients. Client alerts notify the manager GUI when conditions are met, such as changes to critical files, the start or end of a critical process, and performance and capacity statistics. Administrators can view a snapshot of the screen, start a command-line session, transfer files, browse information in the desktop management interface, and view current hardware and software configurations on remote clients. In order to support remote control of Windows NT Server on the Integrated xSeries Server, NetFinity requires a local managing workstation for the remote server, control of the remote console keyboard/mouse, and the capability to inventory the software and hardware and to perform software distribution through the iSeries using Managed System Services (MSS). PC systems supported as clients are Windows 3.1, Windows 95, Windows 98, Windows NT, and OS/2. WebSphere Development Studio WebSphere Development Studio (WDS) for iSeries consolidates the key application development tools for traditional host and e-business development into one attractively priced iSeries product. WDS delivers Java and Web development tools with enhanced functions targeted specifically to increase iSeries development productivity. A WebFacing tool that can be used to quickly, easily, and cost effectively move a 5250 application to a browser interface is introduced. The iSeries product number (5722-WDS) includes all the host and workstation components. This is a no-charge upgrade for iSeries customers of the Application Development tools who have a software subscription. WebSphere Development Studio for iSeries components fit into two categories—host components and workstation components. The host components listed below are described in the tenth edition of Exploring IBM eServer iSeries and AS/400 Computers. Operating Systems • ILE RPG (RPG IV) • ILE COBOL • ILE C • ILE C++. 213 The workstation components include: • WebFacing Tool (First Edition), which helps to build a Web interface to existing 5250 applications and assists in the conversion at development time of the display file source into JavaServer pages (JSPs) and Java data beans. WebFacing easily converts existing interactive applications to e-business applications. The JSPs and Java data beans are deployed to the WebSphere Application Server. Little change is required to the application’s business logic. At runtime, there is a low-level switch in OS/400 that determines if the user is using a browser or a 5250 interface. If the source of the input was a browser, then the output data from the application is directed through a data bean to the generated JSP. This results in HTML forms that are displayed in a browser; no 5250 data stream is ever created. If the source of the input was a 5250 display, then the switch directs the 5250 data to be incorporated into a 5250 data stream and then be shipped to a 5250 display. The same application can support both a 5250 and a browser interface. WebFacing is not a stopgap exercise. The end user can leverage and extend the components created by the WebFacing Tool as part of the evolutionary strategy to sophisticated e-business solutions. • WebSphere Studio (WS) for iSeries (Professional Edition) provides easy access to iSeries data and applications while containing a Web pallet of parts to generate standard HTML and JavaScript. WS includes entry fields with validity checking and support for edit codes. It includes subfile parts, and a wizard to generate a functional Web user interface. • VisualAge for Java for iSeries (Professional Edition) provides easy access to iSeries system functions and generates code to 214 Exploring IBM ~ iSeries access data and applications. This is the best Java Integrated Development Environment (IDE) for creating applications for the iSeries server. VisualAge for Java (Professional Edition) V3.5 is a full Java IDE that includes an editor, a debugger, a Java Development Kit, a WebSphere unit test environment, and a Visual Composition Editor. The Visual Composition Editor lets the customer visually connect GUI and non-GUI parts. It generates the code to enable the connections. The IDE supports incremental automatic compilation of source code and support for third-party Source Control Management Tools as well as support for Java 2. • CODE is the Windows-based, IBM follow-on product set to PDM, SEU, SDA, RLU, and the system debugger. It is a modern, integrated, and comprehensive toolset optimized for creating and maintaining iSeries applications or application fragments written in OPM/ILE RPG, OPM/ILE COBOL, OPM/ILE CL, ILE C, ILE C++, DDS, or Java to help attract, retain, and grow key iSeries development skills. CODE enables development of iSeries host and workstation applications on Windows-based PCs. The CODE functions of editing, syntax checking, and program verification of RPG and COBOL programs has been integrated into WebSphere Studio Site Developer Advanced. CODE is the follow-on to ADTS. CODE includes a PC editor with local and remote compilation; a graphical interface for designing DDS display, printer, and physical files; a debugger that can debug host applications from a workstation; and a project organizer that integrates and organizes your programming projects (PDM for your PC). Languages supported include RPG, COBOL, C, C++, and Java, providing the ability to move between OPM and ILE environments. • VisualAge RPG (VARPG) allows the customer to write or port RPG IV applications to a Windows client. VisualAge RPG can be used to create GUI applications for Windows or any Java GUI-capable client or browser. Again, the user attains seamless access to iSeries data and applications. VisualAge RPG provides a tool to run in Windows environments. The tool includes a compiler, a debugger, runtime, a designer, an editor, and seamless access to iSeries data and programs. VisualAge RPG is based Operating Systems 215 on RPG IV, and much of the RPG IV code can be reused in VARPG. Also, at compile time the user has the option to compile the VARPG code into either Windows EXE or Java Applications/Applets. The latter option means the code can be written once in RPG and be run anywhere in Java. There are some restrictions in RPG that do not compile to Java; however, there are no restrictions on mixing Java code and RPG-derived Java code. RPG IV can make calls to Java programs using the Java Native Interface (JNI), just as C and C++ can make Java program calls. Java can make calls to RPG programs and can also call COBOL programs. • The Program Call Markup Language (PCML) is supported by iSeries. PCML is an Extensible Markup Language (XML). XML is a language for creating new languages, which uses simple <TAG> and </TAG> syntax. PCML defines tags to fully describe the input and output for iSeries programs. Using PCML, calls to the iSeries with the Toolbox classes are automatically created from the PCML tags. WebSphere Studio for iSeries WebSphere Studio for iSeries provides a tool for building and managing Web sites. Easy access is provided for iSeries applications and data through subfile support, iSeries data-type support, wizards, and templates. WebSphere Studio for iSeries addresses the Web site update/customization requirements for ported applications. The 5250 applications can be leveraged and extended to the Web using a WebFacing tool, which can transform those applications to a Web GUI application. The WebFacing tool can create a Java Server Page (JSP) capable of running in WebSphere Application Server to pump the page and data in HTML format to the browser. The resulting Web pages can be customized, with the application that results supporting both 5250 and Web interfaces. The output of the WebFacing tool can then be imported by WebSphere Studio for further customization, such as bouncing heads and flaming arrows. The WebFacing also supports DDS keywords, WAS V4, full national language, authentication, integration to WebSphere Studio Workbench, and the WAS test environment. The long-term objective is to have WebSphere absorb all of the application development tools. Exploring IBM ~ iSeries WebSphere Studio Workbench WebSphere Studio Workbench is a standards-based cross-platform Integrated Development Environment (IDE). Its infrastructure enables the seamless integration of all development tools, IBM and non-IBM. Tool providers can focus on delivering additional function rather than being concerned with the underlying infrastructure and integration with other tools. By definition, products coded to the standards of the WebSphere Studio Workbench will work together. AM FL Y WebSphere Studio Site Developer Advanced WebSphere Studio Site Developer Advanced is a new IBM development environment that merges Java and Web development tools—Visual Age for Java and WebSphere Studio. In the past, as new development roles evolved, developers were required to learn multiple tools with unique user interfaces, unique access methods, and unique extensions. The introduction of IBM’s new development environment provided a consistent user interface, a consistent set of access methods, and a comprehensive set of extensions. IBM delivers development tools based on the WebSphere Studio Workbench. Development Studio Client is one of those suites of tools. Development partners are invited to integrate their tools to this new IDE. TE 216 Web Services In order to support Web Services, tools are delivered to create distributed Internet-based applications that are the fundamental building blocks for dynamic e-business. In Development Studio Client, tools are provided to enable Web Services components from existing iSeries programs. Wizards can be used to create a Java bean by wrappering an iSeries program, and a Web Service can be generated from that Java bean. These Web services can then be sold over the Web or shared over the network between businesses. WebSphere Development Studio Client WebSphere Development Studio Client is the follow-on product to WebSphere Development Tools for iSeries. The tool built on WebSphere Studio Workbench extends WebSphere Studio Site Developer Advanced Team-Fly® Operating Systems 217 to include iSeries-specific tools and features. Classic VisualAge RPG is shipped with Development Studio Client. Key features of Development Studio Client are: • From Site Developer Advanced: – Web development tools – Page Designer – Rich Media – Web Services development environment – Visual XML development environment – Java IDE – Database Tools – WAS Test environment. • A generic “remote systems framework” supports views, tools, and tool extensions for working with remote operating systems. This includes defining persistent “connections” and subsystems that offer services to a remote system connection, as well as a Remote System Explorer for exploring remote system connections and subsystems. Remote System Explorer makes it easy to access UNIX, Windows, and Linux. • Multi-platform common extensions to the remote systems framework, offering explicit services to explicit remote operating systems. This includes a file system for accessing remote file systems on Windows, UNIX, Linux, and iSeries IFS, to leverage the datastore technology, and supports exporting and importing resources from those file systems. • iSeries-specific access from Workbench particularly related to Remote System Exploration of IFS and native file systems on iSeries, including predefined and user-defined actions, a native 218 Exploring IBM ~ iSeries operating system command shell, a Toolbox for Java iSeries extension including JAR files, and an advanced iSeries communication layer specific to Workbench tools. • The IBM WebFacing Tool, which integrates with Web tools, Java tools, and iSeries tools. • iSeries-specific extensions to Java tools enabling the Export and Import to/from IFS, using the common remote system framework above. Special Java action/views are provided for remotely: – Compile for compiling Java classes – Run for running Java applications – Debug for debugging Java applications. A program wizard is provided to wrapper any *PGM/ *SRVPGM as a Java bean. The previously supplied Java beans CDFU, PDM, and Swing formatting continue to be available. • Web tools have received some iSeries-specific extensions: – Page Designer includes Design-Time Controls (DTCs) with a table-based capability. – A Web interaction wizard helps in the building of Web applications integrated with an iSeries host program. Users define the input Web pages, output Web pages, the program call definition, and the mapping between the parameters and the fields of the Web pages. The wizard generates the servlet and other runtime beans. The wizard then puts all the pieces together to create the complete Web application. – A Host Information Setup Wizard captures information such as hostname, user-ID, password, and library list. • CODE/400 functions that support launching from Workbench. • VisualAge RPG functions include some customer-requested enhancements. Operating Systems • 219 WebSphere development Studio Client for iSeries provides the development tools for Web-based applications to be used with the IBM HTTP server, WebSphere Application Server - Express for iSeries and other WebSphere offerings. IBM WebFacing Tool A component of WebSphere Development Studio Client for iSeries is the WebFacing Tool. The WebFacing Tool, described briefly under WebSphere Development Studio, creates a web interface for existing 5250 applications in a development-time conversion process. The conversion process typically requires little or no change to the existing iSeries program. The resulting application continues to support a green screen and will also support the Web interface. The tool generates standard JavaServer Pages and XML definitions, based on the display file DDS, and includes a servlet-based runtime. The WebFacing Tool has been enhanced with performance and scalability improvements to all the WebFacing Tool to support extremely large and complex applications with high traffic flow. Integrated Language Environment (ILE) The Integrated Language Environment (ILE) provides a set of tools and system support designed to enhance program development on the iSeries system. Benefits that ILE offers over previous program models include binding, modularity, reusable components, common run-time services, and coexistence. ILE also offers better control over resources, better control over language interactions, better code optimization, and a better environment for the supported languages. ILE produces a module object (MODULE) that can be combined (bound) with other modules to form a single executable unit—that is, a program object (PGM). The ILE languages continue to be supported under WebSphere Development Studio. Application Development ToolSet (ADTS) Application Development ToolSet is the set of tools largely absorbed into WebSphere Development Studio used for developing applications that will run on iSeries computers. Users with Software Subscription for ADTS are upgraded to WebSphere Development Studio at no charge. 220 Exploring IBM ~ iSeries Application Development Tools—Printing These tools address the programmer’s needs relative to setting up and managing the appearance of output documents, whether provided directly by a printer or indirectly by an interchange methodology such as fax. Print Services Facility/400, or PSF/400 for short, is an integrated feature of OS/400 that provides full system-managed printing to IPDS printers. It is automatically invoked by OS/400 print management when its services are required. PSF/400 is the driver subsystem for Advanced Function Printing (AFP) on iSeries. PSF/400 manages the printing of the following types of iSeries spooled files to IPDS printers: • SCS files • SCS with printer file options (i.e., front or back overlay) • SCS with page or form definitions for print formatting • AFP created from DDS printer file specifications • AFP from the Access/400 AFP driver • AFP from other systems or AFP Toolbox (a PrintSuite product) • Postscript and image files converted by Host Print Transform (HPT) • IPDS files. All of these spooled files (except IPDS) are transformed into IPDS and managed to the printer. As the system-managed print driver, PSF/400 provides full document services, printer services, and print process management. PSF/400 is the IPDS print manager and is the iSeries end of the interactive dialog between iSeries and printer. This dialog ensures the function and control of a direct-attached printer even when the printer is connected across the network using TCP/IP. Good typography through the use of fonts is essential for effective business documents. The Advanced Function Printing (AFP) Font Collection provides a comprehensive set of Advanced Function Printing fonts with over 1,000 fonts from the most popular type families, includ- Operating Systems 221 ing Times New Roman, Helvetica, and Courier. A full range of sizes, resolutions (240 dpi, 300 dpi), and languages (over forty-eight) are included. Outline fonts are now supported, enabling one small font to be dynamically scaled to any size. An optional feature of AFP Font Collection is Type Transformer for Windows. This set of font utilities enables the conversion of any Adobe Type 1 font to an AFP font. It also includes the capabilities to modify and customize fonts. Beginning with V4R5, the AFP Font Collection CD is shipped with new orders of PSF/400. Advanced Function Printing Utilities for iSeries (5769-AFI) is a set of integrated modules for the design and creation of AFP electronic forms, images, and applications. Overlay Utility enables you to create electronic forms right on your iSeries. Native, high-performance overlays are designed with either a near-graphical or a command interface. Fully graphical viewing of overlays in process is available via a command key. Resource Management Utility provides for the creation and management of overlay and image (page segments) objects on iSeries. Print Format Utility is the AFP equivalent of Query/400, enabling you to build print applications interactively directly from the iSeries database. Full AFP design capabilities make applications such as barcoded labels a snap. The Euro currency symbol is supported by iSeries and includes changes to the following system functions: • Code pages and CCSIDs • Keyboard types • Device configurations and device controllers • Fonts and glyphs • Specific currency processing. This phase of Euro support is only for those countries that use the Latin-based alphabet, including those countries that initially participated in the European Monetary Union and other select countries. For the latest information and a roadmap to Euro currency sign support on 222 Exploring IBM ~ iSeries the iSeries, visit the iSeries Web site at http://www.as400.ibm.com/euro. The symbol can be viewed by choosing Symbols, then Coins, at http://www.europa.eu.int/euro/htm//home5.html?lang=5. Advanced Function Printing (AFP) AFP comprises a document architecture, a printer dialog and data stream, and a process for fully system-managed printing. As a document architecture, AFP is also known as MODCA-P, or Mixed Object Document Content Architecture–Presentation. As the name implies, AFP defines pages of output that mix all of the elements normally found in organizational documents—text in typographic fonts, electronic forms, graphics, image, lines, boxes, and barcodes. The AFP data stream consists of a series of structured fields that implement all of these elements. AFP output can be created on iSeries using printer file keywords, DDS, Infoprint Designer for iSeries, Advanced Print Utility (APU), page and form definitions, AFP Utilities (AFP/U), and the AFP Toolbox, as well as many third-party applications. AFP enables more than just printing. In today’s e-business application environment, it is essential that pages of information can be produced electronically and delivered to the desired destination in the appropriate format. AFP is the standard fully graphical page format of iSeries. Once AFP pages are produced and are written to an iSeries output queue, they can be printed on IPDS, PCL, and (with Infoprint Server) PDF printers. AFP pages can also be transformed to PDF and either be cataloged for “inbound” browser access or be e-mailed for immediate “outbound” distribution. Those pages can also be faxed (i.e., using Facsimile Support or Fax for Domino) or archived (i.e., using Content Manager). Intelligent Printer Data Stream (IPDS) AFP is also an interactive printer data stream called IPDS (Intelligent Printer Data Stream). This data stream is similar to the AFP data stream, but is built (on-the-fly) specific to the destination printer in order to facilitate the interactive dialog between the iSeries system (specifically Print Services Facility/400, or PSF/400) and the printer. AFP, SCS, linedata, and ASCII files are transformed into IPDS prior to printing in order to support this dialog. Operating Systems 223 The two-way function of IPDS is a key component in AFP’s systemmanaged printing process. This process includes document services, printer services, and print process management. Document services include identifying and automatically downloading externally referenced document resources such as overlays, images (page segments), and fonts to the IPDS printer. Printer services include monitoring printer resources and memory. Finally, the entire printing process is managed page by page to ensure that each spooled file is printed completely and accurately. Error conditions at the printer are monitored and full error recovery is enabled at the iSeries. The system-managed printing process with IPDS takes on added significance in a network TCP/IP environment. Placing printers within the network and attaching them with an IP connection provides great flexibility. However, TCP/IP print support is very limited—essentially a one-way send of the print file. The AFP printing process and the bidirectionality of IPDS provide a bridge across this type of connection. The result is the same application (i.e., document capabilities) function and print management supported with twinax-attached printers. Network printing has been improved by adding parameters in the device settings panel of Access to send output as text rather than graphics, reducing the size of the printed output file created with the AFP driver and thereby reducing the time required to send large documents across the network for printing on the locally attached PC printers. Network print buffering has been changed to improve performance for applications making small iSeries print requests to redirected PC printers. (That is, DOS applications that send one character at a time are now buffered and sent as one request. This does not apply to the Microsoft Windows NT operating system.) IBM Infoprint Server for iSeries Infoprint Server for iSeries (Infoprint Server) is a separately orderable program (5722-IP1). The focus of Infoprint Server is on the network, extending the considerable capabilities of the iSeries beyond printing to the management and dissemination of output. As business applications are reengineered into e-business applications, the output of those applications may need to change and flow electronically to the consumers of that output. For enterprise printing requirements, Infoprint Server delivers improved efficiency, improved reliability, and lower overall printing costs 224 Exploring IBM ~ iSeries by applying iSeries printing management and iSeries-attached printers to the task of handling all of the essential printing generated across the network. On the e-output side, Infoprint Server provides PDF and portable AFP support for the iSeries. Any standard iSeries-AS/400 output format can be transformed into PDF. The PDF is text-based, fully navigable, and high-performance. In addition, enhancements to DDS (OS/400) enable you to segment an output file, triggering the PDF server to create multiple PDF files—this is an “electronic burst and bind” function. More than this, e-mail of output (via PDF) has been integrated and automated into this process. Output files can be transformed to PDF and automatically sent to any destination. Integrated e-mail also provides user exits for customization (i.e., using the trigger field—a customer number, for instance—to look up an e-mail ID in an address book). AFP output can be treated similarly. A new command—Create AFP Data (CRTAFPDTA)—provides three critical functions: (1) converts print formatted with page definitions to AFP, (2) creates a portable file by pulling in external fonts, page segments, and overlays, and (3) inserts indexing to facilitate easy navigation when viewing the print file. The other key focus of Infoprint Server is iSeries management of network output. Infoprint Server provides transforms for PCL, Postscript, and PDF into AFP so output generated in those formats can be brought into the iSeries and effectively managed to the printer. The Postscript and PDF transforms are the result of joint development by IBM and Adobe and deliver full-function Level 3 capability. Finally, the standard Web e-business image formats are GIF, TIFF, and JPEG. Infoprint Server provides transforms (Windows-based) to convert those to iSeries-AS/400 images (IOCAC page segments). In summary, Infoprint Server delivers five print and e-output components: • PDF services for iSeries • Integrated e-mail of iSeries output, including electronic segmentation • Support for Web AFP and spooled file indexing/segmentation • Transforms for Web image—TIFF, GIF, and JPEG—to iSeries image Operating Systems • 225 Transforms for network print data streams—Postscript, PCL, and PDF—to AFP. IBM Infoprint Designer for iSeries Infoprint Designer for iSeries provides a fully graphical document composition interface to the iSeries-AS/400 printing and e-output system. It supports the requirements of today’s complex documents and reports, producing fully electronic documents combining data, text, electronic forms, graphics, images, bar coding, and typographic fonts. Infoprint Designer for iSeries can be used for the design of new output applications or the reengineering of existing applications. Infoprint Designer for iSeries consists of three components: • Infoprint Overlay Editor designs overlays (electronic forms) to be used in the print application. • Infoprint Image Editor designs the images to be used in the print application. • Infoprint Layout Editor puts all the design components together into the final document or report. With Infoprint Designer for iSeries, you can easily build complex print applications. It enables you to design image components, design electronic forms, automatically retrieve current application data or spooled files, design the final page layout, and upload all component resources to the iSeries-AS/400 so the application can be put into production. The entire interface is designed for a nontechnical user. Infoprint Designer is integrated in three ways: (1) design functions are integrated with automatic retrieval of application data and automatic upload and creation of print resources, (2) iSeries page resources are designed in native formats, and (3) the application resources enable the designed print application to be put into production with a simple printer file change. Under the covers, Infoprint Designer defines the format of pages with page and form definition resource objects. These are part of the iSeries-AS/400 print architecture. Designing with these resources is application-independent (unlike DDS). They are also compatible with ex- 226 Exploring IBM ~ iSeries isting or new applications that define output data with DDS. With V5, OS/400 will automatically write these applications as full AFP (ensuring viewing and PCL support). The iSeries Kernel Threads TE AM FL Y A thread is an independent unit of execution within a program. The amount of system resources used for a thread is far less than the resources used for a job. Threads share a common address space and have access to all job resources. They are used to run different parts of an application concurrently. Multi-threading provides simplified algorithms and more responsive programs in that the functions of I/O, calculations, and user interface are each dealt with through separate threads, and threads use fewer resources than a multiprocessing solution. A threadsafe function can be invoked simultaneously in multiple threads. A function is threadsafe if and only if all functions it calls are threadsafe. OS/400 is threadsafe. Application Environments Three application environments are now available—Frameworks, OpenDoc, and Java. Those environments are being developed by many vendors. OS/400 is putting into place the support structures to embed these environments as quickly as they are available. Frameworks The Frameworks environment is one in which a company such as IBM develops the skeleton of an application, leaving to the final user the tuning of the application to the business’s needs. Object-oriented technology provides for programming—the reuse of parts and components that have been a part of the hardware environment for the past five to ten years. Frameworks groups those components into compatible software sets, capturing the collective experience of a design team and providing a model for a common solution to particular problems, thereby automating much of the development effort. Examples of what Frameworks can do include the following: • Automating tasks associated with distributed applications Team-Fly® Operating Systems 227 • Allowing applications to move easily between different operating systems by disguising the differences in those operating systems • Automating graphical user interface development • Masking/dealing with the complexities within and between transactions and communications. Two different types of frameworks are being developed. One type deals with applications; the other with systems. The application frameworks provide a basic set of cross-industry and vertical functions/objects, which include basic financial management objects, distribution objects, and customer/supplier objects. Over time, application frameworks are expected to provide a rich base to enable the software parts business. IBM is developing a set of frameworks using the code name San Francisco. San Francisco focuses on business-management software. Within the second type of framework, the system framework, the system developer provides the frameworks to support the traditional operating system functions in an object-oriented environment. These functions include graphical operations, data access, and network management. In addition, security, data integrity across multiple cooperating systems, save/restore, activation, and national language support need to be included as business objects. The concept of frameworks has been introduced here to set the stage for what to expect in the long run in system development. The San Francisco Framework. San Francisco is a framework, written in Java, that focuses on business-management software. A user can elect to build an application starting from any of the three layers of San Francisco: 1. Base layer. This provides the technical infrastructure needed before object technology can be used above it. 2. Common business objects layer. These are the building blocks application developers can use to create business applications. 3. Core business processes layer. This is built for one specific application containing the basic functions all applications of this type require. Exploring IBM ~ iSeries The final layer of San Francisco is the commercial applications layer created by the software developers who buy and extend the San Francisco frameworks. In most cases this final layer will be created using Java. The layers of San Francisco are illustrated in Figure 4.14, together with its positioning relative to the Java virtual machine and the technology-independent interface. San Francisco supplies a set of cross-platform, business process components including: Common business objects • General ledger • Accounts receivable/accounts payable ledger ISV Application Software • Partner Application IBM San Francisco Business Process Components Core Business Processes Ledgers Ledger Credit Control Item Entry Payment Handling Budgeting Warehouse Management Warehouse/ Control Stock/Replenishment Manufacturing Enabling Order Management Quotations Sales Orders Cash Sales Supplier Customer Tools: San Francisco Code Generator Wizards - Rose - JBuilder Common Business Objects Entity: Customer, address, currency, calendar Helper: Keys, cached balances, results reporting Enterprise Structure: Company Foundation Object Model Base Classes: Entity, dependent, command, ... Object Services: Xactions, security, persistence ... Platforms 228 Java Virtual Machine Figure 4.14. San Francisco block diagram. Foundation Utilities: Install, Configure, Security, Administration Operating Systems • Order management • Warehouse management. 229 San Francisco is designed to support the distributed-object environment and reduces the complexity, expense, and time-to-market factors related to the building of customized, multiplatform business applications. Performance has been enhanced to three times the initial release performance. IBM Connect Framework for iSeries. IBM Connect Framework for iSeries is a business-to-business (B2B) software integration framework that provides seamless and secure integration of existing core business applications with trading partners. Deployed solutions occur rapidly and are open and cost-effective, are built on industry standards, and work with Domino, WebSphere, and MQSeries. Connector elements included are Plug-N-Connect, e-Catalog, Tools, and MQSeries Lite. The B2B framework integrates your business applications with those of your trading partners, supports multiple trading partner protocols, and provides connectivity to new and existing back-end applications. The focus is on the small to mid-market requirements of low cost, easy deployment with minimal service costs, and an integrated tool set. Connect for iSeries is targeted to the sell side of the B2B environment, including buyer/supplier registration tools, catalog services, and integration with WebSphere Commerce for iSeries. The objective is to put the buyer in control. To this end, it is perceived that the buyer is installing procurement software to streamline the purchasing process and to reduce expenses, making it easier to deal with multiple sellers using new protocols and messages (usually XML based) to communicate with sellers. Sellers must be able to support the new protocols and messages, tie the new requests into existing processes, support multiple buyers’ procurement packages simultaneously, and react rapidly. Connect for iSeries: • Maintains a database of information about suppliers, marketplaces, and buyer organizations • Maintains relationships between both a marketplace and a supplier, and a buyer organization and a marketplace supplier 230 Exploring IBM ~ iSeries • Handles various trading partner protocols including Ariba, cXML, and Metiom mXML • Handles catalog management by building catalog data from existing sources or from scratch, augmenting catalog data with unique data required by trading partners, and publishing catalogs in various formats (cXML, CIF 3.0) • Handles integration with back-end applications by mapping trading partner requests to a format acceptable by an application, and accessing applications through program calls, Java calls, or queues • Handles integration with WebSphere Commerce by associating marketplaces and buyers with merchants and shoppers, allowing B2B catalogs to be hosted at the supplier site, and augmenting WebSphere Commerce (WC) catalog with unique data required by trading partners. Connect for iSeries is built on industry standards like Java and XML, designed to work with different e-business infrastructures like WebSphere or Domino, designed for plug-in connections with different marketplaces, and supports different integration strategies like MQSeries Queue connector/data queues, Program Call connectors, and Java connector. OpenDoc OpenDoc is a cross-platform compound-document architecture designed to simplify the creation of documents, including the multimedia elements of text, spreadsheets, charts, tables, graphics, images, video, and sound. End users can combine the parts as desired. ORB Support iSeries supports Iona’s Orbix product, which is a full implementation of OMG’s Common Object Request Broker Architecture (CORBA). Orbix 2.3 is a CC++ ORB implementation. OrbixWeb 3.0 is a Java ORB designed for use in the Java environment. Significant companies that have adopted this ORB are SAP, Intentia, and Baan. Operating Systems 231 iSeries also supports Inprise’s VisiBroker product, which provides similar CORBA distributed-object services. VisiBroker provides high-level services (naming, transaction, security, etc.) and DCOM connector. Significant companies that have adopted VisiBroker are Netscape and SUN. Java Java is a standardized cross-platform (running on many different types of computers) object-oriented programming language. The standards are being established by Sun Microsystems. The iSeries representatives who have studied Java state that it is a pure object-oriented language similar in syntax to C++ and similar in behavior to SmallTalk. Java is an interpreted language and is machine-independent, meaning that programs written in Java will execute on any system. The Java Developer’s Kit (JDK) from Sun includes a standardized set of class libraries (packages), a Java compiler, and the Java virtual machine. The class libraries support creating GUIs, controlling multimedia data, communicating over networks, accessing data in stream files and relational databases, and more. The Java compiler (also known as the javac compiler) compiles the Java source code to machine-neutral instructions. The instructions are then interpreted and run on the Java Virtual Machine (JVM). The JVM is a fictional processor that is emulated in software. The instructions, called Java bytecodes for that fictional processor, are identical no matter what hardware or OS platform the virtual machine is running on. As each bytecode arrives, the virtual machine reads it, interprets it, and executes the native instructions appropriate for that particular local environment. Each operating system that supports Java has its own platform-dependent JVM to interpret the Java bytecodes. Many common Web browsers, such as Netscape or Internet Explorer, also contain their own Java virtual machines so that Java applets from the Internet can be run inside the browsers. In addition to the Java compiler included in the JDK, many operating systems support just-in-time compilers for Java. A just-in-time compiler can be plugged into the Java virtual machine, and when the virtual machine is ready to execute a method in a class or object, it passes the bytecodes for that method to the just-in-time compiler, which then compiles the bytecodes on the fly to native code. Without a just-in-time compiler, the Java virtual machine must interpret and execute each 232 Exploring IBM ~ iSeries bytecode in succession, a much slower process. Java applets will be downloadable to any system from the Internet. The iSeries eServers have a Java virtual machine residing below the technology-independent machine interface (TIMI) for fast interpretation and execution. The performance of the JVM for iSeries has been improved by modifying the garbage-collection algorithms through a multi-threaded collector and removing the need to touch the objects being deleted, by using synchronized method calls to reduce the nocontention path length, and by improving the JIT compiler and improving object allocation. The IBM Toolbox for Java includes a set of enablers that support an Internet programming model. The new version of IBM ToolBox for Java includes a set of classes for accessing data from a wireless device, an updated JDBC driver supporting JDBC 3.0, the ability to use a Kerberos ticket when authenticating to the server, and a system debugger to graphically debug C, C++, Java, and RPG programs on the iSeries. Provided is a set of client/server programming interfaces for use by Java applets and applications plus a set of applets that can be integrated into HTML documents. Required client support is Java virtual machine and iSeries Developer Kit for Java. Because graphical user interfaces cannot be displayed by an iSeries green-screen, iSeries implements something called Remote AWT. Java on iSeries intercepts GUI requests coming from a Java program and reroutes the requests to an attached workstation running its own JVM, which will interpret and display the JAVA.AWT graphical components. Other Java packages are being integrated with OS/400 to improve ease-of-use and performance. Java objects on iSeries are full-fledged iSeries objects that can be persistent, shared, secure, backed up, and restored—something not available in two-level-store operating systems. Figure 4.15 positions Java in relation to OS/400. Java 2 Enterprise Edition (J2EE) represents an emerging suite of standard requirements placed on Java application servers such as WebSphere. The Java Virtual Machine supports the emerging Java Debug, Performance Profiling, and Wire protocols, enabling third-party tools to work with the iSeries JVM, along with iSeries specific instrumentation for memory leak detection and enhanced debug. Therefore, the suite of XML enablers can stay in step with the latest XML standards providing support for XML schemas. Java Generic Security Services (JGSS) is a Java standard. The JGSS APIs are added to the iSeries Developer Kit for Java. These APIs enable Java applications to access either Java-based or native OS/400 Kerberos Operating Systems 233 Java-based Web Application WebSphere Enterprise Java beans Net.Data (RPG, COBOL, C) Java added as a Language Environment CGI (RPG, Cobol, C, Java) Java server pages (Java) Java Servlets (Java) ICAPI C IBM HTTP Server OS/400 sockets (C, Java), SSL (C) Java added as SSL language option Figure 4.15. Java with OS/400. (client) security services. The Java security extensions leverage the integrated Secure Sockets Layer (SSL) functionality built into the iSeries. All data exchanged between the client and server can be encrypted using the SSL protocol. Customers and business partners can build secure client/server applications using Java. Structured Query Language Java (SQLJ). Structured Query Language Java is a structured query language embedded in Java. SQL statements include queries (SELECT), data-manipulation statements (INSERT, UPDATE, DELETE), and others that operate on data stored in tables in relational databases. SQLJ is a conventional method for embedding those SQL statements in Java. It allows programming tools to perform translation-time (compile-time) analysis of SQL in Java, for syntax checking of SQL statements, for type checking to determine that the data exchanged between Java and SQL have compatible types and proper type conversions, and for schema checking to ensure that the SQL constructs are well formed and valid (in the database schema where they will be executed). Embedded SQL statements are referred to as static because they are textually evident in the Java program and can be compiled when the containing Java program is compiled. SQLJ provides a standard for tightly integrated Java/SQL programs. 234 Exploring IBM ~ iSeries SQLJ finds compatibility with multiple translation approaches. SQLJ can be processed by a standalone SQLJ-to-Java translator in a client environment or by a Java integrated-development environment to emit standard Java code with calls to any appropriate database API. When Java is supported as a stored procedure language (in an RDBMS server), SQLJ translation can be integrated with Java and SQL compilation for ease of use and performance. Dynamic SQL is a call interface for passing strings to a database as SQL commands. No analysis or checking of those strings is done until the database receives them at execution time. JavaSoft has specified a dynamic SQL API called JDBC. Because a calling program can compose SQL strings at runtime, dynamic SQL is more flexible than static SQL. Because the SQL commands used by many applications are fixed, those applications do not have to compose SQL dynamically. Embedded SQL is a better solution for those applications because error checking is allowed at development time and because it permits precompilation of SQL for faster execution at runtime. Other static SQL advantages over dynamic SQL include that the source programs are smaller than equivalent JDBC programs and that they provide greater opportunity for optimization. Also included is a standardized set of class libraries (packages) that support creating GUIs, controlling multimedia data, communicating over networks, and accessing data in stream files and relational databases. The iSeries Developer Kit for Java is a no-cost tool designed to produce Java applets and full-scale applications. Included are a collection of development tools, help files, and documentation for Java programmers. The developer kit is compliant with Sun’s Java 1.3 specifications and provides improved performance either through improved transaction rates or through lower CPU utilization on applications that use the database. A single iSeries can support a wide range of installed Java developer kits concurrently. Toolbox for Java. The iSeries Toolbox for Java, available on iSeries and other Java-compliant platforms, enables Java applets and applications to access iSeries data and resources by providing a collection of classes that represent iSeries data and providing iSeries client/server program interfaces for Java programs. The iSeries Toolbox for Java provides access to the following iSeries system resources: • Connections to the iSeries security Operating Systems 235 • Database access via JDBC 2.0 • Database access via record-level file input/output • iSeries program call • iSeries command call • iSeries integrated file system • iSeries Print Resources, which includes a spooled file viewer class and a GUI for showing print output • iSeries data queues • Data description and conversion • iSeries user space classes, allowing Java to create, read from, write to, and delete iSeries user spaces • Digital certificates stored on iSeries, allowing Java to manage iSeries digital certificates • Job listing, allowing Java to list active jobs and retrieve information about those jobs including listing messages in a job log • iSeries message queues, allowing Java to list, delete, and answer messages in a message queue • User and group classes, allowing Java to list users on the iSeries and retrieve information about the users • Visual access classes that provide a set of classes using Java’s Swing 1.0 framework to retrieve data and then present the data to the user • An integrated file system class that extends Java’s java.io.file class to applications so the applications can act on files in the IFS • Access to iSeries message files Exploring IBM ~ iSeries Access to iSeries data areas • Access to iSeries system values (both low-level and GUI classes) • Access to iSeries authority on an object (both low-level and GUI classes) • Access to iSeries system status • Access to information about jobs running on the iSeries • Access to information about users on the iSeries. AM FL Y • With the iSeries Toolbox for Java, Graphical APIs are available to access the following iSeries resources: • Database data via JDBC • Database data via record-level database access classes • iSeries program call • iSeries command call • iSeries data queues • Files in the iSeries IFS • iSeries print resources • Active jobs on the iSeries • iSeries messages and message queues • iSeries users and groups • Servlet and access classes, including FTP client. TE 236 With the iSeries Toolbox for Java, iSeries data can be presented in the following formats: Team-Fly® Operating Systems 237 • List pane presents a list of iSeries resources and allows selection of one or more resources. • Details pane presents a list of iSeries resources in a table where each row displays various details about a single resource. The table allows selection of one or more resources. • Tree pane presents a tree hierarchy of iSeries resources and allows selection of one or more resources. • Explorer pane combines an iSeries tree pane and iSeries details pane so that the resource selected in the tree is presented in the details. The iSeries Toolbox for Java also includes a set of enablers that supports an Internet programming model. Provided is a set of client/server programming interfaces for use by Java applets and applications. Proxy support extends three-tier application options. The iSeries Toolbox for Java supports the SSL specification data flowing between a workstation and an iSeries running OS/400 and can have data encryption and server authentication through the use of an SSL connection. A user interface framework is included in the Toolbox to provide a development environment for building graphical panels. The framework handles the exchange of data automatically. The developer creates one or more data beans and binds them to the panel component using tags from the Panel Definition Markup Language (PDML). The user interface framework can also create a platform and technology-independent representation of graphical panels based on the Extensible Markup Language (XML). Also provided is a pure Java framework for interpreting XML and constructing user interface panels based on the Java foundation classes. Windows dialogs can be converted to equivalent Java panels using a resource script converter. A WYSIWYG GUI editor can be used to develop Java GUIs. A Program Call Markup Language (PCML)— a tag language—is used to provide a program call framework to support the program call function of the Toolbox. The language fully describes all parameters, structures, and field relationships necessary to call an iSeries program. The iSeries Toolbox for Java requires both the TC1 Licensed Program (TCP/IP Connectivity Utilities for iSeries) and the Host Server 238 Exploring IBM ~ iSeries option of OS/400 to be installed and configured on the iSeries. Client machines and Web browsers must contain a Java virtual machine that fully supports Java Version 1.3. The iSeries Toolbox for Java Classes can access data and resources on V3R2, V3R7, V4R1, and above. Other Java packages are being integrated with OS/400 to improve ease of use and performance. Java objects on iSeries are full-fledged iSeries objects, allowing them to be persistent, shared, secure, backed up, and restored—something not available in two-level-store operating systems. Programmed Access to PDF and e-mail services provides a new spooled-file copy method within the Java Toolbox. This Java method provides for an identical copy of a target spooled file to be made and routed to an output queue. Using this method, application developers can set up dynamic, programmed interface to PDF and e-mail services. This is the same technique used by both iSeries Navigator and iSeries Access for Web to utilize Infoprint Server PDF and e-mail functions. Enterprise Java Beans. Enterprise Java Beans (EJB) is a recent industry standard initiated by Sun for a program model for developing portable, cross-platform, server-side, distributed business components using Java. The EJB programming model supports scalable, distributed, transactionoriented three-tier business applications. EJBs are easy to develop. The IBM iSeries ESJ provides a fully compliant EJB server and container for hosting EJBs. The EJB server and container provide transaction, security, and persistence support, which makes development of server-side business logic considerably easier. EJBs are reusable, portable, serverside business logic components. The EJB server hides complexities of transaction management, security, and persistence. EJB support is provided by the WebSphere Application Server LP. Using Java at the Client. The iSeries also includes a copy of Borland’s J-Builder on a “try-and-buy” basis for those who do not like VisualAge for Java and who still need to develop Java applications. Product Preview—Altered Program Objects Some application providers and customers alter their program objects. IBM recommends against this practice because altered programs may bypass checks made by OS/400 that help ensure system integrity and security. Operating Systems 239 Today you cannot re-create a program object without source code on an iSeries eServer if observable information, which includes program creation data, has been removed. A future enhancement to OS/400 will retain program-creation data when observable information is removed, thus allowing the program to be re-created at the customer’s option. Recreating a program helps ensure its integrity and allows you to take advantage of new hardware or enhancements in translator technology. However, when a program is re-created, alterations that were made to the program object are not retained. Programs that depend upon alterations may fail or behave in an unexpected manner should the customer choose to re-create them. Customers should consult their application providers regarding potential impacts of program re-creation. Linux for iSeries Linux for iSeries introduces the Open Source/Open Standards operating system to the iSeries group of products. Linux has no single vendor, is small and modular, and is derived from UNIX. The Linux source code is distinct from UNIX. Linux offers compatibility, portability, and horizontal scalability across all platforms. Many workloads like Webserving, supercomputing clusters, and appliance serving are well suited to large Linux-based server farms, creating sales opportunities for xSeries and middleware, and accompanying services engagements. Figure 4.16 positions Linux as equal among the other application environments provided on the iSeries servers. Users can run PowerPC Linux applications on the same iSeries as other types of applications are running. Linux on iSeries uses the same Linux distribution model as other platforms. You get your kernel from a standard Linux distributor. The iSeries Navigator provides a Linux partition creation wizard, capability to save the partition configuration data, and ability to export that configuration data to HTML. Linux for iSeries is only functional in a secondary Logical Partition. OS/400 V5R1, or later, must be in the primary partition. If the processor in the system is an SStar-technology-based processor, then the minimum configuration for Linux to function is as little as one-tenth of that processor’s capacity, with at least 64 MB of memory. If the processor is an IStar-technology-based processor, then the minimum configuration for Linux to function is at least one complete processor on a multiprocessor system. The maximum Linux partition configuration can con- 240 Exploring IBM ~ iSeries Iseries Business Applications Integrated Xseries Server Lotus Domino Application Server and Solution Framework IBM WebSphere Java-based Web Application Server UNIX Runtime plus ISV tools Middleware and Application Servers Linux Interconnected for application enhancement Security Database Management - Certificates - Virtual Private - Integrated SSL - Hardware Cryptography - UDB - Net Server - JDBC Interoperability - ODBC Interoperability - Single System Multi-workload - Multi-system - Management Central - Tivoli Java - Java Virtural Machine - WebSphere - Just In Time Compiler - Integrated Memory Management Figure 4.16. Linux positioning relative to other iSeries integrated technologies. tain eight processors and 4 GB of memory. Linux can operate with shared I/O in another partition or with direct I/O dedicated to the Linux partition. Resources such as processors, memory, and I/O can be moved between OS/400 and Linux partitions. Shared resources are owned and managed by OS/400 with space allocated for Linux usage. Virtual storage spaces are easily moved between partitions. The movement of these resources requires an IPL of the Linux partitions involved in the resource movement. The Linux console is a PC connected to the iSeries primary partition using a TCP/IP LAN. A Telnet environment is then used to connect into the Linux environment through the virtual LAN. These limitations are dictated by Linux constraints. A virtual LAN can be used for partition-to-partition communication; a request comes in through an iSeries LAN adapter and is routed to Linux via virtual LAN. Linux partitions are created by defining a guest partition with processor and memory resources, enabling a virtual LAN for the partition, Operating Systems 241 creating a Network Server Description (NWSD), configuring the console, and varying on the NWSD from Linux media. The installation of Linux can continue based on the distributor’s installation instructions. Linux partitions are started and stopped from the primary partition by varying on and off the NWSD. The maximum number of Linux partitions in a shared processor environment is equal to the maximum number of partitions supported on the server minus one, or thirty-one partitions on a twenty-four-way system. The one non-Linux partition must be OS/400 V5R1, or later, as a primary partition. On iSeries, in addition to Linux, users can also deploy Java, UNIX, Windows 2000, PASE, and Domino applications, all on a single system. There are three major areas of use for Linux—consolidation, complementary applications, and replace Windows services. There is little or no integration with OS/400 applications within Linux. Multiple Linux servers can be used to consolidate several separate server-based functions (e.g., file server, e-mail server, and a simple Web server). OS/400 applications can be extended with Linux applications, especially in the area of DB2 UDB for OS/400. Areas of extendability include e-business applications, firewall, and line-of-business extensions. The iSeries Java Toolbox provides numerous functions that facilitate a Java program on Linux working with OS/400 programs, data, and services. Linux can also replace Windows services such as Windows file, print, DNS, DHCP, Web server, etc. Globalization The activity in computer globalization revolves around two separate unrelated activities: the definition of a single programming code set that would meet all the requirements of translation between different languages regardless of the language derivation, and the concept of grid computing, in which case the unused resources resident on the Internet can be used to process against your particular computing task. Unicode The single code set definition activity initially evolved around an activity in the United States called Unicode, and in Europe called ISO-10646. 242 Exploring IBM ~ iSeries Unicode is a standard for the storage and interchange of textual data. The two groups merged their efforts in 1993 and adapted the Unicode name for the joint activity. Currently the Unicode definition includes the behavior and use of characters, a BiDi algorithm, the order and use of nonspacing marks and equivalence rules, mappings for compatibility characters, default shaping for cursive scripts, conversion maps, and directional attributes. Also defined is a byte order mark (BOM) used to identify whether big or little endian is being used. Endian defines the order in which the four bit nibbles of a byte are read; i.e., big endian reads the high-order nibble first followed by the low-order nibble, little endian reverses that order. Currently a format called UTF-8 is used to store Unicode on several UNIX platforms and is the default encoding for most new Internet standards. Advantages of UTF-8 include transparency for ASCII characters 00B7F hex, BOM avoidance, reasonably compact encoding, processor friendliness, self-synchronization, and canonical sort-order. The disadvantages are that it is not fixed width, it uses a large number of processor cycles, and it can need up to 4 bytes for one character. After Unicode was defined in 1992, it was found that 2 bytes was too small a space. This led to the definition of surrogates and UTF-16, which allows the encoding of 917,476 more places. Unicode is not the complete perfect answer; however, Unicode makes programming much easier because there no longer is a need to track fifty or more codes; you can simply convert to Unicode on input, do your logic, then convert to an end language for the output. Unicode also solves the question of how to keep the characters safe. However, Unicode does not address how to enable code for global use, and it still needs to handle sorting, date format, etc. Somewhere there has to be code that recognizes and provides for the conventions of different languages and countries. Those conventions can be quite complex and may require considerable expertise to develop code for and to produce the data formats. Changing conditions and new markets also require considerable maintenance and development. International Components for Unicode IBM’s strategy is to use International Components for Unicode (ICU). ICU provides Unicode support with consistent results in both C/C++ and Java, and is a powerful, portable API available to product development teams. ICU is collaborative, open-source, and freely available. ICU is jointly managed by a group of companies and individual volunteers Operating Systems 243 throughout the world. It was developed using the Internet for interchange. ICU is licensed under the IBM Public License, which has been approved by the Open Source Initiative. The ICU code is capable of: • Character set—independent locales, with multiple locales simultaneously supported in the same thread • Character conversions • Messages and message catalogs (resources) • Transliteration • Collation • Normalization • Formatting and parsing dates, time, numbers, and strings • Searching strings • Sorting strings • Iterating over characters, words, sentences, and line breaks. As an example, the locale support includes a locale object that represents a specific geographical, political, or cultural region, thus providing an interface for defining and accessing localized display text. The user can hold the localized information in a resource bundle that can be retrieved using a Locale identifier. An operation that requires a Locale to perform its task is called locale-sensitive and uses the Locale to tailor information for the user. ICU provides greater than 150 locales to use. ICU can be used to create globalized C and C++ programs, written to be language-independent and to call on separate localized resources that hold all the end-user text. ICU code provides tested, state-of-theart Unicode and is fully portable cross-platform. Any customized data formats that drive the code can be shared at runtime across different platforms to guarantee that you get the same results when collating on an iSeries system as when collating on a PC. 244 Exploring IBM ~ iSeries Grid Computing Grid computing is the next stage in the evolution of the Internet. Grid computing is the ability, using a set of open standards and protocols, to gain access to applications and data, processing power, storage capacity, and a vast array of other computing resources over the Internet. Similar to the user of the World Wide Web seeing content when looking at the Internet, the user when looking at the grid sees one large virtual computer. Grid computing shows the potential of running commercial applications across virtual organizations. The iSeries is poised to take advantage of grid computing as business applications become available. iSeries Communications and e-business—An Introduction 245 5 iSeries Communications and e-business—An Introduction The standard functions offered by iSeries, plus the many communications options and supporting software, provide users with flexibility when configuring iSeries for various environments. However, this flexibility can also cause confusion when you are trying to determine which options and programs are needed for a particular setting. This section provides a guide through the jungle of business communications available. Communications Options in Chapter 2 looked at some communications hardware for Application Systems, and Communications Support in Chapter 4 looked at communications software support in OS/400. In this section, some of the more commonly found communications environments are examined and, where appropriate, example configurations are provided. Computer Communications in the Office— An Introduction If one activity is most crucial to a business of any size, it is the act of communicating accurate, timely, and manageable information to the 245 246 Exploring IBM ~ iSeries TE AM FL Y proper decision maker. Based on the information available, important choices are made that can have far-reaching effects on the success of the business. Improve communications in a business, and productivity and profitability are likely to improve. As a business grows, it becomes both more important and more difficult to maintain efficient, accurate communications—the very thing that facilitates business growth in the first place. Communications difficulties grow geometrically with the size of the business. Today’s businesses are quickly finding that computers are a communications tool unequaled in significance since Bell invented the telephone. Computers are already commonplace in the business environment, and now there is an increasing emphasis on computer communication. This communication can occur between two computers or among a group of computers in a communications network, and allows business information to move at electronic speeds. Furthermore, communication allows users at remote locations access to vital business information on a distant computer. The iSeries computers represent a powerful communications tool. All provide a choice of standard communications features to facilitate getting computer support through IBM iSeries Extreme Support Personalized. As was seen in Chapter 2 (under Communications Options), there is a full complement of communications options and peripherals that, with the associated software, allow iSeries to participate in many different communications environments. This chapter discusses Extreme Support Personalized, iSeries system clustering, an overview of IBM’s overall network blueprint with emphasis on the application support layer, Transport Layer Security, Secure Sockets Layer, and network computing, including environments created by intranets, electronic business (e-business), and the Internet. iSeries Extreme Support Personalized Extreme Support Personalized (ESP) includes the well-established Electronic Customer Support (ECS) functions and Universal Connection for performing many of the ECS functions over the Internet. The iSeries Extreme Support Personalized helps you manage your system, streamline your support, and reduce risk for your business. ESP develops an e-relationship with customers by means of a seamless integration between Web, data, and product; leverages the data inherent in the Team-Fly® iSeries Communications and e-business—An Introduction 247 customer’s machine; and personalizes the support supplied to the customer’s environment. Within ESP, the Universal Connection support functions have gotten faster through the use of VPN tunnels being leveraged via the Internet. Figure 5.1 illustrates the Universal Connection and ECS connection used to connect to the Rochester Support Center. Universal Connection Universal Connection provides the capability through the Internet to perform an inventory of the customer’s system including hardware and software, to download available fixes to ensure that the system is running with the most recent updates, and to gather performance data from the system using PM/400e. The foregoing applies to a single system, or to multiple systems connected on a LAN using a single Internet connection. The Universal Connection is configured using Management Central and Navigator functions. Available fixes, called Program Temporary Fixes (PTFs), are limited to 99 MB in a single Internet session. The same ECS commands are supported on the Universal Connection as are supported on the direct-modem connection for ECS. Users can send Service Application Program OS/400 Support Computer System Modem Switched telephone line 5853 Modem (for equivalent) SLIC iSeries (any model) IBM Information Network Distant computer system Your computer system Figure 5.1. Communications configuration used for electronic customer support. 248 Exploring IBM ~ iSeries Agent/Service Director data to IBM. In the event that a problem occurs in the execution of a command using the Universal Connection, assuming the ECS modem is configured, the connection automatically switches to the ECS modem. IBM Electronic Service Agent for iSeries (Service Agent) IBM Electronic Service Agent for iSeries data contains system values, licensed programs, PTF levels, and other information. IBM’s Rochester Support Center examines this information and notifies the users of information that can be requested, based on the Service Agent data. As an example, if the Service Agent data indicates that the user’s system is behind one release, an e-mail can be sent to the user explaining that a new OS/400 release has been announced. Progress indicators are present at the customer’s system during the download and application of PTFs. Users can enable remote support to allow the Rochester Support Center to connect to their system. Telnet is used to allow the Support Center to connect to the user’s system. IBM Electronic Customer Support Communications The iSeries systems come standard with the communications equipment necessary to participate in IBM Electronic Customer Support. This is a link to IBM or other support providers that allows you to obtain answers to technical questions, report problems, receive PTFs, and the like. Although it is not necessary to be a communications expert to use IBM Electronic Customer Support, understanding the basic communications link can remove the mystery. An integrated modem adapts the computer information into electrical signals suitable for telephone line transmission. OS/400 comes standard with the necessary functions to manage the telephone communications link. When IBM Electronic Customer Support is desired, the user instructs OS/400 to place a toll-free call to the IBM Information Network. The IBM Information Network is a nationwide communications network that provides many services, including connections to the appropriate Electronic Customer Support computer system. The user is then linked to IBM Electronic Customer Support and can perform the desired tasks. For simplicity, the rest of the communications configura- iSeries Communications and e-business—An Introduction 249 tions provided in this chapter do not show the IBM Electronic Customer Support communications link. You should understand that all communications configurations shown are in addition to the IBM Electronic Customer Support link that is provided with most iSeries systems. No matter what computer system a business chooses, the system and its users will require ongoing support. They will have questions that need answering, hardware problems that must be addressed, software updates that must be installed, and so forth. This support can be delivered in many different ways. Personnel from the computer manufacturer, the software company, or the business’s own staff are generally involved in supporting the computer system and its users. With iSeries systems (as well as with other IBM systems), much of this support can be provided electronically over communications networks. This is called IBM Electronic Customer Support (ECS). Just as electronic mail and online business information streamline a business’s operation, the delivery of the various types of support needed can also be improved through IBM Electronic Customer Support. IBM provides five basic areas of IBM Electronic Customer Support: • IBMLink • RETAIN • Question-and-answer database • File transfer • Copy screen. The communications hardware and software necessary to participate in IBM Electronic Customer Support are provided with every iSeries system. Access to IBM Electronic Customer Support is provided through the IBM Information Network (IIN). The kinds of things provided through IBMLink include electronic announcement letters, product catalogs, education catalogs, publication catalogs, pricing information, product configuration aids, and lists of local dealers. Users can exchange electronic notes with IBM marketing and support personnel. With proper authorization, you can also place orders, access a database of technical questions and answers, create new questions, report service hardware or software problems, and so on, all electronically over IBMLink. 250 Exploring IBM ~ iSeries IBM Electronic Customer Support also provides direct access to IBM’s RETAIN network. Over RETAIN, you can electronically report a hardware problem and send accompanying information helpful in diagnosing the problem. IBM service personnel can then automatically be dispatched—all over the RETAIN network. Similarly, software problems can be reported, and any missing program temporary fixes that are indicated by the symptoms often can automatically be sent over RETAIN. With the addition of the SystemView System Management Utilities for the OS/400, the user’s central iSeries system can become a repository for PTFs and can service any other iSeries systems over a communications link, thus becoming centralized support for their own organization. Another element of IBM Electronic Customer Support is the technical question-and-answer database. Each iSeries system is shipped with its own electronic copy of the most commonly asked questions and their answers. If the question is not contained in this local database, IBM Electronic Customer Support provides access to an IBM database with additional questions and answers. With proper authorization, a user can also create new questions that will be answered (electronically) by IBM support personnel. The file transfer capability of IBM Electronic Customer Support allows you to exchange information (e.g., a file containing your system’s configuration) with IBM marketing and support personnel as necessary. The copy screen facility of IBM Electronic Customer Support allows remote support personnel to see the same image you see on your display for the purpose of education or problem troubleshooting. Help is delivered electronically, improving access to technical and product information and streamlining communication between IBM and the users. The iSeries online education and IBMLink tutorials are provided along with an online user’s guide and help text to make the interaction with IBM Electronic Customer Support easier to use. Filter Lists APPN support includes two different types of filter lists that provide a firewall security operation for local networks as well as for the Internet. Filter lists enable the invocation of security functions for either local network protection or Internet network isolation. The session endpoint filter list controls access to and from local locations, and the directory endpoint filter list controls access to and from peripheral nodes. iSeries Communications and e-business—An Introduction 251 The session endpoint filter list defines the remote locations that are allowed to communicate with (or are rejected from communicating with) local locations. As a rule, the session endpoint filter list should be used in conjunction with the APPN remote location list and password security. There is no need to duplicate location in the remote location list. The session endpoint filter list controls user and control-point sessions and supports generic and wildcard naming. The directory search filter list is used to restrict the locations with which peripheral nodes can establish sessions by using the network identifier and control-point name of the peripheral node. Locations on the peripheral node are called filtered locations. Locations that peripheral nodes want to access are called partner locations. The directory search firewall is only as strong as its weakest link. When both session endpoint filter and directory search filter lists have been identified for a single location, the session endpoint filter list will manage the security access function for that location. System Clustering The networking function supports both local and wide area network capabilities on the iSeries. The local area networks (LANs) provide one method for horizontal growth of the system. Horizontal growth implies the ability to increase the networked system from both a capacity and a performance perspective by adding components to the existing system without having to exchange existing system components. The capacity increase occurs because the addition of a system implies the capability to add all functions of the system independent of the path by which the interconnection is achieved. The performance of a system cluster connected in a LAN is limited by the performance of the LAN itself. The types of LANs supported on the iSeries are the token-ring and Ethernet networks. The instantaneous bandwidth of each of these is 1 GBps and 100 MBps, respectively. (FDDI is a special case of a tokenring network with 100 MBps instantaneous bandwidth.) (A 10 MBps option is available for Ethernet, just as the token-ring adapter will also work at 16 MBps and 4 MBps.) The instantaneous bandwidth identifies how fast data can be passed from one system in a cluster to a different system in that cluster once a connection has been established. More important than instantaneous bandwidth is the utilization rate of the 252 Exploring IBM ~ iSeries network. The utilization rate is the proportion of the instantaneous bandwidth that is available for information exchange between systems after connection for network resources, the overhead of the network, and recovery from errors have been accounted for. The following ratios for utilization rate are approximate, but they illustrate that local area networks, although a vast improvement upon wide area networks, still leave significant room for performance improvement. Utilization starts to saturate for token-ring networks at 70 percent, for Ethernet at 40 percent, and for FDDI at 70 percent. A second methodology for adding system performance and growth via system clustering is offered by the iSeries Optical Interconnect with Object Connect/400. The hardware necessary to perform the interconnect is described in OptiConnect and Packaging Technology, both discussed in Chapter 1. The hardware has the capability of interchanging data between any two systems at an instantaneous data rate of 1,063 MBps, with a theoretical utilization rate of 70 percent. Furthermore, if more than three systems are in the cluster, as many as n/2 simultaneous conversations (where n is the total number of systems in the cluster) may be going on at the same time, as long as the necessary data exists on at least one set of each pair of systems. Data Propagator Relational/400 also works over this connection and may be used to ensure that the needed data replication exists. OptiConnect/400 with Distributed Data Management (DDM) is the application support needed to exploit this capability. In this environment, if an application needs greater performance than is available in the existing systems, an additional system is added to the clustered system network. Using the capability of parallel threads, that system will decrease the load on the other systems in the network, thereby providing the performance boost that previously required the existing processing system to be replaced (vertical growth). An additional capability, besides the system and performance growth (occurring as a result of the ability to cluster systems levels) is the capability to build redundancy into the processing, data files, and networking functions. The redundancy methodology may include a mixture of approaches—including N+1, mirroring, RAID-5, and checksums—at system and subsystem levels as needed to achieve the protection desired. All of the pass-through functions for displays and printers continue to function in the clustered-system environment. In fact, the user of the application has no perception of which system in the cluster of systems is actually executing the application. LANs and WANs may iSeries Communications and e-business—An Introduction 253 coexist on each system in a system cluster. OptiConnect/400 is the loosely coupled connection referred to in Chapter 1. ObjectConnect for iSeries ObjectConnect for iSeries provides support for efficiently moving individual objects, entire libraries, or entire Integrated File System (IFS) directories from one iSeries system to another over a standard communications connection or over a high-speed fiber optic bus. Systems can be connected using standard APPC, TCP/IP, LAN, or an HSL OptiConnect loop (fiber or copper). Not requiring save file procedures and copies to distribution queues saves DASD and improves performance in a nondisruptive manner to system operations. IBM’s Overall Networking Blueprint The IBM Networking Blueprint (Figure 5.2) is a guide to IBM’s networking commitments. The Blueprint lays out the framework for integrating into a single network multiple separate networks and their applications that use different communications protocols, different hardware components, different bandwidths, and different network-management techniques. The Blueprint incorporates existing and anticipated industry standards and open systems standards. It complements the Systems Network Architecture (SNA) communications standards as well as Open Software Foundation’s Distributed Computing Environment (DCE) and ISO communications specifications, but it does not replace them. The IBM Networking Blueprint framework provides the freedom to choose network elements to meet application and business needs, rather than force-fitting those requirements to inappropriate networking solutions. The Blueprint allows a mixture of international standards, industry standards, and architectures. As standards evolve, the Blueprint will change to keep pace. In the interest of brevity, readers having an interest in greater detail about the layers of the Blueprint are referred to Chapter 5 of Exploring IBM’s AS/400 and iSeries Computers, 10th edition. The Application Support Layer continues to be explained in detail because of the continued growth in function of the Messaging and Queu- 254 Exploring IBM ~ iSeries Networking Framework Applications CPI-C RPC MQI CONVERSATION REMOTE PROCEDURE CALL MESSAGE QUEUING APPC OSI TP STANDARD APPLICATIONS DISTRIBUTED SERVICES FTAM X.400 TELNET FTP DATA DIRECTORY SECURITY RECOVERY MGMT SOCKETS DCE COMMON TRANSPORT SEMANTICS SNA APPN OSI TCP/IP NetBIOS IPX LANS X.25 Cell/Packet Frame Relay Physical Figure 5.2. tions layer. iSeries Multi-Protocol Networking Blueprint Interface applica- ing Interface (MQI) (MQSeries). The Blueprint is divided into four layers, representing the elements necessary to make up a network: • The applications layer • The application support layer – Multi-Vendor Application Program Interfaces – The CPI-C Interface iSeries Communications and e-business—An Introduction • – The Remote Procedure Call – The Messaging and Queuing Interface (MQSeries) – MQSeries Adapter The transport network layer: SNA-TCP/IP-MPTN-APPN – • 255 Multiprotocol Transport Networking The subnetworking layer Application Support Layer The second layer, the application support layer, represents multi-vendor application interfaces and services. There are three primary interfaces (see Figure 5.3): Common Programming Interface for Communications (CPI-C), Remote Procedure Call (RPC), and the Messaging and Queuing Interface (MQI). Each of these interfaces is described in greater detail in Multi-Vendor Application Program Interfaces, following. The application support layer also contains a set of distributed networking services for handling messages, security, directory, and transaction processing. Standard networking applications, such as file transfer programs, also fall within the application support layer. Although not shown on the IBM Networking Blueprint, CICS/ESA could be considered to span both the applications layer and the application support layer. Both products contain APIs and provide application support services, so they fit within the application support layer, but the APIs are application-enabling APIs, also making them part of the applications layer. The CICS API may be thought of as an extension to many of the application development languages, allowing application development without the concern for the underlying network. Multi-Vendor Application Program Interfaces The following paragraphs discuss the CPI-C interface, the Remote Procedure Call, and the messaging and queuing interface. Exploring IBM ~ iSeries Networking Framework Applications CPI-C RPC MQI CONVERSATION REMOTE PROCEDURE CALL MESSAGE QUEUING APPC OSI TP STANDARD APPLICATIONS DISTRIBUTED SERVICES FTAM X.400 TELNET FTP DATA DIRECTORY SECURITY RECOVERY MGMT SOCKETS AM FL Y DCE COMMON TRANSPORT SEMANTICS SNA APPN LANS OSI TCP/IP TE 256 NetBIOS IPX X.25 Cell/Packet Frame Relay Physical Figure 5.3. iSeries Multi-Protocol Networking Blueprint Interface applications support layer. The Common Program Interface (CPI-C) The CPI-C interface supports communication between application programs over private logical connections called conversations. Conversational communication is a sophisticated method of program-to-program communication requiring simultaneous execution of partner programs. It is designed primarily for a structured exchange of information between programs and requires that a network session be reserved exclusively for the communicating programs. CPI-C applications are generally client/server or peer-to-peer implementations. Team-Fly® iSeries Communications and e-business—An Introduction 257 Operating systems use Advanced Program-to-Program Communication (APPC) services to assist in the implementation of conversational applications through CPI-C. In spite of the sophistication of conversational applications, they are surprisingly easy to implement. APPC/MVS in MVS/ESA, for example, offers built-in server functions that can be used in client/server conversations. APPC/MVS services are callable services, so they can be accessed from a high-level language application without the necessity of writing assembler language routines. The Remote Procedure Call The Remote Procedure Call (RPC) function provides communications between applications using a call/return mechanism, much like doing FORTRAN library subroutine calls. RPC applications are client/server implementations. The client program (the caller) is responsible for determining the server location (the called procedure) in the network, establishing the necessary communication, and passing the required parameters for the procedure execution. This is a synchronous operation. The caller waits until the procedure finishes execution and the results are passed back. Again using MVS/ESA as the example, different vendor implementations of RPC are supported. Today, workstations with applications implementing RPC can operate as clients with MVS/ESA using the TCP/IP product. TCP/IP also supports Apollo Computers’ Network Computing System RPC. The OSF/DCE RPC is supported using the POSIX-compliant application-programming interface. The Messaging and Queuing Interface (MQSeries) The Messaging and Queuing Interface (MQI) MQSeries (5716-MQ1) is an asynchronous program-to-program interface that supports message-driven, deferred processing. Communication is through queues, not through private connections. Programs that use MQI fill and empty message queues. The calling program places the request in a queue but does not wait for a response; instead, it continues with its processing, and when the response arrives, it is placed in a queue to await processing. MQI services route the messages to the appropriate destinations in the network for access by the programs servicing the queue. MQI applications can be client/server, peer-to-peer, or more complex implementations. MQI provides guaranteed message delivery, recoverability, and, 258 Exploring IBM ~ iSeries where applicable, sync-point participation. MQSeries provides messaging services between disparate systems. Delivery of messages is assured. MQSeries Integrator improves the ease of use and ease of deployment of MQSeries. It provides an open, modular development environment where rules and routing can be set up visually to help provide reliable messaging. MQSeries is XML-compatible. When messages are broken into multiple packets that are sent over separate routes, the packets do not necessarily arrive in the correct order, and the sync points allow the message to be reconstructed regardless of the order of the packet reception at the final destination. MQSeries allows distribution lists to put a single message in multiple queues with a single call. Messages can be grouped and segmented. Channel definitions can automatically be created for receiver and server channel connections. Those channels can be fast, use heartbeat detection, and support auto-definition. Large transactions can use message segmentation, ordering, and grouping to improve checking of transactional data. The ability to reference messages with chained exits allows large amounts of data to be transferred between nodes. The ability to use C++ for MQI applications and the ability to perform static bindings in ILE RPG programs make programming easier. Channel heartbeats provide faster recovery when the system stops or resets, and when data needs fast delivery, more programs can take advantage of fast, nonpersistent messages. A dead-letter queue handler has been added. The maximum message size is 100 MB, and the maximum queue size is 2 GB. Multiple queue managers exist with the capability to manage clusters of messages to deliver high availability and redundancy. The configuration can apply to an entire MQSeries installation, or to individual queue managers, or to individual jobs for individual queue managers. Support is provided for threaded applications, MQSeries classes for Java, bindings for COBOL, and utilization of OS/400 Work Management. Nonpersistent messages are stored in shared memory, and persistent messages are stored as objects in the Integrated File System and are logged in the Journal. MQSeries now uses an MQ Object Authority Manager which requires that all Exit programs be recompiled, because OS/400 authorization lists and reference objects are no longer supported; in addition, the Admin object can no longer be used for context and alternate user authorities. Object Authority Manager updates do not require a queue manager restart. MQSeries Adapter. It may not be possible to directly enable existing applications for MQSeries because the source code may not be available; iSeries Communications and e-business—An Introduction 259 or recompiles are not desired; or packaged applications may not have a defined set of interfaces or APIs; or there may exist a tight coupling of user interface and business logic, and the data may not lend itself to being broken down into components. To meet this need, IBM offers an adapter to handle the session layer complexities and the data/presentation layer mappings and transformations. IBM’s MQSeries adapter provides a point-to-point messaging solution for integrating applications by using IBM MQSeries for reliable messaging between different networks, platforms, and applications. A standard XML format is used for representing data and transaction types by means of picking up the Business Object Documents definition from Open Applications Group Inc., defining standard business transactions (e.g., create sales order or show item availability). The adapter can be used with other MQSeries products such as Integrator and Workflow. The MQSeries Application Messaging Interface is a framework for simplifying the messaging API for business application programs which provides a split between the roles of application programming and administration. The framework provides for applications extensions like error handling and audit trails, interoperation with message brokers like MQSeries Integrator, a message transport API, and simplified application development. MQSeries Integrator is an add-on for business integration applications that provides intelligent message routing based on content, data formats, and translations, thereby reducing the programming effort required to integrate platforms and applications. Transport Layer Security (TLS) The TLS protocol is an evolutionary upgrade of the SSL Version 3.0 protocol, and shares the same basic record construction and line flows. TLS provides the same function as SSL and is compatible with SSL, but includes new features and clarification for protocol flows. This helps to standardize the SSL definition and implementation, making the SSL protocol more secure and the specification of the protocol more concise and complete. TLS support on the iSeries server allows IBM customers and Business Partners continued access to take advantage of the latest technology implementation of Internet application security enablement in the industry. TLS support is automatically part of any SSL-enabled application, like HTTP and TELNET servers. Parameter values on the SSL 260 Exploring IBM ~ iSeries APIs enable TLS for business partner and customer-provided SSL applications. e-business Figure 5.4 illustrates the elements of a complete e-business solution, and the paragraphs that follow provide the IBM iSeries implementation of that solution. Chapter 4 described many of the components of that solution. This chapter completes the description of communications components not described in Chapter 4. In the area of security, all OS/400 components and LPPs will be signed in order to detect any piece of OS/400 software that is tampered with. Support is provided for Business Partners to also sign their software. Hardware Cryptography provides secure key storage as required by advanced financial applications, and APIs for business partners to develop financial applications. A Digital Certificate Manager provides the capability to create object signing certificates, and those certificates can elect to use the hardware cryptogra- Device Support Browsers PDAs Cell Phones Applications Networking Services Application Services Utility Services TCP/IP Routers VPN IP Security Wireless Access Quality of Service HTTP Server Web Appl. Server (Servlets, JSP, EJB) Server Side Scripting Java Engine Java Class Library Code Repository XML Services Search Engine Print Services Cache Manager Clustering Services Directory Security Database Queuing Certificate Manager Back-end connectors Payment Services Documentation Tools Redbooks White Papers Experience Reports Web Pages WebSite Development WebSite Management Application Development Setup Wizards Figure 5.4. A complete e-business solution. Solutions Commerce Solutions (B2C And B2B) Mail/Collaborative Solutions Custom Applications iSeries Communications and e-business—An Introduction 261 phy card to store the private key. Kerberos is used to provide distributed authentication in a network environment, and is also used by OS/400 applications to authenticate users. As implemented for the iSeries, e-business encompasses multiple Internet application enablers, IBM HTTP Server for iSeries, WebSphere Application Server for iSeries, Net.Data, IBM HTTP Server for iSeriespowered by Apache, OS/400 Directory Services, Firewall, and Net.Data. E-business is a rapidly emerging environment in which the Internet is used to provide opportunities for building strong customer relations in addition to performing sales transactions. Net.Data can be used by WebSphere Application Server for iSeries. Network Quality of Service (QoS) Network Quality of Service is of interest to Internet users providing application servers for e-business, application service providers, business-to-business providers, network security gateways, and providers of networking hardware devices for network support of QoS (Policy Enforcement Points, or PEPs). Providers of application servers for e-business need: • Predictable e-business transactions and mission-critical applications • Ability to classify important traffic at the source • Ability to enable application vendors to customize their applications for e-business availability (via APIs and or policies). Business-to-Business (B2B) providers and Application Service Providers (ASPs) have a need for servers that will be in B2B or ASP environments to provide predictable e-business service to comply to requirements of Service Level Agreement providers. Network security gateways couple QoS and VPN to provide guaranteed security and predictable e-business flows. Networking hardware devices for network support of QoS include routers and switches. Quality of Service support in iSeries enables the establishment of the class of service required either by honoring application requests for an amount of end-to-end bandwidth or based on a given type of traffic priority (differentiated services). Targets for the QoS support include: 262 Exploring IBM ~ iSeries • Can be secured using integrated VPN • Is standards-based and interoperable • Is easy to set up and deploy. There are several mechanisms included in the technologies for QoS traffic handling. Network QoS for iSeries concentrates on two of those possible mechanisms—Integrated Services and Differentiated Services. Integrated Services is provided by a framework for supporting conversations/per flow bandwidth requirements (using an RSVP method). Differentiated Services creates classifications of traffic flows to aggregate traffic handling based on classes of service. Differentiated Services are usually used for large routed networks. The initial Quality of Service content includes RSVP APIs (comply with the X/Open standard) for the establishment of three types of services. Those services include guaranteed service, controlled load service, and qualitative service. The foregoing are QoS-aware applications. Also offered is policy-based QoS for applications that are not aware of QoS, creating an easy mechanism to enable QoS for applications without changing the application itself (Differentiated Service only). These QoS policies enable the configuration of: • Users • Applications • Classes of service • Schedules • Overall policies for QoS. A Monitoring API is supplied for collecting runtime QoS policy information. The monitor GUI is provided in iSeries Navigator to track traffic flow and QoS policies. It is possible in iSeries to configure the network, not the systems in the network. QoS is directory-enabled, allowing policies stored in LDAP to be shared across many systems in the network. Rather than configur- iSeries Communications and e-business—An Introduction 263 ing a single system in Navigator for iSeries, the Network QoS policy can be exported and stored in an LDAP directory. System-administration tasks associated with building and deploying Network QoS policies have been simplified. Inbound connection controls can be used to limit the rate of inbound connections, not only to provide Network QoS, but also to help prevent denial-of-service-type of network attacks. Denial-of-service attacks are one of the simplest forms of attack, but among the most difficult to prevent. The administrator can build policies based on URLs rather than IP addresses, ports, and protocols, giving priority to the URL used to support online B2B commerce type of transactions. It is also possible to define no signaling QoS policies requiring changes on the server side. This allows RSVP to be completely transparent to the client. Intranet An intranet is a local area network, or network of local area networks, that uses Internet protocols and tools such as a Web browser, File Transfer Protocol (FTP), or TCP/IP to move data and programs between the server and the clients. As a rule, the security functions on an intranet are more relaxed than they are on the Internet because the users are trusted users. Some security policy still needs to be used, and this should include user authentication, resource protection, system integrity, data integrity, and a security audit. Being trusted users means that the users do not fit the definition of hackers, or crackers, at least as far as the enterprise using the intranet is concerned. (A hacker is any unauthorized person who tries to break into the system; a cracker is a hacker with malicious intent.) The transport protocols for the LAN may still be token-ring or Ethernet, but the messaging protocols embedded within the token-ring or Ethernet delimiters are Web-compliant. IBM SecureWay: iSeries and the Internet You might say that an intranet/Internet system is only as good as its security mechanism. In addition to the specific security offerings for protecting the system on the Internet, iSeries has very strong system security characteristics, including the following: 264 Exploring IBM ~ iSeries • Integrated security, which is very difficult to circumvent compared to add-on security software packages offered on other systems. • Object-based architecture, making it technically difficult to create and spread a virus. On an iSeries, a file cannot pretend to be a program, nor can a program change another program. The integrity features of iSeries require the use of system-provided interfaces to access objects. It is not possible to access an object directly by its address in the system. An offset cannot be taken and turned into, or manufacture, a pointer. Pointer manipulation is a popular technique for hackers on other system architectures. • The OS/400 operating system and the Licensed Program Products offered on the iSeries eServers are digitally signed objects, which prevents modification without the appropriate verification of authorization and authentication. • Secure Sockets Layer (SSL) (see discussion below for additional information about SSL) applications communication security allows the configuration of applications to use SSL to establish secure connections between server applications and their clients. Many iSeries server applications are now enabled for SSL, including Access Express for iSeries, File Transfer Protocol, Telnet, and many others. The following sections discuss the security features specifically related to the Internet, including Cryptographic Access Provider, Digital Signatures, HTTP Server for iSeries, HTTP Server for iSeries—Powered by Apache, Digital Certificate Manager with SSL, Secure Sockets Layer, Security Wizard, and Firewalls. Cryptographic Access Provider The cryptographic products listed below enable encryption in the iSeries for use by products such as HTTP Server for iSeries. One of these products must be installed to enable the SSL function. The 128-bit encryption product is now available for most countries. SSL protects data exchanged between a Web server and a browser. Standardization of iSeries Communications and e-business—An Introduction 265 DRDA password encryption with 128-bit DES security between iSeries and DB2 family products ensures secure data exchange between heterogeneous systems using those products. The following products provide software encryption on the iSeries servers: • 40-bit encryption for iSeries (5769-AC1) • 128-bit encryption for iSeries (5769-AC3). In addition, the following products provide software encryption on the iSeries clients: • 40-bit encryption for iSeries (5769-CE1) • 128-bit encryption for iSeries (5769-CE3). There are four options that control the user profile password level of the system, including 10-byte length and netserver passwords and 128-character-length password formats. The default is a level 0, 10character limit with restricted character set. All connected systems must be running with the same password level because of flowing encrypted password substitutes. Care must be taken because some of the older systems do not support long passwords. When observability is removed from a program, the program creation data needed for retranslation is kept in a compressed portion of the program object. No user interface exists to access the program creation data once observability has been removed from the program. This allows re-creation of the program object in order to help ensure integrity, and the capability to take advantage of enhancements in system translator technology for new hardware at a later time. The AES crypto algorithm is supported for application use through the MI CIPHER instruction. The AES crypto algorithm is faster than the DES crypto algorithm. The Generic Security Service (GSS) Application Program Interface for secure exchange of information between applications is supported for network authentication. GSS is a framework into which different mechanisms can be plugged, yielding a set of security services on a permessage basis and providing integrity and confidentiality of the message. GSS also enables message replay and sequencing and source anonymity. 266 Exploring IBM ~ iSeries Digital Signatures AM FL Y The GSS framework can be accessed by applications using a set of generic APIs regardless of the mechanism used to provide the service. Kerberos, a three-party distributed authentication protocol designed by MIT, is also supported for network authentication. Kerberos provides distributed authentication in a heterogeneous environment. Full path names have been added to the IFS auditing entries. Usage parameters have been added to retrieve validation list APIs. A delay has been added for consecutive invalid password attempts, and the client to the iSeries FTP server supports SSL. TE The integrity of software and data is improved through the use of Digital Signatures. Information can be signed by business partners, customers, and IBM to provide improved integrity in their products. Digital Signatures aid in the identification of data tampering, virus introduction, or any other modification to an object. The signature also helps identify the originator of the data or software. OS/400 itself is signed. Support exists for command objects and nonobjects to be signed. The nonobject support can be used to write applications that sign items such as digital receipts and business-to-business (B2B) transactions. HTTP Server for iSeries HTTP Server for iSeries, known previously as Internet Connection Server, provides secure Internet connections. Security is improved through the use of digital certificates. Authentication includes both client and server authentication through the use of Secure Sockets Layer (SSL) V3. Client certificates can be associated with iSeries user profiles or validation lists, allowing users seamless access to Web server resources without having to sign on. If the environment has Socks-based firewall for access to the Internet, the HTTP server for iSeries can be used as a proxy server to access destinations outside the firewall. Client connections using SSL are tunneled through the proxy server, eliminating the need to decrypt and encrypt the data at the proxy. Common Gateway Interface (CGI) support includes Java, REXX, and C++. The server can be bypassed on Team-Fly® iSeries Communications and e-business—An Introduction 267 output using the no-parsed header CGIs. Any code page conversions the server performs on a Web application’s input or output can be fully configured. The HTTP Server for AS/400 is transformed into a Javaenabled Web server using the WebSphere Application Server as a portable, Java Servlet-based execution environment. Support is provided for the latest session-tracking APIs, personalization support, and Java Server Pages. Java servlets can be used to provide additional server cache functions and dynamic Web applications. HTTP Server for iSeries has been enhanced for worldwide use with support for double-byte searches. Users can write applications that extend or customize how the Web server handles client requests with Server API Support, a follow-on to ICAPI. The unique capabilities of customer browsers can be exploited using Automatic Browser Detection—e.g., different documents can be provided to different clients based on the browser those clients are using. Improved management is provided by the addition of: SNMP Subagent, Web Activity Monitor, Web usage mining, logging and archiving of reports, and NLS-enabled logging; the Extended Log format is supported. PICS support allows a security rating of information on a Web site. LDAP support enables storage of ACLs and configuration files. Additional features of IBM HTTP Server for iSeries include: • • Digital ID authentication requires SSL client authentication for HTTP server client certificates, offering resource protection with: – Valid client certificates – Client certificates with certain distinguished name values – Client certificates associated with iSeries user profiles – Client certificates associated with iSeries validation lists. HTTP server logs, statistics, and status can be remotely accessed to see how your HTTP server is functioning. Reports can be generated and viewed on how your HTTP server is being used. SNMP Subagent allows the use of any SNMP-capable network management system, such as TME 10 NetView, TME 10 Distributed Monitoring, or HP OpenView to monitor your server’s throughput and activity. 268 Exploring IBM ~ iSeries • A broader use of industry-wide Log Analysis tools is allowed through Extended Log format. Log file customization and log archiving allow the management and maintenance of log files. Error logs are NLS-enabled. • The administration of certificates is centralized in the Digital Certificate Manager (DCM) product (discussed earlier under Digital Signatures). The HTTP server is a certificate customer. • Dynamic caching of Web pages gives better static page-serving performance without manual configuration. • APIs are provided to allow third-party tools to access configuration information. – To map a URL (request) through the Map/Pass/Exec/Fail rules of the server’s configuration and to output the physical resource on the server. – To return the value(s) of a given configuration directive. • Domino runs on top of IBM HTTP Server. • Built-in search capability for SBCS and DBCS data. Apache Software Foundation (ASF) functions that enhance HTTP Server for iSeries include: • Support for the latest Apache 2.0 level offering filtering, I/O buffering, and the latest code fixes from ASF. • Support and documentation of the Apache Portable Runtime (APR) APIs. The APR APIs allow user-written modules to be platform-independent, allowing Web developers to write modules and applications independent of the platform and easing the applications transition to the iSeries platform. Operatingsystem-specific functionality is encapsulated into the APIs provided by the IBM HTTP Server product. – Header files are provided for all supported APIs. iSeries Communications and e-business—An Introduction – • • • 269 A sample user module (mod_example) which demonstrates a use of the Apache APIs is provided. Support for Server Side Includes (SSI). SSI tags are comments within HTML that direct the Web server to dynamically generate information for the page. SSI tags allow a Web developer to include common HTML statements so that they are easily managed and are consistent across an entire Web site. These HTML statements could be headers and footers. SSI can be used to include static HTML, to call and execute programs (such as through CGI programs), and to allow the insertion of results. SSI support includes two varieties of SSI and CGI combinations: – Parse an HTML document and include the output of a CGI program as a dynamic content on an HTML page. – Parse the output of a CGI program to resolve SSI tags prior to returning the output to the client browser. Support for WebDAV (MOD_DAV). WWW distributed authoring and versioning (DAV) is a set of extensions to the HTTP protocol that allows users to collaborate to edit and manage files on remote Web servers, providing a network protocol to create interoperable, collaborative applications. Features of the protocol include: – Locking (Concurrency Control) provides long-duration exclusive and shared write locks, which prevent the overwrite problem where two or more collaborators write to the same resource without first merging changes. – XML Properties provide storage for arbitrary metadata, such as a list of authors on Web resources. These properties can be set, deleted, and retrieved using the DAV protocol. – Namespace manipulation is required because resources may need to be copied or moved as a Web site evolves. Collections, similar to file system directories, can be created and listed. Support for Apache MOD_REWRITE provides a rule-based rewriting engine to rewrite requested URLs on the fly. 270 Exploring IBM ~ iSeries • Support for named protection setups allows the same set of authentication directives to be defined across multiple containers by the use of include files. • Support for group files proves the ability to grant access to resources based on a defined group of users. The IBM HTTP Server for iSeries includes industry-standard Java Servlet and JavaServer Pages based on technology from the Apache Software Foundation’s Jakarta Tomcat open-source code base: • Lightweight and easy-to-use software is provided as an extension to the IBM HTTP Server (Powered by Apache) Web server and is compliant with Java Servlet 2.2 and JavaServer Pages 1.1 specifications. • ASF’s Jakarta Tomcat support can be used as a simple starting point for those business partners and customers interested in learning about or piloting Java Servlet applications. For more information on HTTP Server for iSeries refer to: http:// www.ibm.com/eserver/iseries/software/http. For more information on WebDAV, refer to: http://www.webdav.org. For more information on Apache Software Foundation, refer to: http://www.apache.org. HTTP Server for iSeries—Powered by Apache HTTP Server for iSeries—Powered by Apache is a collaborative software development implementation of an HTTP (Web) server. The Apache Software Foundation (ASF) was formed in 1995 and consists of a core group of contributors, including IBM. The Apache Web server is a powerful, flexible HTTP/1.1-compliant Web server that is highly configurable and extendable with third-party modules. The Web server can be customized using the Apache module API. Apache provides full source code and comes with an unrestricted license. The Web server runs on Windows NT/9x, Netware 5.x, OS/2, and most versions of Unix, as well as several other operating systems (including OS/400). The Apache Web server implements many features, including: iSeries Communications and e-business—An Introduction • Customized responses to errors and problems • Multiple directory/index directives • Unlimited flexible URL rewriting and aliasing • Content negotiation • Support for Virtual Hosts. 271 Apache is IBM’s strategic HTTP server. The intention is to leverage the large Apache install base and development community to give the IBM programming model WebSphere Application Server (WAS) its widest possible starting base. The iSeries-specific strategy is to port to the iSeries ILE environment by providing equivalent function to the existing HTTP Server for iSeries and add iSeries integration of features including user profile, SSL, validation lists, LDAP, etc., to the eventual replacement of the existing HTTP Server for iSeries. The iSeries implementation of this strategy is as follows: the source code comes from ASF, then add iSeries customization, and subject the result to iSeries development and test processes. Some of the iSeries differentiators from Apache on other platforms include enhanced graphical configuration and administration; configuration APIs; can serve from most iSeries file systems; will perform EBCDIC/ASCII code page conversions; and supports ILE, REXX, Java Net.Data, and PASE CGI programs. HTTP Server Powered by Apache also allows for persistent CGI, user-defined methods, and WebDAV, and supports LDAP configuration. Security requests for iSeries run under user profiles and reference user profile and validation lists. Secure Sockets Layer (SSL) is used for HTTP transactions, including Transport Layer Security (TLS). When required, HTTP communication between the browser and the server is encrypted. This requires a digital server certificate, requires the existence of Cryptographic services on the iSeries, and is supported by iSeries Digital Certificate Manager. Included in the differentiators from other platforms are local and dynamic caching for static documents, and a triggered cache manager for caching of dynamic documents. This HTTP server can use asynchronous I/O, which allows the use of persistent HTTP connections without impacting performance. The server: 272 Exploring IBM ~ iSeries • Performs automatic rollover and archiving • Maintains an NLS-enabled error log and configuration errors • Follows the rules for Automatic Telnet denial of service detection and prevention • Provides a Web Server search engine • Supports dynamic Virtual Hosting. Multiple HTTP servers can exist on a single iSeries system, with each server running separate jobs/processes. The HTTP server also supports multiple IP addresses, multiple Host names. HTTP Server powered by Apache is supported on the WebSphere Application Server (WAS). Digital Certificate Manager with SSL The iSeries is able to serve as a digital certificate manager (DCM). This means that the iSeries can set up an intranet certificate authority, sign client and server certificates, distribute client certificates via a Web browser, and provide support for MD5 and SHA-1 hash algorithms. The iSeries accepts digital certificates for authentication. Both the HTTP and LDAP servers support these certificates, which are used for identification only. A digital certificate is associated with a user profile and with a user in a validation list. Digital certificates are also accepted as a Web server sign-on. The support for X.509 certificates is generalized to allow it to be used by Web server, secure sockets layer, IP/Sec, iSeries Access, and other applications. Global server certificate support has been added to the certificate services available on the iSeries. The Web server and other applications that use certificates for network and Web-based security can use this support. DCM can provide certificates for multiple applications in a single system-certificate store. Applications can also register to use system certificates, and clients can renew certificates. The iSeries Digital Certificate Manager is intended to provide a limited certificate authority (i.e., manage a few certificates, not supply the function of a net registry or a vault registry). iSeries Communications and e-business—An Introduction 273 DCM can create and manage certificates that can be used to sign objects to ensure their integrity and provide proof of origination for objects. DCM can also create and manage the necessary corresponding signature verification certificates used to authenticate the signature on a signed object. This is done to ensure that the data in the object is unchanged and to verify proof of the object’s origination. DCM can also be used with the appropriate APIs to sign an object and verify the signature on an object. OS/400 and IBM LPPs are digitally signed by IBM. Users can verify that programs from IBM have not been altered since they were signed by IBM. Digital signature verification can be performed at restore, or through the CHKOBJITG command. IBM is also making APIs available to allow customers and business partners to digitally sign and verify their applications. Virtual private networking (VPN) certificate support avoids the risk associated with exchanging the private key by using digital certificates to authenticate the endpoints instead of using a pre-shared key. DCM can also be used to manage the certificates that your IKE server uses for establishing a dynamic VPN connection. Secure Sockets Layer (SSL) Secure Sockets Layer (SSL) is the industry standard for enabling applications for secure communication sessions over an unprotected network (read Internet). Following the SSL protocol can establish secure connections between clients and server applications which provide authentication of one or both end points of the communication session. SSL was originally developed by Netscape Communications Corporation for securing Web browser and server communications. The SSL specification was designed with a methodology that allows other applications to be enabled to use SSL. The following iSeries applications are enabled for using SSL support: • IBM HTTP Server for iSeries • IBM HTTP Server for iSeries—Powered by Apache • FTP Server 274 Exploring IBM ~ iSeries • Telnet Server • Distributed relational database architecture (DRDA) and distributed data management (DDM) server • Management Central • Directory Services Server (LDAP) • iSeries Access Express applications, including iSeries Navigator • Applications written to the iSeries Access Express set of application programming interfaces (APIs) • Programs developed with Developer Kit for Java and client applications that use IBM Toolkit for Java • Programs developed with Secure Sockets Layer APIs or Global Secure Toolkit (GSKit) APIs which can be used to SSL-enable applications. SSL is actually two protocols—a record protocol and a handshake protocol. The record protocol controls the flow of data between the two end points of an SSL session. The handshake protocol authenticates one or both end points of the SSL session and establishes a unique symmetric key used to generate keys to encrypt and decrypt data for that SSL session. Security Wizard The iSeries continues the theme of making the interface with the system easier by providing a security wizard to assist in setting up the security function with a Windows-like methodology. The security wizard asks questions about the iSeries system and recommends how base system security should be configured. It is possible to apply some or all of the recommendations or to save the recommendations for later application. If the decision is to save the recommendations, the next time the security wizard is executed, the recommendations can be applied from the first screen. If changes are applied, the next time the wizard is started, a iSeries Communications and e-business—An Introduction 275 reset changes option appears on the first page to change the security configuration back to what it was before the changes were applied. The security wizard generates an administrator report showing the recommended settings and how those settings affect the behavior of the system. The security wizard also generates a user report containing the information that users need to know about the system, including password-composition rules and job time-out intervals. The selected images illustrate the process used by the wizard and the extent of the resulting security management. Both reports are NLS-enabled and are saved as text files that can be loaded into an editor or word processor. Firewalls A firewall controls the access and flow of information between a secure (trusted) network and a nonsecure (untrusted) network. Usually a combination of hardware and software provides the firewall function. IBM suggests the use of firewalls where any connection to the Internet may possibly occur. The firewall may be formed using a separate system. Firewalls can provide the following benefits when your network is connected to the Internet: • Controlled access to internal systems • Concentrated security administration • Enhanced privacy and secrecy of your network configuration • Enforcement of your security policy • Protection of vulnerable services, such as network file systems • Improved system availability by blocking denial-of-service attacks • Statistics of network use and misuse • Protection of your organization’s reputation as secure and reliable. Some common firewall functions are traffic blocking, network gateway, and domain name serving. Traffic blocking blocks unwanted traf- 276 Exploring IBM ~ iSeries fic between the secure and the nonsecure networks. The network gateway function hides both the Internet Protocol (IP) addresses and the domain names of your internal network (intranet) from the Internet. The domain name serving function makes it appear to the Internet that the firewall name is the source of all outbound traffic and also manages the routing of inbound traffic to the appropriate intranet addresses. It is critical that other domain servers be unable to use your firewall to resolve your intranet domain names. AM FL Y iSeries and the Internet TE This section considers the system connection shown in Figure 5.5. In this connection there are several iSeries systems and PCs linked via a local area network. One of the iSeries systems is a server to the local network and acts as a firewall to the modem connection to the Internet iSeries System Firewall Monitoring Integrated PC Server Firewall Proxy Servers SOCKS Server Internet Packet Filter External DNS Untrusted Network Secure Network T Figure 5.5. T Router T Integrated xSeries server firewall inside the iSeries system. Team-Fly® iSeries Communications and e-business—An Introduction 277 systems. The Internet, which grew out of the ARPA net, was defined as a result of the Cold War and today consists of a worldwide network of networks connected to each other and a suite of cooperating applications that allow computers connected to this network of networks to communicate with each other. The Internet provides browsable information, file transfer, remote logon, electronic mail, news, and other services. Often referred to as the Web or the net, the Internet is based on TCP/IP communications and basically uses the addressing and protocols defined in TCP/IP to provide access to its users. Internet terminology is defined at the application protocol level (because that is the level at which most users interact with the Internet), and in the process iSeries-supported functions are identified. Information exchanges on the Internet proceed as follows: 1. A client requests connection to a URL through a Web browser. 2. The Internet server hosting that URL provides the ability to browse that location through a home page and links, transfers files from the server to the client, or allows electronic commerce such as the requesting of information or ordering of products. In any case, the Internet server writes the information to the client’s main storage or disk storage and disconnects from the client while the user takes time to investigate the information received. With the iSeries support for the Internet and the appropriate set of identifiers and passwords, it is possible to access the Web through the iSeries to obtain information; but as an Internet user, the iSeries can also be used to develop a program, download that program to your system from a remote site, download the information to execute against that program, and execute the program at a local system. A user has the option of accessing information in any of the files on the iSeries and having that information HTML-formatted on its way to the user’s system. The user can have the iSeries execute the program and only present the output in HTML format to the Web browser, and it can develop an application on the iSeries using CGI/WGS or the Net.Data and have that application downloaded to the browser. Finally, to make this all work, the HTTP server requires that the system administrator grant object access to the user profiles under which the server runs and then grant permission to the server to serve specific 278 Exploring IBM ~ iSeries objects. If the server is on a system with multiple network addresses, it can be configured to serve different files based on the IP address that comes in on a request. Multiple server instances can also be configured by using either a different IP address or a single IP address and different ports for each server instance. As an example, an Internet service provider can configure a single server for multiple Web site customers with different welcome pages, mapping rules, and access control. Both Java and Java applets fit within this scenario. To complete the discussion of the Internet, let’s use the Distributed iSeries Network example. Instead of connecting the iSeries servers with WAN communications, let’s connect them through the Internet. Each system or system cluster requires a single communications line with a modem. The system user requires a connection to a service provider such as America On-Line, Compuserve, or Prodigy, or to an independent service provider. Assuming maximum security measures have been implemented, data, e-mail, and files as well as programs can be exchanged between the systems at lower costs because there is no charge for leased lines or long-distance telephone services other than the charge for the Internet service provider. IBM allows you to download PTFs via the Internet. IBM WebSphere Application Server for iSeries (WAS) WebSphere Application Server for iSeries is an e-business application deployment environment built on open standards-based technology. It is the cornerstone of WebSphere application offerings and services. WebSphere is a set of software products that help in the development and management of high-performance Web sites to ease the transition from simple Web publishing to advanced e-business Web applications. WebSphere Application Server for iSeries is available in two editions, Advanced Single Server Edition (5733-AS3) and Advanced Edition for iSeries (5733-WA3). The Advanced Single Server Edition is based on a servlet-based engine that turns the existing Web server (HTTP Server for iSeries) into a Java Web application server, and is a core element of the Application Framework for e-business. The Advanced Single Server Edition for iSeries is the foundation of the WebSphere application server family and offers application developers a solution to build, deploy, and manage e-business Web sites. The Advanced Edition includes the capabilities of the Advanced Single Server Edition with additional support for scaling Web sites into security-enhanced, transactional iSeries Communications and e-business—An Introduction 279 e-business application sites. Connection Pooling is supported with the full support of JDBC 2.0. Only 128-bit versions are available; support is dropped for the 56-bit versions. The system administrative tools include XML config, Web-based administration, and a WebSphere Control Program. WebSphere Host Integration WebSphere Host Integration provides a way to rapidly Web-enable host applications. Included are IBM Host access Client Package V1 with Personal Communications V5.0, WebSphere Host On-Demand V5.0, Screen Customizer V2.0, and WebSphere Host Publisher V2.2 which enables the ability to create new host applications by combining multiple host sources into a single HTML page. WebSphere Application Server—Express for iSeries WebSphere application server—Express for iSeries provides fast, productive development, deployment, and management of dynamic Web sites. IBM WAS-Express for iSeries is a Java and Web Services technology-based application platform integrating enterprise data and transactions with the dynamic e-business world. Providing the iSeries in an e-business application deployment environment with a set of application services including transaction management, security, performance, availability, connectivity, and scalability. Leveraging open technologies and application program interfaces (APIs), it manages and integrates enterprise-wide applications. Integrated support for Web services open standards solidify the iSeries role as the integrator of the WebSphere software platform. WAS-Express for iSeries is tightly integrated with the iSeries HTTP server through easy-to-use Web based GUIs. Wizards allow for configuration of multiple application servers and the deployment of those servers, as well as access to iSeries databases. WAS-Express for iSeries offers support for: • Servlets, based on the Java Servlet 2.3 specification • JavaServer pages, based on the JSP 1.2 specification • Web services standards like SOAP, WSDL, and UDDI offers companies the ability to create secure distributed applications that 280 Exploring IBM ~ iSeries integrate software components developed with disparate tools and architectures over the Web. • JDBC 2.0, JNDI, JavaMail 1.2, JavaBean Activation Frameworks (JAF) 1.0, and Java API for XML parsing (JAXP) • Server-side JavaScripts using the Bean Scripting Framework (BSF) • Browser-base administration with easy-to-use wizards for creating HTTP and application server instances, deploying J2EE applications, and management of HTTP and application servers and their applications. • Integration with IBM WebSphere Studio, built on Eclipse, the open systems development environment • Integration with HTTP server for iSeries and Domino for iSeries HTTP servers • Integration with OS/400 security for authentication of users • HTTP session • Migration to more advanced WebSphere Standard Edition (SE) and Apache Software Foundation (ASP) Jakarta Tomcat • Migration to more advanced WebSphere Application Serving configurations. WebSphere Application Server - Express for iSeries offers: • Integrated development tools and runtime – a slimmer version of WAS V5 and WebSphere Development Studio Client for iSeries • Simplified Administration through the inclusion of the basic functions of creating and configuring server instances, configuring data sources and ports, starting and stopping the server, publishing an application to the server, and stopping and restarting the application. Where possible, default settings are established iSeries Communications and e-business—An Introduction 281 so configuration is not required, and maintenance efforts are minimized. • Quick start samples – help speed application development • Tag library and JavaScript support –Jakarta Tag libraries are included with the development tool. JavaScript support is added on both the development and application server side. Existing programming skills can be leveraged. Telephone Directory V5.1 for iSeries Telephone Directory V5.1 for iSeries is integrated with WAS-Express for iSeries. It is a business application that provides a company with a directory for managing information about people. Personnel information is managed securely by the AO/400’s Lightweight Directory Access Protocol (LDAP) server. The telephone directory can be searched and managed using a Web browser, powered by JSPs and servlets running in the application server. The directory can be used as an HTTP server or application server security repository for Web user authentication. The directory provides the following functions: • Ability to search by job description • Ability to see organizational structure (report to chart) • Ability to store personalized information (picture) Web Services Object Runtime Framework (WORF) Web services are XML-based applications functions that can be invoked over the Internet. Web Services Object Runtime Framework provides an environment to easily create simple XML- based Web services that access DB2. Using Apache Simple Object Access Protocol (SOAP) 2.2, or later, and the Document Access Definition Extension (DADX) standards, it is possible, with minimal knowledge of SQL or XML, to specify a Web service. DB2 UDB Extenders can be used to implement Web services within WORF. The DB2 XML Extender (part of 5722-DE1) consists of a set of 282 Exploring IBM ~ iSeries stored procedures, user-defined types (UDT), and user-defined functions (UDF) that can be used to store and retrieve XML data using DB2. The DB2 XML Extender allows XML documents to be stored intact, and optionally indexed in either side tables, using the XML column access method, or as a collection of relational tables using the XML collection access method. Net.Data Net.Data is a compatible follow-on version of DB2 WWW Connection that builds on that tool’s database access and reporting capabilities and provides a comprehensive Web development environment for the creation of simple dynamic to complex Web-based applications (i.e., it builds Web pages). Net.Data is a CGI program that creates a dialog with the user of a Web browser. The macro processor provides searches to the DB2-based database via SQL queries without the use of programming languages. Responses are provided to the Web browser in HyperText Markup Language (HTML). Net.Data is contained in HTTP Server for iSeries. TCP/IP Connectivity and Utilities for iSeries is required to use Net.Data. Net.Data includes Web registry and flat-file support as built-in functions. These functions increase the ease of creating Web pages. Web registry functions allow macro variables to be stored and retrieved, giving these variables persistence across macro boundaries. (The term macro as used here identifies a set of short programs that perform specific functions.) A macro variable and its value can be saved into a Web registry by one macro and later retrieved for use in another macro. Flatfile functions allow the storage and retrieval of user data into files containing single field records. This single field record can contain multiple pieces of data separated by user-defined delimiters, enabling the performance of such tasks as saving a Net.Data table built in one macro and retrieving the table with a second macro used to create a report. Net.Data supports the LOB and DATALINK data types of DB2 UDB for iSeries. SQL stored procedures can be called, and multiple result sets returned by those procedures can be handled. It is possible to make direct program calls to iSeries ILE programs that use input and output parameters. Java support allows access to Java applications or generation of Java applets from Net.Data. Macros are parsed only once and the results are saved for subsequent requests for that macro. Trace logging support makes it easier to find errors in new programming macros. iSeries Communications and e-business—An Introduction 283 Net.Data includes built-in functions to send e-mail, generate browser cookies, and manipulate Net.Data tables. WebSphere Commerce Suite WebSphere Commerce Suite for iSeries enables the building of an electronic storefront on the Web. The storefront can range from a static Web site to a high-volume megasite providing secure links to thousands of consumers. Commerce Suite comes with sample storefronts that can be customized to provide product catalogs and search engines. Commerce Suite allows a user to browse a store’s categories and products. All data presented to the user is dynamically generated from the Commerce Suite specific back-end database. Commerce Suite also seamlessly manages the shopper’s basket as well as letting him or her register as a preferred shopper. When the shopper decides to check out, Commerce Suite will present the proper screens to determine quantities, shipping information, and payment method. Features include virtual shopping carts and credit card validation. Third-party software allows real-time credit card, and HTTP Server for iSeries and Digital Certificate Manager provide SSL level security. There is a capability to check on order status, and frequent-buyer discount programs can be established for multiple groups. Commerce Suite uses Net.Data to generate dynamic Internet pages using its own DB2 UDB for iSeries database tables. Management components are Site Manager and Store Manager. Security functions include Crypto Access Provider (5769ACx) and SSL. Commerce Suite currently uses SSL for encryption. WebSphere Commerce Suite includes Commerce Suite Server (which manages the customer interface, enabling the customer to browse, save, query, and order items in the interactive catalog) and Commerce Suite Administrator (which enables the store and site personnel to create online catalog layouts, product templates, and an interactive product catalog). Commerce Suite Administrator includes designers for site managers, store managers, and templates. Euro currency support is included. Commerce Suite includes Enterprise Commerce Connection for integration with back-end ERP systems. Figure 5.6 provides an overview of the components of WebSphere Commerce Suite, including the elements of those components. In general, the WebSphere Commerce Suite has been converted from C++ code to Java Code, employing Java Servlet Pages and Enterprise Java Beans to increase its portability. 284 Exploring IBM ~ iSeries Tools Programmers Web Operations Authoring WB Workbench Tool Center + Administration + WebSphere + VAJ (Persistors, Studio + Wizards Icontrollers, Commands + System Mgmt Databases) Catalog Subsystem Member Subsystem User Registry Authentication Profile Management Access Control Session Management Navigation Merchandizing +Packages/Bundles +Associations Interests/Items/lists Search Common Server Runtime Programming Model Object Model Persistence/Schema Process/Runtime Model Cache Commerce Accelerator Catalog Management + Catalog Tools + Pricing + Data Import/Export + Rules Transformation + Promotion Negotiation Subsystem Order Subsystem Order Processing Order Management Pricing Fulfillment/ Inventory Mgmt Payment Taxation System Mgmt Scheduler Tivoli Enablement DBClean, Staging System Monitoring Error Logging/Tracing User Traffic Logging Auction Messaging Up and Running Messaging/ Notification Framework Backend Integration Install Configuration Store Models Samples Transition WebSphere Application Server JSP Servlet Engine Platform Figure 5.6. EJB Container JDK WebServers Directory Servers + IBM HTTP Server + SecureWay LDAP + Domino, iPlanet + Domino, iPlanet DataBase Servers + DB2 UDB v7 + Oracle 8i Windows NY/2000, AIX, Solaris, Linux, OS/400, MVS WebSphere Commerce Suite for iSeries components. WebSphere Commerce for iSeries taps into the Internet market to increase your business and improve your productivity by developing a business-to-customer or business-to-business Web site with WebSphere Commerce Professional Edition (WCPE) or WebSphere Commerce Business Edition (WCBE). WCPE and WCBE can reduce the cost of sales transactions, can attract and retain customers with relationship marketing, can create and manage marketing campaigns and promotions with WebSphere Commerce Accelerator, and can track shoppers’ past purchasing activities for improved customer service. WCPE includes order management, catalog editing, commerce accelerator, commerce analyzer, live help collaboration, payment processing, auctions, and a iSeries Communications and e-business—An Introduction 285 new business-to-business store model. WCBE can be used to provide sell-side managed contracts, sell-side request for quotation (RFQ), approvals workflow, requisition lists, online buyer/seller collaboration, and advanced user management and access controls. Domino 5.0.5 for iSeries Domino 5.0.5 for iSeries combines the iSeries system’s features of strength of integration, ease of use, and scalability with Lotus’s leading groupware offering Domino. Domino for iSeries is a full-function Domino server incorporating the Domino architecture. The iSeries system implementation of Domino includes full integration with the OS/400 operating system. Domino software runs as an application on the iSeries system using PowerPC technology, provides the Notes client and Notes applications with direct access to the DB2 UDB for iSeries database, and can coexist with the Integrated xSeries Server, running the Domino software. Figure 5.7 illustrates the Domino development environment and the close relationship of that environment with Java for developing Domino applications. The key features of Domino for iSeries include: Integrated Java development tools A Java editor and class browser is included with Domino for creating Java applications for Domino without need for a 3rd-party development tool Agents (LotusScript, @, Java) CGI (RPG, Cobol, C) Java Server Pages Java Servlets (Java) Domino HTTP APIs Domino HTTP Server Domino Sockets, SSL Figure 5.7. Java with Domino. Exploring IBM ~ iSeries The latest release (a full-fledged Lotus Domino server) is Lotus Domino 5.0.5. • The iSeries is enabled to be a server in a Notes network. Multiple (partitioned) Domino servers can run on a single iSeries. Remote dial-in and dial-out are enabled. All SMTP mail systems are enabled. • Universal mail exchange among multiple e-mail offerings include Lotus Notes, OfficeVision, JustMail, POP3, and Internet e-mail. • Data is integrated between Domino and DB2 UDB for iSeries in both directions. • Simple-to-use mobile computing through the use of Notes replication is provided. • E-commerce solutions are built through the support of WebSphere databases and other Web content databases. • Domino for iSeries coexists with Lotus Domino servers on the iSeries Integrated xSeries Server and supports replication with all other Lotus Domino servers. • The maximum file size for a Domino file has been increased to 64 GB. • Domino servlets support can be enabled. • Domino for iSeries delivers a highly reliable and available Domino server through iSeries availability features, such as RAID-5 and mirrored protection; integrates backup with standard iSeries backup; and runs as an OS/400 application, which isolates the server from other applications and provides server recovery without restarting the entire system. • Domino supports 128-byte passwords, utilizing Web Setup for Domino and QuickPlace. Otherwise, Domino password rules remain unchanged. QuickPlace is a Lotus product that enables Web-based team collaboration. AM FL Y • TE 286 Team-Fly® iSeries Communications and e-business—An Introduction 287 • Domino uses the EZ-Setup Wizard, which is launched from the iSeries Navigator taskpad to install Domino for iSeries, including the Domino plug-in for Navigator. • Domino has been cluster proven. This was provided by the enablement of Domino exit programs, which are driven by the Cluster Management API, and by the addition of a new STANDBY status for Domino Servers. There is a hardware dependency on shared DASD and the presence of V5R1 level of OS/400. • TCP/IP Autostart is included. • LDAP V3 support and a lightweight directory are offered. • Domino Enterprise Connection Services, formerly known as Lotus Enterprise Integrator (LEI) (formerly NotesPump), is extended with connectors to the Enterprise Resource Planning (ERP) applications. Domino Enterprise Connection Services and Domino Connectors can be used to access business-to-business data and applications on the iSeries servers. These services work with the Enterprise Server Preload packages described in Chapter 1. • Lotus Domino.Doc 2.0 support is offered. • OfficeVision/400 has been migrated to Domino for iSeries, allowing migration of users, groups, mail, calendars, and folders to Domino from OV/400. Lotus Calendar Connector for OfficeVision enables free-time search and allows for sending meeting notices between Domino and OfficeVision/400. • Integrated File System stream files up to 256 GB in size are supported in the root, QOpenSys, and user-defined file systems. OS/400 supports 64-bit integers and 64-bit APIs to work with the file system. The iSeries Kernel Threads model is leveraged by Domino software to save time by avoiding job initiation and to allow the software to scale to thousands of mail users on the iSeries system. Lotus Notes clients, both with and without an ODBC driver, can access the DB2 UDB for iSeries program database to import DB2 data 288 Exploring IBM ~ iSeries directly into Notes databases. Notes C and C++ interfaces are provided, enabling iSeries versions of standalone applications, server add-ins, database hook drivers, extension manager hook libraries, and external database drivers. Two-way directory synchronization between the iSeries System Distribution Directory and the Domino Name and Address Book is provided in real time, and any change in either location is automatically reflected in the other location to minimize administration activity related to both locations. The AnyMail framework incorporates the Lotus Simple Mail Transport Protocol/Mail Transfer Agent (SMTP/MTA), enabling the Domino for iSeries to interact with other mail systems on the iSeries system. Domino for iSeries has been benchmarked at over 70,000 mail users. The high availability and reliability of the iSeries result from the combination of the overall reliability of the iSeries system and the incorporation of data mirroring and RAID-5 capabilities. The capability to support multiple instances via partition server support for up to ninetynine partitioned Domino servers provides additional scalability. This partitioning of the Domino servers on a single system enables the workload to be split up for various applications. In addition to the Domino program’s real-time Web-serving capability with its HTTP server, the support and synchronization of the DB2 UDB for iSeries databases enable the establishment of e-commerce storefronts. Domino for iSeries supports Lotus Domino.Doc, a robust object filing system that provides a secure (easy to use and administer) document-management solution. Lotus Domino.Doc also supports a distributed environment and leverages the iSeries reliability and scalability while taking advantage of Domino’s replication, security, and object-storage capabilities. Lotus Domino.Doc features include document checkin/check-out, use of common terms (file rooms, file cabinets, binder, documents, etc.), and access from Web browsers, Notes Client, or ODMA-compliant applications. Lotus Learning Space provides collaborative learning and management tools, enabling media-rich online training and education. Lotus Learning Space can be accessed from the Web or Notes clients to enable cost-effective training where the students can access the product anytime from anywhere. Lotus Learning Space can be used to include the benefits of traditional classroom teaching—team-oriented and instructor-facilitated. Features of Lotus Learning Space include scheduling assignments, testing and grading tools, private or team discussions, and iSeries Communications and e-business—An Introduction 289 student-based home pages. Lotus Script is receiving extensions to support SAP R/3 and MQSeries interfaces. Domino-Licensed Program Server Choices Customers have four server choices available through the Domino Server for iSeries Licensed Program. The Domino Mail Server license provides a messaging license to support Notes clients, browsers, or third-party POP3 or IMAP clients. The Application Server license extends the server to support ISV or custom-written Domino applications—Notes- or Webbased. The Domino Mail and Application Servers support one to four CPU servers and a single partition of Domino. The Domino Enterprise Server provides support for servers from one to eight CPUs and extends the functionality of the Domino server to support Domino partitioning, which allows multiple Domino servers (sharing one copy of the Domino software installed on the iSeries) to be implemented on the same physical iSeries. Domino Enterprise Server also enables Domino-clustering capability for providing high availability to Domino messaging, applications, and Web-serving environments. The Domino Advanced Enterprise Server is offered to support servers that have more than eight CPUs. Domino-Licensed Program Client Choices Customers are offered four client choices for use with their Domino servers through the Domino Server for iSeries Licensed Program. All of the client choices provide a Client Access License (CAL), which provides the ability to authenticate to a Domino server and utilize Domino Mail and Applications. Based on customer requirements, the clients provide additional levels of functionality. iNotes The iNotes client provides authenticated Web browser access to Domino for e-business applications and messaging. Administrators are allowed to manage what the users see and how they interact with data. A Domino mailbox can be used via Web browser, POP, IMAP, HTTP, or MAPI clients. HTTP, SMTP, or LDAP can be used to access Domino applications and services. Soon the iNotes client will be able to deliver off-line browser access to Domino messaging as well as support for Microsoft Outlook 98/2000 access to Domino messaging. 290 Exploring IBM ~ iSeries iNotes Access for Microsoft Outlook allows Outlook users to access mail, calendars, and schedules using Domino Server. This enables exchange customers looking toward server consolidation and improved functionality, reliability, and scalability to upgrade the server without changing clients. Notes Notes is a client desktop application. Notes offers an integrated, Weblike desktop environment from which users get quicker access to and better management of many types of information including Domino and Internet-based e-mail, appointments, contacts, and to-do’s as well as Web pages, news groups, and intranet applications. All of this information is brought together in a single, easy-to-use and easy-to-customize environment providing collaboration and information management. Domino Designer Domino Designer R5 is an integrated development environment for Domino including a set of visual tools for Web pages and site design, relational database access, client and server-side scripting, and access to an extensive set of predefined Web objects. A fast way to develop, maintain, and deploy Web applications that streamline business processes integrated with enterprise data and applications and to facilitate collaborative relationships is provided. iNotes with Domino Per Server CAL The iNotes with Domino Per Server CAL provides a license for authenticated Web access to applications on a Domino server for users who are not employees or contractors of the enterprise. It is the license required for using a Domino server in an extranet or Internet environment where you do not wish to purchase a Domino CAL for each external user who needs to log on with an ID and password. OS/400 Directory Server The OS/400 Directory Server is based on LDAP V3 with some extensions. The OS/400 Directory Server utilizes DB2 UDB for iSeries to store LDAP information by means of a new Application Control Language iSeries Communications and e-business—An Introduction 291 (ACL) design to protect LDAP entries; it uses iSeries Navigator’s graphical user interface for presentation of the LDAP information. The directory server also includes LDAP Data Interchange Format (LDIF) interchange utilities to exchange data between the DB2 UDB for iSeries back-end and other servers. Lightweight Directory Access Protocol (LDAP) Directory Services is the Internet standard protocol for looking up information such as e-mail addresses, phone numbers, and certificate information. Distributed directories that provide distributed name space and interoperability for operating systems and applications have been available for years (some of these are X.500; Novell’s Netware Directory Service, or NDS; and DCE’s Cell Directory Services, or CDS), and each promised to be the network provider of a directory. However, none was completely accepted by the industry. LDAP functionality has been increased to be the equivalent of IBM eDirectory 2.1. The security and integrity of data stored in the LDAP server is better protected by disabling database capabilities for non-operating system programs attempting to access the underlying database files. Directory Services provides a projection of user profiles into the LDAP directory, allowing the creation, retrieval, change, and deletion of OS/400 user profiles through standard LDAP interfaces. This makes LDAP server and client APIs current with SecureWay Directory V3.2.2. In addition to the LDAP server, iSeries Directory Services includes an iSeries-based LDAP client and a Windows 95/Windows NT LDAP client. The iSeries-based LDAP client includes a set of APIs that can be used in OS/400 C programs. The Windows 95/Windows NT LDAP client also includes a set of APIs. Other services that exploit LDAP include NetFinity, Management Central, IBM HTTP Server, WebSphere Application Server, Telnet Server, DDM and DRDA, iSeries Access Services, and eNetwork On-Demand Server. In addition, with SSL support, these services are able to establish secure communications sessions with their corresponding clients. Data exchanged between the clients and servers is encrypted and is not subject to eavesdropping. LDAP implements IBM SecureWay Directory V3.1.1. LDAP-enabled applications, such as Internet mail clients, can access, update, and manage the iSeries directory. OS/400 applications can be developed to use LDAP for managing distributed information across the Internet and intranets using LDAP directories for both IBM and non-IBM platforms. LDAP applications like mail clients can access iSeries user information, such as e-mail addresses. System directory entries in the iSeries can be converted to the entries of LDAP. 292 Exploring IBM ~ iSeries 6 iSeries and Your Business A n important first step in bringing iSeries systems (or any computer systems) into your business environment is planning. Largely depending on how well you plan, introducing new computer resources can be like pouring either water or gasoline on a fire. Many readers will already have a significant number of computers in their business and will add iSeries systems to their computer arsenal, whereas others will be bringing iSeries systems in as their first business computer. In either case, the information in this chapter should help you understand how to introduce iSeries systems into your particular environment. The chapter starts by discussing what you should consider when determining your business needs. Then it covers software selection, followed by some specific iSeries system hardware configurations appropriate for small, medium, and large businesses. In addition, the following topics are discussed: 292 • Business decisions • Implementation management • Physical planning • Training iSeries and Your Business • Ergonomics • Security • Technical support • Service • Migrating from iSeries CISC to iSeries RISC. 293 This chapter is not a complete guide to introducing iSeries systems into any business, but it does provide a starting point for developing your plan and discusses some important issues. What Are My Business Computing Needs? Many businesses today use some type of computer system(s) to help run their business. These businesses must constantly evaluate whether their current system is good enough. Businesses that are still using manual methods for specific functions within the business must determine whether automating their business might help. Whether your business already has millions of dollars’ worth of computer systems or none at all, the way to begin answering these questions is to forget about computer hardware and software, and look very closely at your business. Too often, businesses buy computer systems and then look for problems to solve. A properly managed computer project should start by careful consideration of the collective business needs of all functional areas within the business. Independently attacking specific business problems often can result in a “dead-end” computer solution that provides no coherent strategy for the future. From the very start, key people from all affected business areas should be collected into a project team. Since multiple business areas will be involved, the top management of the business must consistently demonstrate a commitment to the project. Without top management involvement, disagreements among the peer business areas are slow to be resolved and the sense of priority is diminished. Lack of consistent top management commitment at either the investigation or implementation 294 Exploring IBM ~ iSeries phase of a computer project is a common cause of unsuccessful projects, which can prove to be quite expensive. The project team should start by reviewing the overall goals of the business (or segment of a larger business) over the next few years. In some cases, these goals will be well known, but in others a great deal of soul-searching will be necessary. These goals should be as specific as possible and should include any business strategies already in place to achieve these goals. After the business goals are clearly defined, the project team should look closely at the current day-to-day operations of the business as it is and document the movement of information through the entire organization. Only after the information flow is understood can the team candidly discuss what is good and what is bad about the current way of doing business. Work to identify the sources of problems rather than focusing on symptoms. Understand the interaction among the various areas of the business. Consider the flow of information from one group to another as you trace the business cycle. Chances are, not every problem that you will uncover can be solved through a computer. For example, a computerized inventory-tracking system will not solve inventory problems if just anyone can casually walk into the inventory storeroom and walk out with what he or she needs with no controls. Computers are only a tool for effectively managing a business; they will not manage your business for you. Only after you have examined your current operation with a critical eye can you begin to see if a computer solution makes sense for your business. In the case of small businesses, this type of analysis can be done in a matter of weeks or even days. In larger businesses, it can span months or even years and typically is done on an ongoing basis. Some businesses choose to do the analysis on their own. If you want assistance with solving business problems with computers, however, there are plenty of places to turn, including consultants and computer manufacturers. Choosing the Software iSeries system computers become a useful business tool only when they are executing the appropriate software. Although there are many ways of generating a strategy for introducing computers, considering software needs before selecting detailed hardware configurations usually iSeries and Your Business 295 makes sense. The hardware requirements, such as performance levels, memory size, and disk storage space, will be based in part on the needs of the software selected. The application programs you select must perform the tasks needed by your end users both today and in the foreseeable future. Selecting the basic type of application program often is fairly simple: An accounting department needs accounting applications, an e-business initiative needs e-business applications, and so on. What is more difficult is identifying the specific application program that best fits your particular needs. Is a custom application program preferred, or will a prewritten application program be acceptable? If a prewritten application program is desired, exactly which one is the best for your needs? If a custom application program is desired, who should write it and what should it include? The answers to these questions depend largely on the specifics of a given business environment and thus are beyond the scope of this book. However, a few basics remain the same whether you are selecting a program for a multinational corporation or one for a corner fish market. First, you must precisely understand the tasks you are trying to put on a computer before pursuing any application program alternatives. A thorough knowledge of these tasks helps you to identify specific requirements your application program must meet. After a detailed understanding of the tasks is obtained, a search can begin through the many prewritten or off-the-shelf application programs. If you can find an appropriate prewritten application program that fits your needs, you can avoid the expense, delay, and ongoing effort associated with custom software development and maintenance. Good prewritten application programs can be quite flexible. However, because everyone typically has slightly different needs and methods even within a given business function, you can bet that any prewritten application will have some features you do not need and will not have other features you will wish it did. Do not forget to consider the more specialized type of prewritten application program—vertical market applications. Vertical market application programs address a highly specific segment of users such as lawyers, doctors, distributors, or manufacturers. There are several sources of information about the many prewritten application programs on the market. Of course, computer companies and consultants can help you select particular application programs to fit your needs. There are also many popular computer and industry trade magazines that pe- 296 Exploring IBM ~ iSeries TE AM FL Y riodically conduct extensive reviews of prewritten application programs. These can be excellent and timely sources of information. For specific or highly specialized needs, prewritten application programs may not be adequate. In this case, custom-developed software may be desirable. Although the development and maintenance of custom software is a long-term commitment that typically is expensive, it may be less costly in the long run to pay for the development of custom software than to settle for a prewritten application program that does not do the job. If you do select the custom-software route, an important step is to select the proper developer. Businesses that have their own programming staff can do their own custom program development. If you do not have your own programmers, it will be necessary to seek outside help—that is, an outside software developer. In either case, the developer will have the largest effect on the ultimate success or failure of the custom-development activity. The developer’s job is not an easy one. In addition to having programming expertise, the developer must become an expert in all aspects of your business, must be a good communicator to understand and discuss software requirements, must understand human psychology when defining the user interface for the program, must be a proficient teacher to train the end users on the new program, and, finally, must be dependable and reliable and therefore available to provide technical support, software maintenance, and any needed modifications. Choosing the Hardware Selecting the proper iSeries system hardware components that together will fit your needs can be confusing. You must select among the iSeries models and their disk configurations, feature cards, peripherals, and so on. Although we cannot possibly cover all needs for all environments in the limited scope of this book, we can examine some business environments—for example, a small manufacturing establishment, a medium business, and a large business—and outfit them with the appropriate iSeries system configurations. With the insight provided by outfitting these hypothetical business environments, you will be better prepared to properly select the iSeries systems components useful in your environment. Assistance in selecting specific iSeries system configurations is available from IBM or remarketers. Team-Fly® iSeries and Your Business 297 Small Business Environment, Manufacturing—Bob’s Gearbox Co. The hypothetical small business is a gearbox manufacturer named Bob’s Gearbox Co. Bob’s has a standard line of gearboxes and also accepts orders for custom gearboxes. It is a private corporation (owned by Bob, of course) with thirty-two employees. Bob has been in business five years and has experienced moderate growth. He currently conducts business by noncomputer methods but finds himself needing to streamline his operation as the business grows. Bob is particularly concerned that his profits seem to be shrinking as his sales increase. A study of Bob’s business shows that there are two basic causes for this. First, his sales staff often commits to discounted pricing on a gearbox order to capture the business. The trouble is that Bob never really knows what it actually costs him to produce a given gearbox. He uses standard cost estimates to price a customer’s order and hopes that the actual cost of building the gearbox is close to this. The second basic problem uncovered in the study is that Bob’s inventory is not well managed. The production department is often hampered by not having the right parts and raw materials in inventory. This often causes slips in the delivery of customer orders that hurt customer satisfaction and fuel heated arguments among the marketing manager, the production manager, and the materials manager. Finger pointing is commonplace. The study also showed that 25 percent of the inventory items in stock are obsolete and will never be used. In this scenario, it is clear that Bob has outgrown his manual methods of doing business. Bob needs a better way to track the actual costs associated with manufacturing his products. This may uncover the fact that his sales staff often sell gearboxes at or below cost. Bob also needs help tracking his inventory. He needs to know when critical parts are getting low and what parts are moving slowly. The deficiencies in Bob’s business can be addressed with the proper computer solution. Let us examine the iSeries system configuration suitable for Bob’s Gearbox. Bob will use the Manufacturing Accounting Production Information Control System (MAPICS/DB) to help gain better control over his business. By selecting the appropriate modules (programs) within the MAPICS/DB family of software, Bob can track manufacturing costs more closely (Production Control and Costing, and Product Data Management modules) and better manage his inventory (Inventory Control module). Bob also chooses to take advantage of the computer system to automate the general accounting functions of his business such as pay- 298 Exploring IBM ~ iSeries roll, accounts receivable, accounts payable, and general ledger, and he will use the Order Entry and Invoicing module to track and bill customer orders. The Cross-Application Support module is required on all systems. Through a questionnaire, this module allows Bob to customize MAPICS/DB for his particular business environment. Furthermore, the Cross-Application Support module automatically passes information among the various MAPICS/DB modules, making them function as a single system. Based on the requirements of the software and Bob’s business transaction volumes, Bob will get the iSeries Server i810 #2466 processor shown in Figure 6.1. The Model 810 system was selected for its low cost and its ability to first be upgraded to higher-performance processors and the enterprise program package option be replaced by a larger iSeries system. The standard 17,500 MB of disk storage will be expanded to 52,500 MB to provide enough storage for the system software, the iSeries Printer 3488 3488 3488 3488 3488 Terminals Base System iSeries e-server Model 810 w/2466 processor 512-MB main storage 17.5-GB disk unit * Tape unit * Combined Function I/O processor * Base twinaxial support * DVD-ROM Options (2) 17.5 GB disk units Universal power supply 4761 modem *Denotes standard equipment Figure 6.1. Bob’s iSeries advanced system. Peripherals (5) 3488 terminals (1) 4234 printer Software OS/400 V5R2 MAPICS/DB Query/400 RPG/400 Internet Connection Secure Server for iSeries Domino Communications Utilities iSeries Access for Windows iSeries and Your Business 299 MAPICS/DB modules, and associated data and allow a minimum RAID data protection capability. The Model 810 system’s ability to expand to 13,791,000 MB of disk storage will allow for expansion as Bob’s business grows. Bob feels the base 512 MB of main storage is sufficient to get started, but he likes the option to grow to 16,000 MB. The optional uninterruptible power supply unit will help prevent disruption of the system by power failures—Bob can do without the extra headache. The #9771 PCI two-line WAN with modem will be used to access IBM’s Electronic Customer Support (ECS) network. The system console function is performed by a 3489 Modular Display Unit. For the users, four 3488 Displays are provided initially. One display is for the inventory clerk, one is for the purchasing agent, one is for the production department, and one is for Bob so that he can get the management information he needs to make intelligent decisions. The 4234 Printer will be used to produce the various reports provided by MAPICS/DB. The 14 GB 7208 Cartridge Tape Unit will allow data stored on disk to be backed up on tape. This will help prevent important business information from accidentally getting lost. Since OS/400 V4R5 is now bundled with the Model 250 hardware, Bob has no need to concern himself with the iSeries operating system. Bob will also get the Query/400 and Domino programs so that he and his staff can generate customized reports and manage schedules as needed. Bob expects to participate in electronic commerce through the Internet, so he insists on having a #4761 modem attached. He also figures this will provide him closer contact with his sales force (whom he plans to provide with notebook computers) through e-mail while they are interacting with customers for his gearboxes. Because no one on his staff has programming skills, Bob anticipates consulting with IBM about setting up his Internet site and storefront. Medium Business Environment—Johnson & Thornbush The hypothetical medium-sized business is an advertising agency named Johnson & Thornbush. This company has been in business for twelve years. Their business started with one major account, and today they have seventeen active clients. Steve Johnson and Perry Thornbush are both still active in managing the business. The main office, located in Chicago, has seventy-four employees. A second office, with seven em- 300 Exploring IBM ~ iSeries ployees, is located in Fort Lauderdale, Florida, to handle several large accounts in the Southeast. Almost every person at each location has a PC providing personal productivity tools for such tasks as market analysis, trend analysis, word processing, and financial modeling. Steve Johnson recently sponsored a company-wide study to find a way to address the business goals of increasing marketing effectiveness and reducing operating costs. The results of the study revealed that the market analysis being done by one PC user seldom correlated with the market analysis done by another PC user. The cause of the disagreement in information was that there were different versions of the area demographic information residing on the various PC disk units used in the market analysis. Even though one person had responsibility for periodically updating the demographic information and distributing the updates, eventually different versions of the information emerged, making the market analysis inaccurate. Further, as the company’s market coverage grows, the demographic information is growing in size and is becoming impractical to distribute via diskettes. It is apparent that moresophisticated data management and analysis techniques will become necessary as the firm continues to grow. Another area the study uncovered as needing improvement was that basic office operations could be streamlined, increasing productivity and thereby reducing operating expense. Mail delays between the two offices were slowing down many day-to-day business operations. Because of busy schedules, it often was difficult to schedule meetings, as the last attendee contacted often would have a conflict. Although the secretarial staff also had PCs and WordPerfect for word processing, turnaround time for even a simple memo was getting longer as the workload increased. The project team recommended a computer solution that streamlined office functions and centralized the area demographic information. All PCs were to be connected in such a way that they could share information and facilitate business communications. Figure 6.2 shows the system configuration suitable for Johnson & Thornbush. In this solution, the PC users retain their PCs, protecting that investment in hardware, programs, and training, only now all PCs (in both Chicago and Fort Lauderdale) are attached to an iSeries located in Chicago, allowing them to double as PCs and iSeries workstations. As PCs, they can do everything they could before. As workstations on the iSeries, the PCs allow users to interact with the iSeries, providing some additional capabilities provided by iSeries programs. iSeries and Your Business 3486 Display (for System Operator) Leased Communication Line 5 4 9 Model 825 4 3-way + Expansion Tower 6262 Printer 301 4230 Printer PC PC PC Token-Ring Network PC Ft. Lauderdale location (these PCs must have the System 36/38 Workstation Emulation Adapter) PC PC PC Base System iSeries Model i825 *2,048 MB main storage *17.5 GB disk unit *13-GB tape unit *Twinaxial workstation IOA *MFIOP *EIA 232/V.24 cable *CD-ROM *Universal power supply Options (6) 17.5 GB disk unit EIA 232/V.24 50-foot cable #9771 PCI WAN IOA (2) 4761 modems Peripherals Existing PCs w/adapter 3488 display stations 6262 Model T14 printer 5494 remote control unit 4230 printer Software OS/400 V5R2-Enterprise Edition Domino Language dictionaries Communications utilities Query/400 ILE RPG/400 Access Family for Windows Application Development Tools Query and SQL Development Kit *Denotes standard equipment Figure 6.2. iSeries system for Johnson & Thornbush. 302 Exploring IBM ~ iSeries Hardware Configuration Based on the number of users and the growth the business is experiencing, an iSeries Model i825 and a processor option #2473 3-way with CUoD growth to 6-way as needed. For now, 2,0048 MB of main storage should meet the need. Six additional integrated 17.54 GB disk units will expand the standard 17.5 GB to over 122.5 GB of disk storage— more than enough for now. The 25 GB 3-inch cartridge tape unit provides for efficient backup of the information stored in the iSeries disk storage. The 100/16/4 MBps Token-Ring Network Adapter/HP will allow the iSeries to participate in a 100 MBps token-ring network. A 100/16/4 MBps Token-Ring Network Adapter must also be installed in each of the local PCs, allowing them to participate in the network. The 6262 Printer will provide high-speed printing to all local users. In Fort Lauderdale, a 5494 Remote Workstation Controller is attached to a communications line to Chicago, where the PCs are equipped with the Workstation Adapter and attached to the 5494 so they can be used as iSeries workstations. The smaller 4230 Printer, along with the PC printers they already have, will meet printing needs for the Fort Lauderdale users. Although the PCs will be attached to the 5494 via twinaxial cable for now, a token-ring network could be installed later at the Fort Lauderdale location. The PCs can then be attached to the 5494 via the token-ring network to provide for more efficiency and flexibility as the Fort Lauderdale location grows. Johnson & Thornbush Software Scenario The Domino for iSeries application program provides the basic office functions needed to streamline operations. The electronic mail feature of Domino allows any user to electronically send documents or quick notes to any other user. This eliminates mail delays and reduces the word-processing workload, because simple notes and messages can be typed and sent by the users themselves. The calendar-management function of the Domino application can automatically schedule a desired meeting by electronically checking the calendars of all attendees and finding a time suitable for all. OS/400 V5R2 Enterprise Edition will run in the primary partition with Domino for iSeries running in a secondary partition. The customer plans to WebFace their 5250 OLTP applications. The programs for the iSeries and Your Business 303 Fort Lauderdale site will also run as a second OS/400 V5R2 secondary partition with another secondary partition running the required Domino for iSeries for the mail and calendaring services for Fort Lauderdale. Although Domino has a word-processing function, those with primarily word-processing activities to perform will continue to use the WordPerfect word-processing program on the PCs. Since both offices have a heavy word-processing workload, using the intelligence in the PCs for this function will provide the highest productivity (lowest response time). This is particularly true in Fort Lauderdale, because iSeries response time will be reduced by the relatively slow telephone line communications speeds. Furthermore, removing the word-processing tasks from the iSeries provides improved response time for the electronic mail, calendaring, and demographic activities performed on the iSeries system. The iSeries Access Family for Windows program allows iSeries disk storage to act as the central repository (file server) for the demographic information. In effect, a portion of the iSeries disk storage appears to be a giant PC disk unit shared by all PCs. With iSeries Access Family for Windows, all PC users can simultaneously share this single copy of the information, ensuring that all are using the same current data for their marketing analysis. This will result in a more accurate market analysis and thus more effective marketing efforts for the firm’s clients. With the iSeries WebSphere Development Studio, Johnson & Thornbush will develop custom application software over time that will allow the iSeries to act as a database repository and interact with the PCs in a cooperative processing environment. Through the token-ring network, all of the PCs located in Chicago are attached to the iSeries. The token-ring network was selected for its high-speed information transfer rate and because it could use the twisted-pair wiring already installed throughout much of their building. All of the PCs in Fort Lauderdale will be attached to the iSeries system as remote workstations through a 5494 Remote Workstation Controller, appropriate modems, and a leased voice-grade telephone line. This allows every PC, no matter where it is located, to double as an intelligent iSeries workstation. Whether PC users are in Chicago or Fort Lauderdale, they will have access to the same functions. However, because the Fort Lauderdale PC users are attached via a telephone line, their response time will not be as good (fast) as that of those in Chicago, who are attached over the highspeed token-ring network. 304 Exploring IBM ~ iSeries To improve the exchange of ideas and responsiveness of the peopleto-people interactions, Domino 5.0 was installed on the iSeries Model i825, and Lotus Notes was installed on the PCs both in Chicago and in Fort Lauderdale. Large Business Environment—Atole Enterprises The hypothetical large business that will be outfitted with iSeries systems is Atole Enterprises. This multinational corporation is a distributor of canned foods and enjoys financial prowess worthy of its Fortune 500 membership. The many benefits afforded by computers are well known at Atole Enterprises. They have been using computers in their day-to-day operations for many years. The U.S. headquarters is in New York City and currently has a large System/390 computer complex. There are seventeen distribution centers located from coast to coast. Each distribution center has its own small System/36 and Atole-written application programs to track orders and local inventory, and to transmit information to the System/390 in New York. System/36s were originally selected for their ease of operation, which minimizes the need for technical skills at each distribution center. A company-wide study sponsored by headquarters came to the following conclusions: Most of the System/36s are fully depreciated and in many cases are not providing enough computing power to meet growing demands. The custom-written application programs written for the System/36s have been around a long time and need major updates to keep the company’s competitive edge in customer service. The study therefore recommended that Atole convert the distribution centers from System/36s to entry-level iSeries Server i800s using the Processor #2463 with improved application programs. Also, the System/390 located in New York will be right-sized to an iSeries server 870 with Processor Feature #2486 8-way Enterprise Edition, which will save significant operating cost over the next five years. In addition, future applications will be developed on the 870 and verified before being shipped to the distribution centers, thus avoiding the need to install a separate Model i800 at the main office. Atole Solution Scenario The first step in implementing the solution is to install Model i800 systems at the distribution centers. The distribution center staff will use iSeries and Your Business 305 the migration tools to quickly move the current distribution center application programs from the System/36 to the iSeries system. After the initial migration is complete, the headquarters staff on the Model i870 will exploit the programmer productivity features in the iSeries system to enhance the distribution centers’ application programs. It is critical to get the improved application programs ready as soon as possible. Once this is done, each distribution center will download the updated application programs. The headquarters staff will assist each distribution center in performing systems management on the new systems. Figure 6.3 shows the iSeries distribution center configuration that Atole will use. The iSeries Server Model i800 with Processor Option #2463 was selected because its performance and capacity best matched the need and because of its continuing upgrade path. The standard Model i800 configuration will be expanded to 105,000 MB of disk storage and 1,024 MB of main storage to provide enough capacity to meet the needs of the distribution centers for an estimated five years. In the event of a power failure, the UPS power unit will provide power to sustain critical components while they ride through short power outages and will allow the system to perform an orderly shutdown in case of longer outages. This will reduce the disruption associated with power failures at the distribution centers. The #9771 two-line PCI WAN with modem will be used for IBM Electronic Customer Support (ECS). This will derive from the base #9771 PCI WAN/Twinaxial IOA which will support up to twenty-eight twinaxial-attached workstations in addition to the ECS communications line. In this case, however, Atole chooses to provide the ECS for each distribution center from the headquarters location; that is, headquarters will maintain a help desk and a technical question-and-answer database pertaining to their custom software in addition to the IBM question-and-answer database. They will be the first line of support for the distribution centers. A second communications line is provided by the #2772 PCI Two-Line WAN IOA. This leased line will be used to communicate with the Model i870 at headquarters to consolidate information needed from each distribution center much as before. This will allow for communications at 56,000 bps. The NetView program running on the iSeries Model i870 will work with the #4761 Modems to manage the communications network. Further, the SystemView System Manager for OS/400 program will be loaded on the central site’s iSeries to allow the retrained S/390 personnel to perform change and problem management for the remote iSeries systems. Atole will use #3487 Display Stations as color terminals to allow Exploring IBM ~ iSeries 3847 3847 3847 3847 3847 AM FL Y 4234 Printer 3847 iSeries Model i800 Base System iSeries Model i800, w/2463 processor 512 MB memory 35,000 MB disk unit 25-GB tape unit *Twinaxial workstation controller *Combined I/O processor *DVD-ROM *Universal Power Supply TE 306 3847 Peripherals (7) 3487 Display Stations (1) 4234 Printer Software OS/400 V5R2 Standard Edition Domino V5 Communications Utilities Query/400 ILERPG/400 Options 512-MB main storage 70,000-MB disk unit #2721 PCI WAN IOA 4671 Modem *Denotes standard equipment Figure 6.3. iSeries distribution center configuration that will be used by Atole. their custom application programs to exploit color to associate and highlight information on the screen. This will result in improved ease of use. Each distribution center will have a #4234 Printer to produce reports and correspondence-quality documents. The standard streaming tape drive provided with every Model 870 will be used to back up disk storage. Backup will be performed to the Model 870 at the central headquarters site only. Team-Fly® iSeries and Your Business 307 The iSeries software needed, in addition to OS/400, includes IBM’s Communications Utilities, Query, and ILE RPG/400. IBM’s Communications Utilities provides some additional communications functions between the iSeries systems. Query/400 will allow local distribution center management to develop their own custom reports, giving them more flexibility. Finally, Domino for iSeries will facilitate communications between headquarters staff and each distribution center. Dedicated Server for Domino Web Serving Environments The following example describes how the iSeries Dedicated Server for Domino (DSD) can provide value to users. In this example, a manufacturing company with an Enterprise Resource Planning application running on the iSeries is described. The customer begins with a simple requirement to deliver e-mail to its users, but also knows that the possibility exists to leverage adding some Domino applications in the future, after discussing its problems with its counterparts at other companies with some Domino experience. The customer begins with the purchase of a small DSD system to implement e-mail, and they extend the LAN infrastructure to the Internet and install a firewall for protection. The e-mail project is a raging success, so they decide to embark on another small project to deliver a project-management tool for new product development. They install a second partition on the existing DSD, pilot the application there, and roll it out to the product-management team in a third partition. While the project-management application is deployed, two members of the in-house Domino implementation team attend education about Domino R5 and Web development at a Lotus Authorized Education Center. The two return full of ideas, and they implement another Domino partition where they use Domino Designer clients to create a small internal Web site for their colleagues to look up the company softball team schedule, view organization charts, and post ideas for IT improvements to be reviewed by their team. They show it to the IT manager, who quickly expands the idea by requesting the company policy documents and product information online. The members comply and a company intranet site is born and put into production with a bit of tweaking and an upgrade to a larger DSD to serve the expanded user base. The upgrade is installed with minimal disruption over some pizza on Saturday night, and on Monday all the users benefit from the in- 308 Exploring IBM ~ iSeries creased processing power as it is dynamically applied to the various Domino environments: Domino mail during peak access in the morning, then the Domino intranet and applications throughout the remainder of the day. After the success of the Domino intranet, the IT staff decide the Domino collaborative capabilities can be extended even further to improve its competitive capabilities and provide higher levels of customer service. First, Lotus Quickplace is implemented to address some of the new business requirements to work on joint bids and at large opportunities with suppliers, contractors, and other business partners through ad hoc, user-managed Internet workrooms. Quickplace is installed on a separate iSeries Dedicated Server for Domino placed on an external LAN for security purposes and protected by a packet-filtering router. Users in engineering, marketing, and sales work together securely with project teams from other companies and compile information to complete price requests and to create proposals for new business faster and with less e-mail and more organization and quality than ever before. A business partner is engaged to work with the IT staff to develop a new customer service site that lets customers access order and status information from the ERP system. The business partner uses Domino Enterprise Connection Services nightly to pull order summary information into Domino from the database files on the iSeries that runs the majority of its line of business applications. Other DB2 information is accessed from the Domino applications in real time through Domino Enterprise Connection Services. The business partner creates the Domino site, which is tested on the Domino development partition and is then replicated and put into production on the second DSD on the external LAN. Domino Workflow is then utilized to enhance the company’s processes by automating the approval cycles of purchasing, expenses, and pricing exceptions. The growth in the preceding example illustrates how Domino starts small and expands to become integral to a company’s operations. In the past, multiple PC servers would have been used to implement the various Domino application environments, mail, applications, internal Web serving, development, Domino Workflow, and Lotus Quickplace. The iSeries uses logical partitioning to serve these applications on fewer systems, sharing computing resources and minimizing the cost of managing and maintaining many physical servers, while leveraging the integration to the back-end database files through common iSeries remote database technology (DRDA). iSeries and Your Business 309 Server Selection The medium-sized business environment of Johnson & Thornbush could equally well have used an iSeries Server 870. Performance within the locally connected personal computers would have been improved with no degradation at the remote site. In fact, performance would appear to improve if the process of maintaining the database concurrent between the two server systems were managed properly. Figure 6.4 illustrates the preferred configuration for Johnson & Thornbush in a server-based implementation. Note that the #5494 Remote Workstation Controller has been replaced with a LAN-configured iSeries Entry Model 800. This transformation is possible because the servers are specifically set up to manage LAN-connected personal computers. The only non-LAN-connected terminals on either of the systems are the system console and the printers. If the 9771 Base PCI WAN/Twinaxial IOA feature had been chosen using an additional communications line, both the console and printers could have been LAN-connected. It is worthwhile for a business that has almost all of its terminals as personal computers to consider the server configurations because specially priced packages to meet those configurations are available. Figure 6.5 3486 Display System Console iSeries 870 iSeries 800 6262 Printer 3486 Display System Console PC PC 4230 Printer PC PC PC PC 16-MBps Token Ring PC PC PC PC PC PC PC PC Modem Modem PC PC PC PC PC PC . Total PCs = . . 74 on this ring PC 16-MBps Token Ring PC PC PC Figure 6.4. PC PC PC Johnson & Thornbush configuration as a set of servers. 310 Exploring IBM ~ iSeries illustrates the Johnson & Thornbush system configuration as it would appear if implemented as a network configuration. In a network computing configuration, the leased line connecting the two modems in Figure 6.5 would be replaced by an Internet cloud, which would give each group of users (those on the Model 825 and those on the Model 800) access not only to each other’s groupings, but to all the information on the Internet. Of course, it would cost more to provide security—including a firewall, an encryption card to send encrypted corporate information, and the HTTP Server for iSeries software on each system, as a one-time expenditure which would displace the leased-line ongoing expense, eventually resulting in a savings. The Competitive View of 64-Bit Processing One other aspect needs to be considered before deciding which computer system does the best job in the long term for your business. That 3486 Display System Console iSeries-i825 iSeries-i800 4230 Printer 6262 Printer 3486 Display System Console PC PC PC PC PC PC 16 MBps Token Ring PC PC PC PC PC Internet PC PC PC Modem Modem PC PC PC PC PC PC . Total PCs = . 74 on this ring . PC 16 MBps Token Ring PC PC PC PC PC PC Figure 6.5. Johnson & Thornbush system configuration in a network computing environment. iSeries and Your Business 311 consideration is the turmoil associated with getting your applications to execute as the industry migrates from 16-bit and 32-bit processing to 64-bit processing. As described in PowerPC AS Microprocessors in Chapter 1, the iSeries is based on a 64-bit RISC processor. So are DEC’s Alpha and HP’s Precision architecture-based systems and Microsoft’s NT architecture. In the case of DEC and HP, the processor is 64-bit, but the applications that exist are 16-bit and 32-bit; and because they are processor-centric (written with a direct relation to the processor that they were intended to execute on), they must be rewritten to perform in a 64-bit manner on the 64-bit processors. This is not to say that those applications will not run on the 64-bit processors from those vendors, but that they will run as 16-bit or 32-bit applications, dissipating the value of the 64-bit processors they are using. The NT architecture defined by Microsoft has the same problem except that rather than being processor-centric, it is API-centric (each application program is written with a direct relationship to the interface—16-bit or 32-bit—provided by the processor it is expected to be executed on) and the 16-bit and 32-bit applications must be rewritten to match to the interfaces of a 64-bit world before they can leverage the hardware when it becomes available from Intel, Motorola, Sun, or whoever provides it. The IBM iSeries, because of the Technology-Independent Machine Interface (TIMI), can take applications written for 16-bit or 32-bit environments and translate them (i.e., the applications execute as 64-bit applications) to a 64-bit environment. This translation is intrinsic in the iSeries system and has happened with each release of new processing hardware, which did not affect the applications that executed from previous releases. Figure 6.6 illustrates the impact of the architectural decision on the applications for these companies as it relates to the movement to 64-bit processing. The Business Decisions In addition to selecting the hardware and software to solve identified business problems, you must also consider financial questions before you install your computer solution. Two important areas that must be addressed are cost justification and the lease-or-buy decision. 312 Exploring IBM ~ iSeries iSeries Advanced Application Architecture Alpha Architecture Precision Architecture NT Architecture Applications Applications Applications Applications Exploits Impacts Impacts Impacts TechnologyIndependent Machine Interface APIs Accommodates Hardware Hardware Hardware Hardware IBM iSeries DEC HP Microsoft Application Centric Figure 6.6. Processor Centric API Centric Positioning 64-bit processing, a competitive view. Cost Justification All businesses are the same in one respect: They exist to make a profit. In the final analysis, the only reason for a business to buy a computer is to increase profits. In other words, the computer system must be cost justified. There are two parts to the cost-justification analysis: costs and benefits. The price you pay to the computer company is easily identified early in the project. What many people fail to consider are the costs of owning a computer system beyond the original price paid. The costs of operating the computer installation after you buy it should also be considered over several years. Some costs that should be considered beyond the price tag are identified next. Hardware Maintenance This is usually a monthly or annual fee you pay that basically is an extended warranty for the computer hardware. There are various alter- iSeries and Your Business 313 natives, but the basic deal is that if your computer system breaks down, the service company will come out and effect repairs at no charge. You do not have to put your system on a maintenance contract, but if you do not you will have to pay an hourly fee and costs of parts when your system breaks down. Since this parts/labor billing approach can be extremely expensive, most businesses choose to put their system on a maintenance contract. Software Maintenance In some cases you will have to pay the software supplier a fee to get fixes and updates to your programs. Users who purchased applications that used two-digit year designations in date codes in the past have already faced up to the expensive software maintenance job centered around year 2000, unless they used or updated to OS/400 Version 3 Release 2 or Version 3 Release 7 or later. Technical Support Technical support provides answers to your questions and resolves any technical problems in either the hardware or software. This kind of support ranges from providing a telephone number to having permanently assigned personnel from the computer company on your premises. Sometimes this support is provided free of charge; other times it is on a fee basis. Whether a business is large, medium, or small, if more than one computer is functioning within that business, there is a system-management concern, with a very real cost associated. It is difficult to associate a dollar value because each system configuration is different, but estimates of the cost do exist. Whether you hire someone directly to deal with the concern, do it yourself, or get technical support from an external company, you must pay that cost. Cost estimates indicate that for three to forty computers or terminals the cost is one full-time person, and this increases with the addition of one full-time person for each additional forty computers or terminals. Facilities It is often necessary for you to modify your building to accommodate a computer system. These modifications might include adding additional 314 Exploring IBM ~ iSeries air conditioning, running cables between workstations and the computer, or modifying the electrical power services available. Fortunately, the costs of such building modifications are relatively low with iSeries systems as compared with large computers, which often require water cooling and raised floors. The new packaging reduces these costs for new installations, because only the largest systems require two-phase service to operate. Education/Training The people who will be using the new computer system will need education. The computer operators will need to understand how to manage the day-to-day operations of the computer. The users of the computer system will have to understand the application programs. It may also be necessary to train your own programmer(s) to write custom application programs for your business. Fortunately, iSeries systems are easier to operate and use than larger computer systems. However, some education is still necessary. Many different types of education are available, some of which are discussed later in this chapter. Communications Line Costs If your computer system is attached to remote workstations or other remote computers, you will incur communications line costs. There are many different communications services available today, and these costs should be considered in your justification. Environmental Costs Environmental costs are the costs to operate the system over a period of time. It has been calculated that the difference in operational costs for an existing System/36 Model D24 and an Advanced 36 over a period of five years is $20,220. This difference results from the reduced heat load on air conditioning systems, reduced cost in electrical requirements, and reduced cost of a maintenance agreement. That cost reduction will pretty much pay for the new system, and you will reap the benefit of improved performance that increases the efficiency of your workers. Enhancing Applications Any time you either downsize or modify your computer installation to modernize it, it is expected that you will have to pay the cost of updat- iSeries and Your Business 315 ing your applications or purchasing new applications to operate within that new environment. This was dealt with in greater detail in the discussion of WebSphere Development Studio for iSeries in Chapter 4, but the one thing you can trust is that your host-centric applications will not operate in a distributed client/server-centric environment. Benefits On the brighter side, the computer is being purchased to solve identified business problems or address new business opportunities. You will receive benefits after the computer system is installed. (Or else why install it?) Although it is fairly easy to identify and quantify the costs associated with a computer system, it is often difficult to do the same for the benefits. This does not mean that benefits are any less real than costs; it simply means that they require more work to uncover. Benefits are also more specific to your business, so it would be impossible to list all of them here, but we can consider some common benefits associated with the application of computer systems to basic business functions. Improved Business Cycle The basic cycle of most businesses has the same components: The business buys goods/equipment, takes customer orders for goods or services, makes deliveries, and bills the customer. The classic application of computer systems to these areas produces improvements in the basic business cycle that result in real dollar savings. These savings can result from such basic things as collecting accounts receivable more quickly and taking better advantage of accounts payable discount terms. Inventory Reduction Many carrying costs are associated with a business inventory. These include items such as warehouse space, insurance, tax, and interest expense. The proper application of computers can reduce the level of inventory that must be kept on hand, thus reducing carrying costs. Improved Productivity Given the proper tools, anyone in any part of a business can do his or her job more efficiently. This allows a business to get the same amount Exploring IBM ~ iSeries of work done more quickly or with fewer people. Excess time can then be redirected to performing other tasks that help meet the business objectives. Further, as natural attrition reduces the workforce, it may not be necessary to hire replacements, allowing for a reduction of the workforce over time. Improved Quality AM FL Y By providing more timely or better-organized information to personnel, businesses can often improve the quality of the services or products they provide. This is particularly true in manufacturing environments, in which computers can be applied to everything from design simulations to statistical quality control. It has also been found that providing the needed information in a more timely fashion (reduced wait time) results in fewer errors being made by the users, thus increasing productivity. Improved Customer Service TE 316 By allowing a business to respond to customer orders, questions, and special requests, computer systems can improve customer service. These improvements can involve quickly responding to requests for price quotations and accurately quoting and meeting delivery dates. Competitive Advantage The items that have been discussed contribute to reducing costs, improving quality, and improving customer service, so they all work to improve the competitive posture of the business. The flexibility provided by a computer system can also help improve your competitiveness by allowing you to respond more quickly to changing market demands. The business also has the opportunity to use advanced software technology products such as multimedia, telephony, and so on, to increase revenues. This list of general benefits is in no way comprehensive. Every business can add to the list based on its current position and business objectives. Once benefits have been identified, however, you are still not finished. You should try to quantify the benefits in dollars and cents where possible, to help focus on the areas with the largest payoff first. Quantified benefits also help when comparing computer investments Team-Fly® iSeries and Your Business 317 with any other capital projects under consideration. However, quantifying benefits can be difficult and subject to judgment. Unlike the price of a computer, which can be looked up in a catalog, benefits must be calculated according to expected results. For example, if you feel that inventory can be reduced by 10 percent by installing an inventory-management application program, you would multiply 10 percent of your inventory value times the carrying costs to determine the annual benefit. This is not very difficult, but other areas are more difficult to quantify accurately. As another example, if an engineer’s productivity is increased by 15 percent, then you might multiply the annual salary and benefit costs by 15 percent, yielding the annual savings. In this case, some would argue that because the engineer is still paid full salary, nothing is saved. However, if the time is devoted to, say, developing a product to enter a new market, the actual benefit may be much higher than 15 percent of the engineer’s salary. You will have to decide what a benefit is worth to your business. Other benefits that typically are difficult to quantify and thus are often overlooked when tallying savings include increased sales (resulting from improved customer service) and lower employee turnover (resulting from improved working conditions and pride). The fact that these benefits (and others like them) are difficult to quantify does not make them any less valuable, but it does mean that they often are overlooked. After the costs and benefits have been quantified, you can begin to evaluate the proposed computer project against other capital projects. Two guidelines often used to measure a proposed computer system are: 1. The payback period, in which the time to recover the investment from accrued benefits is calculated 2. The net present value, in which the cash flows are calculated and then discounted based on the cost of money and risk associated with the project. Although this type of analysis can be valuable, do not overlook other aspects of the capital project such as its strategic value and its effect on customer-perceived quality and professionalism. Classic accounting techniques are easy to defend but do not always reveal the entire picture. 318 Exploring IBM ~ iSeries Lease or Buy? Just when you think you are through analyzing all the software and hardware alternatives, you are faced with a whole new set of questions concerning the acquisition method you will use. Several methods are commonly used to acquire a computer system. The most obvious alternative is simply to pay cash for the computer system—outright purchase. This is the least expensive way to acquire a computer system. However, it has a direct and usually substantial impact on the business’s cash flow and capital position. The next acquisition alternative is to finance the purchase price over a period of time, just as you would finance a new house or new car. In this case, you simply make a down payment, typically 10 percent, and take out a loan for the balance. The loan and interest are repaid through monthly payments (over a period of from two to five years typically). Since you must pay back the interest on the loan, this is a more expensive alternative than a cash purchase, but it can reduce cash flow requirements. In either case, the title of the computer system passes to the business, as do any tax benefits such as depreciation. The purchaser of a computer also has the ability to sell the computer when it is replaced or is no longer required, thus recovering the residual value of the computer system. Another acquisition alternative is the term lease. In this alternative, the lessor (computer owner) grants use of a computer system to the lessee (the using company), which in turn agrees to make lease payments for some specified period of time, or term. The term of a lease can be any length, but typically runs from two to five years. If the lessee decides to terminate the lease before the end of the term, there is usually a termination fee, which can be substantial. Some of the advantages offered by the term lease alternative include the conservation of business capital and lines of credit, which can then be used to finance other investments. Two commonly found lease types are a capital lease and an operating lease. Capital leases are rent-to-own; at the end of the term, you can purchase the computer system for a relatively small fee (e.g., 5 or 10 percent of the original cost). With a capital lease, the lessee is considered the owner and gets the tax benefits of ownership. Capital leases are much like a financed purchase, the major difference being that a capital lease does not require the user to make a down payment, as does a financed purchase. Operating leases are real leases in which there is no discounted purchase option at the end of the lease term. The lessor is iSeries and Your Business 319 considered to be the owner and thus retains the tax benefits of ownership. Because of this, the lessee typically makes a lower payment than with the capital lease alternative. A final acquisition alternative is to rent the computer system month by month. This provides the most flexibility, because this kind of arrangement typically requires only one to three months’ notice to discontinue. Of course, you usually must pay higher rental payments to get this flexibility; and because the payment is usually not fixed, you are subject to increases. The acquisition of computer software is a whole different story. Typically, you will not have the option to buy software. Most companies license software. A software license grants the licensee the right to use the software under the conditions specified in the document supplied by the software company, called the license agreement. Typically, these licenses allow the licensee to use the software on a specified computer system for a specified fee. Three common ways to pay for this license agreement are one-time charge, lease, or monthly charge. With the one-time charge, the licensee pays a set price and retains the right to use the software indefinitely. The price can be paid in cash or be financed. The leasing alternative is really just another way to finance the one-time charge with no down payment. Finally, the monthly charge is like renting the software month to month indefinitely. Although some basic lease/purchase alternatives have been introduced in this section, the rules governing these various alternatives are complex and subject to change. The effects on a company’s cash flow, income statements, balance sheets, taxes, and so on, can also be strongly affected by the various acquisition methods. You should consult the proper professionals to determine the best alternative for your situation. Education The discussions in the chapter so far should assist you in selecting the appropriate software and hardware to fit your needs. However, no matter what computer hardware and software you select, they will require people to interact with them. To maximize efficiency, these people (users) must be educated in the use of the computer system itself as well as its software. Proper education is critical to the success of any computerautomation project. Inadequate education prevents reaping the productivity benefits of moving a task to the computer. 320 Exploring IBM ~ iSeries The first goal of education is to make users (and system operators) proficient at using the computer hardware and software they need to do their jobs. Another important goal of education is to make the users’ interaction with the computer system enjoyable. If using the computer is enjoyable, users will be more motivated. However, if using the computer is a frustrating struggle (because the users have inadequate education), they will be less productive or perhaps will avoid the computer altogether. Education that is specific for iSeries is available from IBM Education and Training (IBM’s training subsidiary), as well as from other non-IBM companies. The IBM Education and Training educational offerings come in the following forms: • Classroom courses are traditional lectures/discussions led by an IBM instructor. These forums provide for direct interaction between students and instructors. Hands-on, in-class exercises often are part of a classroom course. Public courses are held regularly at IBM facilities. Alternately, private courses can be arranged and held either at IBM locations or at customer locations. • Personalized learning series courses are basically duplicates of classroom courses, except in self-study format. Students are provided with transcriptions of the classroom course lectures in electronic form. Transcribed lectures are loaded on an iSeries system using a CD-ROM and are read on the user’s display screen. Also provided is a booklet containing the foils (illustrations) normally presented in the classroom lectures. An additional offering in the self-study format is a set of diskettes containing the selfstudy courses for the iSeries that may be loaded onto a personal computer and be studied from there. • Discover/education series courses cover additional iSeries-related topics in a format identical to the online education provided as standard with iSeries systems. • Learning centers are educational facilities where students come in and use the materials just discussed (for a fee) without having to buy them. These educational offerings are also available for sale. iSeries and Your Business • 321 There is also a set of self-study courses shipped with every iSeries system. Those courses are listed in Figure 6.7. Security In many business environments, computer systems are the very backbone of business operations. This makes the information stored on the computers a corporate asset at least as valuable as cash. Because of the new methods of accessing the data on your business computer (Internet, intranet), it is necessary to rethink the security aspects of your system. One of the items that distinguishes the iSeries family from most other computer system families is the flexibility of its security features. System security has three important objectives: • • • Confidentiality: – Protecting against disclosing information to unauthorized people – Restricting access to confidential information – Protecting against curious system users and outsiders Integrity: – Protecting against unauthorized changes to data – Restricting manipulation of data to authorized programs – Providing assurance that data is trustworthy Availability: – Preventing accidental changes to or destruction of data – Protecting against attempts by outsiders to abuse or destroy system resources. 322 Exploring IBM ~ iSeries Course ID Type of Course PS586 PS587 Self-study Self-study PS588 Self-study PS589 Self-study PS590 PS682 Self-study Self-study PS684 Self-study PS685 Self-study DE204 DE205 DE206 DE208 DE209 PS153 PS154 PS155 PS156 PS163 PS164 Self-study Self-study Self-study Self-study Software Software Software Software Software Software Self-study PS274 Self-study Course Description AS/400 Getting to Know Your System AS/400 Administrator-Work Management and Basic Tuning AS/400 Administrator-Security Planning and Implementation AS/400 Administrator-Availability and Recovery Management AS/400 Administrator Library Lotus Notes R4 System Administration I: Extending A Notes Lotus Notes System Admin II: Cross Certificates and Multiple Lotus Notes R4 System Admin II: Server Activity and Performance AS/400 Basic Education Series AS/400 Implementation Series Office Vision/400 Support Series AS/400 Implementation for Entry Systems AS/400 Overview and Introductory Topics AS/400 Implementation and Operation Series COBOL/400 and SQL/400 Programming Series RPG/400 and SQL/400 Programming Series AS/400 Library AS/400 System Using the S/36 Environment AS/400 System for the Experienced S/38 Implementer SQL/400 Programming Workshop Additional information on each of these courses can be obtained by accessing the Internet at <http://www.training.ibm.com/ibmedu/news/400f96.htm. Figure 6.7. Listing of self-study courses available for the iSeries on CD-ROM. System security is often associated with external threats, such as hackers or business rivals. The intent of these paragraphs is not to minimize the external exposure, but to present a more balanced approach to system security. More damage can be caused by the accidental depression of the wrong key at the wrong time. A well-designed security system will provide protection against system accidents by authorized system users. iSeries and Your Business 323 As with an application, good results from the system security functions cannot be obtained without good planning. Setting up security in small pieces without planning can be confusing and difficult to maintain and to audit. Planning does not imply designing the security for every file, program, and device in advance. Planning does, however, imply establishing an overall approach to security on the system and communicating that approach to application designers, programmers, and system users. The following questions need to be considered when planning the security on your system and deciding how much security is needed: • Is there a company policy or standard that requires a certain level of security? • Do the company auditors require some level of security? • How important is your system and the data on it to your business? • How important is the error protection provided by the security features? • What are your company security requirements for the future? Like a business’s cash, computer information must be protected from loss or theft. Let us look at how this vital information can be protected. Loss Prevention An ever-present hazard when dealing with information (with or without computers) is the possibility that the information will be lost. This loss can occur in many different ways. A computer system’s breakdown, such as a disk unit failure, can result in lost information; operator error can cause data to be corrupted accidentally, resulting in lost information; or a disaster (such as a fire or flood) can result in a loss of vital business information. For this reason, recovery from the loss of vital business information must be addressed. One way to deal with the risk of losing vital information is to make backup copies of computer information at regular intervals (e.g., daily). Multiple backup copies should be made on a revolving basis and be kept in a place safe from damage or loss. Three copies will allow at least 324 Exploring IBM ~ iSeries one copy to be kept in safe storage at all times and will provide for different levels of backup. In the event of an information loss, the computer system can be restored to the point at which the most recent backup copy was made. The iSeries systems’ operating systems and the various tape devices discussed in Chapter 2 are designed for these kinds of save/restore operations. Any changes to information after the point of the last backup will have to be re-created after the backup copy is used to restore the system. This may involve manually reentering the transactions since the last backup or exploiting OS/400 features such as journaling and checksum, discussed earlier in this book. Any good disaster-recovery plan will also consider how the business will operate in the event the current computer system is destroyed. Many companies, including IBM, offer disaster-recovery services that essentially provide you with emergency access to a similarly configured computer system located elsewhere. Usually, a test allowance is part of the deal so that you can run disaster-recovery drills to ensure readiness. The iSeries Backup and Recovery Guide (SC41-8079), available from IBM, is a good reference when planning your backup strategy. Theft Prevention Theft prevention deals with protecting sensitive information from unauthorized disclosure. These security requirements vary widely from environment to environment. Consider your particular needs early in your planning. The iSeries systems provide various levels of security that help deter unauthorized access. All iSeries eServers are now designed to meet the C2 level of security. Security level 50 enables iSeries servers to operate at the C2 level of trust as defined by the U.S. government. The iSeries is the first system to achieve a C2 security rating for a system (hardware and operating system) with an integrated full-function database. The requirements for the C2 level of security are defined by the U.S. Department of Defense in the its publication DOD 5200.28 STD, Trusted Computing Systems Evaluation Criteria (TCSEC). Additional detail related to the C2 operating environment can be found in the IBM publication iSeries Security—Enabling for C2. Security for iSeries is integrated into the computer system hardware along with the associated operating system. Depending on the needs of the user environment, one of five levels of security can be activated. The first level is basically no security at all. People can access the system and iSeries and Your Business 325 can do anything they wish. The second level of security requires the user to enter a password before access is granted to the system. After the proper password is entered, the user can perform any task. The third level of security is user-access control, which is just like the second level except that the user can be restricted to various functions as well. A security officer is usually assigned to manage the security of the system. The fourth level of security adds operating system integrity by restricting the use of certain operating system functions and unsupported interfaces. The fifth level enhances the integrity protection provided at the fourth level and is designed to meet the requirements of C2-level security. For sensitive environments, you may wish to consider restricting access to the area in which the Application System itself is located. It may also be necessary to restrict access to the area(s) in which workstations are located. These needs should be considered early in a computer-automation project. For additional discussion of security subjects and iSeries security capabilities, obtain Tips and Tools for Securing Your iSeries (SC41-3300-00) from your local IBM branch or IBM representative. Additional security issues relating specifically to Internet/intranet security and operating system security are discussed in Chapters 4 and 5. The complete picture of the security capabilities of the iSeries systems should include all the discussed offerings and the additional capability of the hardware keylock function included with every system. Service Although every effort has been made to make iSeries systems as reliable as possible, some computers will fail. If yours does, you must have a way of getting it fixed. All iSeries systems come with a one-year warranty that provides free on-site repairs from IBM’s service division seven days a week, twenty-four hours a day. Each of the various terminals and printers associated with iSeries systems has its own warranty terms and periods ranging from three months to three years. After the warranty period, you become responsible for maintenance of the system. IBM and other companies offer service agreements that, for a fee, provide postwarranty on-site service just like that provided during the warranty. Various maintenance discounts are available, depending on the level of system management procedures you are willing to imple- 326 Exploring IBM ~ iSeries ment in your business. If your system fails and you do not have any type of service contract, you will have to pay for parts and labor, which can become extremely expensive. For this reason, most people choose to keep their systems on maintenance after warranty. Migrating from System/3X and AS/400 to iSeries TE AM FL Y Some businesses may be replacing System/3X and AS/400 computers with an iSeries. The iSeries has been designed to ease the migration of most programs and data from these earlier computer systems. OS/400 functions plus available tools provide a guided and highly automated procedure for these types of migrations. Although programming skills are still required to guide the migration activities, the tools reduce the manual work of analyzing, documenting, saving, and restoring application programs. Programs are migrated to the iSeries System/38 environment discussed in Chapter 4. If desired, the programs can be further adapted to take advantage of new iSeries functions at your own pace after the migration is complete. Now let us look at sizing a replacement iSeries when migrating from System/3X to iSeries. Software Maintenance Software maintenance combines software subscription and technical support to provide iSeries customers with a full range of benefits including software upgrade entitlement and where available voice and electronic support. Software maintenance will be delivered by two priced Program IDs (one covering support and the other subscription). The PIDs will have a duration of either one year of three years. There will also be a PID representing “after license” if subscription coverage lapses.When buying a new hardware model, a minimum of one year of software maintenance must be purchased. Software maintenance is not transferable outside of the customer enterprise or country. All existing Software Subscription, Support Line and Service Suite contracts will be honored through their termination date. The latest offering will be available to the customers at that time. Team-Fly® iSeries and Your Business 327 Sizing a Replacement iSeries Whether iSeries is your first computer system or you will be replacing a System/38 or AS/400 system, you will have to choose the appropriatesize iSeries. Size refers to the processor speed and capacity, which by model depends on memory size and amount of disk storage. There are many things to consider when choosing the size iSeries needed in a given situation. Those migrating from the System/38 to the iSeries will need more disk-storage and main-storage capacity than they did with the System/38. More disk-storage space is necessary mostly because of the increased requirements of OS/400. More main storage is needed because more information about each task remains resident in memory. More information in main storage has been a traditional advantage of the System/38 because it makes for better system performance. The iSeries takes further advantage of the same concept. Whether you are migrating from a System/38 or AS/400, you must select the correct iSeries processor model. The Performance Overview section of Chapter 1 will give you a rough idea of the relative performance of the various computer systems of interest. To refine your model selection, you must start by examining your current computer system very closely. Tools like the iSeries Performance Tools can be used to determine the workload on your current system. The capacity-planner portion of the PATROL for iSeries—Predict can help analyze your current system to determine which iSeries model is appropriate. An IBM document that will help in using these sizing tools and determining iSeries disk-storage requirements is the iSeries Performance and Capacity Planning Newsletter (GC21-8175). If you are adding additional functions (programs and data) or more users to the new iSeries system, you must also consider the effect of these new requirements on performance, memory, and disk-storage requirements. IBM personnel have tools and resources available to them to help you size the appropriate iSeries system. 328 Exploring IBM ~ iSeries Index #3995 Optical Library, 104–105 #4754 Security Interface Unit (SIU), 114 64-bit addressing, 39, 310–311, 312 7133 Serial Storage Subsystem, 97, 98–99 A Access. See iSeries Access access path recovery, 195–196 access to data benefit of IFS, 139 actuators of disk unit, 57, 97 Address Resolution Protocol (ARP), 167 ADTS (Application Development ToolSet), 219–222 advanced application architecture, 9–12 Advanced Function Printing. See AFP Advanced iSeries Model i800, 16, 18 Advanced Peer-to-Peer Communication (APPC), 60, 61 Advanced Peer-to-Peer Network (APPN), 172, 250 Advanced Print Utility (APU), 131 Advanced Program-to-Program Communication (APPC), 257 advisor function, iSeries Performance Tools, 208 AES crypto algorithm, IBM SecureWay, 265 AFP (Advanced Function Printing), 222–226. See also OS/400 (Operating System/400) Advanced Print Utility (APU), 131 Create AFP DATA (CRTAFPDTA) command, 224 defined, 222 document services, 223 electronic pages, 222 e-Output, 84–85, 224, 225 error recovery, 223 Euro currency symbol support, 221–222 Host Print Transform (HPT), 220 IBM Infoprint Designer for iSeries, 225–226 IBM Infoprint Server for iSeries, 186, 223–225 image files, 220 inbound browser access, 222 Infoprint Image Editor, 225 328 Infoprint Layout Editor, 225 Infoprint Overlay Editor, 225 Intelligent Printer Data Stream (IPDS), 85, 86, 220, 222–223 network printing, 223, 224 outbound distribution, 222 Overlay Utility, 221 page-mode printing, 85 Page Printer Formatting Aid (PPFA), 131 PCL data stream, 85, 222 PDF data stream, 85, 222, 224 postscript files, 220 printer services, 223 Print Format Utility, 221 Print Services Facility/400 (PSF/400), 220–222 Resource Management Utility, 221 SAP R/3 AFP Print, 132 transforms, 85, 222, 224, 225 Transmission Protocol/Internet Protocol (TCP/IP) and, 223 Type Transformer for Windows, 221 Web images, 224–225 AFP Font Collection, 220–221 AFP PrintSuite, 130–132 AFP Toolbox, 131–132, 220 AFP Workbench, 173, 182, 186 air intake, 8 AIX, xviii, 13, 129–130 altered program objects, 238–239 AnyMail, Domino 5.0.5, 288 Apache Portable Runtime (APR), 268 Apache Software Foundation (ASF), 186, 187, 268–273, 270 API (Application Program Interface) HTTP Server for iSeries, 268 Operating System/400 (OS/400), 137 operating systems concepts, 135–136 OptiConnect, 61 API-centric architecture, 311 APPC (Advanced Peer-to-Peer Communication), 60, 61 APPC (Advanced Program-to-Program Communication), 257 applets, Java, 231, 232 Application Development ToolSet (ADTS), 219–222 Index application environments, kernel threads, 226–238 application frameworks environment, 227 Application Program Interface. See API Application Server, Domino 5.0.5, 289 Application Service Providers (ASPs), 261 applications programs, 123–134. See also cross-industry application programs; kernel threads; OS/400 (Operating System/400); software architecture; WDS (WebSphere Development Studio) compatibility, 121–123, 137 custom application programs, 133–134, 296 enhancement costs, 314–315 industry-specific applications programs, 124, 132–134 migration, 7 modular programs, 132–133 prewritten application programs, 123–124, 295–296 resiliency for system availability, 65, 68 selection, 294–296 software layer, 115, 116, 117, 120, 121–123 vertical market application programs, 295–296 applications support layer, IBM Networking Blueprint, 254–255, 255–259 Application Storage Pools. See ASPs APPN (Advanced Peer-to-Peer Network), 172, 250 APR (Apache Portable Runtime), 268 APU (Advanced Print Utility), 131 archiving data, 192 ARP (Address Resolution Protocol), 167 AS/400 family of computers. See IBM AS/400 ASCII formats, printers, 85 AS/Entry system, xxiii ASF (Apache Software Foundation), 186, 187, 268–273, 270 ASPs (Application Service Providers), 261 ASPs (Application Storage Pools). See also IASPs (Independent Application Storage Pools) backup/recovery, 194, 196 integrated file system (IFS), 140 Async communications protocol, 111, 163 Asynchronous Transfer Mode (ATM), 109, 110 Atole Enterprises (large business environment), 149–152, 304–307 329 authentication of DCE, 160–161 authorized users accidents, 322–323 Automatic Browser Detection, HTTP Server for iSeries, 267 autonomic computing element of e-business, xviii, 3 auxiliary storage, 54–59. See also storage hierarchy actuators of disk unit, 57, 97 average latency of disk unit, 56, 57 average seek time of disk unit, 56, 57 backup importance, 57, 58 Compact Disk-Read Only Memory (CD-ROM), 58, 104, 106 data transfer rate of disk unit, 56, 57 Direct Access Storage Devices (DASDs), 55–57, 97, 192 diskette storage, 55 disk storage, 55–57, 97–100, 98 DVD-RAM, 58, 104 DVD-ROM, 58, 104 millions of bytes per second (MBps), 56 nonvolatile storage, 54, 55, 97 optical libraries, 58, 104–106 performance and, 56, 57, 97 platters of disk unit, 55–56, 96 read/write head, 56, 97, 101 tape storage, 58–59, 101–103 Write Many, Read Many (WMRM), 58, 104 Write Once, Read Many (WORM), 58, 104 auxiliary storage controllers, 103–104 auxiliary storage options, 96–106 #3995 Optical Library, 104–105 auxiliary storage controllers, 103–104 CD-ROM, 106 Combined-Function I/O Processor (CFIOP), 97, 106 disk adapters (Input/Output Processors, IOPS), 99–100 disk compression, 97–98, 99 disk storage, 97–100 DVD/CD-ROM, 106 dynamic sparing, 99 Initial Program Load (IPL) device, 106 mirroring, 99 Model 2105 Enterprise/Versatile Storage Server, 97, 98–99 optical libraries, 104–106 RAID-5, 99 Storage Area Network (SAN) device, 98 tape adapters (Input/Output Processors, IOPS), 103–104 330 Exploring IBM ~ iSeries tape storage options, 101–103 availability. See also system availability functions OptiConnect and, 59, 66–67 security goal, 321 Virtual Private Network (VPN), 169 average latency of disk unit, 56, 57 average seek time of disk unit, 56, 57 bandwidth maximization, OptiConnect, 60 base layer of San Francisco Framework, 227, 228 batch commands, iSeries Access Family, 185 BCAL (bus control adapter logic) chip, 46, 47 benchmark testing Domino 5.0.5, 37–38, 288 iSeries computers, 34–36 B benefits and cost justification, 315–317 B2B (business-to-business) BEST/1 users and PATROL for iSeries, 211 IBM Networking Blueprint, 261 BIGINT support, iSeries Access Family, 184 software integration framework, kernel binary-tree pseudo-LRU (lines recently used) threads, 229–230 algorithm, 51 Baan, 230 Bisync communications protocol, 111, 163 backup/recovery, 189–197. See also OS/400 bits, 39, 53 (Operating System/400) blacklist support, TCP/IP, 167 access path recovery, 195–196 Blade Center, 5 Application Storage Pools (ASPs), 194, 196 Bluetooth, 6 archiving data, 192 Bob’s Gearbox Co. (small business BRMS Advanced Functions Feature, environment), 297–299 194–195 BOM (byte order mark), 242 BRMS Network Feature, 194 Borland, 238 business-critical applications protection, branch prediction, POWER 192 microprocessors, 45 data archive and retrieval, 191 BRMS/400 (Backup Recovery and Media Direct Access Storage Devices (DASDs) Services/400), 191, 192–195 for, 55–57, 97, 192 BRMS Advanced Functions Feature, functional-usage model, 193–194 194–195 Hierarchical Storage Management (HSM), BRMS Network Feature, 194 194, 196–197 BSF (Byte Stream File), 70 importance of, 57, 58 bus control adapter logic (BCAL) chip, 46, iSeries Backup and Recovery Guide 47 (IBM), 324 business and iSeries, 292–327. See also cost iSeries Navigator and, 193, 194 justification; security media functions, 194–195 64-bit processing, 39, 310–311, 312 move policies, 194–195 API-centric architecture, 311 parallel backup, 193 application programs selection, 294–296 PASSWORDACCESSGENERATE client classroom courses, IBM Education and option, 193 Training, 320 policy-driven, 193 computing needs identification, 293–294 recovery, step-by-step, 192 current operations, examining, 294 restore commands, 190–191 custom application programs, 133–134, restore wizard, BRMS, 195 296 save commands, 190 Dedicated Server for Domino (DSD) save while active feature, 190 environment, 31–34, 307–309 System-Managed Access Path Protection discover/education series, IBM Education (SMAPP), 195–196 and Training, 320 tape libraries support, 192 education/training, 314, 319–321 Tivoli Storage Manager (TSM) V5.1, goals of business, 294 191–192 hackers, 263, 264 usage frequency for, 194 hardware selection, 296, 318–319 Backup Recovery and Media Services/400 IBM Education and Training, 320–321 (BRMS/400), 191, 192–195 information flow of business, 294 Index large business environment (Atole Enterprises), 149–152, 304–307 learning centers, IBM Education and Training, 320 medium business environment (Johnson & Thornbush), 299–304, 309–310 migrating to iSeries, 7, 72–73, 326–327 personalized learning series, IBM Education and Training, 320 prewritten application programs, 123–124, 295–296 processor-centric architecture, 311 project team for computing needs identification, 293–294 replacement iSeries, sizing, 327 self-study courses, 321, 322 server selection, 309–310 service agreements, 325–326 small business environment (Bob’s Gearbox Co.), 297–299 software maintenance, 313, 326 Technology Independent Machine Interface (TIMI), 10, 11, 119, 232, 311 vertical market application programs, 295–296 warranty, 325–326 business-critical applications protection, 192 business cycle improvements, 315 business data in data warehouse, 125 business-to-business. See B2B bus utilization, 41 bus-wired network, 108 buying vs. leasing, 318–319 bytecodes, Java, 231 byte order mark (BOM), 242 bytes, 39 Byte Stream File (BSF), 70 C C++, 231 C2 level of security, 324, 325 cable-thru wiring scheme, 73–74 cache line replacement, 51 cache memory, 41 CAL (Client Access License), 289 Capacity Upgrade on Demand (CUoD), xviii, 13, 14, 15, 31 capital lease, 318 Carrier Sense Multiple Access-Collision Detect (CSMA-CD), 108 carrying costs reduction, 315 CD-ROM (Compact Disk-Read Only Memory), 58, 104, 106 331 CFIOP (Combined-Function I/O Processor) auxiliary storage options, 77, 89–90, 91–93 workstations, 97, 106 CGI (Common Gateway Interface), 266–267 check bits, 53 CICS/400. See CICS Transaction Server for iSeries (5769-DFH) CICS file support, IFS, 139 CICS Transaction Server for iSeries (5769-DFH), 145–146 class libraries, Java, 231, 234 classroom courses, IBM Education and Training, 320 CL (Control Language), 136 Client Access Express for Windows. See iSeries Access for Windows (5769-XE1) Client Access for iSeries. See iSeries Access Family (5722-XW1) Client Access License (CAL), 289 Client/Access PC5250 Console function and workstations, 77 client application layer, 9–10 client certificates, HTTP Server for iSeries, 266 client choices, Domino 5.0.5, 289–290 Client Encryption, iSeries Access Family, 188 Client for Windows NT/2000 File System, 146 clock rates, POWER microprocessors, 48 clustering OptiConnect, 59, 252–253 system availability, 65, 68–71 cluster nodes, 70 Clusters, 4 CMOS (Complementary Metal Oxide Semiconductor) technology, 73 code, software, 122 CODE, WDS, 214 collaborative computing, 127–128 Collection Services, Management Central, 205 color printers (nonimpact), 89 Combined-Function I/O Processor. See CFIOP commercial applications layer of San Francisco Framework, 228 commercial workloads, POWER microprocessors, 45–46 commitment control, iSeries Access Family, 188–189 common business layer of San Francisco Framework, 227, 228 Common Gateway Interface (CGI), 266–267 332 Exploring IBM ~ iSeries common interface of IFS, 139, 140, 142–143 Common Object Request Broker Architecture (CORBA), 230–231 Common Programming Interface for Communications (CPI-C), 256–257 common resource grouping (CRG), 71 communications and e-business, 245–246. See also Domino 5.0.5 for iSeries; HTTP server for iSeries; IBM Networking Blueprint; IBM SecureWay; iSeries and the Internet; iSeries ESP (Extreme Support Personalized) communications and OS/400, 162–173. See also TCP/IP (Transmission Protocol/ Internet Protocol) Advanced Peer-to-Peer Network (APPN), 172, 250 Communications Utilities (5738-CM1), 172–173 Electronic Customer Support (ECS), 170 NetView/Remote Manager (NV/RM), 171 Network Remote Facilities (NRF), 171 programming support, 163 protocols supported, 163 Remote Job Entry Facility (RJE), 172–173 S/390 communications support, 172–173 support of, 137 Systems Network Architecture (SNA), 171–172 Systems Network Management, 170–171 Wireless Connection for iSeries (5798-TBW), 172 communications functions, software, 119–120 communications lines costs, 314 communications options, 106–112 Async communications protocol, 111, 163 Asynchronous Transfer Mode (ATM), 109, 110 Bisync communications protocol, 111, 163 bus-wired network, 108 Carrier Sense Multiple Access-Collision Detect (CSMA-CD), 108 communications protocols, 111 Ethernet LANs, 108, 163, 251, 252 Frame Relay communications protocol, 111 IDLC communications protocol, 111 Integrated xSeries Server (IXS) and, 108 interfaces (electrical), 111 intranets, 106–107, 168, 263 Local Area Networks (LANs), 107–110 message frames, 109, 110 modems, 111–112 nodes, 108 overview of, 91–92 SDLC communications protocol, 111, 163 token frame, 109 token-passing protocol, 109 token-ring LANs, 108–110, 163, 251 Wide Area Networks (WANs), 106, 111 X.25 communications protocol, 111, 163 communications protocols, 111 Communications Utilities (5738-CM1), 172–173 Compact Disk-Read Only Memory (CD-ROM), 58, 104, 106 Compaq, 99 compatibility of software programs, 121–123, 137 competitive advantage, 316–317 compiler optimization, POWER microprocessors, 45 compiling programs, 122 Complementary Metal Oxide Semiconductor (CMOS) technology, 73 computer terminals (display station), 76 computing needs identification, 293–294 concurrency (synchronization) of DB2 UDB, 151–152 conditional branch instructions, POWER microprocessors, 51 confidentiality (security), 321 configuration/capacity chart iSeries Model i800, 19–20 iSeries Model i810, 22 iSeries Model i810D, 33 iSeries Model i825, 25 iSeries Model i825D, 35 iSeries Model i870, 27 iSeries Model i890, 29 Connect Framework for iSeries, IBM, 229–230 connectivity and Pervasive Computing (PvC), 5–6 Content Manager OnDemand for iSeries (5722-RD1), 162 continuous availability clustering for system availability, 65, 68–71 continuous forms printers, 88 Control Language (CL), 136 Control Panel functions and workstations, 78 copper-interconnect technology, 13 CORBA (Common Object Request Broker Architecture), 230–231 Index core business layer of San Francisco Framework, 227, 228 cost justification, 311–319. See also business and iSeries applications enhancement costs, 314–315 benefits and, 315–317 business cycle improvements, 315 buying vs. leasing, 318–319 capital lease, 318 carrying costs reduction, 315 communications lines costs, 314 competitive advantage, 316–317 customer service improvements, 316 defined, 312 education/training costs, 314, 319–321 employee turnover reductions, 317 environmental costs, 314 facilities costs, 313–314 financing purchase, 318 hardware maintenance costs, 312–313 inventory reduction benefits, 315 lease for software license, 319 leasing vs. buying, 318–319 license agreement for software, 319 loan for purchase, 318 monthly charge for software license, 319 net present value, 317 one-time charge for software license, 319 operating lease, 318–319 outright purchase, 318 payback period, 317 productivity improvement, 315–316 quality improvement benefits, 316 quantified benefits, 316–317 renting computer system, 319 residual value of computer system, 318 sales increases, 317 software maintenance costs, 313 software selection, 319 technical support costs, 313 term lease, 318 costs of printing, 83 CPI-C (Common Programming Interface for Communications), 256–257 CPW (typical business workload performance), 36, 37 crackers, 263 Create AFP DATA (CRTAFPDTA) command, 224 CRG (common resource grouping), 71 cross-industry application programs, 124–132. See also applications programs 333 Advanced Print Utility (APU), 131 AFP PrintSuite, 130–132 AFP Toolbox, 131–132, 220 AIX and, 129–130 business data in data warehouse, 125 collaborative computing, 127–128 data marts, 124 data mining, 125–127 data warehousing, 124–125 DB2 Multisystem and, 126 DB2 UDB and, 10, 15, 128 defined, 124 discovery-driven data mining, 125 Domino Server and, 128 groupware, 127–128 Integration BasePak for Lotus Notes and, 128 Intelligent Miner, 125, 126–127 Linux and, 130 Lotus Notes and, 127–128 Lotus Notes R4 server and, 128 metadata, 124–125 On-Line Analytical Processing (OLAP) products, 124 Page Printer Formatting Aid (PPFA), 131 parallel computing, 126 POP3 and, 128 Portable Application Solution Environment (PASE), 10, 15, 129–130 PowerPC code development and, 129–130 SAP R/3 AFP Print, 132 SMTP/MTA (Simple Mail Transport Protocol/Mail Transfer Agent), 128 technical data in data warehouse, 125 UNIX applications and, 129 CRTAFPDTA (Create AFP DATA) command, 224 Cryptographic Access Provider, IBM SecureWay, 264–266 cryptographic processors, 113–114 CSMA-CD (Carrier Sense Multiple AccessCollision Detect), 108 CUoD (Capacity Upgrade on Demand), xviii, 13, 14, 15, 31 current operations, examining, 294 custom application programs, 133–134, 296 customer service improvements, 316 cutsheet printers, 88 cycle time, 40, 41 334 Exploring IBM ~ iSeries D DADX (Document Access Definition Extension), 281 DASDs (Direct Access Storage Devices), 55–57, 97, 192 data archive and retrieval, 191 Database Navigator, 198 database results and iSeries Access Family, 185, 186 databases. See also DB2 database monitor, 156–157 management, Management Central, 204 Operating System/400 (OS/400) support, 137 relational databases, 147–152 software functions, 119–120, 121 data cache, 41, 47, 48 data confidentiality, TCP/IP, 168 Data Encryption Standard (DES), 113, 161 data formats, Java, 236–237 data integrity, 161, 168 data marts, 124 data mining, 125–127 data origin authentication, TCP/IP, 168 Data Propagator/400, 11 Data Propagator Relational/400, 252 data resiliency for system availability, 65, 68, 70 data streams (print languages), 85 data striping, 158–159 Data Transfer, iSeries Access Family, 183, 184 data transfer rate of disk unit, 56, 57 data warehousing, 124–125 DB2 Data Propagator, 156 DB2 Multisystem, 60, 126 DB2 OLAP Server, 155–156 DB2 Query Manager and SQL Development Kit, 153–161. See also DB2 Universal Database (UDB) for iSeries authentication of DCE, 160–161 database monitor, 156–157 Data Encryption Standard (DES), 161 data-integrity of DCE, 161 data striping, 158–159 DB2 Data Propagator, 156 DB2 OLAP Server, 155–156 DB2 Symmetric Multiprocessing (DB2 SMP), 154–155 DB2 UDB Extenders for iSeries, 155, 281–282 DCE cell directory service, 159, 160 Distributed Computing Environment (DCE) Base Services/400, 159–161 Distributed Time Services of DCE, 161 Interactive SQL (STRSQL), 154 Interface Definition Language (IDL), 159 Internet application serving, 154 iSeries ODBC Driver for Linux, 157–158 Java DataBase Connection (JDBC), 158 Open Database Connection (ODBC), 157 QMF for Windows for iSeries, 156 Remote Procedure Calls (RPCs), 159, 161 security of DCE, 160–161 Structured Query Language (SQL) and, 153 Text Extender, 155 XML Extender, 155 DB2 Symmetric Multiprocessing (DB2 SMP), 154–155 DB2 UDB Extenders for iSeries, 155, 281–282 DB2 Universal Database (UDB) for iSeries, 146–153. See also DB2 Query Manager and SQL Development Kit; OS/400 (Operating System/400) Atole Enterprises example, 149–152 concurrency (synchronization), 151–152 cross-industry application programs, 10, 15, 128 externally described data, 148 fields, 147 industry standards support, 153 lock management, 152 logical files, 148–149, 150, 151, 152 physical files, 148, 149, 150, 151, 152 records, 147 relational databases, 147–152 DCE cell directory service, 159, 160 DCE (Distributed Computing Environment) IBM Networking Blueprint, 253 Management Central, 204 DCE (Distributed Computing Environment) Base Services/400, 159–161 DCM (Digital Certificate Manager) HTTP Server for iSeries, 268 HTTP Server for iSeries (with SSL), 264, 272–273 IBM Networking Blueprint, 260–261 DDM (Distributed Data Management) OptiConnect, 60, 68, 252 OS/400, 162 Dedicated Server for Domino (DSD), 31–34, 307–309 DES (Data Encryption Standard), 113, 161 Index deskside system, iSeries Model i810, 18 deskside system, iSeries Model i825, 21, 24 deskside tower-based server, iSeries Model i800, 9, 16 details pane data format, Java, 237 Developer Kit for Java (iSeries), 234 DHCP (Dynamic Host Configuration Protocol), 164 dial-on-demand networking, TCP/IP, 165–166 Dial-up clients, 164 Differentiated Services, QoS, 262 Digital Certificate Manager. See DCM digital ID authentication, HTTP Server for iSeries, 267 Digital Signatures, IBM SecureWay, 264, 266 Digital Subscriber Line (DSL), 164 Direct Access Storage Devices (DASDs), 55–57, 97, 192 directory endpoint filter list, iSeries ESP, 250, 251 Directory Server, OS/400, 290–291 directory synchronization, Domino 5.0.5, 288 disaster-recovery plan, 323–324 disaster tolerance for system availability, 65, 71–72 discover/education series, IBM Education and Training, 320 discovery-driven data mining, 125 disk adapters (Input/Output Processors, IOPS), 99–100 disk compression, 97–98, 99 diskette storage, 55 disk storage, 53–54, 55–57, 97–100, 98 display station (computer terminals), 76 Distributed Computing Environment. See DCE Distributed Computing Environment (DCE) Base Services/400, 159–161 distributed computing function, 10 Distributed Data Management. See DDM Distributed Relational Database Architecture (DRDA), 68, 162 Distributed Time Services of DCE, 161 DNS (Domain Name Server), 164, 167 Document Access Definition Extension (DADX), 281 documentation (online), OS/400, 137 document characteristics, printers, 83 document services, AFP, 223 Domain Name Server (DNS), 164, 167 335 domain name serving function, HTTP Server for iSeries, 276 Domino, 14 Domino 5.0.5 for iSeries, 285–290 AnyMail, 288 Application Server, 289 benchmark testing of, 37–38, 288 Client Access License (CAL), 289 client choices, 289–290 directory synchronization, 288 features of, 285–287 iNotes, 289–290 iSeries Licensed Program, 289 kernel threads and, 287 Lotus Domino.Doc filing system, 288 Lotus Learning Space, 288–289 Lotus Notes and, 287–288, 290 object filing system support, 288 server choices, 289 Simple Mail Transport Protocol/Mail Transfer Agent (SMTP/MTA), 288 System Distribution Directory synchronization, 288 Domino Advanced Enterprise Server, 289 Domino and HTTP Server for iSeries, 268 Domino Designer, 290 Domino Enterprise Server, 289 Domino Mail Server, 289 Domino Name and Address book synchronization, 288 Domino Server and cross-industry application programs, 128 Domino Server models. See iSeries Model i810D; iSeries Model i825D double words, 39, 53 DRDA (Distributed Relational Database Architecture), 68, 162 DSD (Dedicated Server for Domino), 31–34, 307–309 DSL (Digital Subscriber Line), 164 DVD/CD-ROM, 106 DVD-RAM, 58, 104 DVD-ROM, 58, 104 dynamic caching of Web pages, 268 Dynamic Host Configuration Protocol (DHCP), 164 dynamic sparing, 99 dynamic workload manager, 13 E ease-of-use enhancements, OS/400, 136 e-business. See also iSeries computers 336 Exploring IBM ~ iSeries Monolithic Systems Technology, xx on-demand operating environment, xviii, 13 open standards element of e-business, xviii, 2 Pervasive Computing (PvC), 5–6 pSeries (replacing RS/6000 family), xxiv, 4, 99 reliability of, xviii, 13 self-managing/self-healing, xviii Storage Networking Industry Association (SNIA), 5 System/3 (“Old Reliable”), xx, xxi System/3X family of computers, xx–xxiii, xxiv, 121–123, 137, 326 total cost of ownership (TCO) reduction from, 5 TotalStorage strategy, 4–5 virtualization element of e-business, xviii, 3 Web site for, xix–xx, 222 wireless devices support, 5–6 xSeries (replacing Netfinity family), xxiv, 4 zSeries (replacing S/390 family), xxiv, 4, 172–173 ESP (Encapsulating Security Payload), 169 ESP (Extreme Support Personalized). See iSeries ESP Ethernet LANs, 108, 163, 251, 252 Euro currency symbol support, 221–222 European Monetary Union, 221 event Log (Windows NT), 90 explorer pane data format, Java, 237 Exploring IBM eServer iSeries and AS/400 Computers, 212 Exploring IBM’s AS/400 and iSeries Computers, 253 Extensible Markup Language (XML), xviii, 2, 237 externally described data, 148 extranets, 168 Extreme Support Personalized (ESP). See iSeries ESP EZ Setup and workstations, 78 TE AM FL Y on demand strategy, xviii, 1–2 IBM Networking Blueprint and, 260–263 ECS (Electronic Customer Support), IBM, 170, 246, 247, 248–251 Education and Training, IBM, 320–321 education (online), OS/400, 137 education/training, 314, 319–321 EIM (Enterprise Identity Mapping), 208 EJB (Enterprise Java Beans), 238 Electronic Customer Support (ECS), IBM, 170, 246, 247, 248–251 electronic-output documents, printers, 83, 84–85 electronic pages, AFP, 222 Electronic Service Agent for iSeries, IBM, 248 electronic storefront building, 283–285 eLiza (IBM Project), 158, 198–199 e-mail services, Java, 238 embedded SQL statements, Java, 233 employee turnover reductions, 317 Encapsulating Security Payload (ESP), 169 encryption, 167, 265 Endpoint menus, Management Central, 203 Enterprise Identity Mapping (EIM), 208 Enterprise Java Beans (EJB), 238 Enterprise package, 13 Enterprise Storage Server, 97, 98–99 environmental costs, 314 e-Output, 84–85, 224, 225 error and correction, hardware, 40 error detection and correction, storage, 53 error recovery, AFP, 223 eServer iSeries computers, xviii–6. See also iSeries computers AS/400 family of computers, xxiii–xxiv, 7, 9, 121–122, 326 AS/Entry system, xxiii autonomic computing element of e-business, xviii, 3 Blade Center, 5 Capacity Upgrade on Demand (CUoD), xviii, 13, 14, 15, 31 Clusters, 4 connectivity and Pervasive Computing (PvC), 5–6 dynamic workload manager, 13 e-business on demand strategy, xviii, 1–2 flexibility of, xviii, 13, 14 history, xx–xxiv integration goal of e-business, xviii, 2 iSeries (replacing AS/400 family), xxiv, 4 Logical Partitioning (LPAR), xviii, 11, 13, 14 F fabric controller, POWER microprocessors, 48, 49 facilities costs, 313–314 fault tolerance, TCP/IP, 167 feature cards, 75 fiber channel and disk storage, 54 fiber optic bus, 74 Team-Fly® Index fields in database, 147 File System functions, iSeries Access Family, 185 file systems support, IFS, 142–143 file transfer capability, iSeries ESP, 250 File Transfer Protocol (FTP), 166 filtered locations, iSeries ESP, 251 filter lists, iSeries ESP, 250–251 financing purchase, 318 firewalls, 264, 266, 275–276 flexibility of iSeries computers, xviii, 13, 14 #4754 Security Interface Unit (SIU), 114 Frame Relay communications protocol, 111 Frameworks application environment, 226–230 FTP (File Transfer Protocol), 166 full words, 39 functional-usage model, backup/recovery, 193–194 337 defined, 39, 40 double words, 39, 53 error and correction, 40 full words, 39 half words, 39 high-speed switch, 40, 41 instruction cache, 41, 47, 48 I/O, 40, 41 I/O processors, 40, 42 latency, 41 memory (main storage), 40, 41, 52–53, 54 multiple-memory bus architecture, 40, 41 N-way multiprocessor architecture, 42–44, 48, 64, 126 PCI bus (I/O bus), 40, 42 performance and, 39, 40, 41, 42, 43, 44 service processor, 42 Symmetric Multi-Processor (SMP) architecture, 42–44, 48, 64, 126 System Licensed Internal Code (SLIC), G xviii, 10, 11–12, 41 Gartner Group, 72 system processor, 39, 40 Generic Security Service (GSS) Application Hardware Cryptography, 260 Program Interface, 265–266 hardware layer, 10, 12 globalization, 241–243 hardware maintenance costs, 312–313 goals of business, 294 hardware selection, 296, 318–319 Graphical APIs, Java, 236 hardware side of system availability, 64, 65 graphical interfaces, iSeries Navigator, heartbeat monitoring, 59, 70 200–202 help, OS/400, 137 graphical user interface of IFS, 140 Hewlett-Packard, 99 grid computing, 244 hierarchical directory structure of IFS, 139 group files support, HTTP Server for iSeries, Hierarchical Storage Management (HSM), 270 194, 196–197 groupware, 127–128 High Availability Business Partners growth of business, freedom of, 14, 15 (HABPs), 59 GSS (Generic Security Service) Application high-performance file server function, IXS, Program Interface, 265–266 90 High-Speed Link (HSL), 13–14, 15, 46 H high-speed switch, 40, 41 HABPs (High Availability Business history of eServer iSeries, xx–xxiv Partners), 59 horizontal growth, 59, 72, 251 hackers, 263, 264 host components, WDS, 212–213 half words, 39 Host Print Transform (HPT), 220 handshake protocol of SSL, 274 Host Server option of OS/400 and Java, hardware architecture, 39–44. See also 237–238 POWER microprocessors HPT (Host Print Transform), 220 64-bit addressing, 39, 310–311, 312 HSL (High-Speed Link), 13–14, 15, 46 bits, 39, 53 HSM (Hierarchical Storage Management), bus utilization, 41 194, 196–197 bytes, 39 HTTP performance data, iSeries cache memory, 41 Performance Tools, 209 cycle time, 40, 41 HTTP Server for iSeries, 266–273. See also data cache, 41 IBM SecureWay 338 Exploring IBM ~ iSeries Apache Portable Runtime (APR) support, 268 Apache Software Foundation (ASF) and, 268–273 Application Program Interface (API), 268 Automatic Browser Detection, 267 client certificates, 266 Common Gateway Interface (CGI), 266–267 Digital Certificate Manager (DCM), 268 Digital Certificate Manager (DCM) with SSL, 264, 272–273 digital ID authentication, 267 domain name serving function, 276 Domino and, 268 dynamic caching of Web pages, 268 firewalls, 264, 266, 275–276 group files support, 270 handshake protocol of SSL, 274 Internet and, 277–278 Jakarta Tomcat and, 270 Java Server Pages (JSPs), 267 Java Servlet-based execution environment, 267 Log Analysis tools, 268 MOD-REWRITE support, 269 named protection support, 270 network gateway, 276 overview of, 264 record protocol of SSL, 274 reset changes options of Security Wizard, 275 search capability, 268 Secure Sockets Layer (SSL), 264, 266, 273–274 Security Wizard, 264, 274–275 server logs, 267 Server Side Includes (SSI) support, 269 traffic blocking, 275–276 user profiles, 266 validation lists, 266 virtual private networking (VPN) certificate, 273 WebDAV (MOD_DAV) support, 269, 270 Web server, 270–273 WebSphere Application Server (WAS) and, 267, 272 HTTP Server for iSeries-Powered by Apache, 264, 270–273 I IASPs (Independent Application Storage Pools). See also ASPs (Application Storage Pools) Integrated xSeries Server (IXS), 94 OptiMAL Connect, 61, 71 IBM AS/400 family of computers, xxiii–xxiv, 7, 9, 121–122, 326. See also iSeries computers IBM Connect Framework for iSeries, 229–230 IBM Education and Training, 320–321 IBM Electronic Customer Support (ECS), 170, 246, 247, 248–251 IBM Electronic Service Agent for iSeries, 248 IBM eServer Capacity Upgrade on Demand (permanent capacity), 31 IBM eServer On/Off Capacity Upgrade on Demand (temporary capacity), 31 IBM Infoprint Designer for iSeries, 225–226 IBM Infoprint Server for iSeries, 186, 223–225 IBM Information Network (IIN), 248, 249 IBMLink, 249 IBM Netfinity family (xSeries replacing), xxiv, 4 IBM Networking Blueprint, 253–263 Advanced Program-to-Program Communication (APPC), 257 Application Service Providers (ASPs) and, 261 applications support layer, 254–255, 255–259 business-to-business (B2B) and, 261 Common Programming Interface for Communications (CPI-C), 256–257 crackers, 263 Differentiated Services, QoS, 262 Digital Certificate Manager (DCM), 260–261 Distributed Computing Environment (DCE) and, 253 e-business and, 260–263 hackers, 263, 264 Hardware Cryptography, 260 Integrated Services, QoS, 262 intranets, 263 Kerberos, 261 Messaging and Queuing Interface (MQSeries), 257–258 MQSeries Adapter, 258–259 MQSeries Integrator, 258, 259 Multi-Vendor Application Program Interfaces, 255–259 Network Quality of Service (QoS), 261–263 overview of, 253, 254 Policy Enforcement Points (PEPs), 261 Index Quality of Service (QoS), 261–263 Remote Procedure Calls (RPCs), 257 RSVP APIs, 262, 263 signed components, 260, 264 subnetworking layer, 255 Systems Network Architecture (SNA) and, 253 Transport Layer Security (TLS), 255, 259–260 trusted users, 263 IBM Network Station, 81–82 IBM RS/6000 family (pSeries replacing), xxiv, 4, 99 IBM S/390 family (zSeries replacing), xxiv, 4, 172–173 IBM SecureWay, 263–291. See also HTTP Server for iSeries; iSeries and the Internet AES crypto algorithm, 265 Cryptographic Access Provider, 264–266 Digital Signatures, 264, 266 encryption, 265 Generic Security Service (GSS) Application Program Interface, 265–266 integrated security, 264 Kerberos, 266 object-based architecture, 264 observability, removed from program, 265 passwords, 265 program creation data, 265 Secure Sockets Layer (SSL), 264 signed components, 260, 264 IBM Toolbox for Java, 232 IBS (International Business Systems), 16 I-cache (Instruction Cache ), 119 ICU (International Components for Unicode), 242–243 IDE (Integrated Development Environment), 216 IDLC communications protocol, 111 IDL (Interface Definition Language), 159 IFS (integrated file system), 138–146. See also OS/400 (Operating System/400) access to data benefit of, 139 Application Storage Pools (ASPs), 140 benefits of, 139–140 CICS file support, 139 CICS Transaction Server for iSeries (5769-DFH), 145–146 Client for Windows NT/2000 File System, 146 common interface of, 139, 140, 142–143 file systems support, 142–143 graphical user interface, 140 339 hierarchical directory structure, 139 lock manager, 144 messaging protocols, 140 NetBios and, 140 Network File System (NFS) support, 139, 143–144, 204 ObjectConnect for iSeries, 61, 253 object names continuity, 140 overview of, 10, 11, 138, 139 QDLS support, 142 QLANSrv support, 142, 143 QNTC file system and, 140 QOPENSYS support, 142 QOPT support, 143 QSYS.LIB support, 142, 143 record-oriented files vs. stream files, 141–142 Remote File System (RFS) support, 139, 144–145 Remote Procedure Calls (RPCs), 143 root file system support, 142 separate file systems, 140 stateless design, 144 stream files, 138, 140, 141–142 system monitor, 144 threadsafe integrated file system API interfaces, 143 Transmission Protocol/Internet Protocol (TCP/IP) and, 140 UNIX-based open system standards support, 139, 140 Windows and, 140 IIN (IBM Information Network), 248, 249 IIS (Internet Information Server) and iSeries Access Family, 181 IKE (Internet Key Exchange), 169 ILE (Integrated Language Environment), 219 image files, AFP, 220 impact printers, 86 inbound browser access, AFP, 222 incoming balancing, TCP/IP, 165 Independent Application Storage Pools. See IASPs Independent Service Vendors (ISVs), 16 industry-specific applications programs, 124, 132–134 Infoprint Designer for iSeries, IBM, 225–226 Infoprint Image Editor, 225 Infoprint Layout Editor, 225 Infoprint Overlay Editor, 225 Infoprint Server for iSeries, IBM, 186, 223–225 information exchanges across Internet, 277 340 Exploring IBM ~ iSeries information flow of business, 294 Information Network (IIN), IBM, 248, 249 Info Window II workstations, 77 Initial Program Load (IPL) device, 106 iNotes, 289–290 Inprise, 231 Input/Output Processors (IOPS), 99–100, 103–104 instantaneous bandwidth of network, iSeries ESP, 251 instruction cache, 41, 47, 48 Instruction Cache (I-cache), 119 Integrated Development Environment (IDE), 216 integrated file system. See IFS Integrated Language Environment (ILE), 219 integrated midware layer, 10, 11 Integrated Netfinity Server. See IXS (Integrated xSeries Servers) Integrated PC Server (IPCS). See IXS (Integrated xSeries Servers) integrated security, IBM SecureWay, 264 Integrated Services, QoS, 262 Integrated xSeries Adapter (IXA), 15 Integrated xSeries Server. See IXS (Integrated xSeries Servers) Integration BasePak for Lotus Notes, 128 integration goal of e-business, xviii, 2 integrity (security), 321 intelligent integration, 14–15 Intelligent Miner, 125, 126–127 Intelligent Printer Data Stream (IPDS), 85, 86, 220, 222–223 intelligent workstations, 78–79 Intentia, 16, 230 interactive performance, 36–37 Interactive SQL (STRSQL), 154 interactive vs. server environments, performance, 36–38 Interface Definition Language (IDL), 159 interfaces (electrical), 111 International Business Systems (IBS), 16 International Components for Unicode (ICU), 242–243 Internet. See IBM SecureWay; iSeries and the Internet Internet and grid computing, 244 Internet application serving, 154 Internet Connection Server. See HTTP Server for iSeries Internet Information Server (IIS) and iSeries Access Family, 181 Internet Key Exchange (IKE), 169 Internet programming model support, Java, 237 Internet Protocol (IP) addresses, 278 Internet Service Providers (ISPs), 278 interoperability, TCP/IP, 169 intranets, 106–107, 168, 263 inventory for multiple systems, Management Central, 206 inventory reduction benefits, 315 I/O, 40, 41 I/O adapters, 13 IOAs (PCI I/O Adapters), 91–93 I/O bus (PCI bus), 40, 42 I/O capacity, POWER microprocessors, 46, 47 Iona Orbix, 230 I/O processors, 40, 42 IOPS (Input/Output Processors), 99–100, 103–104 IPComp (IP Payload Compression) protocol, 169 IPCS (Integrated PC Server). See IXS (Integrated xSeries Servers) IPDS (Intelligent Printer Data Stream), 85, 86, 220, 222–223 IP (Internet Protocol) addresses, 278 IPL (Initial Program Load) device, 106 IP masquerading technology, 165 IP Payload Compression (IPComp) protocol, 169 IPSec protocol, 169 IPv6 platform support, 165 iSeries Access (5769-XY1), 173, 174 iSeries Access and workstations, 78, 79 iSeries Access Family (5722-XW1), 173–189. See also OS/400 (Operating System/400) Advanced Function Printing (AFP) Workbench, 173, 182, 186 batch commands, 185 BIGINT support, 184 Client Encryption, 188 commitment control, 188–189 database results and, 185, 186 Data Transfer, 183, 184 File System functions, 185 functions of, 174 Infoprint Server for iSeries, 186, 223–225 Internet Information Server (IIS) and, 181 iSeries Navigator and, 188 iSeries-to-PC connectivity, 173 jobs support, 185 Index 341 journaling, 188–189 WebSphere Application Server-Express for Kerberos server, 182 iSeries (WAS-Express), 279–282 Lotus Notes client support, 188 WebSphere Application Server for iSeries OLE DB and, 184 (WAS), 278–279 Open Database Connection (ODBC) WebSphere Commerce Suite, 283–285 driver capabilities, 183 WebSphere Host Integration, 279 operating systems support, 174–181 iSeries Backup and Recovery Guide (IBM), Operations Console, 182 324 PC 5250 Operating console function, 182 iSeries computers, 7–34. See also auxiliary Personal Folder Container, 186 storage; business and iSeries; remote journaling, 189 communications; hardware Secure Sockets Layer (SSL) and, 182 architecture; iSeries and the Internet; security, 182 operating systems concepts; Terminal Server Edition (TSE) support, OptiConnect technology; OptiMAL 181 Connect; options and peripherals; Toolbox for Java, 182–183 performance; POWER Transmission Protocol/Internet Protocol microprocessors; software (TCP/IP), 181 architecture; specific iSeries Models; WebSphere Application Server (WAS) and, storage hierarchy; system availability 186 functions WebSphere Host Access Transaction advanced application architecture, 9–12 Server, 187 air intake, 8 WebSphere Host Publisher V4, 187–188 application program migration, 7 XML Toolkit for iSeries (5733-XT1), AS/400 family replacement, xxiv, 4 186–187 cable-thru wiring scheme, 73–74 iSeries Access for the Web (5722-XH1), Capacity Upgrade on Demand (CUoD), 185–187 xviii, 13, 14, 15, 31 iSeries Access for Windows (5769-XE1), client application layer, 9–10 181–185 Complementary Metal Oxide iSeries Access for Windows (5769-XW1), Semiconductor (CMOS) 173–174 technology, 73 iSeries Access for Wireless, 187 copper-interconnect technology, 13 iSeries and the Internet, 276–285. See also Dedicated Server for Domino (DSD), IBM SecureWay 31–34, 307–309 DB2 UDB Extenders for iSeries, 155, distributed computing function, 10 281–282 dynamic workload manager, 13 Document Access Definition Extension Enterprise package, 13 (DADX), 281 fiber optic bus, 74 electronic storefront building, 283–285 flexibility of, xviii, 13, 14 HTTP server and, 277–278 growth of business, freedom of, 14, 15 information exchanges, 277 hardware layer, 10, 12 Internet Protocol (IP) addresses, 278 high-speed links, 13–14, 15, 46 Internet Service Providers (ISPs), 278 horizontal growth, 59, 72, 251 macro boundaries, 282 IBM eServer Capacity Upgrade on Net.Data, 282–283 Demand (permanent capacity), 31 Simple Object Access Protocol (SOAP), IBM eServer On/Off Capacity Upgrade on 281 Demand (temporary capacity), 31 Telephone Directory V5.1 for iSeries, 281 Independent Service Vendors (ISVs) and, Transmission Protocol/Internet Protocol 16 (TCP/IP), 277 integrated file system, 10, 11 URLs and, 277 integrated midware layer, 10, 11 Web Services Object Runtime Framework Integrated xSeries Adapter (IXA), 15 (WORF), 281–282 Integrated xSeries Server (IXS), 15 342 Exploring IBM ~ iSeries intelligent integration, 14–15 I/O adapters, 13 Java Virtual Machine (JVM), 10, 11–12, 15, 231–232 legacy applications and, 11 Logical Partitioning (LPAR), xviii, 11, 13, 14 memory-switching technology, 13 multiuser computer systems, 7 Options package, 13 packaging, 8–9, 73–74 personal computers (PCs), 7, 8 price performance improvements, 13 printers, 7, 8 server layer, 10–11 server systems, 7 silicon-on-insulator technology, 13 system console, 7, 8 System Licensed Internal Code (SLIC), xviii, 10, 11–12, 41 system unit, 7, 8 system unit swap, 72–73 Technology Independent Machine Interface (TIMI), 10, 11, 119, 232, 311 terminals, 7, 8 twinaxial cable (twinax), 8 unlimited interactive performance, 16 upgrade paths, 72–73 vertical growth, 72–73, 252 Very Large Scale Integration (VLSI) technology, 73 Web site for, xix–xx, 222 iSeries Developer Kit for Java, 234 iSeries ESP (Extreme Support Personalized), 246–253 Data Propagator Relational/400, 252 directory endpoint filter list, 250, 251 file transfer capability, 250 filtered locations, 251 filter lists, 250–251 horizontal growth, 59, 72 IBM Electronic Customer Support (ECS), 246, 247, 248–251 IBM Electronic Service Agent for iSeries, 248 IBM Information Network (IIN), 248, 249 IBMLink, 249 instantaneous bandwidth of network, 251 iSeries Navigator and, 247 Management Central for, 247 ObjectConnect for iSeries, 61, 253 partner locations, 251 Program Temporary Fixes (PTFs), 247 question-and-answer database, 250 redundancy methodology, 252 RETAIN network, 250 session endpoint filter list, 250, 251 system clustering, 251–253 Universal Connection, 246, 247–248 utilization rate of network, 251–252 vertical growth, 72–73, 252 iSeries Licensed Program, 289 iSeries Model i800 Advanced offering, 16, 18 configuration/capacity chart, 19–20 deskside tower-based server, 9, 16 overview of, 14, 15, 19–20 packaging, 73 partitions supported, 67 performance, 37 Standard offering, 16, 17 standard offering, 16, 17 Value offering, 16–17 iSeries Model i810 configuration/capacity chart, 22 deskside system, 18 overview of, 14, 15, 16, 18, 21, 22 packaging, 73 partitions supported, 67 performance, 37, 42, 44 iSeries Model i810D configuration/capacity chart, 33 overview of, 14, 15, 32–33 performance, 38 iSeries Model i825 configuration/capacity chart, 25 deskside system, 21, 24 overview of, 14, 15, 16, 21–24 packaging, 73 partitions supported, 67 performance, 37, 41, 42, 44 iSeries Model i825D configuration/capacity chart, 35 overview of, 14, 15, 34, 35 performance, 38 iSeries Model i870 configuration/capacity chart, 27 overview of, 14, 15, 16, 24–27 packaging, 46, 73 partitions supported, 67 performance, 37, 41, 42, 44 iSeries Model i890 configuration/capacity chart, 29 overview of, 14, 15, 16, 28–31 Index packaging, 46, 73 partitions supported, 67 performance, 37, 41, 42, 44 iSeries Navigator, 197–202. See also Management Central; systems management backup/recovery and, 193, 194 Database Navigator, 198 graphical interfaces, 200–202 iSeries Access Family and, 188 iSeries Extreme Support Personalized (ESP) and, 247 iSeries Performance Tools and, 208 Logical Partitioning (LPAR) GUI and, 201–202 Project eLiza and, 198–199 Transmission Protocol/Internet Protocol (TCP/IP) configuration, 200 work management by, 197–200 workstations, 78 iSeries ODBC Driver for Linux, 157–158 iSeries Performance Tools, 208–212. See also systems management advisor function, 208 BEST/1 users and PATROL for iSeries, 211 HTTP performance data, 209 iSeries Navigator and, 208 Lightweight Directory Access Protocols (LDAPs) and, 209 NetFinity for iSeries, 211–212 PATROL for iSeries-Predict (5620-FIF), 209–211, 327 Performance Collection Services, 209 Performance Explorer (PEX), 209 performance requirements projections, 208 response-time analysis, 209–211 tuning system performance, 208 “what-if” analyzer, 209 iSeries Toolbox for Java, 182–183, 234–238 iSeries-to-PC connectivity, iSeries Access Family, 173 ISPs (Internet Service Providers), 278 ISVs (Independent Service Vendors), 16 ITG, 5 IXA-based networks, IXS, 93, 94 IXA (Integrated xSeries Adapter), 15 IXS (Integrated xSeries Servers), 93–96 communications options, 108 event Log (Windows NT), 90 high-performance file server function, 90 Independent Application Storage Pools (IASPs), 94 343 IXA-based networks, 93, 94 Local Area Networks (LANs) and, 90, 96, 108 message queue (iSeries), 90 NetServer, 93 overview of, 15 Storage Area Network (SAN), 94 twinaxial support, 95–96 Windows NT/Windows 2000 and, 90, 93 workstation adapters, 95–96 xSeries servers, 94–95 J J2EE (Java 2 Enterprise Edition), 232 Jakarta Tomcat, 186, 270 Java 2 Enterprise Edition (J2EE), 232 Java application environment, 231–238. See also kernel threads applets, 231, 232 bytecodes, 231 class libraries, 231, 234 data formats, 236–237 details pane data format, 237 e-mail services, 238 embedded SQL statements, 233 Enterprise Java Beans (EJB), 238 explorer pane data format, 237 Extensible Markup Language (XML), xviii, 2, 237 Graphical APIs, 236 Host Server option of OS/400 and, 237–238 IBM Toolbox for Java, 232 Internet programming model support, 237 iSeries Developer Kit for Java, 234 iSeries Toolbox for Java, 182–183, 234–238 J-Builder for, 238 just-in-time compilers, 231 list pane data format, 237 machine-independent language, 231 object-oriented programming language, 231 overview of, xviii, 2, 14 Panel Definition Markup Language (PDML), 237 Program Call Markup Language (PCML), 237 Programmed Access to PDF, 238 Secure Sockets Layer (SSL) and, 233, 237 static SQL statements, 233 Structured Query Language Java (SQLJ), 233–234 344 Exploring IBM ~ iSeries TC1 Licensed Program and, 237 Technology Independent Machine Interface (TIMI), 10, 11, 119, 232, 311 tree pane data format, 237 user interface framework, 237 Web browsers and, 231 WYSIWYG GUI editor, 237 javac compiler, 231 Java DataBase Connection (JDBC), 158 Java Developer’s Toolkit (JDK), 231 Java Generic Security Services (JGSS), 232–233 Java Server Pages (JSPs), 215, 267 Java Servlet-based execution environment, 267 Java Virtual Machine (JVM), 10, 11–12, 15, 231–232 J-Builder for Java, 238 J.D. Edwards, 16 JDBC (Java DataBase Connection), 158 JDK (Java Developer’s Toolkit), 231 JGSS (Java Generic Security Services), 232–233 jobs support, iSeries Access Family, 185 Johnson & Thornbush (medium business environment), 299–304, 309–310 journaling, iSeries Access Family, 188–189 JSPs (Java Server Pages), 215, 267 just-in-time compilers, Java, 231 JVM (Java Virtual Machine), 10, 11–12, 15, 231–232 Common Object Request Broker Architecture (CORBA), 230–231 core business layer of San Francisco Framework, 227, 228 Domino 5.0.5 and, 287 Frameworks application environment, 226–230 IBM Connect Framework for iSeries, 229–230 Linux for iSeries, 239–241 multi-threading, 226 OpenDoc applications environment, 226, 230 ORB support, 230–231 San Francisco Framework, 227–229 systems frameworks environment, 227 thread, defined, 226 threadsafe function, 226 key management, TCP/IP, 169 L L1 (Level 1) cache, 47, 48, 49 L2 (Level 2) cache, 47, 48, 49, 51 L2TP (Layer 2 Tunnel Protocol), 170 L3 (Level 3) cache, 48, 49, 51–52 Lakeview Technology, 59 LANs (Local Area Networks), 107–110. See also communications options Asynchronous Transfer Mode (ATM), 109, 110 bus-wired network, 108 Carrier Sense Multiple Access-Collision Detect (CSMA-CD), 108 K communications options, 107–110 Kerberos defined, 107 IBM Networking Blueprint, 261 Ethernet LANs, 108, 163, 251, 252 IBM SecureWay, 266 Integrated xSeries Server (IXS), 90, 96, 108 iSeries Access Family (5722-XW1), 182 intranets, 106–107, 168, 263 Transmission Protocol/Internet Protocol message frames, 109, 110 (TCP/IP), 160, 161, 167 nodes, 108 kernel threads, 226–241. See also Java terminals, Integrated xSeries Server (IXS), application environment; OS/400 96 (Operating System/400) token frame, 109 altered program objects, 238–239 token-passing protocol, 109 application environments, 226–238 token-ring LANs, 108–110, 163, 251 application frameworks environment, 227 large business environment (Atole base layer of San Francisco Framework, Enterprises), 149–152, 304–307 227, 228 Layer 2 Tunnel Protocol (L2TP), 170 business-to-business (B2B) software LCS (Local Controlling System), integration framework, 229–230 workstations, 76, 77 commercial applications layer of San LDAP Data Interchange Format (LDIF), Francisco Framework, 228 OS/400, 291 common business layer of San Francisco LDAPs (Lightweight Directory Access Framework, 227, 228 Protocols) Index iSeries Performance Tools, 209 Management Central, 204 Operating System/400 (OS/400), 291 LDIF (LDAP Data Interchange Format), OS/400, 291 learning centers, IBM Education and Training, 320 lease for software license, 319 leasing vs. buying computer systems, 318–319 legacy applications, 11 Level 1 (L1) cache, 47, 48, 49 Level 2 (L2) cache, 47, 48, 49, 51 Level 3 (L3) cache, 48, 49, 51–52 license agreement for software, 319 Lightweight Directory Access Protocols. See LDAPs line-at-a-time printing, 85 Linux cross-industry application programs, 130 iSeries Linux, 239–241 Operating System/400 (OS/400), 137 overview of, xviii, 2, 10, 13, 14, 15 list pane data format, Java, 237 loan for purchase, 318 Local Area Networks. See LANs Local Controlling System (LCS), workstations, 76, 77 location of printers, 83, 85–86 lock management, 152 lock manager of IFS, 144 Log Analysis tools, 268 logical files, DB2 UDB, 148–149, 150, 151, 152 Logical Partitioning. See LPAR loss prevention, 323–324. See also backup/ recovery Lotus Domino.Doc filing system, 288 Lotus Learning Space, 288–289 Lotus Notes, 127–128 Lotus Notes and Domino 5.0.5, 287–288, 290 Lotus Notes client support, iSeries Access Family, 188 Lotus Notes R4 server, 128 LPAR (Logical Partitioning) GUI and iSeries Navigator, 201–202 overview of, xviii, 11, 13, 14 system availability, 64–68 M machine-independent language, Java, 231 macro boundaries, Internet, 282 Mail and Calendar Users (MCU), 37 345 Mail Services Framework (MSF), 167 main storage (memory), 40, 41, 46, 47, 52–53, 54 Management Central, 203–207. See also iSeries Navigator; systems management Collection Services, 205 database management, 204 Distributed Computing Environment (DCE) and, 204 Endpoint menus, 203 inventory for multiple systems, 206 iSeries ESP (Extreme Support Personalized), 247 Lightweight Directory Access Protocols (LDAPs) and, 204 management-collection objects, 205 multiple systems monitoring with, 203–204 Network File System (NFS) management, 204 Object Packaging and Distribution Graphical Interface, 205–206 optional component of iSeries Navigator, 197 performance monitors, 203 PTF Management Wizards, 206 real-time graphical monitoring, 204 software problems, 205 system-detected software problems, 205 System menus, 203 Transmission Protocol/Internet Protocol (TCP/IP) security, 204 wireless environment, 206–207 Management Central Pervasive, 206–207 management-collection objects, Management Central, 205 Marterie, Ralph, xx Massachusetts Institute of Technology (MIT), 160 Maximum Press Web site, xix–xx MBps (millions of bytes per second), 56 MCM (Multichip Module), 48, 49, 51, 52 MCU (Mail and Calendar Users), 37 media functions, backup/recovery, 194–195 medium business environment (Johnson & Thornbush), 299–304, 309–310 “Members Only” Web site, xix–xx memory coherency, 51 memory (main storage), 40, 41, 46, 47, 52–53, 54 memory-switching technology, 13 message frames, 109, 110 message queue (iSeries), IXS, 90 346 Exploring IBM ~ iSeries NAT (Network Address Translation), 165, 169 Navigator. See iSeries Navigator NetBios and IFS, 140 Net.Data, 282–283 Netfinity family. See IBM Netfinity NetFinity for iSeries, 211–212 net present value, 317 Netscape Communications Corporation, 273 NetServer, IXS, 93 NetView/Remote Manager (NV/RM), 171 Network Address Translation (NAT), 165, 169 Network File System (NFS), 139, 143–144, 204 network gateway, 276 Networking Blueprint. See IBM Networking Blueprint network printing, AFP, 223, 224 Network Quality of Service (QoS), 261–263 Network Remote Facilities (NRF), 171 Network Station, IBM, 81–82 NFS (Network File System), 139, 143–144, 204 nodes, LANs, 108 nonimpact color printers, 89 nonimpact printers, 86, 87 nonvolatile storage, 54, 55, 97 NRF (Network Remote Facilities), 171 NV/RM (NetView/Remote Manager), 171 N-way multiprocessor architecture, 42–44, 48, 64, 126 TE AM FL Y Messaging and Queuing Interface (MQSeries), 257–258 messaging protocols of IFS, 140 metadata, 124–125 MFPs (Multifunction Printers), 83 microprocessors, 44–45. See also POWER microprocessors midsize computing systems. See iSeries computers migrating to iSeries, 7, 72–73, 326–327 millions of bytes per second (MBps), 56 mirroring, 99 MIT (Massachusetts Institute of Technology), 160 Mixed Object Document Content Architecture-Presentation (MODCA-P). See AFP (Advanced Function Printing) Mobile Worker, 168 MODCA-P (Mixed Object Document Content Architecture-Presentation). See AFP (Advanced Function Printing) MOD_DAV (WebDAV) support, HTTP Server for iSeries, 269, 270 Model 2105 Enterprise/Versatile Storage Server, 97, 98–99 models of iSeries computers. See specific iSeries Models modems, 111–112 MOD-REWRITE support, 269 modular application programs, 132–133 Monolithic Systems Technology, xx monthly charge for software license, 319 move policies, backup/recovery, 194–195 Movex V10.5, 16 MQSeries Adapter, 258–259 MQSeries Integrator, 258, 259 MSF (Mail Services Framework), 167 Multichip Module (MCM), 48, 49, 51, 52 Multifunction Printers (MFPs), 83 multiple-memory bus architecture, 40, 41 multiple systems monitoring with Management Central, 203–204 multisystem coupling for system availability, 65, 68 multi-threading, 226 multiuser computer systems, 7 Multi-Vendor Application Program Interfaces, 255–259 O object-based architecture, IBM SecureWay, 264 object code compatibility, 122–123 ObjectConnect/400, 61, 253 object filing system support, Domino 5.0.5, 288 object names continuity, IFS, 140 object-oriented programming language, Java, 231 Object Packaging and Distribution Graphical Interface, Management Central, 205–206 observability, removed from program, 265 ODBC (Open Database Connection), 157, 183 OGSA, xviii N OLAP (On-Line Analytical Processing) named protection support, HTTP Server for products, 124 iSeries, 270 “Old Reliable” (System/3), xx, xxi Team-Fly® Index OLE DB and iSeries Access Family, 184 OMG, 230 on-chip cache memory, POWER microprocessors, 45 on-demand operating environment, xviii, 13 one-time charge for software license, 319 On-Line Analytical Processing (OLAP) products, 124 op codes, POWER microprocessors, 45 Open Applications Group Inc., 259 Open Database Connection (ODBC), 157, 183 OpenDoc applications environment, 226, 230 Open Software Foundation (OSF), 159, 253 open standards element of e-business, xviii, 2 operating lease, 318–319 Operating System/400. See OS/400 operating systems concepts. See also OS/400 (Operating System/400) Application Program Interface (API), 135–136 byte order mark (BOM), 242 Control Language (CL), 136 globalization, 241–243 grid computing, 244 integrity (security), 325 International Components for Unicode (ICU), 242–243 iSeries Access Family, 174–181 software layer, 115, 116–118, 120, 122, 123 Unicode (ISO-10646), 241–243 user interface, 135 UTF-8/16 format, 242 Operations Console iSeries Access Family, 182 workstations, 77–78 optical libraries, 58, 104–106 OptiConnect technology, 59–61 Advanced Peer-to-Peer Communication (APPC), 60, 61 Application Program Interface (API), 61 availability and, 59, 66–67 bandwidth maximization, 60 clustering function, 59, 252–253 DB2 Multisystem and, 60 Distributed Data Management (DDM), 60, 68, 252 heartbeat monitoring, 59, 70 High Availability Business Partners (HABPs), 59 horizontal growth and, 59, 72 347 latency minimizing, 60 ObjectConnect/400 and, 61, 253 OptiMover, 61 Structured Query Language (SQL) and, 60 System Network Architecture Distribution Services (SNADS) and, 61 OptiMAL Connect clustering using, 62, 63 HA Switchable Resources for, 61 HSL OptiConnect, 61, 62 Independent Application Storage Pools (IASPs), 61, 71 OS/400 V5R1 and, 61 optimal decoding, POWER microprocessors, 45 OptiMover, 61 options and peripherals, 75–114. See also auxiliary storage options; communications options; IXS (Integrated xSeries Server); printers; workstations #4754 Security Interface Unit (SIU), 114 cryptographic processors, 113–114 Data Encryption Standard (DES), 113 feature cards, 75 packaging expansion features, 113 peripherals, 75 power options, 112–113 Rack-Mount capabilities, 113 Uninterruptible Power Supply (UPS), 112–113 Options package, 13 ORB support, kernel threads, 230–231 OS/400 (Operating System/400), 136–241. See also AFP (Advanced Function Printing); backup/recovery; communications and OS/400; DB2 Universal Database (UDB) for iSeries; IFS (integrated file system); iSeries Access Family; kernel threads; systems management; WDS (WebSphere Development Studio) application compatibility, 137 Application Development ToolSet (ADTS), 219–222 Application Program Interface (API), 137 communications support, 137 Content Manager OnDemand for iSeries (5722-RD1), 162 database support, 137 Directory Server, 290–291 Distributed Data Management (DDM), 162 348 Exploring IBM ~ iSeries Distributed Relational Database Architecture (DRDA) support, 162 documentation (online), 137 ease-of-use enhancements, 136 education (online), 137 help, 137 LDAP Data Interchange Format (LDIF), 291 Lightweight Directory Access Protocols (LDAPs), 291 Linux and, 137 overview of, xix, xviii, 13, 136–137 System/3X programs compatibility, 137, 326 system availability, 64–68 System Licensed Internal Code (SLIC) and, 136, 137 Windows desktop and, 136 OS/400 V4R5, V5R1 and Host Publisher for Pervasive Computing (PvC), 6 OS/400 V5R2 and Access for Wireless for Pervasive Computing (PvC), 6 OS/400 V5R2 and Enterprise Identity Mapping, xviii OSF (Open Software Foundation), 159, 253 outbound distribution, AFP, 222 outgoing balancing, TCP/IP, 165 out-of-order instruction execution, POWER microprocessors, 49–50 outright purchase, 318 Overlay Utility, 221 passwords, 265, 325 PATROL for iSeries-Predict (5620-FIF), 209–211, 327 payback period, 317 PC 5250 Operating console function, iSeries Access Family, 182 PCI bus (I/O bus), 40, 42 PCI I/O Adapters (IOAs), 91–93 PCL data stream, 85, 222 PCML (Program Call Markup Language), 215, 237 PC (personal computer) terminal emulation, 78–79 PCs (personal computers), 7, 8 PDF data stream, 85, 222, 224 PDML (Panel Definition Markup Language), 237 PEPs (Policy Enforcement Points), 261 performance, 34–38 auxiliary storage and, 56, 57, 97 benchmark testing, 34–36 Domino benchmarks, 37–38, 288 hardware and, 39, 40, 41, 42, 43, 44 interactive performance, 36–37 interactive vs. server environments, 36–38 iSeries Model i800, 37 iSeries Model i810, 37, 42, 44 iSeries Model i810D, 38 iSeries Model i825, 37, 41, 42, 44 iSeries Model i825D, 38 iSeries Model i870, 37, 41, 42, 44 iSeries Model i890, 37, 41, 42, 44 P Mail and Calendar Users (MCU), 37 packaging of iSeries computers monitors, Management Central, 203 expansion features, 113 POWER microprocessors and, 45, 47, 48 iSeries Model i800, 73 requirements projections, 208 iSeries Model i810, 73 server vs. interactive environments, 36–38 iSeries Model i825, 73 Simple Mail Users (SMU), 37 iSeries Model i870, 46, 73 storage hierarchy and, 52–53 iSeries Model i890, 46, 73 typical business workload performance overview of, 8–9, 73–74 (CPW), 36, 37 page-mode printing, AFP, 85 Typical Mail Users, 37–38 Page Printer Formatting Aid (PPFA), 131 Virtual Private Network (VPN), 169 Panel Definition Markup Language (PDML), Performance Collection Services, 209 237 Performance Explorer (PEX), 209 parallel backup, 193 Performance Tools. See iSeries Performance parallel computing, 126 Tools partitioning, 67, 99. See also LPAR (Logical peripherals, 75. See also options and Partitioning) peripherals partner locations, iSeries ESP, 251 personal computer (PC) terminal emulation, PASE (Portable Application Solution 78–79 Environment), 10, 15, 129–130 personal computers (PCs), 7, 8 PASSWORDACCESSGENERATE client Personal Folder Container, iSeries Access option, 193 Family, 186 Index personalized learning series, IBM Education and Training, 320 Pervasive Computing (PvC), 5–6 PEX (Performance Explorer), 209 physical files, DB2 UDB, 148, 149, 150, 151, 152 pipelining, POWER microprocessors, 45 platters of disk unit, 55–56, 96 point-to-point (PPP), 164, 170 policy-driven backup/recovery, 193 Policy Enforcement Points (PEPs), 261 POP3, 128 Portable Application Solution Environment (PASE), 10, 15, 129–130 postscript files, 220 POWER4 Microprocessor, 46, 48–51 POWER microprocessors, 44–51. See also hardware architecture branch prediction, 45 bus control adapter logic (BCAL) chip, 46, 47 clock rates, 48 commercial workloads, 45–46 compiler optimization, 45 conditional branch instructions, 51 data cache, 47, 48 fabric controller, 48, 49 High-Speed Link (HSL), 13–14, 15, 46 instruction cache, 47, 48 I/O capacity, 46, 47 latency to memory, 47, 48 Level 1 (L1) cache, 47, 48, 49 Level 2 (L2) cache, 47, 48, 49 Level 3 (L3) cache, 48, 49 memory (main storage) and, 46, 47 microprocessor defined, 44–45 Multichip Module (MCM), 48, 49, 51, 52 on-chip cache memory, 45 op codes, 45 optimal decoding, 45 out-of-order instruction execution, 49–50 performance and, 45, 47, 48 pipelining, 45 power options, 112–113 processor core, POWER4, 49–51 Reduced Instruction Set Computer (RISC) concept, 45 scientific/engineering workloads, 45–46 sequential instruction execution, 47 speculative execution, 50–51 SStar Microprocessor, 46–48 storage control chip, 46, 47 superscalar design, 45, 47, 49 target address prediction logic, 51 349 PowerPC code development and crossindustry application programs, 129–130 PPFA (Page Printer Formatting Aid), 131 PPP (point-to-point), 164, 170 preprinted forms, 83 prewritten application programs, 123–124, 295–296 price performance improvements, 13 printers, 82–89. See also AFP (Advanced Function Printing) Advanced Print Utility (APU), 131 AFP Toolbox, 131–132, 220 ASCII formats, 85 color printers (nonimpact), 89 continuous forms printers, 88 costs of printing, 83 cutsheet printers, 88 data streams (print languages), 85 defined, 76 document characteristics, 83 electronic-output documents, 83, 84–85 e-Output requirements, 84–85, 224, 225 impact printers, 86 importance (relative) of, 83 Intelligent Printer Data Stream (IPDS), 85, 86, 220, 222–223 line-at-a-time printing, 85 location of, 83, 85–86 Multifunction Printers (MFPs), 83 nonimpact color printers, 89 nonimpact printers, 86, 87 overview of, 7, 8 page-mode printing, 85 Page Printer Formatting Aid (PPFA), 131 PCL data stream, 85, 222 PDF data stream, 85, 222, 224 preprinted forms, 83 printing applications, 83 print window, 83 requirements for, 82–84 SAP R/3 AFP Print, 132 SNA Character Set (SCS), 85, 220 special forms, 83–84 transforms, 85, 222, 224, 225 Transmission Protocol/Internet Protocol (TCP/IP) and, 86 transparency, 85 volume of printing, 83 Print Format Utility, 221 Print Services Facility/400 (PSF/400), 220–222 problem log, 202 procedures, software, 122 350 Exploring IBM ~ iSeries processor-centric architecture, 311 processor core, POWER4, 49–51 productivity improvement, 315–316 Program Call Markup Language (PCML), 215, 237 program creation data, IBM SecureWay, 265 Programmed Access to PDF, 238 programming language, 122 Programming Request per Quote (PRPQ), 61 programming support for communications and OS/400, 163 Program Temporary Fixes (PTFs), 247 Project eLiza, 158, 198–199 project team for computing needs identification, 293–294 protocols supported by OS/400, 163 Proxy ARP Routing, 167 PRPQ (Programming Request per Quote), 61 pSeries (replacing RS/6000 family), xxiv, 4, 99 PSF/400 (Print Services Facility/400), 220–222 PTF Management Wizards, Management Central, 206 PTFs (Program Temporary Fixes), 247 PvC (Pervasive Computing), 5–6 Q QDLS support, IFS, 142 QLANSrv support, IFS, 142, 143 QMF for Windows for iSeries, 156 QNTC file system and IFS, 140 QOPENSYS support, IFS, 142 QOPT support, IFS, 143 QoS (Quality of Service), 261–263 QSYS.LIB support, IFS, 142, 143 quality improvement benefits, 316 Quality of Service (QoS), 261–263 quantified benefits, 316–317 question-and-answer database, iSeries ESP, 250 R Rack-Mount capabilities, 113 RAID-5, 99 RCS (Remote Controlling System), workstations, 76, 77–78 read/write head, 56, 97, 101 real-time graphical monitoring, Management Central, 204 record-oriented files vs. stream files, 141–142 record protocol of SSL, 274 records in database, 147 recovery, step-by-step, 192. See also backup/ recovery Reduced Instruction Set Computer (RISC) concept, 45 redundancy methodology, iSeries ISP, 252 relational databases, 147–152 reliability of eServer iSeries, xviii, 13 Remote Access Extensions, 170 Remote Controlling System (RCS), workstations, 76, 77–78 remote environments, TCP/IP, 168 Remote File System (RFS) support, IFS, 139, 144–145 Remote Job Entry Facility (RJE), 172–173 remote journaling, iSeries Access Family, 189 Remote Procedure Calls. See RPCs remote workstations support, TCP/IP, 162–163 renting computer system, 319 replacement iSeries, sizing, 327 replay protection, TCP/IP, 168 reset changes options of Security Wizard, 275 residual value of computer system, 318 Resource Management Utility, 221 response-time analysis, iSeries Performance Tools, 209–211 restore commands, 190–191 restore wizard, BRMS, 195 retail workstations, 80 RETAIN network, 250 RFS (Remote File System) support, IFS, 139, 144–145 RIP (Routing Information Protocol), 167 RISC (Reduced Instruction Set Computer) concept, 45 RJE (Remote Job Entry Facility), 172–173 Rochester, Minnesota (IBM plant site), xx root file system support, IFS, 142 Routing Information Protocol (RIP), 167 RPCs (Remote Procedure Calls) DB2 Query Manager and SQL Development Kit, 159, 161 IBM Networking Blueprint, 257 IFS (integrated file system), 143 RS/6000. See IBM RS/6000 RSVP APIs, 262, 263 S S/390 family. See IBM S/390 sales increases, 317 San Francisco Framework, 227–229 SAN (Storage Area Network), 94, 98 Index SAP, 230 SAP R/3 AFP Print, 132 save commands, 190 scientific/engineering workloads, POWER microprocessors, 45–46 SCS (SNA Character Set), 85, 220 SDLC communications protocol, 111, 163 search capability, HTTP Server for iSeries, 268 Secure Sockets Layer. See SSL SecureWay. See IBM SecureWay security, 321–325. See also backup/recovery; business and iSeries; IBM SecureWay authorized users accidents, 322–323 availability (security), 321 C2 level of security, 324, 325 confidentiality (security), 321 disaster-recovery plan, 323–324 Distributed Computing Environment (DCE), 160–161 integrity (security), 321 iSeries Access Family, 182 loss prevention, 323–324 operating system integrity, 325 passwords, 265, 325 software functions, 119–120 theft prevention, 324–325 Tips and Tools for Securing Your iSeries (IBM), 325 Transmission Protocol/Internet Protocol (TCP/IP), 167, 168–169, 204 Trusted Computing Systems Evaluation Criteria (TCSEC), 324 user-access control, 325 Security Interface Unit (SIU), 114 Security Wizard, HTTP Server for iSeries, 264, 274–275 self-managing/self-healing, xviii self-study courses, 321, 322 separate file systems, IFS, 140 sequential instruction execution, POWER microprocessors, 47 server choices, Domino 5.0.5, 289 server layer, 10–11 server logs, HTTP Server for iSeries, 267 server selection, 309–310 Server Side Includes (SSI) support, HTTP Server for iSeries, 269 server systems, 7 server vs. interactive environments, performance, 36–38 service agreements, 325–326 service processor, 42 351 session endpoint filter list, iSeries ESP, 250, 251 7133 Serial Storage Subsystem, 97, 98–99 signed components, IBM SecureWay, 260, 264 silicon-on-insulator technology, 13 Simple Mail Transport Protocol/Mail Transfer Agent (SMTP/MTA), 128, 288 Simple Mail Users (SMU), 37 Simple Object Access Protocol (SOAP), 281 SIU (#4754 Security Interface Unit), 114 64-bit addressing, 39, 310–311, 312 SLIC (System Licensed Internal Code) hardware architecture, xviii, 10, 11–12, 41 iSeries computers, xviii, 10, 11–12, 41 OS/400 (Operating System/400), 136, 137 software layer, 115, 116, 118–119, 120, 121, 122, 123 small business environment (Bob’s Gearbox Co.), 297–299 SmallTalk, 231 SMAPP (System-Managed Access Path Protection), 195–196 SMP (Symmetric Multi-Processor) architecture, 42–44, 48, 64, 126 SMTP/MTA (Simple Mail Transport Protocol/Mail Transfer Agent), 128, 288 SMTP scalability, 167 SMU (Simple Mail Users), 37 SNA Character Set (SCS), 85, 220 SNADS (System Network Architecture Distribution Services) and OptiConnect, 61 SNA (Systems Network Architecture), 171–172, 253 SNIA (Storage Networking Industry Association), 5 snoop processors, 51 SOAP (Simple Object Access Protocol), 281 software architecture, 115–123. See also applications programs; OS/400 (Operating System/400) application compatibility, 121–123, 137 application programs layer, 115, 116, 117, 120, 121–123 AS/400 programs compatibility, 121–122, 326 code, 122 communications functions, 119–120 compatibility of software programs, 121–123 352 Exploring IBM ~ iSeries compiling programs, 122 database functions, 119–120, 121 Instruction Cache (I-cache), 119 object code compatibility, 122–123 operating systems layer, 115, 116–118, 120, 122, 123 procedures, 122 programming language, 122 security functions, 119–120 source code, 122 System/3X programs compatibility, 121–123, 326 System Licensed Internal Code (SLIC) layer, 115, 116, 118–119, 120, 121, 122, 123 systems programmers and, 120, 121 Technology Independent Machine Interface (TIMI), 10, 11, 119, 232, 311 traditional computer systems vs. iSeries, 119–121 user’s view of system, 116, 117, 118 software maintenance, 313, 326 software problems, Management Central, 205 software selection, 319 software side of system availability, 64, 65 Software Systems Associates, 16 source code, 122 SPCN (System Power Control Network), 64 special forms printing, 83–84 speculative execution, POWER microprocessors, 50–51 SQLJ (Structured Query Language Java), 233–234 SQL (Structured Query Language), 60, 153 SSI (Server Side Includes) support, HTTP Server for iSeries, 269 SSL (Secure Sockets Layer) HTTP Server for iSeries, 264, 266, 273–274 IBM SecureWay, 264 iSeries Access Family, 182 Java, 233, 237 SStar Microprocessor, 46–48 Standard iSeries Model i800, 16, 17 stateless design, IFS, 144 static SQL statements, 233 Storage Area Network (SAN), 94, 98 storage control chip, POWER microprocessors, 46, 47 storage hierarchy, 51–54. See also auxiliary storage binary-tree pseudo-LRU (lines recently used) algorithm, 51 bits, 39, 53 cache line replacement, 51 check bits, 53 disk storage, 53–54, 55–57, 97–100 double words, 39, 53 error detection and correction, 53 fiber channel and disk storage, 54 Level 2 (L2) cache, 51 Level 3 (L3) cache, 51–52 memory coherency, 51 memory (main storage), 40, 41, 46, 47, 52–53, 54 Multichip Module (MCM), 48, 49, 51, 52 nonvolatile storage, 54, 55, 97 performance, 52–53 snoop processors, 51 virtual storage, 54 volatile storage, 53 storage management, 53–54 Storage Networking Industry Association (SNIA), 5 stream files, IFS, 138, 140, 141–142 STRSQL (Interactive SQL), 154 Structured Query Language Java (SQLJ), 233–234 Structured Query Language (SQL), 60, 153 subnetworking layer, IBM Networking Blueprint, 255 Sun Microsystems, 99, 231 superscalar POWER microprocessors, 45, 47, 49 Symmetric Multi-Processor (SMP) architecture, 42–44, 48, 64, 126 synchronization (concurrency) of DB2 UDB, 151–152 System/3 (“Old Reliable”), xx, xxi System/3X family of computers eServer iSeries computers, xx–xxiii, xxiv, 121–123, 137, 326 Operating System/400 (OS/400), 137, 326 programs compatibility, 121–123, 326 system availability functions, 62–72 actions required for, 64, 65 application resiliency for, 65, 68 Byte Stream File (BSF), 70 clustering for, 65, 68–71 cluster nodes, 70 common resource grouping (CRG), 71 continuous availability clustering for, 65, 68–71 data resiliency for, 65, 68, 70 Index 353 disaster tolerance for, 65, 71–72 TC1 Licensed Program and Java, 237 Distributed Relational Database TCO (total cost of ownership), 5 Architecture (DRDA), 68, 162 TCP/IP (Transmission Protocol/Internet hardware side of, 64, 65 Protocol), 163–170 heartbeat monitoring, 59, 70 Address Resolution Protocol (ARP), 167 Independent Application Storage Pools Advanced Function Printing (AFP), 223 (IASPs), 61, 71 availability of Virtual Private Network Logical Partitioning (LPAR) for, 64–68 (VPN), 169 multisystem coupling for, 65, 68 blacklist support, 167 OS/400 subsystems for, 64–68 data confidentiality, 168 software side of, 64, 65 data integrity, 168 System Power Control Network (SPCN), data origin authentication, 168 64 dial-on-demand networking, 165–166 system clustering, iSeries ESP, 251–253 Dial-up clients, 164 system console, iSeries computers, 7, 8 Digital Subscriber Line (DSL), 164 system-detected software problems, Domain Name Server (DNS), 164, 167 Management Central, 205 Dynamic Host Configuration Protocol System Distribution Directory (DHCP), 164 synchronization, Domino 5.0.5, 288 Encapsulating Security Payload (ESP), 169 System Licensed Internal Code. See SLIC encryption, 167 System-Managed Access Path Protection extranets, 168 (SMAPP), 195–196 fault tolerance, 167 System menus, Management Central, 203 File Transfer Protocol (FTP), 166 system monitor, IFS, 144 incoming balancing, 165 System Network Architecture Distribution Integrated File System (IFS), 140 Services (SNADS) and OptiConnect, Internet and, 277 61 Internet Key Exchange (IKE), 169 System Power Control Network (SPCN), 64 interoperability, 169 system processor, 39, 40 intranets, 168 systems frameworks environment, 227 IP masquerading technology, 165 systems management, 197–212. See also IP Payload Compression (IPComp) iSeries Navigator; iSeries Performance protocol, 169 Tools; Management Central; OS/400 IPSec protocol, 169 (Operating System/400) IPv6 platform support, 165 Enterprise Identity Mapping (EIM), 208 iSeries Access Family, 181 problem log, 202 iSeries Navigator, 200 SystemView System Manager/400, 202–203 Kerberos, 160, 161, 167 Systems Network Architecture (SNA), key management, 169 171–172, 253 Layer 2 Tunnel Protocol (L2TP), 170 Systems Network Management, 170–171 Mail Services Framework (MSF), 167 systems programmers, 120, 121 Mobile Worker, 168 system unit, 7, 8 Network Address Translation (NAT), system unit swap, 72–73 165, 169 SystemView System Manager/400, 202–203 outgoing balancing, 165 overview of, xviii, 15 T performance of Virtual Private Network tape adapters (Input/Output Processors, (VPN), 169 IOPS), 103–104 point-to-point (PPP), 164, 170 tape libraries support for backup/recovery, printers and, 86 192 Proxy ARP Routing, 167 tape storage, 58–59, 101–103 Remote Access Extensions, 170 target address prediction logic, POWER remote environments, 168 microprocessors, 51 remote workstations support, 162–163 354 Exploring IBM ~ iSeries replay protection, 168 Routing Information Protocol (RIP), 167 security, 167, 168–169, 204 SMTP scalability, 167 Telnet Server, 167 Transport Layer Security (TLS)/Secure Sockets Layer (SSL) support, 166 ValuNets, 168 Virtual AP Addressing (VIPA), 165 Virtual Private Networks (VPN), 164, 165, 168–169 TCSEC (Trusted Computing Systems Evaluation Criteria), 324 technical data in data warehouse, 125 technical support costs, 313 Technology Independent Machine Interface (TIMI), 10, 11, 119, 232, 311 Telephone Directory V5.1 for iSeries, 281 Telnet Server, 167 terminal emulation, 78–79 terminals, 7, 8. See also workstations Terminal Server Edition (TSE) support, iSeries Access Family, 181 term lease, 318 Text Extender, 155 theft prevention, 324–325 thread, defined, 226. See also kernel threads threadsafe function, 226 threadsafe integrated file system API interfaces, IFS, 143 #3995 Optical Library, 104–105 TIMI (Technology Independent Machine Interface), 10, 11, 119, 232, 311 Tips and Tools for Securing Your iSeries (IBM), 325 Tivoli Storage Manager (TSM) V5.1, 191–192 TLS (Transport Layer Security), 255, 259–260 TLS (Transport Layer Security)/Secure Sockets Layer (SSL), 166 token frame, 109 token-passing protocol, 109 token-ring LANs, 108–110, 163, 251 Toolbox for Java, IBM, 232 Toolbox for Java, iSeries, 182–183, 234–238 total cost of ownership (TCO), 5 TotalStorage strategy, 4–5 TPC (Transaction Performance Council), 36 traditional computer systems vs. iSeries, 119–121 traffic blocking, HTTP Server for iSeries, 275–276 Transaction Performance Council (TPC), 36 transforms, printers, 85, 222, 224, 225 Transmission Protocol/Internet Protocol. See TCP/IP transparency, printers, 85 Transport Layer Security (TLS), 255, 259–260 Transport Layer Security (TLS)/Secure Sockets Layer (SSL), 166 tree pane data format, Java, 237 Trusted Computing Systems Evaluation Criteria (TCSEC), 324 trusted users, 263 TSE (Terminal Server Edition) support, iSeries Access Family, 181 TSM (Tivoli Storage Manager) V5.1, 191–192 tuning system performance, iSeries Performance Tools, 208 twinaxial cable (twinax), 8 twinaxial support, IXS, 95–96 Type Transformer for Windows, 221 typical business workload performance (CPW), 36, 37 Typical Mail Users, 37–38 U UDB. See DB2 Universal Database Unicode (ISO-10646), 241–243 Uninterruptible Power Supply (UPS), 112–113 Universal Connection, 246, 247–248 Universal Product Code (UPC) barcode reader, 80 UNIX cross-industry application programs, 129 integrated file system (IFS) and, 139, 140 overview of, 10, 14 unlimited interactive performance, 16 UPC (Universal Product Code) barcode reader, 80 upgrade paths, 72–73 UPS (Uninterruptible Power Supply), 112–113 URLs and Internet, 277 U.S. Department of Defense, 324 usage frequency for backup/recovery, 194 user-access control, 325 user interface, operating systems, 135 user interface framework, Java, 237 user profiles, HTTP Server for iSeries, 266 user’s view of system, 116, 117, 118 UTF-8/16 format, 242 Index utilization rate of network, iSeries ESP, 251–252 V validation lists, HTTP Server for iSeries, 266 Value iSeries Model i800, 16–17 ValuNets, 168 VARPG (VisualAge RPG), 214–215 vertical growth, 72–73, 252 vertical market application programs, 295–296 Very Large Scale Integration (VLSI) technology, 73 Virtual AP Addressing (VIPA), 165 virtualization element of e-business, xviii, 3 virtual private networking (VPN) certificate, HTTP Server for iSeries, 273 Virtual Private Networks (VPN), 164, 165, 168–169 virtual storage, 54 VisiBroker, 231 Vision Solutions, 59 VisualAge for Java for iSeries, 213–214 VisualAge RPG (VARPG), 214–215 VLSI (Very Large Scale Integration) technology, 73 volatile storage, 53 volume of printing, 83 VPN (virtual private networking) certificate, HTTP Server for iSeries, 273 VPN (Virtual Private Networks), 164, 165, 168–169 W WANs (Wide Area Networks), 106, 111 warranty, 325–326 WAS-Express (WebSphere Application Server-Express for iSeries), 279–282 WAS (WebSphere Application Server) HTTP Server for iSeries, 267, 272 Internet and, 278–279 iSeries Access Family, 186 WDS (WebSphere Development Studio), 212–219. See also OS/400 (Operating System/400) CODE, 214 host components, 212–213 Integrated Development Environment (IDE), 216 Integrated Language Environment (ILE), 219 Java Server Pages (JSPs), 215 overview of, 213 355 Program Call Markup Language (PCML), 215 VisualAge for Java for iSeries, 213–214 VisualAge RPG (VARPG), 214–215 WebFacing Tool, 213, 215, 218, 219 Web Services, 216 Web site management, 213, 215 workstation components, 213–215 wrappering iSeries programs, 216, 218 Web browsers and Java, 231 WebDAV (MOD_DAV) support, HTTP Server for iSeries, 269, 270 WebFacing Tool, 213, 215, 218, 219 Web images, AFP, 224–225 Web server, HTTP Server for iSeries, 270–273 Web Services, 216 Web Services Object Runtime Framework (WORF), 281–282 Web site for eServer iSeries, xix–xx, 222 Web site management, WDS, 213, 215 WebSphere, 13, 15 WebSphere Application Server. See WAS WebSphere Commerce Suite, 283–285 WebSphere Development Studio. See WDS WebSphere Development Studio Client, 216–219 WebSphere Host Access Transaction Server, 187 WebSphere Host Integration, 279 WebSphere Host Publisher V4, 187–188 WebSphere Studio Site Developed Advanced, 216 WebSphere Studio Workbench, 216 WebSphere Studio (WS) for iSeries, 213, 215–219 WebSphere Transcoding Publisher, 6 “what-if” analyzer, iSeries Performance Tools, 209 Wide Area Networks (WANs), 106, 111 Windows desktop and Operating System/400 (OS/400), 136 integrated file system (IFS) and, 140 iSeries and, xviii, 10, 13, 14, 15 workstations, 77, 79 Windows NT/Windows 2000 and IXS, 90, 93 Wireless Connection for iSeries (5798-TBW), 172 wireless devices support of eServer iSeries, 5–6 wireless environment, Management Central, 206–207 356 Exploring IBM ~ iSeries Remote Controlling System (RCS), 76, 77–78 retail workstations, 80 terminal emulation, 78–79 Windows and, 77, 79 WORM (Write Once, Read Many), 58, 104 wrappering iSeries programs, WDS, 216, 218 Write Many, Read Many (WMRM), 58, 104 Write Once, Read Many (WORM), 58, 104 WS (WebSphere Studio) for iSeries, 213, 215–219 WYSIWYG GUI editor, 237 X TE AM FL Y WMRM (Write Many, Read Many), 58, 104 WORF (Web Services Object Runtime Framework), 281–282 work management by iSeries Navigator, 197–200 workspace for system processor. See memory (main storage) workstation adapters, IXS, 95–96 workstation components, WDS, 213–215 workstations, 76–90. See also auxiliary storage options; IXS (Integrated xSeries Servers); printers Client/Access PC5250 Console function and, 77 Combined-Function I/O Processor (CFIOP), 77, 89–90, 91–93 computer terminals (display station), 76 Control Panel functions and, 78 EZ Setup and, 78 IBM Network Station, 81–82 Info Window II workstations, 77 intelligent workstations, 78–79 iSeries Access and, 78, 79 iSeries Navigator and, 78 Local Controlling System (LCS), 76, 77 Operations Console, 77–78 PCI I/O Adapters (IOAs), 91–93 personal computer (PC) terminal emulation, 78–79 X.25 communications protocol, 111, 163 Xerces-C 2.1, 186 XML Extender, 155 XML (Extensible Markup Language), xviii, 2, 237 XML Toolkit for iSeries (5733-XT1), 186–187 xSeries (replacing Netfinity family), xxiv, 4 xSeries servers, IXS, 94–95. See also IXS (Integrated xSeries Servers) Z zSeries (replacing S/390 family), xxiv, 4, 172–173 Team-Fly® Reader Feedback Sheet Your comments and suggestions are very important in shaping future publications. Please e-mail us at [email protected] or photocopy this page, jot down your thoughts, and fax it to (850) 934-9981 or mail it to: Maximum Press Attn: Jim Hoskins 605 Silverthorn Road Gulf Breeze, FL 32561 Exploring IBM ~ pSeries, Eleventh Edition by Jim Hoskins and Robert Bluethman 344 pages $54.95 ISBN: 1-885068-81-6 Exploring IBM ~ iSeries, Eleventh Edition by Jim Hoskins and Roger Dimmick 386 pages $54.95 ISBN: 1-885068-92-1 Exploring IBM ~ zSeries and S/390 Servers, Eighth Edition by Jim Hoskins and Bob Frank 464 pages $59.95 ISBN: 1-885068-91-3 Exploring IBM ~ xSeries, Twelfth Edition by Jim Hoskins, Bill Wilson, and Ray Winkel 208 pages $49.95 ISBN: 1-885068-83-2 Exploring IBM e-business Software, Second Edition by Casey Young 360 pages $49.95 ISBN: 1-931644-00-4 Exploring IBM Technology, Products & Services, Fifth Edition edited by Jim Hoskins 272 pages $54.95 ISBN: 1-885068-82-4 Building Intranets with Lotus Notes & Domino 5.0, Third Edition by Steve Krantz 320 pages $39.95 ISBN: 1-885068-41-7 Internet Marketing for Information Technology Companies, Second Edition by Barry Silverstein 464 pages $29.95 ISBN: 1-885068-67-0 To purchase a Maximum Press book, visit your local bookstore or call 1-800-989-6733 (US/Canada) or 1-850-934-4583 (International) online ordering available at www.maxpress.com 101 Ways to Promote Your Web Site, Fourth Edition by Susan Sweeney, C.A. 528 pages $29.95 ISBN: 1-885068-90-5 Marketing With E-Mail, Third Edition by Shannon Kinnard 352 pages $29.95 ISBN: 1-885068-68-9 Business-to-Business Internet Marketing, Fourth Edition by Barry Silverstein 432 pages $34.95 ISBN: 1-885068-72-7 Marketing on the Internet, Sixth Edition by Jan Zimmerman 488 pages $34.95 ISBN: 1-885068-80-8 e-Business Formula for Success by Susan Sweeney, C.A. 360 pages $34.95 ISBN: 1-885068-60-3 The Business Guide to Selling Through Internet Auctions by Nancy Hix 608 pages $29.95 ISBN: 1-885068-73-5 101 Internet Businesses You Can Start From Home by Susan Sweeney, C.A. 520 pages $29.95 ISBN: 1-885068-59-X Internet Marketing for Less Than $500/Year, Second Edition by Marcia Yudkin 352 pages $29.95 ISBN: 1-885068-69-7 To purchase a Maximum Press book, visit your local bookstore or call 1-800-989-6733 (US/Canada) or 1-850-934-4583 (International) online ordering available at www.maxpress.com
