DOCSLIB.ORG

Datenverwaltung, Ein-/Ausgabe

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. 2. Builds the channel program which describes the I/O operation to the channel subsystem. As part of the I/O operation, the Access Method: 1. Builds control blocks containing information about the I/O request. 2. Passes control to an I/O driver 3. Issues a WAIT macro to suspend processing of the program's task until the I/O operation is completed. Gepufferte Ein/Ausgabe Im Gegensatz zu READ und WRITE benutzen GET und PUT eine gepufferte Ein/Ausgabe. Die Ein/Ausgabe Puffer werden von der Access Method verwaltet. System CPU Haupt Speicher System Bus Kanal Kanal Kanal 256 Kanäle pro System Control Control Control Unit Unit Unit S/360 E/A Konfiguration Bis zu 65 536 Subchannels pro Channel Subsystem. Jedes E/A Gerät ist, unabhängig von seinem physikalischen Anschluss, logisch über einen „Subchannel“ mit dem Channel Subsystem verbunden. Normalerweise 1 E/A Gerät pro Subchannel. es 0210z ww6 wgs 09-99 SADR Speicheradressregister BCR Bytezählregister (Length Count) DMA (Direct Memory Access) • Aufgaben der DMA-Steuerung: • Adressieren des Haupts.peichers durch Adreßfortschaltung • Adressieren der Geräteschnittstelle • Steuerung der Buszugriffe für Lesen oder Schreiben • Zählen der übertragenen Bytes • Rückmelden an CPU Für einen Übertragungsvorgang werden DMA-Steuerung und I/O Controller (adapter card) von der CPU (Channel Subsystem) initialisiert, z.B. Laden der Steuer- und Adressregister. Channel Program The machine instructions that direct the control unit and device are called channel command words (CCW). A series of channel commands make up a channel program. This is a mini machine-language for I/O which can • read/ write between memory and devices • do device- specific control functions • test device/ channel status and loop. Channel command words provide information such as the address of the data area and the number of bytes of data to be transferred. Some examples of channel command words are SEEK, SETSECTOR, SEARCH, READ and WRITE. Access Method Interface to I/O Drivers Wenn die Access Method alle Aufgaben abgearbeitet hat, verzweigt sie zu einer als I/O Driver bezeichneten z/OS Komponente. Der I/O Driver ist die Schnittstelle zwischen der Access Methode und IOS. Driver passes Control to IOS Driver Interface to IOS The EXCP driver fixes the I/O buffers and the channel program in central storage so that they will be available during the time that the channel subsystem is processing the I/O requests (no paging). The EXCP driver translates the addresses in the channel program from virtual to real. The channel subsystem (the hardware) uses real addresses since it must transfer data into and out of real storage locations. IOS Processing IOS is the interface between the system components (software) and the channel subsystem (hardware). IOS checks to see if the requested device (typically a DASD) is active with a previous I/O request. If the device is active, IOS holds the current request on a queue for that device. If the device is available, IOS issues a Start Subchannel (SSCH) instruction to the channel subsystem to start the I/O request. S/360 I/O Verarbeitung Channel Subsystem Processing A path consists of the channel path, a control unit, and the device. There are often multiple channel paths to a single device. The channel subsystem is responsible for selecting the best path for data transfer between the device and main storage. This capability is a powerful performance feature and a major difference between z/OS or an Unix or Windows I/O subsystems. Start Subschannel SSCH A single instruction (SSCH, Start SubCHannel) initiates I/O. Operands are : • subchannel number • ORB (Operation Request Block) address. The ORB includes the channel program address. SAP (Channel Assist Processor) takes over • copies ORB into UCW • places UCW in initiative queue in HSA • finds appropriate channel path • gets channel to execute channel program When I/O is done • status is stored in UCW. • SAP generates an I/ O interrupt. Note: QDIO (I/O for OSA- Express network) bypasses the Channel Subsystem. SSCH ( ORB, Subchannel) CCWs Channel Control Words CCWs are linked lists of instructions initially pointed to by an operation request block (ORB). The ORB is initially given to the Start Subchannel (SSCH) command along with the subchannel number for the I/O subsystem to process while the CPU continues executing normal code. CCWs come in two flavors: Format 0 (24 bit for backward compatibility) and Format 1 (31 bit). They are typically used to issue read and write (and many other instructions) and consist of a length field and an absolute address field. For each I/O typically 1 or 2 interrupts are produced, one for channel end (primary status) when the channel is idle and the second for device end (secondary status). Often both occur concurrently (CEDE interrupt, Channel End Device End). zSeries Ein/Ausgabe Anschluss Hauptspeicher CPU CPU CPU Benutzer Prozesse Ke r n e l SAP SAP 00 ... 00 HSA CH. CH. CH. CH. Kanäle Channel Subsystem CU CU CU CU CU CU CU = Control Unit Plattenspeicher Das Channel Subsystem wird durch mehrere Prozessoren (als System Assist Prozessoren, SAP, bezeichnet) und entsprechenden Code verwirklicht. Die SAPs greifen parallel zu den CPUs auf den Hauptspeicher zu und entlasten diese von Ein-/Ausgabe Aufgaben. Die HSA (Hardware System Area) ist ein Teil des Hauptspeichers. Sie liegt außerhalb des Adressenraums, auf den die CPUs zugreifen können. Das Channel Subsystem besteht aus SAP Prozessoren und Code in der HSA. Es bildet das virtuelle E/A Subsystem, mit dem der Betriebssystem Kernel glaubt zu arbeiten, auf die reale E/A Struktur ab. Es 0370 ww6 wgs 10-04 Channel Subsystem Components The S/390 channel subsystem contains: A special processor unit (PU) called an SAP. An SAP is a S/390 compatible Microprocessor, but executes I/O licensed internal code (LIC) only (no z/OS Kernel code and no user code). An SAP alleviates the CPU involvement during the execution of an I/O operation. It schedules an I/O operation, but is not in charge of the movement between central storage (CS) and the channel. Channels, which are special processors able to communicate with I/O control units and manage the movement of data between central storage and these control units. Being more specific, the channels can: 1. Send channel commands from the processor to a Control Unit 2. Transfer data during read and write operations 3. Receive status at the end of operations 4. Receive sense information from control units An I/O operation starts when a Start Subchannel (SSCH) machine instruction is executed by the Input Output Supervisor (IOS), an OS/390 component, which issues the instruction on behalf of an OS/390 process. It ends when an I/O interrupt is received by the CPU (forcing the execution of IOS code again). Start Subchannel (SSCH) logic The Start Subchannel (SSCH) is a privileged instruction. It is issued by the Input Output Supervisor (IOS), a z/OS component, and used to start an I/O operation. SSCH has two operands: 1. Subchannel number, which is an index to the UCW associated with the I/O device 2. Operation Request Block (ORB) address. The ORB contains information about what do to during the I/O operation; among other fields it contains the channel program address. The SSCH microcode moves the ORB contents into the respective UCW and places the UCW in an specific Hardware System Area (HSA) queue named the initiative queue. After that process completes, the next IOS instruction is executed, allowing the use of the CPU in another task. HSA is a piece of central storage not addressable by z/OS. It is allocated at power-on reset (POR) and contains microcode work areas, and the I/O configuration (UCWs are stored in HSA) used by the channel subsystem. Haupt- CPU speicher 256 Kanäle Kanal Kanal Kanal Kanal Kanal CU CU CU CU CU 256 Devices pro CU CU CU CU CU Kanal max. S/360 E/A Konfiguration 0 7 8 15 16 Bit I/O Address Channel Device Address Address max. 256 Channels und max.
Load more

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]
  • GC26-3875-0 OS/VS2 MVS Data Management Services Guide
    GC26-3875-0 File No. S370-30 Systems OS/VS2 MVS Data Management Services Guide Release 3.7 Includes the Following Selectable Units: Data Management VS2.03.808 3800 Printing Subsystem VS2.03.810 System Security Support 5752-832 PREFACE This book describes all IBM data management except for VSAM (virtual storage access method) and specialized applications such as the time sharing option (TSO), graphics, teleprocessing, optical character readers, optical reader-sorters, and magnetic character readers. These specialized applications are described in separate publications that are listed in IBM System/370 Bibliography,GC20-0001. To learn about VSAM or to write programs that create and process VSAM data sets, refer to: • Planning for Enhanced VSAM Under OS/VS, GC26-3842, which introduces VSAM and describes its concepts and functions. • OS/VS Virtual Storage Access Method (VSAM) Programmer's Guide, GC26-3838, which describes how to create VSAM data sets and code the macro instructions required to process them. • OS/VS2 Access Method Services, GC26-3841, describes the service program commands used to manipulate VSAM data sets. • OS/VS Virtual Storage Access Method (VSAM) Options for Advanced Applications, GC26-3819, which describes-applications not required in the normal use of VSAM. If you know how to write assembler-language programs and use job control statements, you can use this book and OS/VS2 MVS Data Management Macro Instructions, GC26-3873, to write programs that create and process data sets. To use this book you must have basic knowledge of the operating system as contained in OS/VS2 Release 3 Guide, GC28-0770; of assembler language as described in OS/VS—DOS/VS—VM/370 Assembler Language, GC33-4010; and of job control language (JCL) as explained in OS/VS2 JCL, GC28-0692.
    [Show full text]