DOCSLIB.ORG

Systems OS/VS Message Library: VS2 System Codes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Systems OS/VS Message Library: VS2 System Codes GC38-1008-9 File No. S370-40 OS/VS Message Library: VS2 Systems System Codes Tenth Edition (December 1984) This is a major revision of, and obsoletes, GC38-1008-8. See the Summary of Amendments following the Contents for a summary of the changes made to this manual. Technical changes or additions to the text are indicated by a vertical line to the left of the change. This edition applies to MVS/System Product Version 1 through release 3.4 and to all subsequent releases until otherwise indicated in new editions or Technical Newsletters. Changes are made periodically to the information herein; before using this publication in connection with the operation of IBM systems, consult the IBM System/370 and 4300 Processors Bibliography, GC20-0001, for the editions that are applicable and current. References in this publication 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. Publications are not stocked at the address given below. Requests for 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, Information Development, Department D58, Building 920-2, PO Box 390, Poughkeepsie, New York 12602. IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1982, 1984 Preface This publication lists and describes: determination tables are at the back of the publication. You should perform the actions for • The completion codes issued by the MVS/370 the items listed in the code description before operating system when it uses an ABEND asking your IBM branch office for programming or macro instruction to terminate abnormally a hardware support. task or address space. The sections on system completion codes and wait • The wait state codes placed in the program state codes begin with information useful to those status word (PSW) when the system begins a receiving these codes. Remember to read these wait state. introductions. • Causes of uncoded wait states. The appendix lists the modules that detect and issue system completion codes and wait state codes. • The wait state codes placed in the last four bytes of the PSW when the stand-alone dump program (SADMP) enters a wait state. Who Should Use this Publication • Causes of loops. This publication is needed by operators, system programmers, and applications programmers. The descriptions suggest responses by the operator and, where appropriate, by the programmer. Many Associated Publications descriptions state that an error record is written to the SYS1.LOGREC data set. This error record is Many system completion and wait state codes refer described in OS/VS2 MVS System Programming to messages. See MVS/370 Message Library: Library: SYS1.LOGREC Error Recording, System Messages, Volume 1, GC28-1374, and GC28-0677, and in OS/VS2 System Programming Volume 2, GC28-1375. These volumes give the Library: Debugging Handbook, Volume 1, message text and explanation for many system GC28-1047. messages and list the publications containing all other system messages. The description of most codes ends with a problem determination paragraph, which lists suggested Publications cited in this book or containing actions as items in tables; the problem procedures or concepts mentioned include: Order Number Title GA22-7000 IBM System/370 Principles of Operation GA24-3343 IBM 3203/3211 Printer and 3811 Control Unit Component Descriptions LC28-1371 JES3 System Programming Library: User Modifications and Macros GC26-3792 OS/VS2 System Generation Reference SH35-0060 Print Services Facility Messages SC33-0143 IBM Graphics Access Method/System Product: Messages and Codes GC27-6995 VTAM Macro Language Reference GC28-0674 OS/VS2 MVS System Programming Library: Service Aids Preface iii GC28-1029 OS/VS2 MVS System Programming Library: Initialization and Tuning Guide GC28-0683 OS/VS2 MVS Supervisor Services and Macro Instructions SY28-1133 OS/VS2 System Programming Library: MVS Diagnostic Techniques GC28-1031 Operators Library: OS/VS2 MVS System Commands GC28-1046 OS/VS2 System Programming Library: Supervisor SC30-3152 ACF/TCAM Version 2 Support for IBM Subsystems SH2O-9028 IMS/VS V1 Operators Reference SY26-3823 OS/VS2 Input/ Output Supervisor Logic LYB8-1051 OS/VS2 Data Areas (JES2) LYB8-1055 OS/VS2 Data Areas (JES3) iv OS/VS Message Library: VS2 System Codes Contents System Completion Codes SCC-1 Completion Code Format SCC-1 Abnormal Termination of Subtasks SCC-1 Wait State Codes WSC-1 Uncoded Wait States UWS-1 Stand-Alone Dump Wait State Codes SAD-1 Loops LOP-1 Problem Determination PRB-1 TABLE I PRB-1 TABLE II PRB-3 TABLE III PRB-4 Appendix: Code to Module Tables CMT-1 System Completion Code to Module Table CMT-2 Wait State Code to Module Table CMT-7 Contents v vi OS/VS Message Library: VS2 System Codes Contents Directory System Completion (ABEND) Codes ABEND Wait State Codes WT CDS Uncoded Wait States UNCDED Stand-Alone Dump Wait State Codes SADMP Loops LOOPS Problem Determination PROB Appendix: Code to Module Tables CD/MOD Contents Directory V11 viii OS/VS Message Library: VS2 System Codes Summary of Amendments Summary of Amendments • The seven separate sections listed in the for GC38-1008-9 Contents Directory now have separate paging. as updated December 21, 1984 • The text following each system completion code This revision supports MVS/System Product - JES3 and each wait state code is indented to offset Version Release 1.3.4 program number 5740-XYN. the code number and make them easier to find. Changes to the system completion codes issued by • Dictionary-type headings appear at the top of JES3 include: 1FB, 2FB, 3FB, 4FB, 5FB, 6FB, each page in the system completion codes and 722, 7FB, 8FB, 9FB, AFB, BFB, and CFB. wait state codes sections of the manual. The headings indicate which code or codes are This revision also includes the addition of one new documented on the given page. code: DFB. All of these changes have been made to improve the usability of this manual. Most of the changes were made in response to user requests. If you have any comments or suggestions to further improve this Summary of Amendments manual please feel free to use the form for readers for GC38-1008-8 comments provided at the back of the manual. as updated September 14, 1984 The technical changes and additions in this revision are: Summary of Amendments • New system completion codes 024 and 027 to for GC38-1008-7 support the Print Services. Facility (PSF). as updated December 30, 1983 by TNL GN28-0873 • New system completion codes 0A1, 0A2, 0A3, 0A4, 0A5, 147, 149, 14A, 14B and 247 to This TNL contains: support the Graphics Access Method/System Product. • A new system completion code, 02C, issued to support MVS/System Product - JES2 Version 1 • Service updates. Release 3.4 program number 5740-XYS. In addition to the technical information, the • Service updates. following changes have been made to the format of this manual: • This edition is printed in ten-point type, rather than the smaller eight-point type used in previous editions. Summary of Amendments ix x OS/VS Message Library: VS2 System Codes Introduction The OS/VS Message Library is designed so that you can have Basic Books the messages and codes documentation that fits your specific needs. You no longer have to maintain an enormous manual; Each installation will require at least one copy of VS1 System instead, you can tailor message documentation to meet your Messages or VS2 System Messages. You will receive at the particular needs. See Figure 1 for an overview of how to console or in your output listings, some subset of the customize your OS/VS Message Library. messages in these books, no matter which options have been included in your operating system. All programming personnel, If you are a system programmer or installation manager, you especially operations personnel, will require access to these may want to have all the books in the Message Library in a books; although it may not be necessary for consolidated document. applications-oriented personnel to have their own copies. If you are an operator, you may want to include System Each installation must have at least one copy of VS1 System Messages and System Codes in your Operators Library. Codes or VS2 System Codes, which contains the system If you are an assembler language programmer, you may want completion codes and wait state codes. All programming to have System Messages, System Codes, Linkage Editor and personnel, especially operations personnel, will require access Loader Messages, and the message section from the Assembler to one of these books, although applications-oriented Language Programmers Guide in a consolidated document. personnel may not need to have their own copies. If you are a COBOL programmer, you may want VS1 Utilities Messages or VS2 Utilities Messages added to your COBOL Optional Books programmers guide. Routing and Descriptor Codes contains routing and descriptor In any case, you can select the appropriate books to build a codes for all messages that have these codes. Your Message Library to meet your needs. For a list of the books installations system programmer will need this book, especially containing documentation for OS/VS messages and codes, see if your operating systems have multiple console support Figure 2.
Load more

Recommended publications
  • Brocade Mainframe Connectivity Solutions
    PART 1: BROCADE MAINFRAME CHAPTER 2 CONNECTIVITY SOLUTIONS The modern IBM mainframe, also known as IBM zEnterprise, has a distinguished 50-year history BROCADEMainframe I/O and as the leading platform for reliability, availability, serviceability, and scalability. It has transformed Storage Basics business and delivered innovative, game-changing technology that makes the extraordinary possible, and has improved the way the world works. For over 25 of those years, Brocade, MAINFRAME the leading networking company in the IBM mainframe ecosystem, has provided non-stop The primary purpose of any computing system is to networks for IBM mainframe customers. From parallel channel extension to ESCON, FICON, process data obtained from Input/Output devices. long-distance FCIP connectivity, SNA/IP, and IP connectivity, Brocade has been there with IBM CONNECTIVITY and our mutual customers. Input and Output are terms used to describe the SOLUTIONStransfer of data between devices such as Direct This book, written by leading mainframe industry and technology experts from Brocade, discusses Access Storage Device (DASD) arrays and main mainframe SAN and network technology, best practices, and how to apply this technology in your storage in a mainframe. Input and Output operations mainframe environment. are typically referred to as I/O operations, abbreviated as I/O. The facilities that control I/O operations are collectively referred to as the mainframe’s channel subsystem. This chapter provides a description of the components, functionality, and operations of the channel subsystem, mainframe I/O operations, mainframe storage basics, and the IBM System z FICON qualification process. STEVE GUENDERT DAVE LYTLE FRED SMIT Brocade Bookshelf www.brocade.com/bookshelf i BROCADE MAINFRAME CONNECTIVITY SOLUTIONS STEVE GUENDERT DAVE LYTLE FRED SMIT BROCADE MAINFRAME CONNECTIVITY SOLUTIONS ii © 2014 Brocade Communications Systems, Inc.
    [Show full text]
  • 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]
  • IBM 3380 Direct Access Storage Description and User's Guide, Order No
    GA26-1664-1 File No. 5/370-07, 4300-07 Systems ------- - - ---- ------ ---,------ - - --- Federal Communications Commission (FCC) Statement Warning: This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pGrsuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference. In addition to the FCC statement above, the user of this manual should be aware that the referenced statement applies only to devices used in the United States of America. Second Edition (December 1981) This is a major revision of and obsoletes IBM 3380 Direct Access Storage Description and User's Guide, Order No. GA26-1664-0, and Technical Newsletter TNL GN 26-0362. Technical changes to the original publication are indicated by a vertical line to the left of the changes. Information in th~s publication is subject to change. Before using this publication in connection with the use of IBM equipment, contact the local IBM branch office for revisions. It is possible that this material may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country.
    [Show full text]
  • To Download This Section of the Yearbook
    Arcati Mainframe Yearbook 2019 Compiled by Trevor Eddolls of GlossaryiTech-Ed Glossary of Terminology Definitions of some mainframe-related terms This glossary is intended as an aide memoire for experienced mainframers and a useful reference for those new to the z/OS world. If you would like to suggest any new entries for the next edition, please send them to [email protected] (we will even list you as a contributor!). 3270 Access method IBM’s family of dumb, block-mode synchronous screen IBM-specific jargon for software that moves data and printer terminals, which became the standard for between main storage and I/O devices. terminal/mainframe connectivity. ACF/VTAM 3270 data stream Advanced Communications Function / Virtual Format used by 3270 devices for communication, and Telecommunications Access Method is IBM’s proprietary much used for emulation to make PCs look like dumb telecommunications software. terminals. ACID 5250 This acronym describes the properties of a transaction. Terminal standard for the iSeries/400, System/3x etc. Atomicity refers to a transaction’s changes to the state – either it all happens or nothing happens. Consistency ABARS refers to the state of a transaction. It must not violate Aggregate Backup And Recovery Support. A disaster any of the integrity constraints associated with the state. recovery feature within DFSMShsm for automatically Isolation refers to the transaction not being affected by creating files containing back-ups of critical data. The others. Durability refers to the survival of changes to main use of ABARS is to group all the datasets relating state after a transaction completes.
    [Show full text]
  • Hardware Configuration Definition Planning
    z/OS Version 2 Release 3 Hardware Configuration Definition Planning IBM GA32-0907-30 Note Before using this information and the product it supports, read the information in “Notices” on page 129. 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 1989, 2018. 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 use this document...................................................................................................................xi How to use this document.......................................................................................................................... xi z/OS information..........................................................................................................................................xi How to send your comments to IBM.....................................................................xiii If you have a technical problem................................................................................................................xiii
    [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]
  • MVS JCL User's Guide
    z/OS Version 2 Release 3 MVS JCL User's Guide IBM SA23-1386-30 Note Before using this information and the product it supports, read the information in “Notices” on page 261. 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....................................................................................................... xi List of Tables.......................................................................................................xiii About this document............................................................................................xv Who should use this document..................................................................................................................xv Where to find more information................................................................................................................. xv How to send your comments to IBM.................................................................... xvii If you have a technical problem............................................................................................................... xvii Summary of changes........................................................................................
    [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]
  • Introduction to the New Mainframe: Z/OS Basics Access
    Glossary of terms and abbreviations This glossary defines technical terms and abbreviations used in the z/OS® Basic Skills Information Center. If you do not find the term you are looking for, refer to the IBM® Glossary of Computing Terms, available from: http://www.ibm.com/ibm/terminology. The following cross-references are used in this glossary: Contrast with: This refers to a term that has an opposed or substantively different meaning. See: This refers the reader to (a) a related term, (b) a term that is the expanded form of an abbreviation or acronym, or (c) a synonym or more preferred term. Synonym for: This indicates that the term has the same meaning as a preferred term, which is defined in its proper place in the glossary. Synonymous with: This is a reference from a defined term to all other terms that have the same meaning. Obsolete term for: This indicates that the term should not be used and refers the reader to the preferred term. This glossary includes terms and definitions from American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright 1990 by the American National Standards Institute (ANSI). Copies may be purchased from the American National Standards Institute, 11 West 42nd Street, New York, New York 10036. Definitions are identified by an asterisk (*) that appears between the term and the beginning of the definition; a single definition taken from ANSI is identified by an asterisk after the item number for that definition. © Copyright IBM Corp. 2006. All rights reserved. 1 2 Introduction to the New Mainframe: z/OS Basics access.
    [Show full text]
  • I/O Configuration Using Z/OS HCD and HCM
    Front cover I/O Configuration Using z/OS HCD and HCM Understand the I/O configuration process, concepts, and terminology Use HCD and HCM to define and manage hardware configurations Review configuration examples of IOCP data sets Karan Singh Preben Esbensen Peter Hoyle Mark Pope Jean Sylvester ibm.com/redbooks International Technical Support Organization I/O Configuration Using z/OS HCD and HCM April 2010 SG24-7804-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (April 2010) This edition applies to Version 1, Release 11 of z/OS (product number 5694-A01). © Copyright International Business Machines Corporation 2010. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x Preface . xi The team who wrote this book . xi Now you can become a published author, too! . xiii Comments welcome. xiii Stay connected to IBM Redbooks . xiii Part 1. Concepts . 1 Chapter 1. Introduction. 3 1.1 I/O configuration . 4 1.1.1 Who performs the I/O configuration . 4 1.1.2 I/O configuration flow . 4 1.2 Hardware Configuration Definition (HCD) and benefits. 6 1.3 Hardware Configuration Manager (HCM) and benefits. 7 1.4 I/O configuration: POR, IPL, dynamic reconfiguration . 8 1.4.1 Power-on reset (POR). 9 1.4.2 Initial program load (IPL). 9 1.4.3 Dynamic reconfiguration . 9 1.5 Hardware Management Console and Support Element . 10 Chapter 2.
    [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]