DOCSLIB.ORG

Channel Subsystem

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Channel Subsystem Datenverwaltung, Ein-/Ausgabe it-Akademie Bayern z/OS und OS/390 Lehrgang 2008 Prof. Dr.-Ing. Wilhelm G. Spruth Teil 8 Adressierung des Ein-/Ausgabe Subsystems EA 0701 ww6 © copyright W. G. Spruth, 08-2004 wgs 10-02 Adressierung im Ein-/Ausgabe Subsystems IBM zSeries Connectivity Handbook International Technical Support Organization, May 2003 SG24-5444-03 f:\grx\redbooks\connect1.pdf Devices System z verwendet den Begriff “Device”, eine Abkürzung für I/O Device. Typische Devices sind • Plattenspeicher (DASD, Disk Drive), • Magnetbänder, • Drucker, • .......... Heute werden fast ausschließlich logische DASDs vom Typ 3390 eingesetzt. Diese werden von einem Enterprise Storage Subsystem (ESS) auf regulären 3 ¼ Zoll Platten emuliert. Devices werden von einem System mit Hilfe eines Device Identifiers adressiert Early system design The DASD (disk drive) marked with an X has address 132, derived as shown below 8 Bit 8 Bit Device Address The disk drive marked with an Y can be addressed as 171, 571, or 671 because it is connected through three channels. By convention the device is known by its lowest address (171), but all three addresses could be used by the operating system to access the disk drive. Multiple paths to a device are useful for performance and for availability. When an application wants to access disk 171, the operating system will first try channel 1. If it is busy (or not available), it will try channel 5, and so forth. Shown is another S/360 system with two channels connected to control units used by the first system. This sharing of I/O devices is common in all mainframe installations. Tape drive Z is address A31 for the first system, but is address 331 for the second system. Current mainframes use a different approach. In the good old S/360 days, a device address such as 583 meant channel 5, control unit 8, device 3 and this was the address of the device. No S/390 machines work this way today, but the old terminology is often used. This terminology is technically incorrect, but is so widely used that you must understand it. If someone tells you to “IPL from address 583” they really mean to IPL from device number 583. For all S/390 machines, the hardware address of a device will be something like chipd 05, CU 3, UA 7. This is similar to the old S/390 addresses; a chpid is a channel, the CU number is a control unit address, and the UA is a unit address (that can normally range up to x’FF’). However, the software never sees this hardware address. The S/390 I/O subsystem, using the IOCDS data, converts the chpid/CU/UA “hardware address” into a device number. The operating system uses the device number to connect to I/O devices. The operating system and applications never see the actual hardware addresses (the chpid, CU, and UA numbers). Historische Entwicklung Parallel-I/O-interface For a channel path of the parallel-I/O-interface type, the device identifier is called a device address (unit address) and consists of an eight-bit value. ESCON-I/O interface For the ESCON-I/O interface, the device identifier consists of a four-bit control-unit address and an eight-bit unit address . FICON-I/O interface For the FICON-I/O interface, the device identifier consists of an eight-bit control-unit-image ID (address) and an eight-bit unit address. The unit address (device address) identifies the particular I/O device (and, on the parallel-I/O- interface, the control unit) associated with a subchannel. E/A Konfigurations-Netzwerk Channel Subsystem Hauptspeicher FF ... FF CPU CPU CPU Benutzer Prozesse Ke r n e l SAP SAP 00 ... 00 HSA CH. CH. CH. CH. Kanäle Channel Subsystem CU CU CU CU CU CU CU = Control Unit Plattenspeicher Das Channel Subsystem wird durch mehrere Prozessoren (als System Assist Prozessoren, SAP, bezeichnet) und entsprechenden Code verwirklicht. Die SAPs greifen parallel zu den CPUs auf den Hauptspeicher zu und entlasten diese von Ein-/Ausgabe Aufgaben. Die HSA (Hardware System Area) ist ein Teil des Hauptspeichers. Sie liegt außerhalb des Adressenraums, auf den die CPUs zugreifen können. Das Channel Subsystem besteht aus SAP Prozessoren und Code in der HSA. Es bildet das virtuelle E/A Subsystem, mit dem der Betriebssystem Kernel glaubt zu arbeiten, auf die reale E/A Struktur ab. Es 0370 ww6 wgs 10-04 Haupt- CPU speicher 256 Kanäle Kanal Kanal Kanal Kanal Kanal CU CU CU CU CU 256 Devices pro CU CU CU CU CU Kanal max. S/390 Device Identifikation 0 7 8 15 16 Bit I/O Address Channel Device Address Address max. 256 Channels und max. 256 Devices pro Channel Heutige Konfiguration Die früheren parallelen Kanäle wurden durch serielle ESCON und FICON Kanäle ergänzt. Letztere werden gemeinsam als „Channel Path“ bezeichnet und durch eine 8 Bit Channel Path ID (CHPID) or physical channel identifiers (PCHIDs) gekennzeichnet. Ein Channel Subsystem kann maximal 256 Channel Path unterstützen. Auf eine Control Unit kann über unterschiedliche Channel Path zugegriffen werden, Heutige Konfiguration (3) Eine Ein/Ausgabe Einheit (Device), z.B. ein Plattenspeicher, wird eines 16 Bit Device Identifiers angesprochen. Für FICON besteht dieser aus einer 8 Bit Control Unit Nr. und einer 8 Bit Device Address. Letztere wird auch als Unit Address bezeichnet. 0 7 8 15 16 Bit Device Identifier Control Device Unit Nr. Address Auszug aus z/Architecture Principles of Operation (1) One subchannel is provided for and dedicated to each I/O device accessible to the channel sub- system. Up to 256 I/O devices can be addressed on a single parallel-I/O interface. Up to 256 devices can be attached to each control unit that uses the serial-I/O interface The channel subsystem provides information about associated I/O devices to CPUs, which obtain this information by executing I/O instructions. The actual number of subchannels provided depends on the model and the configuration; the maximum addressability is 65,536. The maximum addressability of channel paths provided by a channel subsystem is 256. Auszug aus z/Architecture Principles of Operation (2) A device identifier is an address, not apparent to the program, that is used by the channel subsystem to communicate with I/O devices. The type of device identifier used depends on the specific channel-path type and the protocols provided. Each subchannel contains one or more device identifiers. For the FICON-I/O inter-face, the device identifier consists of an eight-bit control-unit-image ID and an eight-bit device address. Identifikation von Fritz Müller Normalerweise: Fritz Müller geb. 21. Juni 1985 Geburtsort Augsburg Vater Staat benutzt statt dessen für die deutsche Rentenversicherung eine Nummer, z.B.: 970 63210685S048 11 die Fritz Müller eindeutig identifiziert. Identifikation von Fritz Müller System z Devices Normalerweise: Fritz Müller geb. 21. Juni 1985 Device Nr. Geburtsort Augsburg Vater Staat benutzt statt dessen für die deutsche Rentenversicherung eine Nummer, z.B.: 970 63210685S048 11 Device Identifier die Fritz Müller eindeutig identifiziert. Heutige Konfiguration (1) 4 Begriffe: Channel Path ID (CHPID) 8 Bit Subchannel Number 16 Bit Device Nr. (1 pro Subchannel) 16 Bit Device Identifier 16 Bit Der Device Identifier besteht aus einer 8 Bit Control Unit Address und einer 8 Bit Device Address. Die 8 Bit Device Address wird häufig auch als Unit Address bezeichnet und ist nicht zu verwechseln mit der 16 Bit Device Nr. Subchannel A subchannel provides the logical appearance of a device to the program and contains the information required for sustaining a single I/O operation. The subchannel consists of internal storage (UCW) that contains information in the form of a • CCW address, • channel-path identifier, • device number, as well as additional Information like count, status indications, and I/O-interruption sub-class code, path availability and functions pending or being performed. I/O operations are initiated with a device by exe- cuting I/O instructions that designate the subchannel associated with the device. Subchannel Number A subchannel number is a system-unique 16-bit value used to address a subchannel. The subchannel is addressed by eight I/O instructions: • CANCEL SUBCHANNEL, • CLEAR SUBCHANNEL, • HALT SUBCHANNEL, • MODIFY SUBCHANNEL, • RESUME SUBCHANNEL, • START SUBCHANNEL, • STORE SUBCHANNEL, and • TEST SUBCHANNEL. Each I/O device accessible to the channel subsystem is assigned a dedicated subchannel at installation time. All I/O functions relative to a specific I/O device are specified by the program by designating the subchannel assigned to the I/O device. Normally, subchannel numbers are only used in communication between the CPU program and the channel subsystem. START SUBCHANNEL Machine Instruction When START SUBCHANNEL is executed, parameters are passed to the target subchannel requesting that the channel subsystem perform a start function with the I/O device associated with the subchannel. The channel subsystem performs the start function by using information at the sub- channel, including the information passed during the execution of the START SUBCHANNEL instruction, to find an accessible channel path to the device. Once the device has been selected, execution of an I/O operation is accomplished by the decoding and executing of a CCW by the channel subsystem and the I/O device. Am operation-request block (ORB) is designated by a START SUBCHANNEL instruction. Subchannel Number • Device identification used for communication between z/OS and channel subsystem • 16 Bit, 65 536 possible devices • Index for the UCW table (Unit Control Word table) within the HSA. • Used by microcode during execution of the SSCH (Start Subchannel) machine instruction • Stored in the UCB at IPL time • Independent of device number • Used for communication between I/O Supervisor and Channel Subsystem (CSS) UCW Table UCW Subchannel Number Each device is identified to • humans by a 16- bit device number • the Channel Subsystem by a 16- bit subchannel number Subchannel Number A subchannel number is a system-unique 16-bit value used to address a subchannel.
Load more

Recommended publications
  • IBM System/360 Operating System Sequential Access Methods Program Logic Manual
    Y28-6604-1 Program Logic IBM System/360 Operating System Sequential Access Methods Program Number 3S0S-DM-50B This publication describes the internal logic of the routines of the queued sequen­ tial access method, the basic sequential access method, and the basic partitioned access method of IBM System/360 Operating System. Program Logic Manuals are intended for use by IBM customer engineers involved in program maintenance, and by system pro­ grammers involved in altering the program design. Program logic information is not necessary for program operation and use; therefore, distribution of this manual is limited to persons with program maintenance or modification responsibilities. Restricted Distribution PREFACE This publication describes the sequen­ • Buffer pool management routines that tial access method facilities in IBM Oper­ furnish buffer space in main storage. ating System/360. It describes routines in five categories: PREREQUISITE PUBLICATIONS • Queued sequential access method rou­ tines that cause storage and retrieval Knowledge of the information in the of data records arranged in sequential following publications is required for an order .• understanding of this publication: • Basic sequential access method routines IBM system/360 Operating System: Data that cause storage and retrieval of Management, Form C28-6537 data blocks arranged in sequential order. IB,M Systerol360 Operating System: Intro­ duction to Control Program Logic. Pro­ • Basic partitioned access method rou­ gram Logic Manual, Form Y28-6605 tines that cause storage and retrieval of data blocks in a member of a parti­ tioned data set, and construct entries and search for entries in the directory RECOMMENDED READING of a partitioned data set. The publication IBM System/360 Operating • Executors that operate with System: Control Program SerVices, Form input/output supp~rt routines.
    [Show full text]
  • PKZIP MVS User's Guide
    PKZIP for MVS MVS/ESA, OS/390, & z/OS User’s Guide PKMU-V5R5000 PKWARE, Inc. PKWARE, Inc. 9009 Springboro Pike Miamisburg, Ohio 45342 Sales: 937-847-2374 Support: 937-847-2687 Fax: 937-847-2375 Web Site: http://www.pkzip.com Sales - E-Mail: [email protected] Support - http://www.pkzip.com/support 5.5 Edition (2003) PKZIP for MVS™, PKZIP for OS/400™, PKZIP for VSE™, PKZIP for UNIX™, and PKZIP for Windows™ are just a few of the many members in the PKZIP® family. PKWARE, Inc. would like to thank all the individuals and companies -- including our customers, resellers, distributors, and technology partners -- who have helped make PKZIP® the industry standard for Trusted ZIP solutions. PKZIP® enables our customers to efficiently and securely transmit and store information across systems of all sizes, ranging from desktops to mainframes. This edition applies to the following PKWARE of Ohio, Inc. licensed program: PKZIP for MVS™ (Version 5, Release 5, 2003) PKZIP(R) is a registered trademark of PKWARE(R) Inc. Other product names mentioned in this manual may be a trademark or registered trademarks of their respective companies and are hereby acknowledged. Any reference to licensed programs or other material, belonging to any company, is not intended to state or imply that such programs or material are available or may be used. The copyright in this work is owned by PKWARE of Ohio, Inc., and the document is issued in confidence for the purpose only for which it is supplied. It must not be reproduced in whole or in part or used for tendering purposes except under an agreement or with the consent in writing of PKWARE of Ohio, Inc., and then only on condition that this notice is included in any such reproduction.
    [Show full text]
  • IBM Mainframe Utility Programs ­ Wikipedia, the Free Encyclopedia IBM Mainframe Utility Programs from Wikipedia, the Free Encyclopedia
    9/11/2015 IBM mainframe utility programs ­ Wikipedia, the free encyclopedia IBM mainframe utility programs From Wikipedia, the free encyclopedia IBM mainframe utility programs are Utility software supplied with IBM mainframe operating systems such as MVS to carry out various tasks associated with datasets, etc. The following list describes utilities distributed with OS/360 and successors. No VSE or VM utilities are included. Contents 1 History/Common JCL 2 Dataset utilities 2.1 IDCAMS 2.2 IEBCOMPR 2.3 IEBCOPY 2.4 IEBDG 2.5 IEBEDIT 2.6 IEBGENER 2.7 IEBIMAGE 2.8 IEBISAM 2.9 IEBPTPCH 2.10 IEBUPDTE 3 Scheduler utilities 3.1 IEFBR14 4 System utilities 4.1 ICKDSF 4.2 IEHDASDR 4.3 IEHINITT 4.4 IEHLIST 4.5 IEHMOVE 4.6 IEHPROGM 5 Supporting programs 5.1 SORT 5.2 Compilers/Linker 5.3 DFSMS 6 References 7 See also 8 External links History/Common JCL Many of these utilities were designed by IBM users, through the group SHARE, and then modified or extended by IBM from versions originally written by a user. https://en.wikipedia.org/wiki/IBM_mainframe_utility_programs 1/14 9/11/2015 IBM mainframe utility programs ­ Wikipedia, the free encyclopedia These utilities are usually invoked via Job Control Language (JCL). They tend to use common JCL DD identifiers for their data sets: DDNAME Usual function input file for the 'commands' for the utility. Often set to DUMMY if the default action is SYSIN desired SYSUT1 input file SYSUT2 output file SYSUT3 work (spill) file for input (SYSUT1) (often not used) SYSUT4 work (spill) file for output (SYSUT2) (often not used) SYSPRINT output file for printed output from the utility SYSOUT output file for messages from the utility SYSUDUMP output file for a system 'dump' if the program fails Dataset utilities IDCAMS IDCAMS ("Access Method Services") generates and modifies Virtual Storage Access Method (VSAM) and Non­VSAM datasets.
    [Show full text]
  • Systems Introduction to OS/VS2 Release 2 First Edition (March, 1973)
    GC28-0661-1 File No. S370-34 Systems Introduction to OS/VS2 Release 2 First Edition (March, 1973) This edition is a reprint of GC28-0661{) incorporating some editorial changes. It does not obsolete GC28-0661-O. This edition applies to Release 2 of OS/VS2 and to all subsequent releases until otherwise indicated in new editions or Technical Newsletters. Changes are continually made to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM System/360 and System/370 Bibliography, Order No. GA22-6822, and the current SRL Newsletter. Order No. GN20-0360, for the editions that are applicable and current. Requests for copies of IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. A form for readers' comments is provided at the back of this pUblication. If the form has been removed, comments may be addressed to IBM Corporation, Publications Development, iJepartment 058, Building 706-2, PO Box 390, Poughkeepsie, N.Y. 12602. Comments and suggestions become the property of IBM. © Copyright International Business Machines Corporation 1973 Preface This publication contains introductory information Design Concepts -- shows sequence of operation and about OS/VS2 Release 2, a system control other highlights of system design. program (SCP) that features virtual storage, System Requirements -- lists the basic hardware multiprogramming, multiprocessing, time sharing, requirements. and job entry subsystems. It is assumed that readers have a basic knowledge of programming Compatibility -- points out the major differences systems such as OS/MVT or OS/VS2 Release 1.
    [Show full text]
  • State of Florida Department of Children and Families Access Florida System Technical Architecture Overview Itn
    STATE OF FLORIDA DEPARTMENT OF CHILDREN AND FAMILIES ACCESS FLORIDA SYSTEM TECHNICAL ARCHITECTURE OVERVIEW ITN# - 03F12GC1 JUNE 1, 2012 STATE OF FLORIDA – DEPARTMENT OF CHILDREN AND FAMILIES June 1, 2012 Table of Contents 1.0 Background and Organization Overview .......................................................................................... 1 1.1 Background ................................................................................................................................... 1 1.2 Program of Service Specific Terms ................................................................................................ 3 1.3 ACCESS Florida IT Organization and Activity Overview................................................................. 6 1.4 Northwood Shared Resource Center ............................................................................................ 7 2.0 Technical Overview ........................................................................................................................... 8 2.1 Application Frameworks ............................................................................................................... 8 2.2 Databases Types ........................................................................................................................... 9 2.3 Data Access Technologies ........................................................................................................... 10 2.4 Data Security ..............................................................................................................................
    [Show full text]
  • VSAM Demystified
    Front cover VSAM Demystified Learn the latest VSAM functions and manage VSAM data Understand, evaluate, and use VSAM properly Learn problem determination and recommendations Mary Lovelace Jose Dovidauskas Alvaro Salla Valeria Sokal ibm.com/redbooks International Technical Support Organization VSAM Demystified March 2013 SG24-6105-02 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Third Edition (March 2013) This edition applies to z/OS Version 1 Release 13 DFSMS (product number 5694-A01). © Copyright International Business Machines Corporation 2001, 2012, 2013. 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 . xi Trademarks . xii Preface . xiii The team who wrote this book . xiii Now you can become a published author, too! . xiv Comments welcome. xiv Stay connected to IBM Redbooks . xiv Summary of changes. xvii March 2013, Third Edition . xvii Chapter 1. VSAM basics . 1 1.1 VSAM functions by release level. 2 1.2 What is VSAM? . 4 1.2.1 What is an access method? . 4 1.2.2 VSAM access types . 4 1.3 VSAM functions. 5 1.3.1 Catalog management . 5 1.3.2 Record management . 5 1.4 VSAM terminology and concepts . 5 1.4.1 Logical record . 5 1.4.2 Physical record . 8 1.4.3 Control interval . 10 1.4.4 Spanned records. 11 1.4.5 Control area . 12 1.4.6 Components . 13 1.4.7 Clusters. 15 1.4.8 Alternate indexes .
    [Show full text]
  • Software Guide the Computer with Growth Potential
    February 1980 Volume 3 Issue 2 NEW: Professional software guide The computer with growth potential The System Three is Cromemco's best selling small business computer. It's easy to see why. Not only is it ideal for the first time computer user. But perhaps more important, it can be expanded into a comprehensive business facility servicing many varied company requirements. Single -user system You can start small. A 64K computer with a megabyte of floppy disc storage costs under £4,000.* Perhaps your initial reason for choosing Cromemco was its flexible database management system-ideal for client records, order processing, sales analysis, inventory control, and many more business uses; or you might have required the full screen word processing system, capable of printing up to 20 original letters an hour; possibly you needed Cobol, Basic or Fortran to develop your own customised packages. Single -user System Three, with 64K memory, 2 discs, terminal and printer. Easy to use Ideal for small businesses. Whatever the reason, you were highly impressed with the ease with which your Will it expand? Multi-user system very first computer application got off the It was then you discovered that the Fortunately, we can readily expand your ground. So you added another. And terminal is the limiting factor, because ofCromemco. Unlike other makers' systems, another. And pretty soon quite a lot of the time taken to input data. If only you all we need to do is add some memory and a company business was running on your could connect a second terminal you ®TU-ART interface, and the multi-user Cromemco.
    [Show full text]
  • 16Th, Las Vegas, Nevada, June 12-17, 1993)
    DOCUMENT RESUME ED 431 280 EC 307 264 AUTHOR Binion, Mary, Ed. TITLE Engineering the ADA from Vision to Reality with Technology (16th, Las Vegas, Nevada, June 12-17, 1993). Volume 13. INSTITUTION RESNA: Association for the Advancement of Rehabilitation Technology, Washington, DC. ISBN ISBN-0-932101-33-X ISSN ISSN-0883-4741 , PUB DATE 1993-06-17 NOTE 583p. PUB TYPE Collected Works Proceedings (021) EDRS PRICE MF03/PC24 Plus Postage. DESCRIPTORS Adults; Appropriate Technology; *Assistive Devic.3s (for Disabled); *Augmentative and Alternative Communication; *Computer Uses in Education; Delivery Systems; *Disabilities; *Educational Technology; Elementary Secondary Education; Employment; Federal Legislation; Gerontology; Learning Disabilities; Mobility Aids; Older Adults; Public Policy; Rehabilitation Programs; Robotics; Severe Disabilities; Special Education; Teacher Education; Transitional Programs; Transportation IDENTIFIERS Americans with Disabilities Act 1990 ABSTRACT This compilation of presentations from RESNA's conference proceedings focused on the progress and potential of assistive and rehabilitation technology for individuals with disabilities and ways that RESNA members could help these ideas to be realized. Papers were presented on the following topics:(1) service delivery and public policy issues; (2) personal transportation;(3) augmentative and alternative communication; (4) droolin:7; (5) quantitative assessment;(6) special education, including computer applications for students with learningdisabilities, wearable computers
    [Show full text]
  • Systems OS/VS Virtual Storage Access Method (VSAM) Planning Guide
    GC26-3799-0 OS/VS Virtual Storage Access Method (VSAM) Systems Planning Guide First Edition (July 1972) This edition applies to release 2 of OS/VS1, to release 1 of OS/VS2, and to all subsequent releases until otherwise indicated in new editions or technical newsletters. Changes may be made to the information in this publication at any time; before using this publication in connection with the operation of IBM systems, consult the System/360 and System/370 Bibliography~ GA22-6822, and the latest System/360 and System/3 70 SRL Newsletter~ GN20-0360, for the editions that are applicable and current. Requests for copies of IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. Forms for readers' comments are provided at the back of this publication. If the forms have been removed, comments may be addressed to IBM Corporation, Programming Publications, Department D78, Monterey and Cottle Roads, San Jose, California 95114. Comments become the property of IBM. © Copyright International Business Machines Corporation 1972 USING THIS PUBLICATION This publication is intended to enable prospective users of VSAM (virtual storage access method), an access method of OS/VS (operating system/virtual storage), to prepare for using VSAM. The intended audience is data-processing managers whose decisions will influence the use of VSAM, system and application programmers who will make detailed preparations, and others seeking an introduction to VSAM. This planning guide has six chapters: "Introducing VSAM" outlines how VSAM meets the requirements of an access method in today's data-processing environment.
    [Show full text]
  • Introduction to the New Mainframe: Z/OS Basics
    Front cover Introduction to the New Mainframe z/OS Basics Basic mainframe concepts, including usage and architecture z/OS fundamentals for students and beginners Mainframe hardware and peripheral devices Mike Ebbers John Kettner Wayne O’Brien Bill Ogden ibm.com/redbooks International Technical Support Organization Introduction to the New Mainframe: z/OS Basics March 2011 SG24-6366-02 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Third Edition (March 2011) © Copyright International Business Machines Corporation 2006, 2009, 2011. 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 . xi Trademarks . xii Preface . xiii How this text is organized . xiv How each chapter is organized . xiv The team who wrote this book . xv Acknowledgements . xvi Now you can become a published author, too! . xix Comments welcome. xix Stay connected to IBM Redbooks . xix Summary of changes . xxi March 2011, Third Edition . xxi August 2009, Second Edition . xxi Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 3 1.1 The new mainframe. 4 1.2 The System/360: A turning point in mainframe history . 4 1.3 An evolving architecture . 5 1.4 Mainframes in our midst . 8 1.5 What is a mainframe . 9 1.6 Who uses mainframe computers. 12 1.7 Factors contributing to mainframe use . 15 1.8 Typical mainframe workloads . 22 1.9 Roles in the mainframe world . 29 1.10 z/OS and other mainframe operating systems .
    [Show full text]
  • Configuration Guide--SAS 9.4 Foundation for Microsoft Windows For
    Configuration Guide for SAS® 9.4 Foundation for Microsoft Windows for x64 Copyright Notice The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2. 0 Guide for SAS® 9.4 Foundation for Microsoft Windows for x64, Cary, NC: SAS Institute Inc. Configuration Guide for SAS® 9.4 Foundation for Microsoft Windows for x64 Copyright © 2020, SAS Institute Inc., Cary, NC, USA All rights reserved. Produced in the United States of America. For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. The scanning, uploading, and distribution of this book via the Internet or any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support of others’ rights is appreciated. U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513. August 2020 SAS® Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential.
    [Show full text]
  • Paper SAS1715-2015 More Data, Less Chatter: Improving Performance on Z/OS Via IBM Zhpf Lewis King and Fred Forst, SAS Institute Inc., Cary, NC
    Paper SAS1715-2015 More Data, Less Chatter: Improving Performance on z/OS via IBM zHPF Lewis King and Fred Forst, SAS Institute Inc., Cary, NC ABSTRACT This paper describes how we reduced elapsed time for the third maintenance release for SAS® 9.4 by as much as 22% by using the High Performance FICON for IBM System z (zHPF) facility to perform I/O for SAS® files on IBM mainframe systems. The paper details the performance improvements, internal testing to quantify improvements, and the customer actions needed to enable zHPF on their system. The benefits of zHPF are discussed within the larger context of other techniques that a customer can use to accelerate processing of SAS files. INTRODUCTION To achieve optimum input/output (I/O) performance, the SAS product on the IBM mainframe operating system z/OS dynamically generates low-level I/O instructions (in the form of channel programs) to process SAS direct access bound libraries. For the types of I/O operations required by SAS processing, the channel programs generated by SAS provide a higher rate of throughput (amount of data per unit of elapsed time) than what is possible with standard IBM DFSMS access methods. In October 2008, IBM introduced High Performance FICON for System z (zHPF), which is a set of I/O architecture improvements that enable higher rates of I/O throughput (IBM 2015a). Over the next several years, zHPF capabilities were extended (IBM 2015a), and in October 2012, IBM announced functionality that enables programs like SAS to execute channel programs that take advantage of the zHPF feature (IBM 2015b).
    [Show full text]