OS ISAM Logic

Total Page:16

File Type:pdf, Size:1020Kb

OS ISAM Logic File Number S360-30 Order Number GY28-6618-5 Program Logic OS ISAM Logic Release 21 Program Number 3605-10-526 This publication describes the program logic of the two indexed sequential access methods: the queued indexed sequential access method (QISAM) and the basic indexed sequential access method (BISAM). It also discusses the relationship of indexed sequential access method routines to other parts of the control program. Sixth Edition (February 1972) This is a major revision of, and makes obsolete, the edition of this manual identified as GY28-6618-4. This edition applies to OS Release 21 and to all subsequent releases until otherwise indicated in new editions or technical newsletters. Changes to the information in this book may be made at any time; before using this publication in connection with the operation of IBM systems, consult the latest 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 property of IBM. © Copyright International Business Machines Corporation 1966, 1968, 1969, 1971, 1972 PREFACE This publication describes the program structure of the two indexed sequential access methods: queued indexed sequential access method (QISAM) and basic indexed sequential access method (BISAM). The manual is divided into seven sections: "Section 1: Introduction" is an overview of indexed sequential access method organization and an overall description of ISAM operations. "Section 2: Method of Operation" comprises four parts: 1. ISAM common open, common close, and validation modules - a discussion of the common processing operations for QISAM scan, QISAM load, and BISAM. 2. Queued Indexed Sequential Access Method, Load Mode - a discussion of the operations and routines unique to creating data sets with QISAM. 3. Queued Indexed Sequential Access Method, Scan Mode - a discussion of the operations and routines involved in retrieving and updating records sequentially using QISAM. 4. Basic Indexed Sequential Access Method - a discussion of the techniques and operations used in the direct storage and retrieval of records in an indexed sequential data set. "Section 3: Program Organization" contains flowcharts of individual ISAM routines. "Section 4: Director" contains a table of ISAM modules, by type, and module selection tables for QISAM load mode, open executors, and close executors. "Section 5: Data Areas" contains descriptions of data management control blocks and work areas used by ISAM. "Section 6: Diagnostic Aids" summarizes appendage, asynchronous, and exception codes set and used by ISAM routines. "Section 7: Appendixes" supplements this manual and program listings with a description of ISAM data set organization (Appendix A) and the ISAM channel programs (Appendix B). Prerequisite Knowledge Before reading this book, you should understand the material presented under "Processing an Indexed Sequential Data Set" in OS Data Management Services Guide, GC26-3746. Recommended Reading The following publications contain information that you may need in conjunction with reading this book: OS DADSM Logie, GY28-6607 OS Data Management Macro Instructions, GC26-3794 iii OS Data Management for System Programmers, GC28-6550 OS I/O Supervisor Logic, GY28-6616 OS MFT Guide, GC27-6939 OS MVT Guide, GC28-6720 OS Open/Close/EO V Logic, GY28-6609 OS Supervisor Services and Macro Instructions, GC28-6646 OS Sytem Control Blocks, GC28-6628 iv CONTENTS iii Preface xiii Summary of Changes for Release 21 1 Section 1: Introduction 1 Open Phase 2 Processing Phase 5 Close Phase 7 Section 2: Method of Operation 9 ISAM Common Open, Common Close, and Validation Modules 9 The ISAM Common Open Executors 12 The Validation Modules 13 Common Close Phase Executors 14 Queued Indexed Sequential Access Method, Load Mode 15 Load Mode Open Phase Operations 15 Initial Load or Reload Open Operations 15 Resume Load Open Operations 16 Full-Track-Index-Write Open Operations 16 The Final Load Mode Open Phase Operations 16 Load Mode Open Phase Organization 17 Initial Load Organization 20 Resume Load Open Organization 22 Full-Track-Index-Write Phase Organization 22 The Final Executors in Load Mode Open Phase Organization 23 Load Mode Processing Phase Operations 24 Put Routine 27 Beginning-of-Buffer Routine 27 End-of-Buffer Routine 28 Full Track-Index-Write 29 Appendages 30 Load Mode Processing Phase Organization 31 Channel Programs 33 Control Blocks and Work Areas 33 Load Mode Close Phase Operations 33 Load Mode Close Phase Organization 35 Queued Indexed Sequential Access Method, Scan Mode 36 Scan Mode Open Phase Operations 37 Scan Mode Open Phase Organization 38 Scan Mode Processing Phase Operations 39 Buffer Control Techniques 42 SETL Routine 43 Get Routine 45 EOB Routine 45 Scheduling Routine 47 PUTX Routine 48 ESETL Routine 49 RELSE Routine 49 Appendages v 51 Scan Mode Processing Phase Organization 51 Processing Routines 51 Scan Mode Channel Programs 52 Scan Mode Control Blocks and Work Areas 52 Scan Mode Close Phase 55 Basic Indexed Sequential Access Method 55 BISAM Open Phase Operations 56 BISAM Open Phase Organization 60 BISAM Processing Phase Operations 61 An Example of BISAM Processing Flow 62 Privileged Macro-time Routines 64 Nonprivileged Macro-time Routines 65 Appendage and Asynchronous Routines 67 Dynamic Buffering Routines 68 Check Routine 71 BISAM Processing Phase Organization 71 BISAM Channel Programs 89 BISAM Control Blocks and Work Areas 91 BISAM Close Phase 93 Section 3: Program Organization 139 Section 4: Directory 141 ISAM Module Identified in Alphameric Sequence 147 Section 5: Data Areas 149 ISAM Control Blocks and Data Areas 149 Data Control Block (DCB) 159 Data Event Control Block (DECB) 160 Data Set Control Block (DSCB) 167 Data Extent Block (DEB) 170 Input/Output Block (lOB) 172 Buffer Control Block (BCB)-BISAM 174 Buffer Control Block (BCB)-QISAM 175 Buffer Control Table (IOBBCT) 179 QISAM Load Mode DCB Work Area 187 QISAM Scan Mode DCB Work Area 193 BISAM DCB Work Area 196 QISAM Track-Index Save Area 198 ISAM DCB Field Area 199 Section 6: Diagnostic Aids 201 Appendage Codes 201 QISAM Scan Mode Appendage Codes 201 BISAM READ and WRITE K Appendage Codes 201 BISAM WRITE KN Appendage Codes 202 Asynchronous Codes 202 BISAM READ and WRITE K Asynchronous Codes 203 BISAM WRITE KN Asynchronous Codes 204 Exception Codes 204 QISAM Exception Codes 205 BISAM Exception Codes vi 207 Section 7: Appendixes 209 Appendix A: ISAM Data Set Organization 209 Introduction 209 Data Set Structure 211 Prime Data Area 211 Index Areas 213 Adding Records to a Data Set 215 Detailed Index Description 222 Appendix B: ISAM Channel Programs 285 Index vii ILLUSTRATIONS Figures 3 Figure 1. SIO Appendage for ISAM RPS 10 Figure 2. ISAM Open Flow of Control 11 Figure 3. RPS Identification Field in the Data Event Block 14 Figure 4. Flow of control through the Close Executors 17 Figure 5. Flow of Control through Load Mode Open Executors 25 Figure 6. Load Mode Put Routine 26 Figure 7. Load Mode BOB Routine 27 Figure 8. Load Mode EOB Routine 28 Figure 9. Load Mode Channel-end Appendage Routine 29 Figure 10. Load Mode Abnormal-end Appendage Routine 30 Figure 11. Load Mode Processing Modules 31 Figure 12. QISAM-Load Mode Channel Program Flow (Fixed-Length Records) 32 Figure 13. QISAM-Load Mode Channel Program Flow (Variable-Length Records) 34 Figure 14. Load Mode Control Blocks and Work Areas 36 Figure 15. The Flow of Control through QISAM Load Mode Close Executors 38 Figure 16. Flow of Control through Scan Mode Open Executors 40 Figure 17. Scan Mode Channel Program/Buffer Queues 40 Figure 18. Buffer Queuing and Movement in Scan Mode 43 Figure 19. Scan Mode SETL Routine 44 Figure 20. Scan Mode GET Routine 46 Figure 21. Scan Mode EOB Routine 47 Figure 22. Scan Mode Scheduling Routine 48 Figure 23. Scan Mode ESETL Routine 51 Figure 24. QISAM Scan Mode Processing Modules 53 Figure 25. Scan Mode Channel Program 54 Figure 26. Scan Mode Control Blocks and Work Areas 56 Figure 27. BISAM Open Executors 59 Figure 28. Flow of Control through BISAM Open Executors 62 Figure 29. Privileged Macro-time Routines 64 Figure 30. Nonprivileged Macro-time Routines 66 Figure 31. BISAM Appendage and Asynchronous Routines 67 Figure 32. Dynamic Buffering Routines 68 Figure 33. BISAM Check Routine 69 Figure 34. BISAM Processing Flow (Not WRITE KN) 70 Figure 35. BISAM Privileged Macro-time Modules 71 Figure 36. BISAM Nonprivileged Macro-time Modules 71 Figure 37. BISAM Asynchronous Modules 72 Figure 38. BISAM Appendage Modules 73 Figure 39. BISAM Channel Program Modules 76 Figure 40. READ K, WRITE K, READ KU Channel Program Flow 77 Figure 41. WRITE KN Channel Program Flow-Index Searching 78 Figure 42. WRITE KN Channel Program Flow-Add to Prime (Fixed-Length Unblocked Records, System Work Area) ix 79 Figure 43. WRITE KN Channel Program Flow-Add to Prime (Fixed-Length Unblocked Records, User Work Area) 80 Figure 44. WRITE KN Channel Program Flow-Add to Prime (Fixed-Length Blocked Records, System Work Area) 81 Figure 45. WRITE KN Channel Program Flow-Add to Prime (Fixed-Length Blocked Records, User Work Area) 82 Figure 46. WRITE KN Channel Program Flow-Add to Prime (Variable- Length Records, System Work Area) 83 Figure 47. WRITE KN Channel Program Flow-Add to End (Fixed-Length Records, System Work Area) 84 Figure 48. WRITE KN Channel Program Flow-Add to End (Fixed-Length Records, User Work Area) 85 Figure 49. WRITE KN Channel Program Flow-Add to End (Variable- Length Records) 86 Figure 50.
Recommended publications
  • 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]
  • EREP User's Guide
    Environmental Record Editing and Printing Program (EREP) Version 3 Release 5 User’s Guide IBM GC35-0151-30 Note Before using this information and the product it supports, read the information in “Notices” on page 87. This edition applies to Version 3 Release 5 of EREP and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-02-16 © Copyright International Business Machines Corporation 1983, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures...................................................................................................... vii List of Tables........................................................................................................ ix About this document.............................................................................................xi Who Should Read This Publication............................................................................................................. xi Organization and Contents..........................................................................................................................xi z/OS information.........................................................................................................................................xii How to send your comments to IBM.....................................................................xiii If you have a technical problem................................................................................................................xiii
    [Show full text]
  • Systems OS/VS2 MVS Overview
    GC28-0984-0 File No. S37o.20 Systems OS/VS2 MVS Overview I i .• i -.-------- ---- .- - ---.---.. _...... - .-.--"'­..-.-.-r- - - _---- -\11 - GC28-0984-0 File No. 5370-20 Systems OS/VS2 MVS Overview 1"0 --- - -----... ---- --- - ----- - --- -------- .~- , .,~ .:." ....... F"1I'St Ectitioa (June, 1978) This edition applies to reJease 3.7 of OS/VS2 MVS, and to aU subsequent releases and modifications until otherwise indicated in new editions or Technical Newsletters. Changes may be made to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM 51*1113'7' BIItUopa,by, GC2()'()()()1. for the editions that are applicable and current. Publications are not stocked at the address given below; 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 reader's comments is provided at the back of this publication. If the form has been removed. comments may be addressed to IBM Corporation, Department DS8. Building 7()6.2, PO Box 390, Poughkeepsie, New York. 12602. Comments become the property of IBM. C Copyright International Business Machines Corporation 1918 Preface This book describes the main features of MVS. It explains each of these features and describes the flow of work through the major parts of the system. It does not, however, describe every feature of the system. The emphasis here is on what MVS does and how it accomplishes its objectives. The book is intended for a general audience, but some knowledge of operating systems is necessary. Chapter 1 is an introduction to the basic features of MVS.
    [Show full text]
  • C28-6537-1 Os
    File No. S360-30 Form C28-6537-1 OS Systems Reference Library IBM System/360 Operating System Data Management This publication contains information concerning the data management facilities of the IBM System/360 Operating system. It provides programmers coding in the assem­ bler language with the information neces­ sary to deSign programs using these facili­ ties. This publication describes the catalog­ ing, space allocation, and data access features of the operating system. Informa­ tion is also included on record and label formats and data organizations. PREFACE This publication, primarily directed to glossary of IBM System/360 Operatinq Sys­ applications programmers coding in the tem: Concepts and Facilities, Form assembler language, is a guide to the data C28-6535. management facilities of the System/360 Operating System. Because it provides detailed information on the facilities It is suggested that the reader be available and how they are used, program­ familiar with the information contained in mers coding in a language other than the the prerequisite publications listed below, assembler language will also find this as well as with the functional and opera­ publication useful. tional characteristics of direct-access devices as described in the recommended ,This is one of a group of publications publication. that describe the organization, functions, and applications of the System/360 Operat­ ing System. Detailed information on and PREREQUISITE PUBLICATIONS coding specifications for the macro­ instructions and the control statements IBM System/360 Operating System: Intro­ described herein may be found in the duction, Form C28-6534 publications IBM System/360 Operating Sys­ tem: control Program Services, Form IBM System/360 Operating System: Con­ C28-6541 and IBM System/360 Operating Sys­ cepts and Facilities, Form C28-6535 tem: Job control Language, Form C28-6539, respectively.
    [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]
  • Symbiotic Computer System Measurement and Evaluation Dana Wayne Zimmerli Iowa State University
    Iowa State University Capstones, Theses and Retrospective Theses and Dissertations Dissertations 1972 Symbiotic computer system measurement and evaluation Dana Wayne Zimmerli Iowa State University Follow this and additional works at: https://lib.dr.iastate.edu/rtd Part of the Computer Sciences Commons Recommended Citation Zimmerli, Dana Wayne, "Symbiotic computer system measurement and evaluation " (1972). Retrospective Theses and Dissertations. 5235. https://lib.dr.iastate.edu/rtd/5235 This Dissertation is brought to you for free and open access by the Iowa State University Capstones, Theses and Dissertations at Iowa State University Digital Repository. It has been accepted for inclusion in Retrospective Theses and Dissertations by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. INFORMATION TO USERS This dissertation was produced from a microfilm copy of the original document. While the most advanced technological means to photograph and reproduce this document have been used, the quality is heavily dependent upon the quality of the original submitted. The following explanation of techniques is provided to help you understand markings or patterns which may appear on this reproduction. 1. The sign or "target" for pages apparently lacking from the document photographed is "Missing Page(s)". If it was possible to obtain the missing page(s) or section, they are spliced into the film along with adjacent pages. This may have necessitated cutting thru an image and duplicating adjacent pages to insure you complete continuity. 2. When an image on the film is obliterated with a large round black mark, it is an indication that the photographer suspected that the copy may have moved during exposure and thus cause a blurred image.
    [Show 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.
    [Show full text]
  • PAMELA: an Interactive Assembler System for the IBM North Carolina
    DOCUMENT RESUME ED 082 490 EM 011 459 AUTHOR Brownlee, Edward H., Jr. TITLE PAMELA: An Interactive Assembler System for the IBM System/360 Computer. INSTITUTION North Carolina Univ., Chapel Hill. Dept. of Computer Science. PUB DATE 70 NOTE 82p.; Thesis submitted to the Department of Computer and Information Science of the University of North Carolina EDRS PRICE MF-$0.65 HC-$3.29 DESCRIPTORS Computer Based Laboratories; *Computer Programs; Computers; *Computer Science Education; Digital Computers; Interaction; *Man Machine Systems; Masters Theses; Program Descriptions; *Programing; Technical Reports IDENTIFIERS CC 30 Communications; CC 30 Terminal; CC 300 Screen; CC 303 Keyboard; IBM Model 40; IBM System 360; OS 360 Assembler Language; PAMELA; *Program Assembly Monitor Execution Learn Applicat; Station ABSTRACT A description of the Program Assembly and Monitored Execution for Learning App]'rations (PAMFL7) is presented. It is intended for instructors whc, propose to u.. the system and for programers who wish to modify it. PAMELA an interactiv.a system designed to teach the operating principles of the IBM System/360 digital coLputer at the machine language level. It runs on an IBM 360 Model 40, zommunicating with the user via a remote CC-30 Communications Station. The system can assemble and execute programs written in a subset of OS/360 Assembler Language. The source code can be entered from the CC-30 terminal, or from punched cards previously input. It can be edited by insertion, deletion or alteration of statements and instructions can be executed continuously or singly. Contents can he displayed on the CC-300 screen or modified from the CC-303 keyboard.
    [Show full text]
  • I Data Management for System Programmers
    File No. S360-20 Order No. GC28-6550-10 os Systems Reference Library IBM System/360 Operating System: I Data Management for System Programmers OS Release 21 This publication consists of self-contained chapters, each of which provides information on how to modify, extend, or implement the data I management capabilities of the IBM System/360 Operating System control program. It is designed primarily for system programmers responsible for maintaining, updating, and extending the operating system features. Topics: Catalog and VTOC Maintenance IECDSECT, IEFJFCBN, and IEFUCBOB Macro Instructions The EXCP Macro Instruction The XDAP Macro Instruction Implementing Data Set Protection Adding a UCS Image to the System Library Tenth Edition (March, 1972) This is a major revision of, and obsoletes, GC28-6550-9 and Technical Newsletter GN28-2494. Changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. I This edition applies to release 21 of IBM System/360 Operating system, 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 SRL Newsletter, Order No. GN20-0360, for th€ editions that are current and applicable. Requests for copies of IBM publications should be made to your IBM representative or to the branch office serving your locality. A form for readers' comments is provided at the back of this publication. If the fonn has been removed, comments may be addressed to IBM Corporation, Programming Publications, Department D78, Monterey and Cottle Roads, San Jose, California 95114.
    [Show full text]
  • Introduction Control Blocks Are Used in Z/OS to Manage the Work and Resources of the System. They Are Represented Internally As
    #31 zNibbler (z/OS Control Blocks) zTidBits Series ______________________________________________________________________________________ Introduction Control blocks are used in z/OS to manage the work and resources of the system. They are represented internally as real, virtual and hard storage areas containing specific information pertaining to events, activity and status occurring within the infrastructure’s operation. Control blocks in most situations are usually chain to one another and can span many areas of an operating system’s internal structure. Knowledge of control blocks are useful in finding out vital information about the system and its status when a failing component occurs. What are control blocks Control blocks are mostly segments of storage designated for a particular operating system component providing specific data about an artifact within the z/OS infrastructure. Each control block contains fields and offsets (displacements) that use used by the operating system during its processing. Control blocks are referenced like DSECTs (dummy sections) or copybook members containing multiple pieces of data relevant to the operational characteristics of a particular function. They may appear similar to a record layout although normally contain pointers to other control blocks that are related. Control Blocks are usually abbreviated by the nouns in their name. As an example, a Unit Control Block is used to define an I/O device to the z/OS System and is abbreviated as a UCB which contains almost all of the information necessary for the device to be used to perform I/O requests as well as providing status of the I/O. UCBs are used by tapes and disk devices.
    [Show full text]
  • T9x40 Tape Drive Planning and Migration Guide
    Document MT6004 T9x40 Tape Drive Planning and Migration Guide T9x40 Tape Drive Planning and Migration Guide Information contained in this publication is subject to change without notice. Comments concerning the contents of this publication should be directed to: Technical Information Services Storage Technology Corporation One StorageTek Drive Louisville, CO 80028-2121 USA http://sts.stortek.com/sts/tis StorageTek, the signature, and Information Made Powerful are trademarks of Storage Technology Corporation. Other product names, features, and terms used in this publication are for informational purposes only and might be trademarks of Storage Technology Corporation or of other companies. ©1999, 2002 by Storage Technology Corporation, Louisville, CO, USA. All rights reserved. Printed in the USA. ii MT6004J List of Pages Document Title: T9x40 Tape Drive Planning and Migration Guide Manual Part Number: MT6004 Initial Release Date: February 1999 Ninth Edition Date: August 2002 This publication has 66 pages, consisting of: Pages Cover Blank page Title page Copyright page (ii) iii through xvi 1-1 through 1-12 2-1 through 2-10 3-1 through 3-2 4-1 through 4-4 5-1 through 5-4 A-1 through A-4 Glossary-1 through Glossary-6 Index-1 through Index-2 Reader’s Comment Form Business Reply Mailer Blank Page Back Cover MT6004J iii Summary of Changes Date Edition Change 2/99 A Initial Release 10/99 B Refer to this edition for a description of the changes. 2/00 C Refer to this edition for a description of the changes. 4/00 D Refer to this edition for a description of the changes.
    [Show full text]
  • Datenverwaltung, Ein-/Ausgabe
    Datenverwaltung, Ein-/Ausgabe it-Akademie Bayern z/OS und OS/390 Lehrgang 2008 Prof. Dr.-Ing. Wilhelm G. Spruth Teil 7 Ein-/Ausgabe Verarbeitung EA 0601 ww6 © copyright W. G. Spruth, 08-2004 wgs 10-02 Program I/O Functions The data set organization and processing method are usually described in the program. In addition, some data set information may be specified on the DD statement. OPEN processing merges information from various sources to build a complete data set description. After OPEN processing the program is logically associated with the data set and the program can access the data records. The GET/PUT or READ/WRITE macro instructions are used to request the movement of data between the device and main storage. CLOSE processing breaks the logical connection between the data set and the program. CLOSE processing also does clean-up such as writing end-of-file marks. I/O Request Initiation Wenn das Anwendungsprogramm eine I/O Macro Instruction (GET/PUT oder READ/WRITE) ausführt, verzweigt das Anwendungsprogramm über einen SVC Befehl in die Access Method innerhalb des Kernels. Supervisor Status GET/PUT EXCP STARTI/O SSCH S 1 2 3 4 C U H B Program Access EXCP IOS A S Method Processor N Y N S 8 7 6 5 E T L E M Return Dispatcher Process Interrupt Interruption I/O Services IOS = Input/Output Supervisor Access Method I/O Functions In this example the Queued Sequential Access Method (QSAM) will be invoked by the GET macro. This access method: 1. Provides I/O buffers within the program's address space.
    [Show full text]