DOCSLIB.ORG

Top Physics RTT Samples & Plots

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Top Physics RTT Samples & Plots eX Computing from my PhD onwards All the way from ALGOL68 to C++, Python and the Grid, by way of Fortran, CERNLIB and RAL/CERN batch systems 2008-11-27 Joe Foster 1 eX Itinerary • Leeds (late 1970s): PhD computing - the simple life. • CERN (1980s): Heroic days of HEP computing. • All over: Distributed computing before the WWW and the Grid. • 1992: “A World Wide Web?”: my response. • After the millenium: The Grid 2008-11-27 Joe Foster 2 eX Leeds: PhD Computing (late 1970s) • Stand alone program to analyze spark chamber photos – Small group working on cosmic rays. – Simple detector. – Small data volumes. – Chose ALGOL68. – Recommended by computer scientists. – Modular, procedures and variables have scope. – Define new data types. – A precursor of C, Ada, Python... – Example ... IF a = b THEN x := y ELSE x := z FI; ... – Nice! 2008-11-27 Joe Foster 3 eX Leeds: PhD Computing (late 1970s) • ICL 1906A mainframe computer at Leeds – 128K(?) of 24-bit core memory using 6 bit ‘characters’. – ?MB fixed disc + 8M char exchangeable disc store. – Drum store for paging. – Tape drives for archive storage. – User input: • Line mode VDU (later on) • Teletype terminal • IBM card punch – George 4 operating system. – Huge power consumption (~0.5MW?). – Slow, limited local area network. – Email? 2008-11-27 Joe Foster 4 eX Some Early Hardware ICL 1906A at RAL 2008-11-27 Joe Foster 5 eX Storage in the 1970s 8M character exchangeable disc Core Memory Tape Drives 2008-11-27 Joe Foster 6 eX User Data Entry Teletype Terminal with tape punch Card punch 2008-11-27 Joe Foster 7 eX CERN (1980s): HEP computing • HEP computing was very different. – Data: • Large complex datasets, resident on tape. • Event based. Events too big for memory. – Need memory management! • Time dependent alignment and calibration data. – Software: • Large bodies of code with many contributors. – Code management system needed. • FORTRAN – Fast, well understood. – Initially only FORTRAN 4 compiler. – Code management needed for COMMON blocks, etc. – Memory management from separate libraries. • Much functionality provided by CERN Program Library. • IBM JCL for scripting. • WYLBUR user interface. – Hardware • IBM mainframe. PDP11 for DAQ in EMC. • Line mode terminals in common user area. • Fast CERN-wide network. Email, with limitations. 2008-11-27 Joe Foster 8 eX PDP 11 DEC PDP11 mini- computer like the one used in EMC for data acquisition. Note the programming switches on the front panel. They were used to set up the start address for the initial program load when booting. 2008-11-27 Joe Foster 9 eX IBM JCL • Unix: cp OldFile NewFile • IBM JCL: //IS198CPY JOB (IS198T30500),'COPY JOB',CLASS=L,MSGCLASS=X //COPY01 EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=OLDFILE,DISP=SHR //SYSUT2 DD DSN=NEWFILE, // DISP=(NEW,CATLG,DELETE), // SPACE=(CYL,(40,5),RLSE), // DCB=(LRECL=115,BLKSIZE=1150) //SYSIN DD DUMMY 2008-11-27 Joe Foster 10 eX FORTRAN • FORTRAN 77 has some nice features, but there was much legacy code in FORTRAN 4. • FORTRAN 77: IF (A .EQ. B) THEN X = Y ELSE X = Z END IF • FORTRAN 4: IF (A .EQ. B) GOTO 10 X = Z GOTO 30 10 X = Y 30 CONTINUE 2008-11-27 Joe Foster 11 eX FORTRAN • Standard FORTRAN was well understood and fast, but had serious limitations for HEP computing: – Subroutine, function, common block names have global scope, and are limited to six upper case characters. It is hard to generate meaningful names that don’t collide with library functions, etc. – Rigid code format based on IBM punch cards. – Arrays can’t be allocated at run time, but fixed arrays for HEP event data would be too big. – Common blocks must be declared in full at the start of all program units that use them, and they can have many variables. There is no FORTRAN equivalent of the C preprocessor to manage this. – It is hard to write well structured code with features like GOTO. – Limited ability to define new complex data types. – No IO access by keywords like Python dictionary type. • Proprietary extensions were nice, but not portable. • Most of the missing features were supplied by the CERN Program Library (CERNLIB). 2008-11-27 Joe Foster 12 eX Some (old) CERNLIB Addons • PATCHY code management library – Let many users work on a common body of code. – Select particular versions of program units. – Conditionally include platform dependent code. – Managed FORTRAN COMMON block inclusion in a platform independent way. – Superseded by CMZ, and now by CVS and Subversion. • HBOOK histogram package – Used to fill and display histograms in batch mode. – Superseded by PAW, and now by ROOT, JAS, etc. • KAPACK, FFREAD keyed random access packages – Useful for calibration databases, read from text file. – Now we have SQL databases and XML. 2008-11-27 Joe Foster 13 eX Memory Management and FORTRAN • ZBOOK was an early FORTRAN based memory management package. – Declare a large array in a COMMON block which can contain either REALs or INTEGERs. – ‘Book’ space (banks) in the array and access data there by bank pointers and offsets. – ‘Drop’ the banks after use and book new ones. – Garbage collection occurs when the array gets too full. Current banks are shuffled over into space left by dropped ones. Old pointers are lost only now. • More recent packages ZEBRA, HYDRA, BOS work in essentially the same way. • Now we use malloc in C, new in C++. – Continuing source of memory leaks! • Python does it all for us. 2008-11-27 Joe Foster 14 eX ZBOOK Example SUBROUTINE ZEXAM1 C ID1 may be used in another COMMON/ZCOMM/Z(1), ID1, ID2, ID3, WS(1) DIMENSION IZ(1000), IWS(1) subroutine. Invalid there? EQUIVALENCE (IZ(1),Z(1)), (IWS(1),WS(1)) No type checking possible! C C INITIALIZATION CALL ZINIT (Z,WS,1000) C C BOOKING NWORDS = 23 CALL ZBOOK (Z, ID1,NWORDS) C CHECK IF BANK EXISTS IF (ID1.EQ.0) GOTO 999 C FILLING DO 10 I=1, NWORDS 10 IZ(ID1 + I) = I C C ACCESS TO DATA STORED IN THE BANK ILAST = IZ(ID1 + NWORDS) C 999 RETURN END 2008-11-27 Joe Foster 15 eX 1980S Batch Analysis • Typical 1980s batch analysis job: Compile Link Process Visualize Debug Debug Debug Debug – Could take hours to run even a small job. – Rerun whole job just to add one histogram. – Errors caught late in cycle. 2008-11-27 Joe Foster 16 eX Modern Job with PAW or ROOT • Typical modern analysis chain using PAW or ROOT Compile Link Process Visualize Debug Debug Debug Debug – Break job into separate steps - easy with Unix scripting. – Debug each step separately - faster error catching. – Easily add new histograms using PAW ntuple or ROOT TTree. 2008-11-27 Joe Foster 17 eX Cost of Fixing Bugs (from memory) 40 30 20 Cost (log scale) 10 0 Design Code Test Deploy 2008-11-27 Joe Foster 18 eX 1980s Distributed Computing By 1984 most UK Universities were linked to SERCNET (later JANET ) - some via sites like Manchester or Daresbury. Connection to CERN and US sites was possible via gateways. Services included remote login, remote job submission, email. 2008-11-27 Joe Foster 19 eX 1980s Networks • Many UK HEP users in the 1980s had three network protocols to learn. – SERCNET/JANET - e.g. ‘[email protected]' – IBM based BITNET (USA), EARN (Europe) - e.g. ‘JF2 AT RALVM’ – VAX based DECNET - (‘RALMVS:JFS’) – Others, too... • Login, job submission, email were easy within any network. • These networks were incompatible, but connected via gateways. • You could get info from remote computers anywhere in the world, but only if you had an account there and you could navigate the gateways. • Connectivity could be lost for hours or days at a time. 2008-11-27 Joe Foster 20 eX 1980s Attitudes to Network Use “2. ARPANET ACCESS SERC users wishing to use ARPANET to access machines in the USA are reminded that formal approval is required from SERC and the ARPANET Governing Committee. Approved users are provided with identifiers and password and must observe the strict rule that this is only for their use. Anyone who allows their identifier and password to be used by someone not authorised to access ARPANET will have their approval withdrawn immediately. Use of this International Network is carefully scrutinised by British Telecom who have a representative on the Governing Committee. Abuse of the system could seriously prejudice the future for ARPANET.” 2008-11-27 Joe Foster 21 eX Hot Topics from CHEP ‘87 • Physics Analysis Workstation (PAW) . • Supercomputing, parallel computing (e.g. transputers). • Vectorization of HEP software. • Relational databases for HEP. • Use of structured analysis and software engineering. • Working towards object oriented software. • Compatibility: networks, languages, graphics. • Optical storage for HEP. • Dream of a terabyte scale disk farm somewhere... 2008-11-27 Joe Foster 22 eX HEP Computing in the 1990s • The 1990s brought many improvements to HEP computing. – C and C++ began to replace FORTRAN. – Object oriented techniques began to be widely adopted. – Open source and ‘Free’ software became important. – Most HEP computing done under some form of Unix. – Farms of cheap PCs running linux replaced mainframes as workhorses. – Many new productivity tools became available: • Interactive Development Environments, e.g. LabView. • Powerful text editors with features like syntax colouring. • Database Management Systems for relational databases. • Interpreted languages like PERL and PYTHON made scripting easy and powerful. • Tools like CMT (Configuration Management Tool) make it easy to define standard releases of large applications with many components - e.g. ATLAS reconstruction. 2008-11-27 Joe Foster 23 eX 1990s Distributed Computing • Big changes came in the 1990s – UK joined the rest of the Internet and adopted TCP/IP protocols, ditching the old ‘big-endian’ SERCNET addresses, as well as BITNET + DECNET.
Load more

Recommended publications
  • Introduction to Mainframe Networking TCP/IP Problem Determination
    z/OS Basic Skills Information Center Networking on z/OS z/OS Basic Skills Information Center Networking on z/OS Note Before using this information and the product it supports, read the information in “Notices” on page 251. This edition applies to z/OS (product number 5694-A01). We appreciate your comments about this publication. Comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. For technical questions and information about products and prices, please contact your IBM branch office, your IBM business partner, or your authorized remarketer. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. Send your comments through this web site: http://publib.boulder.ibm.com/infocenter/zoslnctr/v1r7/index.jsp?topic=/com.ibm.zcontact.doc/webqs.html © Copyright IBM Corporation 2006, 2010. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Before you begin the topic about Coupling channels ...........40 networking on z/OS .........vii Open Systems Adapter (OSA) .......40 HiperSockets ..............46 The I/O cage ..............48 Part 1. Introduction to networking on the mainframe...........1 Chapter 4. Sample network configuration ............49 Chapter 1.
    [Show full text]
  • Acrobat Distiller, Job 2
    A BRIEF HISTORY OF THE IBM ES/9000, SYSTEM/390 AND zSERIES 1990 IBM makes its most comprehensive product announcement in 25 years by introducing the System/390 family consisting of 18 Enterprise System/9000 processors ranging from midrange computers for office environments to the most powerful computers IBM has ever offered. Featuring enhanced function and capability to manage information systems, the System/390 provides increased processing power, better network management, improved communication among multivendor systems and the Enterprise System/9000 processors. In many cases, customers currently using IBM Enterprise System/3090 systems can easily upgrade their systems to System/390 processors. Other 1990 announcements include: several networking products to make it easier for customers to use their midrange, desktop and System/390 computers to communicate with non-IBM computers. 1991 IBM unveils seven new Enterprise System/9000 processors and operating system software — Advanced Interactive Executive/Enterprise System Architecture (AIX/ESA) — for the System/390 family. AIX/ESA is a further step in IBM’s implementation of open-systems computing across its product line and is based on UNIX and the Open Software Foundation’s OSF/1 standards. The company begins shipping in volume and on schedule two top-of-the-line ES/9000 models that were announced in September 1990. IBM Japan says it will supply Enterprise System/9000 processors and operating system software to Mitsubishi Electric Corp. for remarketing. The agreement marks the first time IBM has sold large processors as an original equipment manufacturer for resale. 1992 IBM introduces two entry-level Enterprise System/9000 processors and ships five new Enterprise System/9000 water-cooled processors — Models 520, 640, 660, 740 and 860 — one-to-four months ahead of schedule.
    [Show full text]
  • IBM Zenterprise BC12 (Zbc12) Enabling Enterprises of All Sizes to Build a Better Customer Experience with IBM Z Systems
    IBM Systems and Technology Data Sheet IBM zEnterprise BC12 (zBC12) Enabling enterprises of all sizes to build a better customer experience with IBM z Systems Organizations around the world are recognizing the increasing role that Highlights technology plays in driving change as they shift investments from infra- structure maintenance towards new projects, such as cloud, data analytics ●● ●●Delivers increased performance, flexibility and mobile applications. To remain competitive, they must constantly and scale in a lower cost package adapt and respond with increased speed to deliver new services through ●● ●●Helps save money through consolidation multiple channels to customers, partners and employees. To capitalize on Linux® and an efficient cloud delivery on this opportunity, organizations must be able to tap into their valuable model data and energize applications without going over budget while keeping ●● ●●Enables workloads to be deployed where everything protected and secure to reduce organizational and reputation they run best and cost less with proven risk. This requires an optimized infrastructure that is integrated, agile, hybrid computing trusted and secure. ●● ●●Lets you secure it all with confidence on a trusted and resilient infrastructure The newest member of the IBM® zEnterprise® System family is the IBM zEnterprise BC12 (zBC12). Designed as an entry point for enterprise computing it embodies the same innovation and value, flexible growth options, industry-leading virtualization, trusted resiliency, secure cloud, enterprise mobility and operational analytics capabilities as the massively scalable IBM zEnterprise EC12. The zBC12 delivers a lower and more granular cost structure with significant improvements in pack- aging, performance and total system scalability over prior generations.
    [Show full text]
  • Rising IBM Mainframe Software Costs
    Rising IBM Mainframe Software Costs By Kim A. Eckert, Certified IT Architect Rising IBM mainframe software costs started getting the attention of high level executives some years ago. This was partially due to realizing the software inventories analysis was inefficient and limited. In addition, a third party company was hired to review IBM Strategic Outsourcing (SO) account’s inventory. In other words, IBM was paying "green" dollars to save "blue" dollars! In order for the team to become competitive and provide extra value to our Integrated Technology Delivery (ITD) accounts, I architected an automated system that merged data from several sources and made it easy for the technical support teams to verify the inventory. Once the reports were produced, my team would analyze the data and make recommendations for cost take out opportunities. There were several issues surrounding software licensing and validation: 1. IBM only had tools that would report on what was installed on a customer’s machine then that output would be matched up to what was actually licensed. This approach had benefits as in ensuring they are paying for what they use, but did not do the opposite - ensuring they are actually using what they are paying for. 2. The only place to find where a product was superseded by another was either Announcement letters or the Dawn report web page. The Dawn report lists all monthly license type software and their replacement if available. For example, it would show 5647-A01 OS/390 is replaced by 5694-A01 z/OS. 3. End of Support information was only available through Announcement letters or the Lifecycle Support web page.
    [Show full text]
  • Oracle® Database Gateway for APPC Installation and Configuration Guide
    Oracle® Database Gateway for APPC Installation and Configuration Guide 19c for IBM AIX on POWER Systems (64-Bit), Linux x86-64, Oracle Solaris on SPARC (64-Bit), and HP- UX Itanium F18241-01 April 2019 Oracle Database Gateway for APPC Installation and Configuration Guide, 19c for IBM AIX on POWER Systems (64-Bit), Linux x86-64, Oracle Solaris on SPARC (64-Bit), and HP-UX Itanium F18241-01 Copyright © 2002, 2019, Oracle and/or its affiliates. All rights reserved. Primary Author: Rhonda Day Contributing Authors: Vira Goorah, Govind Lakkoju, Peter Wong, Juan Pablo Ahues-Vasquez, Peter Castro, Charles Benet This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S.
    [Show full text]
  • Audit Report No.: 2007-DP-0004
    Issue Date February 22, 2007 Audit Report Number 2007-DP-0004 TO: Lisa Schlosser, Chief Information Officer, Q Joseph A. Neurauter, Chief Procurement Officer, N Keith A. Nelson, Assistant Secretary, Administration, A FROM: Hanh Do, Director, Information Systems Audit Division, GAA SUBJECT: Fiscal Year 2006 Review of Information Systems Controls in Support of the Financial Statements Audit HIGHLIGHTS What We Audited and Why We reviewed general and application controls for selected information systems to assess management controls over HUD’s computing environments as part of the Office of Inspector General’s (OIG) audit of the U.S. Department of Housing and Urban Development’s (HUD) financial statements for fiscal year 2006 under the Chief Financial Officer’s Act of 1990. What We Found HUD did not ensure that its general and application controls over its financial systems conformed to federal requirements and guidelines. Proper configuration management controls for software and document changes are not always employed, and access controls and support for the IBM mainframe operating system console are inadequate. Physical security controls over computing operations facilities are weak, and personnel security practices continue to pose the risk of unauthorized access to HUD systems. As a result, HUD’s financial systems are at risk of compromise. What We Recommend We recommend that the chief information officer, chief procurement officer, and assistant secretary for the Office of Administration ensure that Office of Management and Budget requirements, Federal Information Security Management Act requirements, National Institute of Standards and Technology guidelines, and HUD’s own internal policies and procedures are implemented. For each recommendation without a management decision, please respond and provide status reports in accordance with HUD Handbook 2000.06, REV-3.
    [Show full text]
  • Print Services Facility for Z/OS Version 4, Release 6.0
    Print Services Facility for z/OS Version 4, Release 6.0 Introduction IBM G550-0430-05 Note Before using this information and the product it supports, read the information in “Notices” on page 31. 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 G550-0430-04. © Copyright International Business Machines Corporation 1999, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures........................................................................................................ v List of Tables........................................................................................................vii About this publication...........................................................................................ix Who should read this publication............................................................................................................... ix How this publication is organized............................................................................................................... ix Related information.....................................................................................................................................ix How to send your comments to IBM.......................................................................xi
    [Show full text]
  • IBM Z Connectivity Handbook
    Front cover IBM Z Connectivity Handbook Octavian Lascu John Troy Anna Shugol Frank Packheiser Kazuhiro Nakajima Paul Schouten Hervey Kamga Jannie Houlbjerg Bo XU Redbooks IBM Redbooks IBM Z Connectivity Handbook August 2020 SG24-5444-20 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Twentyfirst Edition (August 2020) This edition applies to connectivity options available on the IBM z15 (M/T 8561), IBM z15 (M/T 8562), IBM z14 (M/T 3906), IBM z14 Model ZR1 (M/T 3907), IBM z13, and IBM z13s. © Copyright International Business Machines Corporation 2020. 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 . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . xi Comments welcome. xi Stay connected to IBM Redbooks . xi Chapter 1. Introduction. 1 1.1 I/O channel overview. 2 1.1.1 I/O hardware infrastructure . 2 1.1.2 I/O connectivity features . 3 1.2 FICON Express . 4 1.3 zHyperLink Express . 5 1.4 Open Systems Adapter-Express. 6 1.5 HiperSockets. 7 1.6 Parallel Sysplex and coupling links . 8 1.7 Shared Memory Communications. 9 1.8 I/O feature support . 10 1.9 Special-purpose feature support . 12 1.9.1 Crypto Express features . 12 1.9.2 Flash Express feature . 12 1.9.3 zEDC Express feature . 13 Chapter 2. Channel subsystem overview . 15 2.1 CSS description . 16 2.1.1 CSS elements .
    [Show full text]
  • Mainframe Hardware Course: Mainframe’S Processors
    Mainframe hardware course: Mainframe’s processors z/OS Basic Skills: The mainframe’s processors Mainframe’s processors This hardware course introduces you to one model of IBM® mainframe computer, the IBM System z9™, to help you learn about the hardware parts that constitute the mainframe’s processor by comparing processing parts and functions to personal computers or notebooks. Time to complete: 10 - 15 minutes ¾The central processor complex ¾The multichip module ¾Memory cards ¾Input/output connections ¾The mainframe’s processing capacity © Copyright IBM Corp. 2006. All rights reserved. The central processor complex z/OS Basic Skills: The mainframe’s processors Mainframe’s processors > The central processor complex Mainframes have one or two metal frames that contain specialized cages, as well as other physical elements. This diagram shows the interior front view of an IBM System z9 Enterprise Class (z9 EC) model that has two frames. The z9 EC is slightly larger than a household refrigerator. The central processor complex, or CPC, resides in its own cage inside the mainframe, and consists of one to four book packages. Just like its personal-computer counterpart, the motherboard or system board, each book package consists of processors, memory, timers, and I/O connections. These collections of hardware parts are called “book packages” because you can slide them in or out of the CPC cage almost as easily as you can slide a book on or off a bookshelf. © Copyright IBM Corp. 2006. All rights reserved. z/OS Basic Skills: The mainframe’s processors Mainframe’s processors > The book package In the System z9, as well as earlier IBM mainframe models, the book package consists of three distinct areas, one each for: • The z9 EC's processors, which are inside one multichip module • Memory cards • Connections to input/output devices All of the book packages plug into a backplane in the z9 EC's frame.
    [Show full text]
  • The IBM Z Mainframe Table of Contents
    WHITEPAPER The Rockstar in Your Data Center: The IBM Z Mainframe Table of contents Why read this? 3 Key takeaways 4 Executive summary 5 The IBM Z platform does what? 8 Next steps and additional resources 17 Whitepaper The Rockstar in Your Data Center: The IBM Z Mainframe ROCKETSOFTWARE.COM 2 Why read this? Some CIOs may think it’s time to retire their IBM Z® mainframe. They may think the technology has become outdated, they may not understand the full benefits they provide, or both. The mainframe has design strengths that, today, make it invaluable to IT organizations for hosting their most important, mission-critical applications. These applications typically include customer order processing, financial transactions, production and inventory control, payroll, as well as many other types of computationally intensive and high-volume tasks. This whitepaper demonstrates why IBM Z mainframes are the best choice to be the bedrock for critical, “can’t fail” processing tasks, and why, over the long term, they deliver among the best value in the IT ecosystem. Whitepaper The Rockstar in Your Data Center: The IBM Z Mainframe BACK TO TABLE OF CONTENTS ROCKETSOFTWARE.COM 3 Key takeaways Don’t automatically dismiss IBM Z when making strategic decisions about your current and future IT environment. It continues to have significant market and competitive strength, and IBM makes sure it works with the latest technologies, including cloud computing and open-source tools. It’s a key innovation player that drives better ROI on core infrastructure while supporting the latest advancements in technology and user experience. The at-risk platform in large organization data centers is not the mainframe.
    [Show full text]
  • Z/OS Basic Skills Information Center: Mainframe Concepts
    z/OS Basic Skills Information Center Mainframe concepts z/OS Basic Skills Information Center Mainframe concepts Note Before using this information and the product it supports, read the information in “Notices” on page 45. This edition applies to z/OS (product number 5694-A01). We appreciate your comments about this publication. Comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. For technical questions and information about products and prices, contact your IBM branch office, your IBM business partner, or your authorized remarketer. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. Send your comments through this Web site: http://publib.boulder.ibm.com/infocenter/zoslnctr/v1r7/ index.jsp?topic=/com.ibm.zcontact.doc/webqs.html © Copyright International Business Machines Corporation 2005, 2008. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Introduction to the mainframe . .v Mainframe operating system: z/TPF . .22 Chapter 1. The value of the mainframe Chapter 2. Mainframe hardware today . .1 concepts . .23 The S/360: A turning point in mainframe history . .1 Mainframe hardware: Terminology . .23 Mainframe architecture: Secure, compatible, and still Mainframe hardware: Evolving design .
    [Show full text]
  • IBM Mainframe Configuration
    VITA Draft Discussion Document // REV – 091117 Service Management & Delivery (SMD) Conceptual Data View Mainframe (MF) Configuration IBM Mainframe Configuration CIPPS FINDS CSS pvacms VABS VECTAX VECHRMS.* APECS SCBPLIDS Mantissa pspider COIN DB2 SCCM IBM Tivoli FAACS VEC.JS BLS Bureau of DocProc VECFGS.* Commonwealth Financial Citizen Services Sys / Adabas DATA Virginia Employment Commission DB2 State Reports Constitutional Monitoring Labor Statistics Datasets Integrated Payroll and Information Compensation Distribution Officer CSS-REV-RTC-230-A Virginia Automated LAUS Local Area Personnel System Downloading Automated Program to Board Local System DB Information Unemployment System DB195 Benefits Enforce Child Inmate Data Network Appeals Same as CSS ADABAS file. Statistics Data System WRIS Support System MBS DMV-CSS-TITLE FAACS SP Wage Record DR Mainframe Billing SVES Interchange Debt APECS System Fixed Asset OES – SPAM State BK System Recovery Automated Accounting CTS Applications CIPPS Verification Bankruptcy System Program to TDS and Control Customer PH and Exchange OES Enforce Child Tivoli Decision System – Tracking LS Tele- FINDS FINDS CSS System VABS VABS Spam System (SP) DG90 DG90 APECS LIDS Mantissa Support COIN TDS Support Mainframe System LAUS System DocProc communications ????? Operating Systems Virtual CPU’s DOA Voucher File Logical Partitions COVA1-SYS1 COVA2-SYS2 COVA3-SYS3 COVA4-SYS4 COVA5-SYS5 COVA6-SYS6 Logical Processor Units (PU’s) Production Engineering / Testing DEV Processor Resource (PR) / Systems Manager™ (SM) (PR/SM™) – Type-1 Hypervisor – Firmware Layer The PR/SM™ facility creates logical partitions (LPARs) and assigns processing capacity to them. An LPAR is a logical subdivision of a CPC. Central processor complex (CPC) = an IBM Z server that runs the z/Architecture® instruction set (aka mainframe computer).
    [Show full text]