DOCSLIB.ORG

Z/OS Concepts

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Z/OS Concepts Intro to z/OS Steve Warren IBM November 2020 Session 5AO Introduction • This presentation will cover (at the 50,000 foot level) many different areas (but not all) of z/OS • Don’t be overwhelmed. There is a ton of material here. The purpose of this session is to acquaint you with some of the major concepts of z/OS z/OS Concepts #CC 2 Agenda Why Z Matters and Why z/OS z/OS UNIX/ISHELL/OMVS/Remote Hardware/LPAR Address Spaces & Modes z/OS Components Storage & DAT Software Stack Batch Processing/JES/JCL App Dev, App Exec and Mgmt Envs SDSF DASD Job Flow Data Sets / Allocation System Log PDS & PDSE IPL VTOC & Catalogs Sysplex/GDPS SMS Serialization TSO/E Managing Workloads ISPF z/OS Concepts #CC 3 Why Z Matters? 4 Why Z Matters Utilities Retail Government Financial Healthcare Travel Telecoms Automotive Weather z/OS Concepts #CC 5 Why Z Matters Mainframes process 30 billion business transactions per day Mainframes process 1.3 million CICS transactions. Every second. Every day. Mainframes enable $6 trillion in card payments annually 80 percent of the world’s corporate data originates on mainframes 91 percent of CIOs said new customer- facing apps are accessing the mainframe z/OS Concepts #CC 15 Why z/OS? • Ideally suited for processing large workloads for many concurrent users • Highest security ratings for an OS • Highest reliability • Low TCO compared to other enterprise competitors • Designed for: • Serving 1000s of users concurrently • I/O and numeric intensive computing • Processing very large heterogeneous workloads • Running mission critical applications securely z/OS Concepts #CC 16 Naming of OS 17 z/OS Lineage • At the beginning there was: • OS/360 (1966) • Configuration options PCP, MFT and MVT • OS/VS2 R1 (~1972) Since 2001 the name • Retroactively renamed to SVS has remained z/OS • OS/VS2 R2 (~1974) • Also called MVS • MVS/370 (~1977) • MVS/SP V1 • Optionally DFDS and DFEF • MVS/XA (1983) • MVS/SP V2 or V3 and MVS/DFP • MVS/ESA (~1990) • MVS/SP V4 or V5 This is the longest • Either MVS/DFP or DFSMS/MVS that it has been called • OS/390 (1996) one name! • z/OS (2001) z/OS Concepts #CC 18 Hardware Context of z/OS 19 IBM Z Server – the IBM z15 z/OS Concepts #CC 20 IBM Z Server – Multiple LPARs Each LPAR can Up to 85 be allocated LPARs can be different defined amounts of resources (up to 16TB memory) LPAR LPAR LPAR LPAR LPAR LPAR LPAR PR/SM™ CP, Memory, I/O Support Element (SE) z/OS Concepts #CC 21 IBM Z Hardware and z/OS CFCC z/OS® – z/TPF z/OS® z/VSE® ICF Linux on z Systems® Linux on z Systems® Linux on z Systems® Linux on z Systems® z/VM® PR/SM™ z/OS (a.k.a. Multiple VirtualCP, Memory, I/O Storage - MVS)Support Element (SE) Where we will be spending our z/OS Concepts time #CC 22 z/OS Elements, Features, and Components 23 z/OS Concepts – Elements, Features, Components • z/OS is a collection of elements • Each element consists of a collection of modules (called components) Examples: IOS, RSM, GRS, Contents, Allocation, Consoles, NIP, Scheduler, SMF, BCPii, Logger z/OS Concepts #CC 24 z/OS Concepts – Elements, Features, Components • z/OS is a collection of elements • Each element consists of a collection of modules (called components) • Base elements are always included in z/OS • BCP (Base Control Program) • DFSMSdfp (Data Facility Storage Management Subsystem) • Deliver essential operating system functions Other Base Elements: Communication Server, z/OSMF, HLASM, TSO, ISPF, JES2, Metal C Runtime Library z/OS Concepts #CC 25 z/OS Concepts – Elements, Features, Components • z/OS is a collection of elements Optional Features • Each element consists of a collection of modules (calledExamples: components) • Base elements are always included in z/OS Security Server, SDSF, • BCP (Base Control Program) XL C/C++, RMF, JES3, • DFSMSdfp (Data Facility Storage Management Subsystem)DFSMShsm, DFSMSdss • Deliver essential operating system functions • Optional features installed in addition to base elements • Requested separately from base elements • Can be priced or free z/OS Concepts #CC 26 Software Stack 27 IBM z/OS Software Stack Applications Middleware z/OS® Operating System Provides critical set of system services made possible by the z/Architecture® and firmware z/OS Concepts #CC 28 IBM z/OS Software Stack Applications Middleware Software that is z/OS® neither operating Operating System system code nor an end-user application z/OS Concepts #CC 29 IBM z/OS Software Stack Applications Middleware z/OS® Db2® OperatingData Base System 2 CICS® Customer Information Control System IMS™ Information Management System WAS WebSphere® Application Server IBM MQ IBM Message Queuing SAP® Systems, Applications and Products in Data Processing TSO/E Time Sharing Option/Extensions SAP is the registered trademark of SAP SE in Germany and in several other countries. z/OS Concepts #CC 30 IBM z/OS Software Stack Applications Provide end-user interface to product Middleware solutions z/OS® Operating System ISPF Interactive System Productivity Facility SA z/OS IBM System Automation for z/OS z/OS Concepts #CC 31 Application Development Environments, Application Execution Environments and z/OS Management Environments 32 Application Development Env z/OS supports many programming languages as well as modern IDEs and environments z/OS Concepts #CC 33 Application Development Env z/OS supports many programming languages as well as modern IDEs and environments • Assembler • COBOL • C/C++ • PL/I • Fortran • REXX • JAVATM • Python • Node.js • Scala z/OS Concepts #CC 34 Application Development Env Legacy interactive interface z/OS Concepts #CC 35 Application Development Env Integrated Development Legacy interactive interface Environment (IDE) z/OS Concepts #CC 36 Application Development Env Integrated Development Other Modern Application Legacy interactive interface Environment (IDE) Development Tools z/OS Concepts #CC 37 Application Development Env z/OS Concepts #CC 38 Application Execution Env Traditional z/OS z/OS UNIX application application environments, environment including middleware Java Virtual Machine z/OS Container Extensions application environment #CC application environment z/OS Concepts 39 Management Environments z/OS Management Facility (z/OSMF) provides modern interface to help manage your z/OS systems z/OS Concepts #CC 40 DASD 41 IBM Speak – DASD • DASD – Direct Access Storage Device • Think “Hard Drive” z/OS Concepts #CC 42 IBM Speak – DASD • DASD – Direct Access Storage Device • Think “Hard Drive” • a.k.a. DASD Volume • Volume needs a label • Volume Serial Number (VOLSER) • 1 to 6 characters z/OS Concepts #CC 43 Data Sets 44 IBM Speak – Data Set • Data set • Think “File” • Contains data in different structured formats • Need to choose the format of data set and reserve space (allocate dataset) prior to using for the first time • Resides on DASD, Tape • z/OS has types of data sets • Legacy Data set • Unix file IBM prefers the spelling “data set” to “dataset” z/OS Concepts #CC 45 IBM Speak – Data Set DSORG=PS (Physically Sequential) Data Editing the data set gives you all the data in the data set z/OS Concepts #CC 46 IBM Speak – Data Set DSORG=PS (Physically Sequential) Data DSORG=PO (Partitioned) Directory Member 1 Data Member 2 Data Member 3 Data The PDS contains a directory to locate the members z/OS Concepts #CC 47 PDS & PDSE • PDSE data sets can be used in place of nearly all PDS data sets • PDSE designed to address running out of space issues • Compression is not necessary • PDSE directory expands to fit the members z/OS Concepts #CC 48 IBM Speak – Data Set Name • Data set name (DSN or DSName) • Think “File Name” z/OS Concepts #CC 49 IBM Speak – Data Set Name • Data set name (DSN or DSName) • Think “File Name” • 1 to 22 segments • segments separated by a period • each segment limited to 8 characters FRED.ASSEMBLE.SOURCE z/OS Concepts #CC 50 IBM Speak – Data Set Name • Data set name (DSN or DSName) • Think “File Name” • 1 to 22 segments • segments separated by a period • each segment limited to 8 characters • Up to 44 characters (includes periods) • High-level qualifier (HLQ) is typically your userid High-level Low-level qualifier qualifier (HLQ) FRED.ASSEMBLE.SOURCE z/OS Concepts #CC 51 Data Set Allocation 52 IBM Speak – Data Set Allocation • Data set allocation • Think “Create Space” for a data set on disk z/OS Concepts #CC 53 IBM Speak – Data Set Allocation • Data set allocation • Think “Create Space” for a data set on disk • Need: • Data set name • VOLSER (i.e., the DASD volume) where the space should be allocated • Data set attributes (Size, RECFM, LRECL, BLKSZE, DSORG) z/OS Concepts #CC 54 VTOC and Catalogs 55 IBM Speak – VTOC & Catalogs Allocate space for data set FRED.ASSEMBLE.SOURCE on volume VOL100 FRED.ASSEMBLE.SOURCE VOL100 VOLSER z/OS Concepts #CC 56 IBM Speak – VTOC & Catalogs DASD volume has a Volume Table of Contents (VTOC) that locates a data set on the volume VTOC FRED.ASSEMBLE.SOURCE VOL100 z/OS Concepts #CC 57 IBM Speak – VTOC & Catalogs To simplify find the data set, the name and location information is placed in a catalog VTOC SYS1.USERCAT FRED.ASSEMBLE.SOURCE FRED.ASSEMBLE.SOURCE is on VOL100 VOL002 VOL100 z/OS Concepts #CC 58 IBM Speak – VTOC & Catalogs There can be many catalogs so how do we locate the correct one? VTOC SYS1.USERCAT FRED.ASSEMBLE.SOURCE FRED.ASSEMBLE.SOURCE is on VOL100 VOL002 VOL100 z/OS Concepts #CC 59 IBM Speak – VTOC & Catalogs We look in the “Master” catalog (of which there is only one) VTOC SYS1.MSTRCAT SYS1.USERCAT FRED.* data sets cataloged in FRED.ASSEMBLE.SOURCE FRED.ASSEMBLE.SOURCE SYS1.USERCAT
Load more

Recommended publications
  • The Operating System Handbook Or, Fake Your Way Through Minis and Mainframes
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme MVS Table of Contents Chapter 22 MVS: An Introduction.................................................................................... 22.1 Batch Jobs..................................................................................................................1 22.2 Interacting with MVS................................................................................................3 22.2.1 TSO.........................................................................................................................3 22.2.2 ISPF........................................................................................................................3 22.2.3 CICS........................................................................................................................4 22.2.4 Other MVS Components.........................................................................................4 22.3 History........................................................................................................................5 Chapter 23 Getting Started with MVS............................................................................... 23.1 Starting Up.................................................................................................................6 23.1.1 VTAM.....................................................................................................................6 23.1.2 Logging On.............................................................................................................6
    [Show full text]
  • OS/390 Introduction to ISPF
    z/OS Basic Skills Information Center: ISPF Course Module Module 1: Main Features of ISPF © Copyright IBM Corp., 2005. All rights reserved. z/OS Basic Skills Information Center: ISPF Course Module Introduction This module, Main Features of ISPF, introduces you to the z/OS Interactive System Productivity Facility, or ISPF, with special emphasis on the Program Development Facility, or PDF. Time to complete: 10 – 15 minutes © Copyright IBM Corp., 2005. All rights reserved. Page 2 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF - Objectives Upon completion of this module, you should be able to: • Describe the purpose of ISPF and its relationship to TSO • List the four major components of ISPF • Explain the function of each of the four components © Copyright IBM Corp., 2005. All rights reserved. Page 3 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF – Purpose of ISPF The Interactive System Productivity Facility, or ISPF, is a development tool set for the z/OS operating system. It has been used since 1975 to increase the productivity of the development of mainframe applications, because it provides an extensive set of programmer oriented facilities. © Copyright IBM Corp., 2005. All rights reserved. Page 4 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF – The Time Sharing Option/Extended (TSO/E) The Time Sharing Option/Extended, or TSO/E, is a base element of IBM's mainframe z/OS operating system. TSO/E allows you to communicate interactively with the MVS operating system by typing commands (one line at a time) on a computer terminal.
    [Show full text]
  • PKZIP MVS User's Guide
    PKZIP for MVS MVS/ESA, OS/390, & z/OS User’s Guide PKMU-V5R5000 PKWARE, Inc. PKWARE, Inc. 9009 Springboro Pike Miamisburg, Ohio 45342 Sales: 937-847-2374 Support: 937-847-2687 Fax: 937-847-2375 Web Site: http://www.pkzip.com Sales - E-Mail: [email protected] Support - http://www.pkzip.com/support 5.5 Edition (2003) PKZIP for MVS™, PKZIP for OS/400™, PKZIP for VSE™, PKZIP for UNIX™, and PKZIP for Windows™ are just a few of the many members in the PKZIP® family. PKWARE, Inc. would like to thank all the individuals and companies -- including our customers, resellers, distributors, and technology partners -- who have helped make PKZIP® the industry standard for Trusted ZIP solutions. PKZIP® enables our customers to efficiently and securely transmit and store information across systems of all sizes, ranging from desktops to mainframes. This edition applies to the following PKWARE of Ohio, Inc. licensed program: PKZIP for MVS™ (Version 5, Release 5, 2003) PKZIP(R) is a registered trademark of PKWARE(R) Inc. Other product names mentioned in this manual may be a trademark or registered trademarks of their respective companies and are hereby acknowledged. Any reference to licensed programs or other material, belonging to any company, is not intended to state or imply that such programs or material are available or may be used. The copyright in this work is owned by PKWARE of Ohio, Inc., and the document is issued in confidence for the purpose only for which it is supplied. It must not be reproduced in whole or in part or used for tendering purposes except under an agreement or with the consent in writing of PKWARE of Ohio, Inc., and then only on condition that this notice is included in any such reproduction.
    [Show full text]
  • Facility/370: Introduction
    File No. S370-20 Order No. GC20-1800=9 IDl\n \/:u+ •• ".1 I\n"n"': ..... ft IDIVI V IIlUQI .Via"'lllIlv Facility/370: Systems Introduction Release 6 PLC 4 This publication introduces VM/370, and is intended for anyone who is interested in VM/370. However, the reader should have a basic understanding of I BM data processing. VM/370 (Virtual Machine Facility/370) is a system control program (SCP) that tailors the resources and capabilities of a single System/370 computer to provide concurrent users their one unique (virtual) machine. VM/370 consists of a Control Program (CP), which manages the real computer, a Conversational Monitor System (CMS), which is a general-purpose conversational time-sharing system that executes in a virtual machine, a Remote Spooling Communications Subsystem (RSCS), which spools files to and from geographically remote locations, and a Interactive Problem Control System (I PCS), which provides problem analysis and management faci I ities. The first section of the publication is an introduction; it describes what VM/370 can do. The second, third, fourth, and fifth sections describe the Control Program, Conversational Monitor System, Remote Spooling Communications Subsystem, and Interactive Problem Control System respectively. The appendixes include information about VM/370 publication-to-audience relationship and VM/370-related publications for CMS users. , This publication is a prerequisite for the VM/370 system library. --...- --- ---.-- ------- ------ --..- --------- -~-y- Page of GC20-1800-9 As Updated Aug 1, 1979 by TNL GN25-0U89 ~b Edition (Karch 1919) This edition (GC20-1800-~ together with Technical Newsletter GN25-0489. dated August 1, 1919, applies to Release 6 PLC 4 (Program Level Change) of IBM Virtual Machine Facility/310 and to all subsequent releases until otherwise indicated in new editions or Technical Newsletters.
    [Show full text]
  • Download for Z/OS
    Print Services Facility for z/OS Version 4, Release 6.0 Download for z/OS IBM S550-0429-05 Note Before using this information and the product it supports, read the information in “Notices” on page 83. This edition applies to the IBM® Print Services Facility™ Version 4 Release 6 Modification 0 for z/OS®, Program Number 5655-M32, and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces S550-0429-04. © Copyright International Business Machines Corporation 1995, 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 publication...........................................................................................xi Who should read this publication............................................................................................................... xi How this publication is organized............................................................................................................... xi Understanding the syntax notation used in this publication......................................................................xi Related information....................................................................................................................................xii
    [Show full text]
  • Airline Control System Version 2: General Information Manual Figures
    Airline Control System Version 2 IBM General Information Manual Release 4.1 GH19-6738-13 Airline Control System Version 2 IBM General Information Manual Release 4.1 GH19-6738-13 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page ix. This edition applies to Release 4, Modification Level 1, of Airline Control System Version 2, Program Number 5695-068, and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. A form for readers’ comments appears at the back of this publication. If the form has been removed, address your comments to: ALCS Development 2455 South Road P923 Poughkeepsie NY 12601-5400 USA 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 2003, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures .................................... v Tables .................................... vii Notices .................................... ix Trademarks ................................... ix About this book ................................ xi Who should read this book .............................. xi Related publications ...............................
    [Show full text]
  • Z/OS ♦ Z Machines Hardware ♦ Numbers and Numeric Terms ♦ the Road to Z/OS ♦ Z/OS.E ♦ Z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services
    Mainframes The Future of Mainframes Is Now ♦ z/Architecture ♦ z/OS ♦ z Machines Hardware ♦ Numbers and Numeric Terms ♦ The Road to z/OS ♦ z/OS.e ♦ z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services by Steve Comstock The Trainer’s Friend, Inc. http://www.trainersfriend.com 800-993-8716 [email protected] Copyright © 2002 by Steven H. Comstock 1 Mainframes z/Architecture z/Architecture ❐ The IBM 64-bit mainframe has been named "z/Architecture" to contrast it to earlier mainframe hardware architectures ♦ S/360 ♦ S/370 ♦ 370-XA ♦ ESA/370 ♦ ESA/390 ❐ Although there is a clear continuity, z/Architecture also brings significant changes... ♦ 64-bit General Purpose Registers - so 64-bit integers and 64-bit addresses ♦ 64-bit Control Registers ♦ 128-bit PSW ♦ Tri-modal addressing (24-bit, 31-bit, 64-bit) ♦ Over 140 new instructions, including instructions to work with ASCII and UNICODE strings Copyright © 2002 by Steven H. Comstock 2 z/Architecture z/OS ❐ Although several operating systems can run on z/Architecture machines, z/OS is the premier, target OS ❐ z/OS is the successor to OS/390 ♦ The last release of OS/390 was V2R10, available 9/2000 ♦ The first release of z/OS was V1R1, available 3/2001 ❐ z/OS can also run on G5/G6 and MP3000 series machines ♦ But only in 31-bit or 24-bit mode ❐ Note these terms: ♦ The Line - the 16MiB address limit of MVS ♦ The Bar - the 2GiB limit of OS/390 ❐ For some perspective, realize that 16EiB is... ♦ 8 billion times 2GiB ♦ 1 trillion times 16MiB ❐ The current release of z/OS is V1R4; V1R5 is scheduled for 1Q2004 Copyright © 2002 by Steven H.
    [Show full text]
  • Microkernel Vs
    1 VIRTUALIZATION: IBM VM/370 AND XEN CS6410 Hakim Weatherspoon IBM VM/370 Robert Jay Creasy (1939-2005) Project leader of the first full virtualization hypervisor: IBM CP-40, a core component in the VM system The first VM system: VM/370 Virtual Machine: Origin 3 IBM CP/CMS CP-40 CP-67 VM/370 Why Virtualize 4 Underutilized machines Easier to debug and monitor OS Portability Isolation The cloud (e.g. Amazon EC2, Google Compute Engine, Microsoft Azure) IBM VM/370 Specialized Conversation Mainstream VM al Monitor OS (MVS, Another Virtual subsystem System DOS/VSE copy of VM machines (RSCS, RACF, (CMS) etc.) GCS) Hypervisor Control Program (CP) Hardware System/370 IBM VM/370 Technology: trap-and-emulate Problem Application Privileged Kernel Trap Emulate CP Classic Virtual Machine Monitor (VMM) 7 Virtualization: rejuvenation 1960’s: first track of virtualization Time and resource sharing on expensive mainframes IBM VM/370 Late 1970’s and early 1980’s: became unpopular Cheap hardware and multiprocessing OS Late 1990’s: became popular again Wide variety of OS and hardware configurations VMWare Since 2000: hot and important Cloud computing Docker containers Full Virtualization 9 Complete simulation of underlying hardware Unmodified guest OS Trap and simulate privileged instruction Was not supported by x86 (Not true anymore, Intel VT-x) Guest OS can’t see real resources Paravirtualization 10 Similar but not identical to hardware Modifications to guest OS Hypercall Guest OS registers handlers Improved performance VMware ESX Server 11 Full virtualization Dynamically rewrite privileged instructions Ballooning Content-based page sharing Denali 12 Paravirtualization 1000s of VMs Security & performance isolation Did not support mainstream OSes VM uses single-user single address space 13 Xen and the Art of Virtualization Xen 14 University of Cambridge, MS Research Cambridge XenSource, Inc.
    [Show full text]
  • Floboss 107 Flow Manager Instruction Manual
    Part Number D301232X012 May 2018 FloBoss™ 107 Flow Manager Instruction Manual Remote Automation Solutions FloBoss 107 Flow Manager Instruction Manual System Training A well-trained workforce is critical to the success of your operation. Knowing how to correctly install, configure, program, calibrate, and trouble-shoot your Emerson equipment provides your engineers and technicians with the skills and confidence to optimize your investment. Remote Automation Solutions offers a variety of ways for your personnel to acquire essential system expertise. Our full-time professional instructors can conduct classroom training at several of our corporate offices, at your site, or even at your regional Emerson office. You can also receive the same quality training via our live, interactive Emerson Virtual Classroom and save on travel costs. For our complete schedule and further information, contact the Remote Automation Solutions Training Department at 800-338-8158 or email us at [email protected]. ii Revised May-2018 FloBoss 107 Flow Manager Instruction Manual Contents Chapter 1 – General Information 1-1 1.1 Scope of Manual ............................................................................................................................1-2 1.2 FloBoss 107 Overview ...................................................................................................................1-2 1.3 Hardware ........................................................................................................................................1-5
    [Show full text]
  • TITLE SPIRES (Stanford Public Information Retrieval System) 1970-71 Annual Report INSTITUTION Stanford Univ
    DOCUMENT REsUME ED 057 828 LI 003 325 AUTHOR Parker, Edwin B. TITLE SPIRES (Stanford Public Information Retrieval System) 1970-71 Annual Report INSTITUTION Stanford Univ. , Calif. Inst. for Communication Research. SPONS AGENCY National Science Foundation, Washington, D.C. Office of Science Information Services. PUB DATE Dec 71 NOTE 154p.;(23 References) EDRS PRICE MF-$0.65 HC-$6.58 DESCRIPTORS *Computer Programs; *Information Retrieval; *Information Storage; *Information Systems; *On Line Systems IDENTIFIERS Computer Software; SPIRES; *Stanford Public Information Retrieval System ABSTRACT SPIRES (Stanford Public Information REtrieval System) is a computer information storage and retrieval system being developed at Stanford University with funding from the National Science Foundation. SPIRES has two major goals: to provide a user-oriented, interactive, on-line retrieval syste for a variety of researchers at Stanford; and to support the automation efforts of the university libraries by developing and implementing common software. SPIRES I, a prototype system, was implemented at the Stanford Linear Accelerator Center (SLAC) in 1969, from a design based on a 1967 information study involving physicists at SLAC. Its primary data base is a high-energy-physics preprints file. Evaluation of SPIRES I resulted in the definition of a production information storage and retrieval system, SPIRES II. This system will be available -daily, beginning in mid-1972, to faculty, staff, and students of the University.- It is characterized by flexibility, simplicity, and economy. _SPIRES II will operate on-line on an IBM 360/67 computer. This report summarizes the uses of the SPIRES I system over the past year and describes both the nature of SPIRES II and this system,s development over the past year.
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • Specifications
    Specifications SYSTEM PERFORMANCE Standard & Advanced Editions Advanced Edition Only 96-Well Verification Plate 384-Well Verification Plate Time Requirements < 5 minutes < 10 minutes Tip Configurations 1, 2, 4, 6, 8, 12, and 96 1, 8, 12, 16, 24, 96, and 384 Traceable Volume Range 0.1000 - 350.0 µL 0.0100 - 55.00 µL Operating Volume Range* 0.0001 - 350.0 µL 0.0001 - 55.00 µL Artel 800TSNB Plate Reader Uncertainty (Inaccuracy)** 0.2000 - 350.0 µL, ± 2.0% 0.0500 - 55.00 µL, ± 2.5% 0.1000 - 0.1999 µL, ± 3.0% 0.0200 - 0.0499 µL, ± 3.5% 0.0100 - 0.0199 µL, ± 5.5% Random Error (Imprecision)** 0.2000 - 350.0 µL, ≤ 0.4% 0.0500 - 55.00 µL, ≤ 0.8% 0.1000 - 0.1999 µL, ≤ 0.4% 0.0200 - 0.0499 µL, ≤ 0.8% 0.0100 - 0.0199 µL, ≤ 0.9% Operating Temperature for Aqueous Sample Solutions 15 - 30 °C 15 - 30 °C Operating Temperature for DMSO Sample Solutions 19 - 30 °C 19 - 30 °C Traceability to national & international standards using Yes Yes Artel MVS Verification Plates PERFORMANCE SPECIFICATION DEFINITIONS • When each well in an MVS Verification Plate is uniformly1 filled with a known2 volume of MVS Sample Solution and measured with an Artel MVS Plate Reader, each individual well measurement will be within the stated MVS inaccuracy specification at a statistical confidence of 95% or better.3 • The CV across the full plate (96 or 384 individual results) will also be within the stated imprecision specification at a statistical confidence of 95% or better.4 1.
    [Show full text]