DOCSLIB.ORG

SAS(R) 9.1.3 Companion for Z/OS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SAS(R) 9.1.3 Companion for Z/OS SAS® 9.1.3 Companion for z/OS The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. SAS ® 9.1.3 Companion for z/OS. Cary, NC: SAS Institute Inc. SAS® 9.1.3 Companion for z/OS Copyright © 2004, SAS Institute Inc., Cary, NC, USA ISBN 1-59047-529-1 All rights reserved. Produced in the United States of America. For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227-19 Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513. 1st printing, July 2004 SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/pubs or call 1-800-727-3228. SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies. Contents What’s New vii Overview vii Details vii PART1 Running SAS Software under z/OS 1 Chapter 1 Initializing and Configuring SAS Software 3 Invoking SAS in the z/OS Environment 4 Connecting to SAS under z/OS 6 Customizing Your SAS Session 7 Specifying Physical Files 14 SAS Software Files 15 Transporting SAS Data Sets between Operating Environments 25 Accessing SAS Files in Other Operating Environments 25 Utilizing Input/Output Features 26 Reserved z/OS DDnames 26 Setting Up the Remote Help System 27 Exiting or Terminating Your SAS Session in the z/OS Environment 28 Support for SAS Software 29 Solving Problems under z/OS 31 Chapter 2 Using SAS Data Libraries 35 Introduction 36 SAS Library Engines 36 SAS View Engines 39 Library Implementation Types for Base and Sequential Engines 40 Assigning SAS Data Libraries 53 Chapter 3 Accessing BMDP, SPSS, and OSIRIS Files 67 Introduction to the BMDP, SPSS, and OSIRIS Engines 67 Accessing BMDP Files 68 Accessing SPSS Files 69 Accessing OSIRIS Files 70 Chapter 4 Allocating External Files 73 Introduction to External Files 73 Ways of Allocating External Files 73 Using the FILENAME Statement or Function to Allocate External Files 74 Using the JCL DD Statement to Allocate External Files 76 Using the TSO Allocate Command to Allocate External Files 77 Allocating External Files on Tape 77 Allocating External Files to a Pipe 78 iv Allocating Generation Data Sets 79 Allocating Nonstandard External Files 80 Concatenating External Files 81 Displaying Information about External Files 81 Deallocating External Files 81 Chapter 5 Accessing External Files 83 Referring to External Files 84 How SAS Determines Device Types 85 Writing to External Files 85 Reading from External Files 92 Accessing Nonstandard Files 97 Accessing UNIX System Services Files 100 Writing Your Own I/O Access Methods 107 Accessing SAS Statements from a Program 107 Using the INFILE/FILE User Exit Facility 107 Chapter 6 Directing SAS Log and SAS Procedure Output 109 Types of SAS Output 110 Directing Output to External Files with the PRINTTO Procedure 112 Directing Output to External Files with System Options 113 Directing Output to External Files with the DMPRINT Command 115 Directing Output to External Files with the FILE Command 115 Directing Output to External Files with DD Statements 115 Directing Output to a Printer 116 Directing Output to a Remote Destination 122 Directing Procedure Output: ODS Examples 123 Sending E-Mail from within SAS Software 131 Chapter 7 Universal Printing 147 Introduction to Universal Printing 148 Using Universal Printing in the Windowing Environment 148 Using Universal Printing in a Batch Environment 154 Sample Programs and Summary 160 The SASLIB.HOUSES Data Set 178 PART2 Application Considerations 181 Chapter 8 SAS Interfaces to ISPF and REXX 183 SAS Interface to ISPF 184 SAS Interface to REXX 199 Chapter 9 Data Representation 207 Representation of Numeric Variables 207 Using the LENGTH Statement to Save Storage Space 207 How Character Values Are Stored 208 v Line-Feed Characters and Transferring Data between EBCDIC and ASCII 209 Chapter 10 Optimizing Performance 211 Introduction to Optimizing Performance 212 Collecting Performance Statistics 212 Optimizing I/O 213 Efficient Sorting 218 Some SAS System Options That Can Affect Performance 218 Managing Memory 219 Loading SAS Modules Efficiently 221 Other Considerations for Improving Performance 221 PART3 Host-Specific Features of the SAS Language 223 Chapter 11 Data Set Options under z/OS 225 Data Set Options in the z/OS Environment 225 Summary of SAS Data Set Options in the z/OS Environment 228 Chapter 12 Formats under z/OS 233 Formats in the z/OS Environment 233 Considerations for Using Formats in the z/OS Environment 233 Chapter 13 Functions and CALL Routines under z/OS 245 Functions and CALL Routines under z/OS 245 Chapter 14 Informats under z/OS 277 Informats in the z/OS Environment 277 Considerations for Using Informats under z/OS 277 Chapter 15 Macros under z/OS 287 Macros in the z/OS Environment 287 Automatic Macro Variables 287 Macro Statements 289 Macro Functions 290 Autocall Libraries 290 Stored Compiled Macro Facility 292 Other Host-Specific Aspects of the Macro Facility 293 Additional Sources of Information 293 Chapter 16 Procedures under z/OS 295 Procedures in the z/OS Environment 295 Chapter 17 Statements under z/OS 359 Statements in the z/OS Environment 359 Chapter 18 System Options under z/OS 407 System Options in the z/OS Environment 410 Summary Table of SAS System Options 529 vi Chapter 19 Windows and Commands in z/OS Environments 547 Windows and Commands in the z/OS Environment 548 Using the Graphical Interface 548 Host-Specific Windows in the z/OS Environment 550 Host-Specific Windows of the FORM Subsystem 556 Host-Specific Window Commands 559 SAS System Options That Affect the z/OS Windowing Environment 569 Terminal Support in the z/OS Environment 569 PART4 Appendixes 573 Appendix 1 Using the INFILE/FILE User Exit Facility 575 Introduction 575 Writing a User Exit Module 575 Function Descriptions 579 SAS Service Routines 585 Building Your User Exit Module 587 Activating an INFILE/FILE User Exit 587 Sample Program 588 Appendix 2 Host-System Subgroup Error Messages 599 Introduction 599 Messages from the SASCP Command Processor 599 Messages from the TSO Command Executor 601 Messages from the Internal CALL Command Processor 603 Appendix 3 Recommended Reading 605 Recommended Reading 605 Glossary 607 Index 615 vii What’s New Overview New features in SAS 9.0 (and later) under z/OS include support for the following items: long format names remote help record-level sharing (RLS) for VSAM data sets and extended-format VSAM data sets. Note: This section describes the features of SAS software under z/OS that are new or enhanced since SAS 8.2. z/OS is the successor to the OS/390 operating system. SAS 9.1 (and later) for z/OS is supported on both OS/390 and z/OS operating systems and, throughout this document, any reference to z/OS also applies to OS/390, unless otherwise stated. For important information about new developments for SAS 9.1 (and later) for z/ OS, see support.sas.com. R Details Long Format Names Beginning with version 9.0, SAS supports “Long Format Names” on page 38 up to a maximum length of 32 bytes. Because earlier versions of SAS support format names that are only a maximum length of 8 bytes, you will not be able to use earlier versions of SAS to read SAS 9.0 (and later) data sets that contain long format names. viii What’s New Remote Help The “Setting Up the Remote Help System” on page 27 enables users who access SAS by using a z/OS emulator (or a real 3270) to view SAS documentation with a Web browser on a PC that is running Microsoft Windows. Previously, all documentation was displayed by the itemstore help in the SAS Help window in the z/OS emulator. By displaying this documentation in your Windows Web browser, the browsing capability is improved and the documentation content is more complete. SAS Language Elements The following SAS statements have been enhanced: The NRLS option in the INFILE statement instructs SAS not to attempt to open a VSAM data set in record-level sharing (RLS) mode, even if the data set is defined as RLS eligible. The libref argument in the LIBNAME statement now supports library names that contain underscores (_). The following SAS system options are new: The DLEXCPCOUNT option reports EXCPs (Execute Channel Program calls) to direct access bound libraries. The DLMSGLEVEL option specifies which level of messages to generate for SAS data libraries. The FILESPACE option at initialization specifies how the FILENAME and LIBNAME statements should provide default values when allocating a new z/ OS data set. The new SAS function DSNCATLGD verifies the existence of a file in the z/OS system catalog.
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]
  • 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]