DOCSLIB.ORG

System/38 Employs Both Advanced Tech­ Nology and Many New Data Processing Concepts

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
System/38 Employs Both Advanced Tech­ Nology and Many New Data Processing Concepts Preface The IBM System/38 employs both advanced tech­ nology and many new data processing concepts. While the laboratory in Rochester, Minnesota, had primary responsibility for design and development, IBM people in laboratories in Boeblingen, Germany, Burlington, Vermont, and East Fishkill, New York, made important contributions. Our mutual objective was to produce a system that would be both accessible and extendable, and at the same time offer efficient conversion facilities. Function menus, help keys, multilayer messages, and a system-wide control language are essential elements of System/38, along with a flexible "user authoriza­ tion" scheme for system integrity and security. We chose to avoid traditional hardware-dependent addressing and storage management and instead to readily accommodate new technologies and storage organizations through a high-level machine archi­ tecture that not only frees the user from earlier restrictions but also supports a new kind of data base facility. Finally, because System/38 is viewed as a growth path from present systems, especially the IBM System/3, we developed conversion techniques rather than an emulator to give these users an opportunity The papers in this volume are not intended to replace IBM to benefit from the novel, even unique, capabilities of publications in describing the capabilities of the system the System/38. components and how to use them. Keep in mind that the papers are for general technical communication purposes; they do not represent an IBM warranty or commitment to Some 50 authors are represented in this special specific capabilities in the referenced products. collection of papers. I want to thank them and their Different structures and levels of detail may exist in the many colleagues whose combined efforts made papers because they were written as technical articles by System/38 a distinguished family of IBM products. various developers of the System/38. In order to preserve their technical integrity and vitality, they have not been integrated relative to consistency of style, language, or method of presentation. B. G. Utley Note that these papers will not be updated as changes are Manager, GSD Advanced Systems December 1978 made over time to the System/38 products. ------- - E==ffi Product esign and development I t mISS General yst ms Division T hni I v I m nls IBM S/38 TECH DEV, pp. 1-110, 1978 Table of contents G. G. Henry 3 Introduction to IBM System/38 architecture ENGINEERING TECHNOLOGY SUPPORT N. C. Berglund 7 Processor development in the LSI environment H. W. Curtis 11 Integrated circuit design, production, and packaging for System/38 M. N. Donofrio, B. Flur, and R. T. Schnadt 16 Memory design/technology for System/38 UNDERLYING MACHINE STRUCTURE R. L. Hoffman and F. G. Soltis 19 Hardware organization of the System/38 M. E. Houdek and G. R. Mitchell 22 Translating a large virtual address D. O. Lewis, J. W. Reed, and T. S. Robinson 25 System/38 I/O structure E. F. Dumstorff 28 Application of a microprocessor for I/O control F. X. Roellinger, Jr. and D. J. Horn 32 Microprocessor-based communications subsystem J. N. Tietjen and W. E. Hammer 36 Microprocessor-based work station controller D. T. Brunsvold 38 Microprocessor control of impact line printers for printing character-string data J. W. Froemke, N. N. Heise, and J. J. Pertzborn 41 System/38 magnetic media controller R. A. Peterson 44 Shared function controller design © 1978 by International Business Machines Corporation. See individual articles for copying information. ISBN 0-933186-00-2. Printed in U.S.A. HIGH -LEVEL MACHINE STRUCTURE S. H. Dahlby, G. G. Henry, D. N. Reynolds, 47 System/38-A high-level machine and P. T. Taylor V. Berstis, C. D. Truxal, and J. G. Ranweiler 51 System/38 addressing and authorization K. W. Pinnow, J. G. Ranweiler, and J. F. Miller 55 System/38 object-oriented architecture C. T. Watson and G. F. Aberle 59 System/38 machi.ne data base support R. E. French, R. W. Collins, and L. W. Loen 63 System/38 machine storage management P. H. Howard and K. W. Borgendale 67 System/38 machine indexing support SOME ADVANCES IN PROGRAMMING SUPPORT A. J. Conway and D. G. Harvey 70 User-System/38 interface design considerations D. G. Harvey and A. J. Conway 74 Introduction to the System/38 Control Program Facility c. T. Watson, F. E. Benson, and P. T. Taylor 78 System/38 data base concepts H. T. Norton, R. T. Turner, K. C. Hu, 61 System/38 work management concepts and D. G. Harvey J. H. Botterill and W. O. Evans 83 The rule-driven Control Language in System/38 C. D. Truxal and S. R. Ridenour 87 File and data definition facilities in System/38 R. O. Fess and F. E. Benson 91 File processing in System/38 H. T. Norton and T. R. Schwalen 94 Table-driven work management interface in System/38 R. A.Demers 97 The generalized message handler in System/38 J. K. Allsen 100 System/38 common code generation 103 Authors 109 Appendix: Reader's guide © 1978 by International Business Machines Corporation. See individual articles for copying information. ISBN 0-033186-00-2. Printed in U.S.A. States that new concepts in System/38 architecture include a layered structure providing consistent interfaces, a Introduction to unique high-level machine architecture, and capabilities for virtual addressing and task management. Support IBM System/38 functions are summarized and architectural concepts are described. architecture G.G. Henry The IBM System/38 is a new general-purpose data' oriented to support advanced user requirements. library, test and debug, source maintenance, and processing system designed to provide a high level data base utility functions. of function, ease of use, reliability, serviceability, and non<:lisruptive growth. It supports advanced data Figure 1 shows a high-level view of the system, in­ base and interactive work station applications as well cluding the dependency of all programming upon The remainder of this paper addresses the key con­ as traditional batch applications. These extensive the machine instruction set and the dependency of cepts of System/38 architecture. capabilities are made possible by the use of novel RPG III and IDU upon CPF functions. .architecture and design concepts, advanced techno­ logies, and new implementation of system compo­ Some key characteristics of the user-oriented support nents, both hardware and software. The new concepts are: include a layered structure providing consistent inter­ • Extensive data base facilities providing field-level faces, a unique high-level machine architecture, Control described data, .pro~am independence from _p~ysical Program and powerful capabilities for virtual addressing and Facility fue structures through use of logical fues, and simul­ task management. taneous access to data by multiple users. The data base concepts are discussed by Watson, et al [1]. This paper first summarizes the user support provided • Flexible work management functions supporting by the System/38 components and then introduces several different application approaches and allowing some of the salient archit~ctural concepts that per­ dynamic sharing of storage and other system re­ System/38 machine vade the design of System/38. sources. Work management aspects are treated by Norton, et al [2,3] . • High levels of device independence provided to System function programs-including screen formats and local/remote Figure 1 A high-level view of the architecture of System/38 consists of a machine and three major transparency. Various aspects are covered by-Truxal System/38 IBM licensed programs: Control Program Facility and Ridenour [5], and Fess and Benson [12]. (CPF), RPG III, and Interactive Data Base Utilities • New control language and data definition inter­ (IOU). The CPF provides operating system functions faces providing consistent access to all control to other programming components and to the end­ program and utility functions. These are discussed © 1978 by International Business Machines Corporation. Copying is permitted without royalty provided that (1) each user. RPG III is an enhanced version of the well­ by Botterill and Evans [4], and by Truxal and reproduction is unaltered and (2) the IBM copyright notice established RPG II language. IOU provides inter­ Ridenour [5] . and a reference to this book are on the first page. The title active data entry, source language entry, and query • Comprehensive and integrated authorization facili- and abstract may be used without further permission in information-service systems. Permission to republish in full functions. These components fit together to provide ties, which are reviewed by Berstis, et a1 [6]. should be obtained from IBM GSD Technical Communica­ a comprehensive and cohesive set of capabilities • Powerful program development facilities such as tions, Atlanta, GA 30301. HENRY INTRODUCTION TO IBM SYSTEM/38 ARCHITECTURE 3 System-oriented design and implementation Layered system structure Most systems have a layered structure to some degree. A total-system approach was used for the architec­ The significant concepts of the System/38 approach ture, design, and implementation of System/38. This approach to system-wide design and integrated are that there is only one interface for any general That is, system-wide design trade-offs were made function is supported by the layered structure of the type of usage; this interface is designed such that during the design and implementation of all compo­ system. System/38 support is structured into hori­ all functions are presented in a consistent and extend­ nents of the system. This approach toward eliminat­ zontal layers, each providing a consistent interface able fashion, and the interface does not require or ing potential p~oblems of design mismatch was sup­ that is not dependent upon implementation details permit use of implementation details of the next ported by imposing no internal compatability con­ of the other layers.
Load more

Recommended publications
  • On-Line Computing with a Hierarchy of Processors
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science December 1968 On-Line Computing With a Hierarchy of Processors Richard P. Morton University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Richard P. Morton, "On-Line Computing With a Hierarchy of Processors", . December 1968. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-69-13. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/804 For more information, please contact [email protected]. On-Line Computing With a Hierarchy of Processors Abstract Time shared computer systems have been based upon the two techniques of multiprogramming and swapping. Multiprogramming is based on restricting each program to a portion of the total computer memory. Swapping requires considerable overhead time for loading and unloading programs. To alleviate the size restriction due to multiprogramming, segmentation is employed, resulting in fact in vastly increased swapping. A new system architecture is proposed for time shared computing that alleviates the high overhead or program size restriction. It utilizes a hierarchy of processors, where each processor is assigned tasks on the basis of four factors: interactive requirements, frequency of use, execution time, and program length. In order to study the hierarchical approach to system architecture, the Moore School Problem Solving Facility (MSPSF) was built and used. The study of the manner of operation and the reactions of the users clarified and defined the Hierarchy of Processors system architecture. The Moore School Problem Solving Facility was implemented on second generation equipment, the IBM 7040, and therefore it is not possible to adequately compare the efficiency with third generation computers operating in a swapping mode.
    [Show full text]
  • Security on the Mainframe Stay Connected to IBM Redbooks
    Front cover Security on the IBM Mainframe Operating system and application security IBM Security Blueprint and Framework IBM mainframe security concepts Karan Singh Lennie Dymoke-Bradshaw Thomas Castiglion Pekka Hanninen Vincente Ranieri Junior Patrick Kappeler ibm.com/redbooks International Technical Support Organization Security on the IBM Mainframe April 2010 SG24-7803-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (April 2010) This edition applies to the IBM System z10 Enterprise Class server, the IBM System z10 Business Class server, and Version 1, Release 11, Modification 0 of z/OS (product number 5694-A01). © Copyright International Business Machines Corporation 2010. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x Preface . xi The team who wrote this book . xi Now you can become a published author, too! . xii Comments welcome. xii Stay connected to IBM Redbooks . xiii Part 1. Introduction . 1 Chapter 1. Introduction. 3 1.1 IBM Security Framework. 4 1.1.1 People and identity . 5 1.1.2 Data and information. 5 1.1.3 Application and process . 5 1.1.4 Network, server, and endpoint . 5 1.1.5 Physical Infrastructure . 6 1.2 Framework and Blueprint . 7 1.3 IBM Security Blueprint. 7 Chapter 2. Security of the IBM Mainframe: yesterday and today . 13 2.1 Operating systems . 14 2.1.1 z/OS operating system family . 14 2.1.2 z/VM Hypervisor family .
    [Show full text]
  • IBM Iseries Universal Connection for Electronic Support and Services
    IBM iSeries Universal Connection for Electronic Support and Services Explains the supported functions with Universal Connection Shows how to install, tailor, and configure Universal Connection Helps you determine communications problems Masahiko Hamada Michael S Alexander Makoto Kikuchi ibm.com/redbooks International Technical Support Organization SG24-6224-00 iSeries Universal Connection for Electronic Support and Services August 2001 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix A, “Special notices” on page 209. First Edition (August 2001) This edition applies to Version 5 Release 1 of OS/400. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2001. All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface . vii The team that wrote this redbook . vii Comments welcome . viii Chapter 1. Extreme Support Personalized (ESP) . .1 1.1 Introduction to ESP . .1 1.1.1 Customer Care Advantage . .1 1.1.2 ESP approach. .3 1.1.3 Benefits for customers. .4 1.2 Available applications in electronic support . .5 1.2.1 Electronic Customer Support (ECS) connection . .5 1.2.2 Service Agent . .6 1.2.3 Consolidated inventory collection using Management Central .
    [Show full text]
  • Data Definition Language
    1 Structured Query Language SQL, or Structured Query Language is the most popular declarative language used to work with Relational Databases. Originally developed at IBM, it has been subsequently standard- ized by various standards bodies (ANSI, ISO), and extended by various corporations adding their own features (T-SQL, PL/SQL, etc.). There are two primary parts to SQL: The DDL and DML (& DCL). 2 DDL - Data Definition Language DDL is a standard subset of SQL that is used to define tables (database structure), and other metadata related things. The few basic commands include: CREATE DATABASE, CREATE TABLE, DROP TABLE, and ALTER TABLE. There are many other statements, but those are the ones most commonly used. 2.1 CREATE DATABASE Many database servers allow for the presence of many databases1. In order to create a database, a relatively standard command ‘CREATE DATABASE’ is used. The general format of the command is: CREATE DATABASE <database-name> ; The name can be pretty much anything; usually it shouldn’t have spaces (or those spaces have to be properly escaped). Some databases allow hyphens, and/or underscores in the name. The name is usually limited in size (some databases limit the name to 8 characters, others to 32—in other words, it depends on what database you use). 2.2 DROP DATABASE Just like there is a ‘create database’ there is also a ‘drop database’, which simply removes the database. Note that it doesn’t ask you for confirmation, and once you remove a database, it is gone forever2. DROP DATABASE <database-name> ; 2.3 CREATE TABLE Probably the most common DDL statement is ‘CREATE TABLE’.
    [Show full text]
  • Origins of Operating Systems OS/360 Martin Grund
    Origins of Operating Systems OS/360 Martin Grund HPI Table of Contents ● IBM System 360 ● Functional Structure of OS/360 ● Virtual Machine Time Sharing Juni 2006 Origins of Operating Systems - OS/360 2 Martin Grund Welcome to Big Blue Juni 2006 Origins of Operating Systems - OS/360 3 Martin Grund IBM System 360 ● In 1964 IBM announced the IBM-360 family for computers ● All machines, despite their differences, had the same user instruction set ● Different operating systems available for these machines ● Only midrange and high-end system run OS/360 ● IBM introduced the new term of hardware architecture ● In 1970 IBM announced System 370 with hardware virtual memory support Juni 2006 Origins of Operating Systems - OS/360 4 Martin Grund IBM System 360 ● High-end machines established 32 bit as standard for computers ● Virtual Memory Support – hardware support for dynamic address translation ● Within ten years S/360 achieved standard status ● Flashback prices: ● 1970 – $279/MB hard disk ● 1980 - $35/MB hard disk | $50.000 /MB DRAM Juni 2006 Origins of Operating Systems - OS/360 5 Martin Grund IBM System 360 Specials ● Introduced 8bit entities ● Introduction of 32 or 64 bit floating point words based on a hexadecimal base ● Variable length strings using length field in the first byte ● All registers are universal registers – accumulators as well as address registers ● Registers use 32 bit, 24 bit for addressing -> 16MB Juni 2006 Origins of Operating Systems - OS/360 6 Martin Grund IBM S/360 - Pictures Juni 2006 Origins of Operating Systems -
    [Show full text]
  • - -:§';'§: ISG PROGRAM INDEX (Alphabetic)
    --- - Do not reproduce without written permission PI.1 ------ ---- Jan 84 :: - -:§';'§: ISG PROGRAM INDEX (Alphabetic) Program Name Number Available Type Page No. A Departmental Reporting System II (ADRS) 5796-PLN Now IUP 5796-PLK.1 A8CS Format Distribution Services - 4700 5799-8QZ Now PRPQ 5799-8QZ.1 Access Method Services Cryptographic Option Re1.1.0 5740-AM8 Now PP 5740-AM8.1 Accounting Applications - 5120 - Accounts Payable 5721-X83 Now PP 5721-X81.1 Accounting Applications - 5120 - Accounts Receivable 5721-X84 Now PP 5721-XB1.1 Accounting Applications - 5120 - Billing 5721-XB1 Now PP 5721-XB1.1 Accounting Applications - 5120 - General Ledger 5721-XB6 Now PP 5721-XB1.1 Accounting Applications - 5120 - Inventory Reporting 5721-XB5 Now PP 5721-XB1.1 Accounting Applications - 5120 - Payroll 5721-XB2 Now PP 5721-XB1.1 Account Network Management Programs - CICS/DOS/VS 5798-DAT Now FDP 5798-DAP.1 Account Network Management Programs - CICS/OS/VS 5798-DAQ Now FDP 5798-DAP.1 Account Network Management Program - IMS/VS 5798-DBP Now FDP 5798-DBJ.1 Accounts Payable 5798-CAC Now FDP 5798-BCT.1 Accounts Receivable 5798-CAE Now FDP 5798-BCT.1 ACF/NCP Version 2 5735-XX9 Now PP 5735-XX9.1 ACF/NCP Version 2 for the 3275 5735-XX9 Now PP 5735-XX9.1 ACF/NCP Version 3 for 3705/3725 5667-124 4/84 PP 5667-124.1 ACF/NCP/VS Releases 1, 2, 2.1 & 3 5735-XX1 Now PP 5735-XX1.1 ACF/NCP/VS Releases 2,2.1 & 3 Sys. Supp. Prog. 5735-XX3 Now PP 5735-XX3.1 ACF/System Support Programs V2 5735-XXA Now PP 5735-XXA.1 ACF /System Support Programs V2 R1.1 5735-XXA Now PP 5735-XXA.1
    [Show full text]
  • IBM AIX Version 6.1 Differences Guide
    Front cover IBM AIX Version 6.1 Differences Guide AIX - The industrial strength UNIX operating system AIX Version 6.1 enhancements explained An expert’s guide to the new release Roman Aleksic Ismael "Numi" Castillo Rosa Fernandez Armin Röll Nobuhiko Watanabe ibm.com/redbooks International Technical Support Organization IBM AIX Version 6.1 Differences Guide March 2008 SG24-7559-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (March 2008) This edition applies to AIX Version 6.1, program number 5765-G62. © Copyright International Business Machines Corporation 2007, 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . xi Tables . xiii Notices . xvii Trademarks . xviii Preface . xix The team that wrote this book . xix Become a published author . xxi Comments welcome. xxi Chapter 1. Application development and system debug. 1 1.1 Transport independent RPC library. 2 1.2 AIX tracing facilities review . 3 1.3 POSIX threads tracing. 5 1.3.1 POSIX tracing overview . 6 1.3.2 Trace event definition . 8 1.3.3 Trace stream definition . 13 1.3.4 AIX implementation overview . 20 1.4 ProbeVue . 21 1.4.1 ProbeVue terminology. 23 1.4.2 Vue programming language . 24 1.4.3 The probevue command . 25 1.4.4 The probevctrl command . 25 1.4.5 Vue: an overview. 25 1.4.6 ProbeVue dynamic tracing example . 31 Chapter 2. File systems and storage. 35 2.1 Disabling JFS2 logging .
    [Show full text]
  • IBM Application System/400 System/38-Compatible COBOL User's Guide and Reference
    IBM IBM Application System/400 SC09-1814-00 System/38-Compatible COBOL User’s Guide and Reference Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page xv. First Edition (June 1994) This edition applies to the System/38-Compatible feature of the IBM* ILE* COBOL/400* licensed program, (Program 5763-CB1), Version 3 Release 0 Modification 5, and to all subsequent releases and modifications until otherwise indi- cated in new editions. Make sure you are using the proper edition for the level of the product. Order publications through your IBM representative or the IBM branch serving your locality. Publications are not stocked at the address given below. A form for readers’ comments is provided at the back of this publication. If the form has been removed, you may address your comments to: IBM Canada Ltd. Laboratory Information Development 2G/345/1150/TOR 1150 Eglinton Avenue East, North York, Ontario, Canada M3C1H7 You can also send your comments by facsimile (attention: RCF Coordinator), or you can send your comments elec- tronically to IBM. See "Communicating your Comments to IBM" for a description of the methods. This page imme- diately precedes the Readers' Comment Form at the back of this publication. When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1994. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
    [Show full text]
  • Preparation of Papers for AIAA Technical Conferences
    NASA KSC – Internship Final Report Unit Testing and Remote Display Development Nicholas Costa Kennedy Space Center Computer Science USRA Summer Session 18 07 2014 NASA Center 1 18/7/2014 NASA KSC – Internship Final Report Unit Testing and Remote Display Development Nicholas Costa Denison University, Granville, Ohio, Abstract The Kennedy Space Center is currently undergoing an extremely interesting transitional phase. The final Space Shuttle mission, STS-135, was completed in July of 2011. NASA is now approaching a new era of space exploration. The development of the Orion Multi- Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) launch vehicle that will launch the Orion are currently in progress. An important part of this transition involves replacing the Launch Processing System (LPS) which was previously used to process and launch Space Shuttles and their associated hardware. NASA is creating the Spaceport Command and Control System (SCCS) to replace the LPS. The SCCS will be much simpler to maintain and improve during the lifetime of the spaceflight program that it will support. The Launch Control System (LCS) is a portion of the SCCS that will be responsible for launching the rockets and spacecraft. The Integrated Launch Operations Applications (ILOA) group of SCCS is responsible for creating displays and scripts, both remote and local, that will be used to monitor and control hardware and systems needed to launch a spacecraft. It is crucial that the software contained within be thoroughly tested to ensure that it functions as intended. Unit tests must be written in Application Control Language (ACL), the scripting language used by LCS.
    [Show full text]
  • IBM Powervp Introduction and Technical Overview
    Front cover IBM PowerVP Introduction and Technical Overview Liviu Rosca Stefan Stefanov Redpaper International Technical Support Organization IBM PowerVP: Introduction and Technical Overview August 2015 REDP-5112-01 Note: Before using this information and the product it supports, read the information in “Notices” on page v. Second Edition (August 2015) This edition applies to Version 1, Release 1, Modification 3 of PowerVP Standard Edition (product number 5765-SLE). This document was created or updated on August 14, 2015. © Copyright International Business Machines Corporation 2014, 2015. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . .v Trademarks . vi IBM Redbooks promotions . vii Preface . ix Authors. ix Now you can become a published author, too! . .x Comments welcome. xi Stay connected to IBM Redbooks . xi Chapter 1. Introduction. 1 1.1 PowerVP overview . 2 1.2 PowerVP features and benefits. 2 1.3 PowerVP architecture . 4 Chapter 2. Planning and installation . 9 2.1 Planning for PowerVP . 10 2.1.1 PowerVP security considerations . 12 2.2 PowerVP installation . 12 2.2.1 PowerVP installation overview . 13 2.2.2 PowerVP installer on Microsoft Windows systems . 13 2.2.3 Installing PowerVP GUI on AIX or Linux. 27 2.2.4 Installing PowerVP agent manually on IBM i . 30 2.2.5 Installing PowerVP agent on AIX and the VIOS . 31 2.2.6 Installing PowerVP agent on Linux . 34 2.3 Starting and stopping PowerVP . 39 2.4 Upgrading PowerVP agents . 40 2.5 PowerVP SSL configuration .
    [Show full text]
  • Programming the Cell Broadband Engine Examples and Best Practices
    Front cover Draft Document for Review February 15, 2008 4:59 pm SG24-7575-00 Programming the Cell Broadband Engine Examples and Best Practices Practical code development and porting examples included Make the most of SDK 3.0 debug and performance tools Understand and apply different programming models and strategies Abraham Arevalo Ricardo M. Matinata Maharaja Pandian Eitan Peri Kurtis Ruby Francois Thomas Chris Almond ibm.com/redbooks Draft Document for Review February 15, 2008 4:59 pm 7575edno.fm International Technical Support Organization Programming the Cell Broadband Engine: Examples and Best Practices December 2007 SG24-7575-00 7575edno.fm Draft Document for Review February 15, 2008 4:59 pm Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (December 2007) This edition applies to Version 3.0 of the IBM Cell Broadband Engine SDK, and the IBM BladeCenter QS-21 platform. © Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review February 15, 2008 4:59 pm 7575TOC.fm Contents Preface . xi The team that wrote this book . xi Acknowledgements . xiii Become a published author . xiv Comments welcome. xv Notices . xvii Trademarks . xviii Part 1. Introduction to the Cell Broadband Engine . 1 Chapter 1. Cell Broadband Engine Overview . 3 1.1 Motivation . 4 1.2 Scaling the three performance-limiting walls. 6 1.2.1 Scaling the power-limitation wall . 6 1.2.2 Scaling the memory-limitation wall .
    [Show full text]
  • Redbooks Paper Bringing PHP to Your IBM Iseries
    David Larson Bryan Logan Redbooks Paper Tim Massaro Heiko Mueller Brian R. Smith Bringing PHP to Your IBM iSeries Server Hypertext Preprocessor (PHP) is a powerful server-side scripting language for the Apache Web server. PHP is popular for its ability to process database information and create dynamic Web pages. Server-side refers to the fact that PHP language statements, which are included directly in your HTML, are processed by the Web server. Scripting language means that PHP is not compiled. Since the results of processing PHP language statements is standard HTML, PHP-generated Web pages are quick to display and are compatible with most all Web browsers and platforms. PHP is for the open source Apache community as Net.Data® is for the IBM® community. To “run” PHP scripts with your HTTP Server (powered by Apache), a PHP engine is required on your IBM ^™ iSeries™ server. The PHP engine is an open source product, so this IBM Redpaper demonstrates the process to download, compile, install, and then configure PHP on your iSeries. It explains how to install versions 4.3.0 and the older version 4.2.2 of PHP. The PHP engine is available both as an Apache module and a CGI-BIN. Support for PHP as a module is not yet available for OS/400®. The step-by-step implementation discussed in this Redpaper involves the CGI version of PHP running in OS/400 Portable Application Solutions Environment (PASE). This allows you to run AIX® binaries directly on an iSeries. It includes the necessary patches for the minor modifications needed to the PHP source code.
    [Show full text]