MVS Programming:Extended Addressability Guide

Total Page:16

File Type:pdf, Size:1020Kb

MVS Programming:Extended Addressability Guide z/OS Version 2 Release 3 MVS Programming: Extended Addressability Guide IBM SA23-1394-30 Note Before using this information and the product it supports, read the information in “Notices” on page 233. 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-02-16 © Copyright International Business Machines Corporation 1988, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures....................................................................................................... ix List of Tables........................................................................................................ xi About this document...........................................................................................xiii Who should use this document.................................................................................................................xiii How this document is organized............................................................................................................... xiii How to use this document.........................................................................................................................xiv z/OS information........................................................................................................................................xiv How to send your comments to IBM......................................................................xv If you have a technical problem.................................................................................................................xv Summary of changes...........................................................................................xvi Summary of changes for z/OS Version 2 Release 3..................................................................................xvi Summary of changes for z/OS Version 2 Release 2..................................................................................xvi z/OS Version 2 Release 1 summary of changes.......................................................................................xvii Chapter 1. An introduction to extended addressability............................................1 Basic concepts............................................................................................................................................. 3 Asynchronous cross memory communication...................................................................................... 3 Synchronous cross memory communication........................................................................................ 3 Access register ASC mode......................................................................................................................3 Data-in-Virtual........................................................................................................................................ 4 Virtual lookaside facility......................................................................................................................... 4 Data spaces and hiperspaces.................................................................................................................4 Basic decision: data space or hiperspace................................................................................................... 5 What can a program do with a data space or a hiperspace?.................................................................5 What are the differences?...................................................................................................................... 6 Which one should your program use?....................................................................................................8 Choosing VIO instead of a data space or a hiperspace......................................................................... 9 Chapter 2. Linkage stack......................................................................................11 Linkage stack considerations for asynchronous exit routines..................................................................12 Instructions that add and remove a linkage stack entry.......................................................................... 12 Branch and stack (BAKR) instruction...................................................................................................12 Program return (PR) instruction...........................................................................................................12 Example of using the linkage stack......................................................................................................13 Contents of the linkage stack entry...........................................................................................................14 Instructions that manipulate the contents of a linkage stack entry........................................................ 14 Extract stacked registers (EREG) instruction...................................................................................... 14 Extract stacked state (ESTA) instruction............................................................................................. 15 Modify stacked state (MSTA) instruction............................................................................................. 16 Expanding a linkage stack to a specified size........................................................................................... 16 Relationship between the linkage stack and ESTAE-type recovery routines...........................................17 Dumping the contents of the linkage stack...............................................................................................17 Chapter 3. Synchronous cross memory communication.........................................19 When should you use synchronous cross memory communication?...................................................... 19 Terminology, macros, and assembler instructions................................................................................... 19 Cross memory terminology..................................................................................................................19 Macros used for synchronous cross memory communication........................................................... 21 Instructions used for cross memory communication......................................................................... 22 iii An overview of cross memory communication......................................................................................... 22 PC routines........................................................................................................................................... 22 Summary of cross memory communication........................................................................................25 The cross memory environment................................................................................................................26 Entry tables...........................................................................................................................................26 Linkage tables.......................................................................................................................................26 The PC number..................................................................................................................................... 26 Program authorization — the PSW-key mask (PKM)........................................................................... 27 Address space authorization................................................................................................................27 Considerations before using cross memory..............................................................................................31 Environmental considerations............................................................................................................. 31 Restrictions...........................................................................................................................................31 Requirements....................................................................................................................................... 31 Establishing cross memory communication............................................................................................. 31 Making a PC routine available to all address spaces...........................................................................32 Making a PC routine available to selected address spaces................................................................ 33 Examples of how to establish a cross memory environment...................................................................35 Example 1 - Making services available to selected address spaces.................................................. 36 Example 2 - Making services available to all address spaces............................................................ 43 Example 3 - Providing non-space switch services.............................................................................. 45 PC linkages and PC routine characteristics...............................................................................................45 PC linkage capabilities........................................................................................................................
Recommended publications
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • SAS/ASSIST ® 9.1 the Correct Bibliographic Citation for This Manual Is As Follows: SAS Institute Inc
    Getting Started with SAS/ASSIST ® 9.1 The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. Getting Started with SAS/ASSIST ® 9.1. Cary, NC: SAS Institute Inc. Getting Started with SAS/ASSIST® 9.1 Copyright © 2004, SAS Institute Inc., Cary, NC, USA ISBN 1–59047–205–5 All rights reserved. Produced in the United States of America. 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. 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. 1st printing, January 2004 SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/pubs or call 1-800-727-3228. SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. IBM® and all other International Business Machines Corporation product or service names are registered trademarks or trademarks of International Business Machines Corporation in the USA and other countries.
    [Show full text]
  • NBS FORTRAN Test Programs 3^1 No "I Volume 1- Documentation for Versions 1 and 3 V.I
    j I i Vt NBS SPECIAL PUBLICATION 399 J Volume 1 U.S. DEPARTMENT OF COMMERCE / National Bureau of Standards] National Bureau of Standards Library, £-01 Admin. BIdg. ncT 1 1981 13102^1 NBS FORTRAN Test Prog Volume 1-Documentation for Versions 1 and 3 NATIONAL BUREAU OF STANDARDS The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to promote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, and the Office for Information Programs. THE INSTITUTE FOR BASIC STANDARI>S provides the central basis within the United States of a complete and consistent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essential services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of a Center for Radiation Research, an Office of Meas- urement Services and the following divisions: Applied Mathematics — Electricity — Mechanics
    [Show full text]
  • On the Need of Compilepretation for Legacy Languages
    On the Need of Compilepretation for Legacy Languages Vadim Zaytsev Raincode [email protected] Abstract handle it. The third family of reasons lies somewhere in be- The context of this work is the research and development tween: system elements could have been written in HLASM effort that went into creating a product called Raincode As- for optimisation purposes, to reduce program size, running sembler Compiler (Blagodarov et al. 2016), a reimplemen- time, memory footprint, implement very sophisticated er- tation of the IBM mainframe assembler language retargeted ror recovery strategies, fine-tune memory allocation. On the and replatformed for .NET Framework (ECMA-335 June grand scheme of things this may seem like a detail, but such 2012). The assembler language for IBM System/360 and details are what usually make grand schemes fall apart. In newer mainframes has existed and evolved since 1964 (Abel our case, such considerations demanded high efficiency and 1989; Carrano 1987; GC24-3414-7 1970; GC26-4943-06 productivity of our “compiler”. 2013; Kacmar 1988; McQuillen 1975; McQuillen and Prince Writing a language processor by the book seems to be 1987; O’Kane 2011; SA22-7832-09 2012; SC26-4940-06 straightforward (Grune et al. 2012): you parse the code, you 2013; SC26-4941-06 2013). The current version is called handle contexts and static semantics, you generate some in- High Level Assembler, or HLASM, and is widely accepted termediate representation, optimise it, generate code, opti- among mainframe developers and architects as a “second mise it and finally interpret it or let it be interpreted by the generation programming language”, thus positioning it be- target machine directly.
    [Show full text]
  • YES/MVS: a Continuous Real Time Expert System
    From: AAAI-84 Proceedings. Copyright ©1984, AAAI (www.aaai.org). All rights reserved. YEWMVS: A Continuous Real Time Expert System J.H. Griesmer, S.J. Hong, M. Karnaugh, J.K. Kastner, M.I. Schor Expert Systems Group, Mathematical Science Department R.L. Ennis, D.A. Klein, K.R. Milliken, H.M. VanWoerkom Installation Management Group, Computer Science Department IBM T. J. Watson Research Center Yorktown Heights, NY 10598 ABSTRACT: as they arise. A long training period is required to produce a skilled operator; trained operators, in turn, are often pro- YES/MVS (Yorktown Expert System for MVS opera- moted to systems programmers. The resulting shortage of tors) is a continuous, real time expert system that exerts skilled operators and the increasing complexity of the op- interactive control over an operating system as an aid to erator’s job calls for more powerful installation manage- computer operators. This paper discusses the YES/MVS ment tools. We have chosen the management of a Multiple system, its domain of application, and issues that arise in Virtual Storage (MVS) operating system, the most widely the design and development of an expert system that runs used operating system on large IBM mainframe computers, continuously in real time. as an example of the application of expert systems to problems in computer installation management. I INTRODUCTION B. Use of Expert System Techniques Each installation has a different configuration and dif- ferent local policies for computer operations, both of which Expert systems techniques are beginning to be success- change over time. The software running in a large com- fully applied to real problems in industry, although only a puter installation represents hundreds of man-years of de- handful are reportedly in use so far.
    [Show full text]
  • IBM Power Systems Compiler Strategy
    Software Group Compilation Technology IBM Power Systems Compiler Strategy Roch Archambault IBM Toronto Laboratory [email protected] ASCAC meeting | August 11, 2009 @ 2009 IBM Corporation Software Group Compilation Technology IBM Rational Disclaimer © Copyright IBM Corporation 2008. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service
    [Show full text]
  • IBM XL Fortran Compilers Features
    IBM IBM XL Fortran compilers features December 2018 References in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM program product in this publication is not intended to state or imply that only IBM's program product may be used. Any functionally equivalent program may be used instead. IBM, the IBM logo, ibm.com, AIX, Blue Gene, Blue Gene/L, Blue Gene/P, Blue Gene/Q, POWER, POWER6, POWER7, POWER7+, POWER8, POWER9, Power, PowerPC, Power Architecture, and Power Systems are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. NVIDIA and CUDA are either registered trademarks or trademarks of NVIDIA Corporation in the United States, other countries, or both. © Copyright IBM Corporation 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Chapter 1. Overview The IBM® XL Fortran compilers are full-featured Fortran language compilers available for AIX® and Linux on Power® Systems. IBM XL Fortran supports the latest international programming language standards and industry specifications. More information about
    [Show full text]
  • XL Fortran: Optimization and Programming Guide Linkage Convention for Argument Passing ....267 Minimizing Rounding Errors
    IBM XL Fortran for Blue Gene/Q, V14.1 Optimization and Programming Guide Ve r s i o n 1 4 .1 SC14-7370-00 IBM XL Fortran for Blue Gene/Q, V14.1 Optimization and Programming Guide Ve r s i o n 1 4 .1 SC14-7370-00 Note Before using this information and the product it supports, read the information in “Notices” on page 311. First edition This edition applies to IBM XL Fortran for Blue Gene/Q, V14.1 (Program 5799-AH1) and to all subsequent releases and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product. © Copyright IBM Corporation 1990, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this information ........vii Chapter 3. Advanced optimization Who should read this information.......vii concepts ..............41 How to use this information ........vii Aliasing ...............41 How this information is organized ......vii Inlining................41 Conventions ..............viii Finding the right level of inlining ......42 Related information ...........xii IBM XL Fortran information........xii Chapter 4. Managing code size ....45 Standards and specifications .......xiii Steps for reducing code size .........46 Other IBM information .........xiv Compiler option influences on code size.....46 Technical support ............xiv The -qipa compiler option ........46 How to send your comments ........xiv The -qinline inlining option ........46 The -qhot compiler option ........47 Chapter 1. Optimizing your applications 1 The -qcompact compiler option.......47 Distinguishing between optimization and tuning . 1 Other influences on code size ........47 Steps in the optimization process .......2 High activity areas ...........47 Basic optimization ............2 Computed GOTOs and CASE constructs .
    [Show full text]
  • An Execution Batch Monitor for Processing Student Jobs
    AN EXECUTION BATCH MONITOR FOR PROCESSING STUDENT JOBS By SHARON JOYCE ~LARKE Bachelor of Science Oklahoma State University Stillwater, Oklahoma 1974 Submitted to the Faculty of the Graduate College of the Oklahoma State University in partial fulfillment of the requirements for the Degree of MASTER OF SCIENCE December, 1979 -1~. '9/'1 C!.91 /e Cop.~ AN EXECUTION BATCH MONITOR PROCESSING STUDENT JOBS Thesis Approved: Dean of Graduate College 1042920 ii PREFACE This study deals with the investigation and implementa­ tion of a method of reducing operating system overhead for the short-running student jobs at Oklahoma State University. The method chosen is that of an execution batch monitor which eliminates much of the job overhead in processing these student jobs. Sound operating system principles and techniques are studied and incorporated into the monitor, as it assumes some of the operating system functions for the jobs which it processes. I wish to express deep appreciation to my major adviser, Dr. Donald Fisher, for his guidance and assistance throughout my graduate study. I would also like to thank Dr. John Chandler and Dr. Eugene Bailey for serving on my graduate committee and for their continuing support throughout my college career. Thanks also to Dr. George Hedrick for all his help and guid­ ance. A very special thanks goes to Dr. Verlin Drinen whose technical expertise made this study possible. I wish to thank all my friends in the Computing and Infomation Sci­ ences Department and the University Computer Center for their friendship and encouragement. I am especially indebt- iii ed to John Sherblom who pleasantly and patiently answered all my questions about SCRIPT, the text formatting program used to produce this thesis.
    [Show full text]
  • Fortran 90 Handbook Complete ANSI / ISO Reference
    Fortran 90 Handbook Complete ANSI / ISO Reference Jeanne C. Adams Walter S. Brainerd Jeanne T. Martin Brian T. Smith Jerrold L. Wagener Intertext Publications McGraw-Hill Book Company Library of Congress Catalog Card Number 91-77211 Copyright © 1992 by Jeanne C. Adams, Walter S. Brainerd, Jeanne T. Martin, Brian T. Smith, and Jerrold L. Wagener. All rights reserved. Printed in the United States of America. Except as permitted under the United States Copyright Act of 1976, no part of this book may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system without the prior written permission of the authors and the publisher. 10 9 8 7 6 5 4 3 2 1 ISBN 0-07-000406-4 Intertext Publications/Multiscience Press, Inc. One Lincoln Plaza New York, NY 10023 McGraw-Hill Book Company 1221 Avenue of the Americas New York, NY 10020 Composition by UNICOMP Preface The Fortran 90 Handbook is a definitive and comprehensive guide to Fortran 90 and its use. Fortran 90, the latest standard version of Fortran, has many excellent new features that will assist the programmer in writing efficient, portable, and maintainable programs. The Fortran 90 Handbook is an informal description of Fortran 90, developed to provide not only a readable explanation of features, but also some rationale for the inclusion of features and their use. In addition, “models” give the reader better insight as to why things are done as they are in the language. This handbook is intended for anyone who wants a comprehensive survey of Fortran 90, including those familiar with programming language concepts but unfamiliar with Fortran.
    [Show full text]
  • Systems Software Development
    526 IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. SE-4, NO. 6, NOVEMBER 1978 ASSIST-V: An Environment Simulator for IBM 360 Systems Software Development CHARLES E. HUGHES, MEMBER, IEEE, AND CHARLES P. PFLEEGER Abstract-This paper describes ASSIST-V, a software tool designed their own operating systems without significantly degrading for use in the teaching of operating systems, fie management, and ma- performance for other users ofthe machine. However, VM/370 chine architecture courses. ASSIST-V is a program that provides an en- and are not student oriented. Although this situation vironment for the implementation, testing, and evaluation of systems CP/67 software for the IBM 360 series machines. This capability is achieved is "real-life," we feel it is too harsh for the beginning student by simulating all relevant aspects of the machine's architecture. In of operating systems. particular, ASSIST-V simulates interrupts, I/O channels, and I/O devices, A number of software aids have been developed to provide as well as all IBM 360 machine instructions. In addition, ASSIST-V students the opportunity to write and test operating system provides extensive debugging and statistics-gathering aids. modules. These simulators may be divided into three groups. Index Terms-Educational software, IBM 360/370, interrupt handling, Programs in the first group, exemplified by Donovan [21 I/O channel programming, operating systems, simulation, systems and Hughes and Walker [7] simulate the environment for software. some one or more operating system modules. A user writes the appropriate modules, links these with the simulator, and 1. 0 BJECTIVES executes the resultant program.
    [Show full text]
  • NUMERICAL RECIPES in FORTRAN 90: the Art of PARALLEL Scientific Computing (ISBN 0-521-57439-0) Copyright (C) 1986-1996 by Cambridge University Press
    visit website http://www.nr.com or call 1-800-872-7423 (North America only), or send email to [email protected] (outside North readable files (including this one) to any server computer, is strictly prohibited. To order Numerical Recipes books, diskettes, Permission is granted for internet users to make one paper copy their own personal use. Further reproduction, or any copyin Copyright (C) 1986-1996 by Cambridge University Press. Programs Copyright (C) 1986-1996 by Numerical Recipes Software. Sample page from NUMERICAL RECIPES IN FORTRAN 90: The Art of PARALLEL Scientific Computing (ISBN 0-521-57439-0) Numerical Recipes in Fortran 90 Second Edition Volume 2 of Fortran Numerical Recipes or CDROMs g of machine- America). Sample page from NUMERICAL RECIPES IN FORTRAN 90: The Art of PARALLEL Scientific Computing (ISBN 0-521-57439-0) Copyright (C) 1986-1996 by Cambridge University Press. Programs Copyright (C) 1986-1996 by Numerical Recipes Software. Permission is granted for internet users to make one paper copy for their own personal use. Further reproduction, or any copying of machine- readable files (including this one) to any server computer, is strictly prohibited. To order Numerical Recipes books, diskettes, or CDROMs visit website http://www.nr.com or call 1-800-872-7423 (North America only), or send email to [email protected] (outside North America). Numerical Recipes visit website http://www.nr.com or call 1-800-872-7423 (North America only), or send email to [email protected] (outside North readable files (including this one) to any server computer, is strictly prohibited.
    [Show full text]