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 3 Data Sets EA 0601 ww6 © copyright W. G. Spruth, 08-2004 wgs 10-02 Volume Ein “Volume” ist eine Standard Sekundärspeicher Einheit, beispielsweise ein Plattenspeicher oder ein Magnetband. Volume Ein “Volume” ist eine Standard Sekundärspeicher Einheit, beispielsweise ein Plattenspeicher oder ein Magnetband. Datei, File, Data Set Eine Ansammlung von logisch aufeinander in Bezug stehenden Daten wird als Datei bezeichnet. Die englischen Bezeichnungen sind file für Unix, Linux und Windows Dateien, sowie data set für konventionelle z/OS Dateien. Neben konventionellen z/OS Data Sets existiert das z/OS Unix System Services (USS) Hierarchical File System (HFS), welches in einem konventionellen z/OS Data Set abgespeichert wird. Names The z/OS disk and data set characteristics differ considerably from UNIX, Linux and Windows systems, and carry their own specialized terminology. The following terms are used to describe various aspects of storage management on System z and z/OS: • Direct Access Storage Device (DASD) is another name for a disk drive. • A disk drive is also known as a disk volume, a disk pack, or a Head-Disk-Assembly (HDA). Another term for physical volume. • A disk drive contains cylinders. • Cylinders contain tracks. • Tracks contain data records and are in most cases in the Count Data or Count Key Data (CKD) format. • Data blocks are the units of recording on disk. Es kann sich bei einer Datei um ein Quellprogramm, eine Makrobibliothek, ein ausführbares Programm, eine lineare Folge von Bits oder um eine Gruppierung von Datensätzen (data records) handeln, die von einem Programm verarbeitet werden. E/A Puffer im Hauptspeicher Bei einem READ Zugriff auf den Plattenspeicher wird eine Gruppe von Bytes aus einer Datei in den Hauptspeicher gelesen. 0 1 n Unix, Linux oder Windows z/OS Im Unterschied zu Unix, Linux oder Windows Files (aber auch dem USS File System) bestehen z/OS Data Sets aus Records. Ein Record (Datensatz) ist eine Gruppe von Bytes und die die fundamentale Dateneinheit, mit der ein Programm arbeitet. Bei einem Lesezugriff auf einen z/OS Data Set READ (Anton, ID ) wird aus der Datei mit dem Namen Anton ein Record mit der Bezeichnung ID in einen Puffer im Hauptspeicher gelesen In einem gegebenen Data Set haben die Records (Datensätze) entweder alle eine unterschiedliche Länge, oder aber alle die gleiche Länge. Anfang der Datei „Anton“ +++++++++++++++++ ////////////////////////////////////// xxxxxxxxxxxxxxxxx Offset Länge 0 1 n j i Eine Unix, Linux oder Windows File besteht aus einer linearen Folge von Bytes mit den Adressen 0 .. n. Bei einem Lesezugriff READ (Anton, i, j ) wird aus der Datei mit dem Namen Anton eine Gruppe von j aufeinanderfolgenden Bytes in einen Puffer im Hauptspeicher gelesen, beginnend mit Byte i . i stellt einen Zeiger in die Datei dar und wird vom Anwendungsprogramm verwaltet. Unix Datei Zugriff Dateien sind in UNIX Dateien strukturlose Zeichenketten (Byte Streams). Deshalb muss ein Unix Anwendungsprogramm den Offset zu den Daten und die Länge definieren, auf die zugegriffen werden soll. Da im UNIX Dateien Byte Streams sind, muss eine Anwendung den Offset zu den Daten und die Länge definieren, auf die zugegriffen werden soll. Bei dem Record-orientierten Zugriff unter z/OS definiert die Anwendung die Nummer des Records, auf den zugegriffen werden soll. Standard-Zugriffsmethoden für die Ein- und Ausgabe sind in das UNIX-System eingebaut und werden von der UNIX-Programmiersprache C/C++ unterstützt. Einige Anwendungen verwenden außerdem noch direkte (raw) Zugriffe auf Dateien. Dies wird in erster Linie von Datenbankanwendungen verwendet. Unter einem Betriebssystem sind unterschiedliche File Systems möglich. Beispiele: Windows • NTFS • FAT32 Linux • ext2fs • ext3fs • ReiserFS z/OS • PDSE • VSAM • HFS Unterschiedliche High Level Formattierung für die einzelnen File Systems. Unter Linux kann eine NTFS Datei gelesen, aber nicht geschrieben werden (Stand 2007). z/OS benötigt eine unterschiedliche High Level Formattierung für die unterschiedlichen Arten von Data Sets. Data Sets konventionell VSAM Partitioned HFS non-VSAM BSAM entry seq. PDS QSAM key seq. PDSE ISAM relative rec. BDAM linear z/OS basic Unix System Services Arten von z/OS Data Sets OS/390 kannte non-VSAM und PDS. VSAM und PDSE kamen später hinzu. Die Einführung von Unix System Services erfordete HFS. Arten von Data Sets sequentiell (SEQUENTIAL) Die Sätze in der Datei sind fortlaufend organisiert. Der Zugriff auf die Datei erfolgt sequentiell in der Reihenfolge wie die Sätze gespeichert sind. indiziert (INDEXED) Die Sätze in der Datei sind mit einem beliebigen Schlüssel gespeichert. Durch eine zusätzlich gespeicherte Indextabelle ist ein direkter Zugriff über diesen Schlüssel möglich. relativ (RELATIVE) - wahlfrei (RANDOM) Die Sätze in der Datei sind fortlaufend nummeriert. Der Zugriff auf die Datei erfolgt direkt über Satznummer. Partitioned Sequentiell: Datensätze werden in der Reihenfolge der Ankunft geschrieben. Datensätze können am Anfang oder am Ende der Datei beginnend verarbeitet werden. Um auf den 5. Datensatz zuzugreifen muss das System die 4 vorhergehenden Datensätze lesen Datensätze können am Ende der Datei hinzugefügt werden. Sie können jedoch nicht zwischen zwei vorhandenen Datensätzen eingefügt werden. Sequentielle Data Sets können auf DASD oder Magnetband gespeichert werden. Sie sind eine Voraussetzung für die Speicherung auf Magnetband oder eine Drucker-Ausgabe, Partitioned (Untergliedert): Eine Gruppe von Datensätzen, sogenannte Member, werden in sequentieller Reihenfolge geschrieben. Jedem Member wird ein Name in einem Verzeichnis (Directory) zugeordnet, welches Teil des Data Sets ist. Jeder Verzeichniseintrag enthält den Namen des Members und seine Anfangsadresse innerhalb des Data Sets. Die Verzeichniseinträge sind alphabetisch geordnet gilt die aufsteigende Reihenfolge (alphanumeric collating sequence); die einzelnen Member können jedoch in jeder beliebigen Reihenfolge gespeichert sein. Eine untergliederte Datei muß sich auf einem DASD befinden, und wird im allgemeinen als Bibliothek bezeichnet. Die folgenden Dateiformen verwenden die untergliederte Organisation: • PDS • PDSE • HFS Partitioned data set extended: In appearance, a Partitioned Data Set Extended (PDSE) is very similar to a partitioned data set. For accessing a partitioned data set directory or member, most PDSE interfaces are indistinguishable from PDS data set interfaces. However, PDSEs have a different internal format, which gives them increased usability. The main advantage of using a PDSE over a PDS is that PDSEs use DASD space much more efficiently. The size of a PDS directory is fixed regardless of the number of members in it, while the size of a PDSE directory is flexible and expands to fit the members stored in it. Also, the system reclaims space automatically whenever a member is deleted or replaced, and returns it to the pool of space available for allocation to other members of the same PDSE. The space can be reused without having to reorganize the data set. Direkt: Datensätze werden in der Reihenfolge in den Datenbestand geschrieben, die das Programm vorgibt. Direkt organisierte Dateien können sich nur auf DASD befinden. Indexsequentiell: Nach dem Laden, befinden sich die Datensätze in Reihenfolge. Verschiedene Indexsätze werden durch die Organisation automatisch erstellt und verwaltet. Diese Organisation wird aufgrund der geringen Leistung nicht mehr empfohlen. Als Alternative wird VSAM empfohlen. VSAM: VSAM (Virtual Storage Access Method) Dateien können über ein Dienstprogramm, IDCAMS, erstellt werden. Wenn SMS aktiv ist, können VSAM Dateien auch mittels JCL erstellt werden. VSAM- Dateien müssen sich auf DASD befinden und können auf vier verschiedene Arten organisiert sein: • ESDS - Ähnlich einer sequentiellen Datei • KSDS - Ähnlich einer indexsequentiellen Datei • RRDS - Ähnlich einer direkt organisierten Datei • LDS - Eine ESDS ohne jegliche Steuerinformationen Type AM JCL-Parameter Description sequential BSAM, QSAM DSORG=PS, Consecutive series of logical records, no directory blocks originally a pile of punched cards in SPACE= partitioned BPAM DSORG=PO, Dataset space consists of two areas: directory blocks - Directory space with TTRs to members. in SPACE= - Member space to hold the data. Program Libraries partitioned Dataset space is formatted into 4K data extended DFSMS DSNTYPE=LIBRARY blocks which can hold directory or member data PDSE HFS DFSMS DSNTYPE=HFS Special dataset type to hold UNIX System PATH=’/usr/lpp/tcpip’ Services file systems Related to PDSEs direct BDAM DSORG=DA Historic way to organize random access to data usinga disk drive’s actuator echanism VTOC keyed VSAM RECORG=KS Data is organized in control areas and control interval which are mapped into virtual storage. Random access is carried out by storage address calculation. Database DL/I N/A A great variety of database formats has IMS DB developed over the years. DB2 Nowadays, relational database managers Oracle dominate this area. Dateiarten, Access Methods Partitioned Data Set Boot Block Block Block Block Block Group1 Group 2 Group 3 Group n Super FS Inode Datenblöcke Block Descriptor Liste Linux ext2fs File System Format Das Linux ext2fs File System besteht aus einer Folge von Datenblöcken, z.B. je 1 KByte groß. Der Boot Block (Boot Sector) beginnt auf Oberfläche 0, Spur 0, Sektor 1, gefolgt von einer Liste von Block Groups. Jede Block Group enthält
Load more

Recommended publications
  • Abcs of IBM Z/OS System Programming Volume 3
    Front cover ABCs of IBM z/OS System Programming Volume 3 Jose Gilberto Biondo Jr. Redbooks International Technical Support Organization ABCs of IBM z/OS System Programming Volume 3 January 2018 SG24-6983-04 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. Fifth Edition (January 2018) This edition applies to version 2 release 3 of IBM z/OS (product number 5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2004, 2018. 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! . xii Comments welcome. xii Stay connected to IBM Redbooks . xiii Chapter 1. DFSMS introduction . 1 1.1 Introduction to DFSMS . 2 1.1.1 DFSMS components. 2 1.2 DFSMSdfp base element . 3 1.2.1 Managing storage . 3 1.3 DFSMSdss optional feature . 5 1.4 DFSMSrmm optional feature. 5 1.4.1 Library management . 5 1.4.2 Shelf management . 6 1.4.3 Volume management . 6 1.4.4 Data set management. 6 1.5 DFSMShsm optional feature . 6 1.5.1 Storage and space management . 6 1.5.2 Tape mount management. 7 1.5.3 Availability management . 7 1.6 DFSMStvs optional feature . 7 1.6.1 VSAM record-level sharing . 7 1.6.2 Recoverable resource management services.
    [Show full text]
  • Implementing IBM Content Manager Ondemand Solutions with Case Studies
    Front cover Implementing IBM Content Manager OnDemand Solutions with Case Studies Product philosophy and history Platform specific implementation guidelines Multiple case studies for various platforms Wei-Dong (Jackie) Zhu Carol Allen Terry Brown James Ilardi Dewey Jackson Hassan A Shazly Edward E Stonesifer Vanessa T Stonesifer ibm.com/redbooks International Technical Support Organization Implementing IBM Content Manager OnDemand Solutions with Case Studies December 2007 SG24-7511-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (December 2007) This edition applies to Version 8 Release 4 of IBM DB2 Content Manager OnDemand for Multiplatforms (program number 5724-J33), Version 7 Release 1 of IBM DB2 Content Manager OnDemand for z/OS and OS/390 (Program Number 5655–H39), Version 5 Release 4 of IBM DB2 Content Manager OnDemand for i5/OS (Product number 5722-RD1). © Copyright International Business Machines Corporation 2007. 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 that wrote this book . xii Become a published author . xiv Comments welcome. xv Part 1. Implementation guidelines. 1 Chapter 1. Introduction to IBM Content Manager OnDemand . 3 1.1 IBM Content Manager OnDemand product philosophy. 4 1.2 Content Management OnDemand history. 5 Chapter 2. IBM Content Manager OnDemand for Multiplatforms implementation guidelines. 11 2.1 Identify project resources . 12 2.2 Content Manager OnDemand server sizing . 13 2.2.1 Architecture and platform . 14 2.2.2 CPUs.
    [Show full text]
  • IBM Content Manager Ondemand Guide
    Front cover IBM Content Manager OnDemand Guide Administration, database structure, and single instance setup Storage management, security, data indexing, conversion, and expiration User exits, retention management, preferred practices, and much more Wei-Dong Zhu Jim Ilardi Deborah Matamoros Trina D Morgans Paula Muir Hassan A Shazly Edward E Stonesifer Vanessa T Stonesifer Sebastian Welter ibm.com/redbooks International Technical Support Organization IBM Content Manager OnDemand Guide October 2013 SG24-6915-03 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. Fourth Edition (October 2013) This edition applies to Version 9, Release 0, IBM Content Manager OnDemand for Multiplatforms (product number 5724-J33), Version 9, Release 0, IBM Content Manager OnDemand for z/OS (product number 5697-CMD), and Version 7, Release 1, IBM Content Manager OnDemand for i™ (product number 5770-RD1). © Copyright International Business Machines Corporation 2003, 2013. 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 . xiii Trademarks . xiv Preface . xv Authors . xv Now you can become a published author, too! . xviii Comments welcome. xix Stay connected to IBM Redbooks publications . xix Summary of changes . xxi September 2013, Third Edition. xxi Part 1. Basic system concepts and design . 1 Chapter 1. Overview and concepts . 3 1.1 Overview of Content Manager OnDemand . 4 1.2 Content Manager OnDemand concepts . 6 1.2.1 Background information of an example company . 6 1.2.2 Reporting and documenting . 7 1.2.3 Application, application group, folder, and cabinet .
    [Show full text]
  • Front Cover Content Manager Ondemand Guide
    Front cover Content Manager OnDemand Guide Administration, database structure, and multiple instances Storage management and performance PDF indexing, ODWEK, Xenos, and user exits Wei-Dong Jackie Zhu Stephanie Kiefer Jefferson Mike Adair Martin Pepper Henry Martens ibm.com/redbooks International Technical Support Organization Content Manager OnDemand Guide February 2003 SG24-6915-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. First Edition (February 2003) This edition applies to Version 7, Release 1, IBM DB2 Content Manager OnDemand for Multiplatforms (product number 5697-G34), Version 7, Release 1, IBM DB2 Content Manager OnDemand for z/OS and OS/390 (product number 5655-H39), and Version 5, Release 2, IBM DB2 Content Manager OnDemand for iSeries ™ (product number 5722-RD1). © Copyright International Business Machines Corporation 2003. 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 Figures . vii Tables . .xi Notices . xiii Trademarks . xiv Preface . xv The team that wrote this redbook. xv Become a published author . xvii Comments welcome. xviii Chapter 1. Overview and concepts . 1 1.1 Overview . 2 1.2 Concepts . 4 1.2.1 OnDemand Web Enablement Kit . 15 Chapter 2. Administration . 17 2.1 Report administration . 18 2.1.1 Storage sets . 19 2.1.2 Application groups. 19 2.1.3 Applications. 26 2.1.4 Folders . 28 2.2 User and group administration . 34 2.2.1 User types, authorities, and functions . 35 2.2.2 Decentralized system administration . 36 2.2.3 Summary.
    [Show full text]
  • IBM Content Manager Ondemand Guide
    Front cover IBM Content Manager OnDemand Guide Wei-Dong Zhu Jim Ilardi Deborah Matamoros Trina D Morgans Paula Muir Hassan A Shazly Edward E Stonesifer Vanessa T Stonesifer Sebastian Welter Redbooks International Technical Support Organization IBM Content Manager OnDemand Guide October 2015 SG24-6915-04 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Fifth Edition (October 2015) This edition applies to IBM Content OnDemand Version 9.5. © Copyright International Business Machines Corporation 2003, 2015. 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 IBM Redbooks promotions . xiii Preface . .xv Authors. .xv Acknowledgment. xvi Now you can become a published author, too! . xviii Comments welcome. xviii Stay connected to IBM Redbooks . xviii Summary of changes. xxi October 2015, Fifth Edition . xxi Part 1. Basic system concepts and design . 1 Chapter 1. Overview and concepts . 3 1.1 Overview of Content Manager OnDemand . 4 1.2 Content Manager OnDemand concepts . 6 1.2.1 Background information of an example company. 6 1.2.2 Reports and documents . 6 1.2.3 Application, application group, folder, and cabinet . 8 1.2.4 Indexing methods . 9 1.3 Content Manager OnDemand server and its components . 10 1.3.1 Library server and object server . 10 1.3.2 Content Manager OnDemand server components . 11 enChoice . 13 Chapter 2. Setting up a Content Manager OnDemand instance. 15 2.1 Introduction . 16 2.2 Architecture and platform .
    [Show full text]
  • Uni Hamburg Zos A5 IBM Z Akronyme
    Abkürzungen ADS Application Data Structure (CICS). AFQ Available Frame Queue (OS/390 Memory Management) AIX Advanced Interactive Executive (the IBM Unix based operating System) AOR Application owning Region (CICS) APF Authorization Program Facility APPC Advanced Program-to Profram Communication (SNA) APPN Application to Application Node (SNA) ARM Automatic Restart Manager (Sysplex) ATM Automatic Teller Machine ATM Asynchronous Tramsfer Mode BCP Base Control Program BCS Basic Catalog Structure BHT Branch History Table BSDS Bootstrap Dataset (DB2) BLI Business Logic Interface (CICS) BM Buffer Manager (DB2) BMS Basic Mapping Support (CICS zeichenorientierte Präsentationslogik) BNN Boundary Network Node (SNA) BOIM Business Object Instance Manager Framework. BP Buffer Pool (Datenbanken) BTS Backup Time Server CB Component Broker CB/390 Component Broker Implementation for OS/390 CCU Cluster Control Unit (z.B. für IBM 3174) CCW Channel Command Word (S/390 Ein-/Ausgabe Architektur) CEC Maschine mit Prozessoren CFCC Coupling Facility Control Code CPC Central Processing Complex CDM Common Data Model CDS Cell Directory Service (DCE) CF Sysplex Coupling Facility CFCC Coupling Facility Control Code CFRM Coupling Facility Resource Manager CICS Customer Information Control System CICSPlex Collection of related CICS Regions CICS TS CICS Transaction Server CIU Customer Initiated Update CKD Count Key Data CO Cast Out (DB2) COBOL Common Business Oriented Language COM Component Object Model (Microsoft) CORBA Common Object Request Broker Architecture COS CORBA
    [Show full text]
  • CICS). AFQ Available Frame Queue (OS/390 Memory Management
    Abkürzungen ADS Application Data Structure (CICS). AFQ Available Frame Queue (OS/390 Memory Management) AIX Advanced Interactive Executive (the IBM Unix based operating System) AOR Application owning Region (CICS) APF Authorization Program Facility APPC Advanced Program-to Profram Communication (SNA) APPN Application to Application Node (SNA) ARM Automatic Restart Manager (Sysplex) ATM Automatic Teller Machine ATM Asynchronous Tramsfer Mode BCP Base Control Program BCS Basic Catalog Structure BHT Branch History Table BSDS Bootstrap Dataset (DB2) BLI Business Logic Interface (CICS) BM Buffer Manager (DB2) BMS Basic Mapping Support (CICS zeichenorientierte Präsentationslogik) BNN Boundary Network Node (SNA) BOIM Business Object Instance Manager Framework. BP Buffer Pool (Datenbanken) BTS Backup Time Server CB Component Broker CB/390 Component Broker Implementation for OS/390 CCU Cluster Control Unit (z.B. für IBM 3174) CCW Channel Command Word (S/390 Ein-/Ausgabe Architektur) CEC Maschine mit Prozessoren CFCC Coupling Facility Control Code CPC Central Processing Complex CDM Common Data Model CDS Cell Directory Service (DCE) CF Sysplex Coupling Facility CFCC Coupling Facility Control Code CFRM Coupling Facility Resource Manager CICS Customer Information Control System CICSPlex Collection of related CICS Regions CICS TS CICS Transaction Server CIU Customer Initiated Update CKD Count Key Data CO Cast Out (DB2) COBOL Common Business Oriented Language COM Component Object Model (Microsoft) CORBA Common Object Request Broker Architecture COS CORBA
    [Show full text]
  • Large-Scale Commercial Computing
    Front cover Introduction to the New Mainframe: Introduction to the New Mainframe: Large-Scale Learn why mainframes process much of the world’s commercial workload Find out why mainframes are so reliable Understand mainframe popularity Mike Ebbers Frank Byrne Pilar Gonzalez Adrados Rodney Martin Jon Veilleux ibm.com/redbooks International Technical Support Organization Introduction to the New Mainframe: Large-Scale Commercial Computing December 2006 SG24-7175-00 Note: Before using this information and the product it supports, read the information in “Notices” on page 237. First Edition (December 2006) © Copyright International Business Machines Corporation 2006. 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 Preface . ix How this text is organized . x How each chapter is organized. x About the authors . x Acknowledgements . .xi Reviewers . xi Chapter 1. The new mainframe . 1 1.1 What is a mainframe? . 2 1.2 An evolving architecture . 3 1.3 Mainframes in our midst . 4 1.4 Who uses mainframe computers?. 5 1.5 Factors contributing to mainframe use . 6 1.5.1 Capacity . 7 1.5.2 Scalability . 7 1.5.3 Integrity and security . 8 1.5.4 Availability . 8 1.5.5 Access to large amounts of data. 9 1.5.6 Systems management . 10 1.5.7 Autonomic capabilities . 10 1.6 Typical mainframe workloads . 10 1.6.1 Batch processing. 11 1.6.2 Online transaction processing. 14 1.7 Summary . 17 1.8 Questions for review . 18 1.9 Topics for further discussion .
    [Show full text]
  • Z/OS V2R2 Security Target
    Security Target for IBM z/OS Version 2 Release 3 Version: 12.10 Status: RELEASE Last Update: 2019-02-25 Classification: Unclassified Security Target for IBM z/OS Version 2 Release 3 Trademarks The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: Advanced Function Presentation AFP BladeCenter DFS DFSORT IBM Infoprint MVS PR/SM Print Services Facility Processor Resource/Systems Manager RACF System z z System VTAM z/Architecture zEnterprise z/OS z/VM zSeries z10 z12 z13 z14 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. IBM Corporation Classification: Unclassified Page 2 of 417 Last update: 2019-02-25 © Copyright IBM Corp. 2004, 2019 Security Target for IBM z/OS Version 2 Release 3 Revision History Revision Author(s) Date Changes to Previous Revision 12.10 Clemens Wittinger 2019-02-25 Public Version. IBM Corporation Classification: Unclassified Page 3 of 417 Last update: 2019-02-25 © Copyright IBM Corp. 2004, 2019 Security Target for IBM z/OS Version 2 Release 3 Table of Contents 1 Introduction ................................................................................................ 13 1.1 Security Target Identification .....................................................................................
    [Show full text]
  • DFSMS Object Access Method Planning, Installation, and Storage Administration Guide for Object Support
    z/OS Version 2 Release 3 DFSMS Object Access Method Planning, Installation, and Storage Administration Guide for Object Support IBM SC23-6866-30 Note Before using this information and the product it supports, read the information in “Notices” on page 597. 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-06-24 © Copyright International Business Machines Corporation 1986, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................. xi Tables..................................................................................................................xv About This Document..........................................................................................xix Required product knowledge.................................................................................................................... xix z/OS information........................................................................................................................................xix How to Read Syntax Diagrams.................................................................................................................. xix How to send your comments to IBM................................................................... xxiii If you
    [Show full text]
  • Z/OS V1R11.0 DFSMS OAM Planning, Installation, and Storage
    z/OS DFSMSObjectAccessMethodPlanning, Installation, and Storage Administration Guide for Tape Libraries SC35-0427-09 z/OS DFSMSObjectAccessMethodPlanning, Installation, and Storage Administration Guide for Tape Libraries SC35-0427-09 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 371. Tenth Edition, March, 2010 This edition applies to Version 1 Release 11 of z/OS (5694-A01), and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC35-0427-08. IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication, or you may address your comments to the following address: International Business Machines Corporation Department 55JA, Mail Station P181 2455 South Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States & Canada): 1+845+432-9405 FAX (Other Countries): Your International Access Code +1+845+432-9405 IBMLink (United States customers only): IBMUSM10(MHVRCFS) Internet e-mail: [email protected] World Wide Web: http://www.ibm.com/servers/eserver/zseries/zos/webqs.html If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: v Title and order number of this document v Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1993, 2010.
    [Show full text]
  • IBM Content Manager Ondemand Best Practices Guide, March 2015
    IBM Content Manager OnDemand Best Practices Guide March 2015 IBM Software Group Enterprise Content Management IBM Content Manager OnDemand Development Team Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: IBM AFP AIX CICS DB2 DFSMS/MVS i5/OS IBM i iSeries Language Environnent MVS Oracle OS/390 OS/400 RACF RMF SQL-Server Tivoli TotalStorage z/OS zSeries Adobe, Portable Document Format (PDF), and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Windows is a trademark of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names might be trademarks or service marks of others. IBM Content Manager OnDemand Best Practices Guide, March 2015. @Copyright International Business Machines Corporation 2012… 2015. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Page 2 of 112 Table of Contents 1 INTRODUCTION ............................................................................................................................................
    [Show full text]