DOCSLIB.ORG

High Availability and Scalability of Mainframe Environments Using System Z and Z/OS As Example

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
High Availability and Scalability of Mainframe Environments Using System Z and Z/OS As Example robert vaupel _ of mainframe environments high availability and scalability of mainframe environments r. vaupel Robert Vaupel High Availability and Scalability of Mainframe Environments using System z and z/OS as example High Availability and Scalability of Mainframe Environments using System z and z/OS as example by Robert Vaupel Impressum Karlsruher Institut für Technologie (KIT) KIT Scientific Publishing Straße am Forum 2 D-76131 Karlsruhe www.ksp.kit.edu KIT – Universität des Landes Baden-Württemberg und nationales Forschungszentrum in der Helmholtz-Gemeinschaft Diese Veröffentlichung ist im Internet unter folgender Creative Commons-Lizenz publiziert: http://creativecommons.org/licenses/by-nc-nd/3.0/de/ KIT Scientific Publishing 2013 Print on Demand ISBN 978-3-7315-0022-3 Contents 1. Introduction 1 1.1. Motivation . 1 1.2. High Availability . 3 1.3. Scalability . 5 2. z/Architecture 9 2.1. A Little History . 9 2.2. System z CMOS Heritage . 12 2.3. System zEC12 Central Electronic Complex . 13 2.4. System zEC12 Components . 14 2.5. System z Multi Chip Module . 16 2.5.1. Memory . 17 2.5.2. Book . 18 2.5.3. Processor Characterization . 18 2.6. System z High Availability Design . 19 2.6.1. Transparent CPU Sparing . 20 2.6.2. CPU Error Detection for newer System z machines . 21 2.6.3. Redundant Array of Independent Memory . 22 2.7. System z Software and Firmware Layers . 25 2.8. Instruction Execution . 27 2.8.1. CISC versus RISC Architecture . 27 2.8.2. Register Sets . 30 2.8.3. Program Status Word . 31 2.8.4. System z Instructions . 33 2.8.5. Decimal Arithmetic . 35 2.8.6. Floating Point Arithmetic . 37 2.8.7. View of Instruction Execution . 40 2.8.8. Super-Scalar Instruction Execution . 42 2.8.9. System z10 Microprocessor Pipeline . 43 2.8.10. Instruction Re-Ordering . 46 2.8.11. Register Renaming . 47 2.8.12. Instruction Cracking . 49 ii Contents 2.8.13. Out-Of-Order Execution . 49 2.8.14. System z196 Microprocessor Core . 51 2.8.15. System z196 Instruction Handling . 54 2.8.16. System z196 Instruction Optimization . 54 2.8.17. System z196 Microprocessor Summary . 57 2.9. Interrupts . 57 2.9.1. Enabling and Disabling . 59 2.10. Timing Facilities . 60 2.10.1. Time-of-Day Clock . 60 2.10.2. Clock Comparator . 62 2.10.3. CPU Timer . 62 2.11. Storage Addressing . 63 2.11.1. Address Types . 63 2.11.2. Dynamic Address Translation . 64 2.11.3. Large Page Support . 66 2.11.4. Storage Protection . 66 2.11.5. Prefixing . 67 2.12. Multiprocessing . 68 2.12.1. Atomic Instructions . 69 2.13. Input and Output . 70 2.13.1. z196 I/O Infrastructure . 71 2.13.2. I/O System Overview . 72 2.13.3. I/O Drawer . 74 2.13.4. I/O Operation . 74 2.13.5. Logical Channel Subsystem . 76 2.13.6. I/O Configuration . 78 2.14. Logical Partitioning . 78 2.14.1. z/VM . 80 2.14.2. Start Interpretive Execution . 81 2.14.3. Logical Processor Management . 82 2.14.4. Storage of a Logical Partition . 84 2.14.5. Storage of a Virtual Machine under z/VM . 85 2.15. Summary . 86 3. z/OS 87 3.1. z/OS Structure . 87 3.2. Address Spaces . 89 3.2.1. Address Space Types and Storage . 91 3.2.2. Control Block Areas . 93 3.2.3. Storage Protection . 94 Contents iii 3.2.4. Address Space Creation . 94 3.3. Program Execution . 96 3.3.1. Reentrant Programming . 97 3.3.2. Program Recovery . 99 3.3.3. Recovery Processing . 101 3.4. Program Data Exchange . 102 3.4.1. Data Exchange via Common Storage . 103 3.4.2. Data Exchange via Cross Memory . 104 3.4.3. Access Registers . 108 3.5. Storage Management . 108 3.5.1. z/OS Storage Managers . 109 3.5.2. Managing Storage . 110 3.6. z/OS Data Sets . 114 3.6.1. Sequential Data Sets . 116 3.6.2. Partitioned Data Sets . 117 3.6.3. Allocating a Data Set . 118 3.6.4. Virtual Storage Access Method . 118 3.6.5. Data Set Organization . 119 3.7. Starting z/OS . 119 3.8. Job Entry System . 123 3.9. Time Sharing Option . 124 3.10. Unix System Services . 126 3.11. Summary . 127 4. Dispatching 129 4.1. Dispatching Requirements . 129 4.2. z/OS Dispatching . 132 4.2.1. CPU and Storage Management . 133 4.2.2. Dispatcher Queue . 134 4.2.3. Dispatching Work . 135 4.2.4. Preemption and Time Slicing . 137 4.2.5. Interrupt Processing . 138 4.2.6. I/O Enablement . 139 4.2.7. CPU Report Example . 141 4.3. PR/SM Dispatching . 143 4.3.1. Dispatching Logical Processors . 144 4.3.2. LPAR Report Example . 147 4.3.3. CEC Utilization Example . 149 4.4. Offload Processors . 151 4.4.1. Using zIIPs and zAAPs . 152 iv Contents 4.4.2. Processor Pools . 154 4.4.3. LPAR Report Example including Offload Processors . 155 4.5. Example on how z/OS and PR/SM Dispatcher work together . 156 4.5.1. z/OS Serialization . 156 4.5.2. z/OS Spin Lock Processing . 158 4.6. Limitations of Dispatching . 160 4.6.1. Large System Effects . 161 4.7. Hiperdispatch . 163 4.7.1. Vertical CPU Management . 164 4.7.2. Processor Shares . 165 4.7.3. Example for Unparking Low Processors . 167 4.7.4. Hiperdispatch in z/OS . 170 4.7.5. Affinity Nodes . 171 4.7.6. Assessment for Parking and Unparking Low Processors 173 4.7.7. Balancing Work . 174 4.7.8. Helper Processing . 175 4.7.9. System Work . 177 4.8. Hiperdispatch Analysis . 178 4.8.1. Processor Utilization . 178 4.8.2. Cycles per Instruction . 179 4.8.3. Hiperdispatch on z196 and zEC12 . 181 4.9. Summary . 182 5. Workload Management 185 5.1. Workload Management Concepts . 185 5.2. Why Workload Management . 186 5.3. Workload Management on z/OS . 186 5.4. z/OS Workload Management Basics . 187 5.4.1. Work Classification . 187 5.4.2. Service Class Goals . 190 5.4.3. Response Time Goals . 191 5.4.4. Execution Velocity Goals . 193 5.4.5. Managing Work in z/OS . 195 5.4.6. WLM Transaction Management . 196 5.4.7. Enclaves . 197 5.4.8. Managing CICS and IMS Transactions . 199 5.4.9. Service Definition . 201 5.4.10. Service Unit . 202 5.4.11. Goal Achievement . 203 Contents v 5.5. z/OS Workload Manager Algorithms . 204 5.5.1. Data Sampling . 205 5.5.2. Histories . 207 5.5.3. Data Plots . 209 5.5.4. Policy Adjustment . 210 5.5.5. Policy Adjustment Example: Fix MPL Delay . 213 5.5.6. Projecting a Change for Accessing a Resource . 215 5.5.7. Receiver Value Assessment . 216 5.5.8. Net Value Assessment . 217 5.5.9. Policy Adjustment Example: Fix CPU Delay . 218 5.5.10. Policy Adjustment Example: Time-line for Changes . 221 5.5.11. Test Scenario versus Real Environment . 224 5.5.12. Resource Adjustment . 226.
Load more

Recommended publications
  • Cloud Enabling CICS
    Front cover Cloud Enabling IBM CICS Discover how to quickly cloud enable a traditional IBM 3270-COBOL-VSAM application Use CICS Explorer to develop and deploy a multi-versioned application Understand the benefits of threshold policy Rufus Credle Isabel Arnold Andrew Bates Michael Baylis Pradeep Gohil Christopher Hodgins Daniel Millwood Ian J Mitchell Catherine Moxey Geoffrey Pirie Inderpal Singh Stewart Smith Matthew Webster ibm.com/redbooks International Technical Support Organization Cloud Enabling IBM CICS December 2014 SG24-8114-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2014) This edition applies to CICS Transaction Server for z/OS version 5.1, 3270-COBOL-VSAM application. © Copyright International Business Machines Corporation 2014. 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 . vii Trademarks . viii IBM Redbooks promotions . ix Preface . xi Authors. xii Now you can become a published author, too! . .xv Comments welcome. .xv Stay connected to IBM Redbooks . xvi Part 1. Introduction . 1 Chapter 1. Cloud enabling your CICS TS applications . 3 1.1 Did you know?. 4 1.2 Business value . 4 1.3 Solution overview . 5 1.4 Cloud computing in a CICS TS context. 6 1.5 Overview of the cloud-enabling technologies in CICS TS V5 . 11 1.5.1 Platform overview . 12 1.5.2 Application overview . 13 Chapter 2. GENAPP introduction. 15 2.1 CICS TS topology . 16 2.2 Application architecture. 17 2.2.1 GENAPP in a single managed region.
    [Show full text]
  • MVS Planning: Workload Management
    z/OS Version 2 Release 3 MVS Planning: Workload Management IBM SC34-2662-30 Note Before using this information and the product it supports, read the information in “Notices” on page 235. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-06-24 © Copyright International Business Machines Corporation 1994, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................. xi Tables..................................................................................................................xv About this information....................................................................................... xvii Who should use this information..............................................................................................................xvii Where to find more information............................................................................................................... xvii Other referenced documents.................................................................................................................. xviii Information updates on the web...............................................................................................................xix How to send your comments to IBM.....................................................................xxi
    [Show full text]
  • Bull SAS: Novascale B260 (Intel Xeon Processor 5110,1.60Ghz)
    SPEC CINT2006 Result spec Copyright 2006-2014 Standard Performance Evaluation Corporation Bull SAS SPECint2006 = 10.2 NovaScale B260 (Intel Xeon processor 5110,1.60GHz) SPECint_base2006 = 9.84 CPU2006 license: 20 Test date: Dec-2006 Test sponsor: Bull SAS Hardware Availability: Dec-2006 Tested by: Bull SAS Software Availability: Dec-2006 0 1.00 2.00 3.00 4.00 5.00 6.00 7.00 8.00 9.00 10.0 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0 12.7 400.perlbench 11.6 8.64 401.bzip2 8.41 6.59 403.gcc 6.38 11.9 429.mcf 12.7 12.0 445.gobmk 10.6 6.90 456.hmmer 6.72 10.8 458.sjeng 9.90 11.0 462.libquantum 10.8 17.1 464.h264ref 16.8 9.22 471.omnetpp 8.38 7.84 473.astar 7.83 12.5 483.xalancbmk 12.4 SPECint_base2006 = 9.84 SPECint2006 = 10.2 Hardware Software CPU Name: Intel Xeon 5110 Operating System: Windows Server 2003 Enterprise Edition (32 bits) CPU Characteristics: 1.60 GHz, 4MB L2, 1066MHz bus Service Pack1 CPU MHz: 1600 Compiler: Intel C++ Compiler for IA32 version 9.1 Package ID W_CC_C_9.1.033 Build no 20061103Z FPU: Integrated Microsoft Visual Studio .NET 2003 (lib & linker) CPU(s) enabled: 1 core, 1 chip, 2 cores/chip MicroQuill SmartHeap Library 8.0 (shlW32M.lib) CPU(s) orderable: 1 to 2 chips Auto Parallel: No Primary Cache: 32 KB I + 32 KB D on chip per core File System: NTFS Secondary Cache: 4 MB I+D on chip per chip System State: Default L3 Cache: None Base Pointers: 32-bit Other Cache: None Peak Pointers: 32-bit Memory: 8 GB (2GB DIMMx4, FB-DIMM PC2-5300F ECC CL5) Other Software: None Disk Subsystem: 73 GB SAS, 10000RPM Other Hardware: None
    [Show full text]
  • Comparing Filesystem Performance: Red Hat Enterprise Linux 6 Vs
    COMPARING FILE SYSTEM I/O PERFORMANCE: RED HAT ENTERPRISE LINUX 6 VS. MICROSOFT WINDOWS SERVER 2012 When choosing an operating system platform for your servers, you should know what I/O performance to expect from the operating system and file systems you select. In the Principled Technologies labs, using the IOzone file system benchmark, we compared the I/O performance of two operating systems and file system pairs, Red Hat Enterprise Linux 6 with ext4 and XFS file systems, and Microsoft Windows Server 2012 with NTFS and ReFS file systems. Our testing compared out-of-the-box configurations for each operating system, as well as tuned configurations optimized for better performance, to demonstrate how a few simple adjustments can elevate I/O performance of a file system. We found that file systems available with Red Hat Enterprise Linux 6 delivered better I/O performance than those shipped with Windows Server 2012, in both out-of- the-box and optimized configurations. With I/O performance playing such a critical role in most business applications, selecting the right file system and operating system combination is critical to help you achieve your hardware’s maximum potential. APRIL 2013 A PRINCIPLED TECHNOLOGIES TEST REPORT Commissioned by Red Hat, Inc. About file system and platform configurations While you can use IOzone to gauge disk performance, we concentrated on the file system performance of two operating systems (OSs): Red Hat Enterprise Linux 6, where we examined the ext4 and XFS file systems, and Microsoft Windows Server 2012 Datacenter Edition, where we examined NTFS and ReFS file systems.
    [Show full text]
  • Hypervisors Vs. Lightweight Virtualization: a Performance Comparison
    2015 IEEE International Conference on Cloud Engineering Hypervisors vs. Lightweight Virtualization: a Performance Comparison Roberto Morabito, Jimmy Kjällman, and Miika Komu Ericsson Research, NomadicLab Jorvas, Finland [email protected], [email protected], [email protected] Abstract — Virtualization of operating systems provides a container and alternative solutions. The idea is to quantify the common way to run different services in the cloud. Recently, the level of overhead introduced by these platforms and the lightweight virtualization technologies claim to offer superior existing gap compared to a non-virtualized environment. performance. In this paper, we present a detailed performance The remainder of this paper is structured as follows: in comparison of traditional hypervisor based virtualization and Section II, literature review and a brief description of all the new lightweight solutions. In our measurements, we use several technologies and platforms evaluated is provided. The benchmarks tools in order to understand the strengths, methodology used to realize our performance comparison is weaknesses, and anomalies introduced by these different platforms in terms of processing, storage, memory and network. introduced in Section III. The benchmark results are presented Our results show that containers achieve generally better in Section IV. Finally, some concluding remarks and future performance when compared with traditional virtual machines work are provided in Section V. and other recent solutions. Albeit containers offer clearly more dense deployment of virtual machines, the performance II. BACKGROUND AND RELATED WORK difference with other technologies is in many cases relatively small. In this section, we provide an overview of the different technologies included in the performance comparison.
    [Show full text]
  • 13347 CICS Introduction and Overview
    CICS Introduction and Overview Ezriel Gross Circle Software Incorporated August 13th, 2013 (Tue) 4:30pm – 5:30pm Session 13347 Agenda What is CICS and Who Uses It Pseudo Conversational Programming CICS Application Services CICS Connectivity CICS Resource Definitions CICS Supplied Transactions CICS Web Services CICS The Product What is CICS? CICS is an online transaction processing system. Middleware between the operating system and business applications. Manages the user interface. Retrieves and modifies data. Handles the communication. CICS Customers Banks Mortgage Account Reconciliations Payroll Brokerage Houses Stock Trading Trade Clearing Human Resources Insurance Companies Policy Administration Accounts Receivables Claims Processing Batch Versus Online Programs The two ways to process input are batch and online. Batch requests are saved then processed sequentially. After all requests are processed the results are transmitted. Used for order entry processing such as warehouse applications. Online requests are received randomly and processed immediately. Results are transmitted as soon as they are available. Response time tends to be sub-second. Used for applications – such as: Credit Card Authorization. Transaction Processing Requirements Large volume of business transactions to be rapidly and accurately processed Multiple users, single/sysplex or distributed With potentially: – A huge number of users – Simultaneous access to data – A large volume of data residing in multiple database types – Intense security and data integrity controls necessary The access to the data is such that: – Each user has the perception of being the sole user of the system – A set of changes is guaranteed to be logically consistent. If a failure occurs, any intermediate results are undone before the system becomes available again – A completed set of changes is immediately visible to other users A Business Transaction A transaction has a 4-character id.
    [Show full text]
  • DB2 V8 Exploitation of IBM Ziip
    Systems & Technology Group Connecting the Dots: LPARs, HiperDispatch, zIIPs and zAAPs Share in Boston,v August 2010 Glenn Anderson IBM Technical Training [email protected] © 2010 IBM Corporation What I hope to cover...... What are dispatchable units of work on z/OS Understanding Enclave SRBs How WLM manages dispatchable units of work The role of HiperDispatch What makes work eligible for zIIP and zAAP specialty engines Dispatching work to zIIP and zAAP engines z/OS Dispatchable Units There are different types of Dispatchable Units (DU's) in z/OS Preemptible Task (TCB) Non Preemptible Service Request (SRB) Preemptible Enclave Service Request (enclave SRB) Independent Dependent Workdependent z/OS Dispatching Work Enclave Services: A Dispatching Unit Standard dispatching dispatchable units (DUs) are the TCB and the SRB TCB runs at dispatching priority of address space and is pre-emptible SRB runs at supervisory priority and is non-pre-emptible Advanced dispatching units Enclave Anchor for an address space-independent transaction managed by WLM Can comprise multiple DUs (TCBs and Enclave SRBs) executing across multiple address spaces Enclave SRB Created and executed like an ordinary SRB but runs with Enclave dispatching priority and is pre-emptible Enclave Services enable a workload manager to create and control enclaves Enclave Characteristics Created by an address space (the "owner") SYS1 AS1 AS2 AS3 One address space can own many enclaves One enclave can include multiple Enclave dispatchable units (SRBs/tasks) executing concurrently in
    [Show full text]
  • Operating System
    OPERATING SYSTEM INDEX LESSON 1: INTRODUCTION TO OPERATING SYSTEM LESSON 2: FILE SYSTEM – I LESSON 3: FILE SYSTEM – II LESSON 4: CPU SCHEDULING LESSON 5: MEMORY MANAGEMENT – I LESSON 6: MEMORY MANAGEMENT – II LESSON 7: DISK SCHEDULING LESSON 8: PROCESS MANAGEMENT LESSON 9: DEADLOCKS LESSON 10: CASE STUDY OF UNIX LESSON 11: CASE STUDY OF MS-DOS LESSON 12: CASE STUDY OF MS-WINDOWS NT Lesson No. 1 Intro. to Operating System 1 Lesson Number: 1 Writer: Dr. Rakesh Kumar Introduction to Operating System Vetter: Prof. Dharminder Kr. 1.0 OBJECTIVE The objective of this lesson is to make the students familiar with the basics of operating system. After studying this lesson they will be familiar with: 1. What is an operating system? 2. Important functions performed by an operating system. 3. Different types of operating systems. 1. 1 INTRODUCTION Operating system (OS) is a program or set of programs, which acts as an interface between a user of the computer & the computer hardware. The main purpose of an OS is to provide an environment in which we can execute programs. The main goals of the OS are (i) To make the computer system convenient to use, (ii) To make the use of computer hardware in efficient way. Operating System is system software, which may be viewed as collection of software consisting of procedures for operating the computer & providing an environment for execution of programs. It’s an interface between user & computer. So an OS makes everything in the computer to work together smoothly & efficiently. Figure 1: The relationship between application & system software Lesson No.
    [Show full text]
  • System Automation for Z/OS : Planning and Installation About This Publication
    System Automation for z/OS Version 4.Release 1 Planning and Installation IBM SC34-2716-01 Note Before using this information and the product it supports, read the information in Appendix H, “Notices,” on page 201. Edition Notes This edition applies to IBM System Automation for z/OS® (Program Number 5698-SA4) Version 4 Release 1, an IBM licensed program, and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC34-2716-00. © Copyright International Business Machines Corporation 1996, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................. xi Tables................................................................................................................ xiii Accessibility........................................................................................................ xv Using assistive technologies...................................................................................................................... xv Keyboard navigation of the user interface................................................................................................. xv About this publication........................................................................................ xvii Who Should Use This Publication.............................................................................................................xvii
    [Show full text]
  • Brocade Mainframe Connectivity Solutions
    PART 1: BROCADE MAINFRAME CHAPTER 2 CONNECTIVITY SOLUTIONS The modern IBM mainframe, also known as IBM zEnterprise, has a distinguished 50-year history BROCADEMainframe I/O and as the leading platform for reliability, availability, serviceability, and scalability. It has transformed Storage Basics business and delivered innovative, game-changing technology that makes the extraordinary possible, and has improved the way the world works. For over 25 of those years, Brocade, MAINFRAME the leading networking company in the IBM mainframe ecosystem, has provided non-stop The primary purpose of any computing system is to networks for IBM mainframe customers. From parallel channel extension to ESCON, FICON, process data obtained from Input/Output devices. long-distance FCIP connectivity, SNA/IP, and IP connectivity, Brocade has been there with IBM CONNECTIVITY and our mutual customers. Input and Output are terms used to describe the SOLUTIONStransfer of data between devices such as Direct This book, written by leading mainframe industry and technology experts from Brocade, discusses Access Storage Device (DASD) arrays and main mainframe SAN and network technology, best practices, and how to apply this technology in your storage in a mainframe. Input and Output operations mainframe environment. are typically referred to as I/O operations, abbreviated as I/O. The facilities that control I/O operations are collectively referred to as the mainframe’s channel subsystem. This chapter provides a description of the components, functionality, and operations of the channel subsystem, mainframe I/O operations, mainframe storage basics, and the IBM System z FICON qualification process. STEVE GUENDERT DAVE LYTLE FRED SMIT Brocade Bookshelf www.brocade.com/bookshelf i BROCADE MAINFRAME CONNECTIVITY SOLUTIONS STEVE GUENDERT DAVE LYTLE FRED SMIT BROCADE MAINFRAME CONNECTIVITY SOLUTIONS ii © 2014 Brocade Communications Systems, Inc.
    [Show full text]
  • IBM System Z10 Business Class - the Smart Choice for Your Business
    IBM United States Hardware Announcement 108-754, dated October 21, 2008 IBM System z10 Business Class - The smart choice for your business. z can do IT better Table of contents 4 Key prerequisites 36 Publications 4 Planned availability dates 38 Services 5 Description 38 Technical information 35 Product positioning 55 IBM Electronic Services 36 Statement of general direction 55 Terms and conditions 36 Product number 57 Pricing 36 Education support 57 Order now 58 Corrections At a glance The IBM® System z10 BC is a world-class enterprise server built on the inherent strengths of the IBM System z® platform. It is designed to deliver new technologies and virtualization that provide improvements in price/performance for key new workloads. The System z10 BC further extends System z leadership in key capabilities with the delivery of granular growth options, business-class consolidation, improved security and availability to reduce risk, and just-in-time capacity deployment helping to respond to changing business requirements. Whether you want to deploy new applications quickly, grow your business without growing IT costs, or consolidate your infrastructure for reduced complexity, look no further - z Can Do IT. The System z10 BC delivers: • The IBM z10 Enterprise Quad Core processor chip running at 3.5 GHz, designed to help improve CPU intensive workloads. • A single model E10 offering increased granularity and scalability with 130 available capacity settings. • Up to a 5-way general purpose processor and up to 5 additional Specialty Engine processors or up to a 10-way IFL or ICF server for increased levels of performance and scalability to help enable new business growth.
    [Show full text]
  • AN OS/360 MVT TIME-SHARING SUBSYSTEM for DISPLAYS and TELETYPE Lij Gary D
    ,DOCUMENT RESUME ED 082 488 BM 011 457 , _ AUTHOR Schultz, Gary D. 1 TITLE The CHAT System:1)ln OS/360 MVT Time-Sharing Subsystem for Displays and Teletype. Technical Progress Report. INSTITUTION North Carolina Univ., Chapel Hill. Dept. of Computer Science. SPONS AGENCY National Science Foundation, Washington, D.C. REPORT NO UNC-TPR-CAI-6 PUB DATE May 73 NOTE 225p.; Thesis submitted to the Department of Computer Science, University of North Carolina EDRS PRICE MF-$0.65 HC-:-$9.87 DESCRIPTORS Computer Programs; Input Output Devices; *Interaction; *Man Machine Systems;, Masters Theses; Program Descriptions; *Systems DeVelopment; Technical Reports; *Time Sharidg IDENTIFIERS *Chapel Hill Alphanumeric Terminal; CHAT; CRT Display Stations;. OS 360; PI. I; Teletype ABSTRACT The design and operation of a time-sharing monitor are described. It runs under OS/360 MVT that supports multiple application program interaction with operators of CRT (cathode ray tube) display stations and of .a teletype. Key. design features discussed include:1) an interface. allowing application programs to be coded in either PL/I or assembler language; 2) use of the teletype for:subsystem control and diagnostic purposes; and 3)a novel interregional conduit allowing an application program running under the Chapel Hill Alphanumeric Terminal (CHAT)_: monitor to interact--like a terminal operator--with a conversational language processor in another region of the OS/360 installation. (Author) FILMED FROM BEST A7AILABLE COPY University of North Carolina atChapel Hill Department of Computer Science CO -4. CNJ CO THE CHAT SYSTEM: AN OS/360 MVT TIME-SHARING SUBSYSTEM FOR DISPLAYS AND TELETYPE LiJ Gary D.
    [Show full text]