DOCSLIB.ORG

Airline Control System Version 2: General Information Manual Figures

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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 ................................ xi Chapter 1. Introduction ............................. 1 Overview of ALCS ................................. 1 General description of ALCS ............................. 2 Application programming interface ........................... 3 Chapter 2. Highlights of ALCS Version 2...................... 5 Operating environment ................................ 7 Storage above 2 GB, 64-bit addressing ........................... 7 Communication .................................. 7 Online Communication Table Maintenance (OCTM) ...................... 7 E-mail ..................................... 7 Web Server .................................... 7 Access control ................................... 8 Automated operations ................................ 8 Online help.................................... 8 Simplified installation and operation ........................... 8 System takeover facility................................ 8 Real-time database reorganization ............................ 8 High-level language support .............................. 8 Relational database support .............................. 9 WebSphere MQ for z/OS interface ............................ 9 Optimized Local Adapters for WebSphere Application Server for z/OS ............... 10 Chapter 3. Operating environment ........................ 11 End-user facilities ................................. 11 Chapter 4. Communication ........................... 13 VTAM networks.................................. 13 TCP/IP networks ................................. 14 ATA/IATA SLC networks............................... 14 Chapter 5. Online monitor functions ....................... 17 Task management ................................. 17 Storage management ................................ 17 Application program management............................ 18 DASD management ................................ 18 Real-time database data sets ............................. 19 General files and general data sets........................... 19 Files and records ................................ 19 Virtual file access ................................ 21 Recoup and Pool Directory Update .......................... 21 TPF Database Facility product ............................ 22 © Copyright IBM Corp. 2003, 2019 iii Sequential file management .............................. 22 System sequential files............................... 23 Application sequential files ............................. 24 Communication management ............................. 24 Printer support ................................. 24 Chapter 6. Messages on WebSphere MQ for z/OS ................. 25 Chapter 7. Access to relational databases .................... 27 Chapter 8. High-level languages ......................... 29 Chapter 9. Maintenance ............................ 31 Performance monitoring ............................... 31 Reconfiguration .................................. 31 Database organization ................................ 31 Communication network reconfiguration ......................... 31 Testing facilities .................................. 32 Recovery .................................... 32 Chapter 10. Testing .............................. 33 ALCS testing facilities ................................ 33 Other testing facilities ................................ 34 Chapter 11. Integrity .............................. 35 ALCS features .................................. 35 Chapter 12. Security .............................. 37 ALCS features .................................. 37 Chapter 13. Installation and migration ...................... 39 Migrating from predecessor ALCS versions and releases .................... 39 Migrating from TPF ................................ 39 Installation and migration summary ........................... 40 Required hardware ................................. 41 Required software ................................. 41 Control program................................. 41 Required software for special functions ......................... 41 Recommended software .............................. 41 Acronyms and abbreviations .......................... 43 Glossary ................................... 53 Bibliography ................................. 79 iv Airline Control System Version 2: General Information Manual Figures 1. Centralized systems ............................... 2 2. Distributed systems ............................... 3 3. ALCS overview ................................ 6 4. WebSphere MQ allows ALCS to share data ....................... 9 5. Communication facilities supported by ALCS ...................... 13 6. ALCS DASD files: Overview ............................ 18 7. ALCS file address: compressing the class, type and ordinal ................. 19 8. Chains of records ............................... 21 9. Sequential file management in ALCS ......................... 23 10. Relational database access............................. 27 © Copyright IBM Corp. 2003, 2019 v vi Airline Control System Version 2: General Information Manual Tables 1. VTAM networks ................................ 14 2. ATA/IATA SLC network ............................. 14 3. Migrating to ALCS Version 2 Release 4 ........................ 39 4. Installing ALCS Version 2 Release 4 ......................... 40 © Copyright IBM Corp. 2003, 2019 vii viii Airline Control System Version 2: General Information Manual Notices References in this publication to IBM® products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: The Director of Licensing IBM Corporation 500 Columbus Avenue Thornwood, NY 10594 USA Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Department 830A 522 South Road Mail Drop P131 Poughkeepsie, NY 12601-5400 USA Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. Trademarks IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. © Copyright IBM Corp. 2003, 2019 ix x Airline Control System Version 2: General Information Manual About this book This book presents general overview and planning information for Release 4.1 of Airline Control System (ALCS) Version 2, an IBM licensed program. ALCS is one of a family of IBM programs designed to satisfy the needs of airlines and other industries with similar requirements for high-volume and high-availability transaction processing. Who should read this book This publication is intended for executives and data processing professionals wishing to choose a transaction processing system. After reading this
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]
  • 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]
  • 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]
  • Sabre Corporation (Exact Name of Registrant As Specified in Its Charter)
    ' UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D. C. 20549 FORM 10-K ~ ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended December 31, 2018 or • TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 Sabre Corporation (Exact name of registrant as specified in its charter) Delaware 001-36422 20-8647322 (State or other jurisdiction (Commission File Number) (I.R.S. Employer of Incorporation or organization) Identification No.) 3150 Sabre Drive Southlake, TX 76092 (Address, including zip code, ofprinc ipal executive offices) (682) 605-1000 (Registrant's telephone number, including area code) Securities registered pursuant to Section 12(b) of the Act: Common Stock, $0.01 par value The NASDAQ Stock Market LLC (Title of class) (Name of exchange on which registered ) Securities registered pursuant to Section 12(g) of the Act: None Indicate by check mark if the registrantis a well-known seasoned issuer, as defined in Rule 405 of the Securities Act. Yes l!I No • Indicate by check mark if the registrant is not required to file reports pursuant to Section 13 or Section 15(d) of the Act Yes • No l!I Indicate by check mark whether the registrant (1) has fi led all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.
    [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]
  • Forging the Future of Hospitality: Blockchain for Trust Now And
    Expert Insights Forging the future of hospitality Blockchain for trust now—and in a post-pandemic world In collaboration with: Experts on this topic Kurt Wedgwood Kurt leads IBM’s Blockchain North America practice for the Retail, Consumer Product and Travel industries. He helps IBM North America Blockchain clients build deeper trust in information and process Leader for Retail, Consumer execution. He is an adjunct professor, chair emeritus of Products, Travel & Transport Seattle University’s Innovation and Entrepreneurship [email protected] Board, and is working with the World Business Council for linkedin.com/in/wedgwood Sustainable Development. Kurt lives in Seattle, WA and received his MBA from the University of Chicago. Rob Grimes Robert (“Rob”) Grimes is the Founder & CEO of the IFBTA (International Food & Beverage Technology Association), International Food and Beverage a non-profit professional trade association promoting and Technology Association advancing technology and innovation for the global food Founder & CEO and beverage industries. Previously, Rob also founded [email protected] FSTEC (Foodservice Technology Conference and linkedin.com/in/rogrimes Showcase) and ConStrata Consulting & Services, which www.ifbta.org provides IT services for the global hospitality, foodservice and retail industries. Greg Land Greg serves as Global Industry Leader with global responsibility for Aviation, Hospitality, and Travel Related IBM Distinguished Industry Leader, Services industry segment. Prior to joining IBM, held Travel & Transportation leadership roles with American Airlines, Sabre, Wyndham [email protected] Hotel Group and Radius Global Travel Management, linkedin.com/in/gregland spanning a 23-year career across the travel industry. Greg holds bachelor’s degrees in Computer Science and Accounting, and an MBA from Oklahoma State University.
    [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]
  • Mobile to Mainframe Devops for Dummies®, IBM Limited Edition Published by John Wiley & Sons, Inc
    These materials are © 2015 John Wiley & Sons, Inc. Any dissemination, distribution, or unauthorized use is strictly prohibited. Mobile to Mainframe DevOps IBM Limited Edition By Rosalind Radcliffe These materials are © 2015 John Wiley & Sons, Inc. Any dissemination, distribution, or unauthorized use is strictly prohibited. Mobile to Mainframe DevOps For Dummies®, IBM Limited Edition Published by John Wiley & Sons, Inc. 111 River St. Hoboken, NJ 07030‐5774 www.wiley.com Copyright © 2015 by John Wiley & Sons, Inc. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without the prior written permission of the Publisher. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748‐6011, fax (201) 748‐6008, or online at http://www.wiley.com/go/permissions. Trademarks: Wiley, For Dummies, the Dummies Man logo, The Dummies Way, Dummies.com, Making Everything Easier, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates in the United States and other countries, and may not be used without written permission. IBM and the IBM logo are registered trademarks of International Business Machines Corporation. All other trademarks are the property of their respective owners. John Wiley & Sons, Inc., is not associated with any product or vendor mentioned in this book. LIMIT OF LIABILITY/DISCLAIMER OF WARRANTY: THE PUBLISHER AND THE AUTHOR MAKE NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THIS WORK AND SPECIFICALLY DISCLAIM ALL WARRANTIES, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE.
    [Show full text]
  • Timeline of Computer History
    Timeline of Computer History By Year By Category Search AI & Robotics (55) Computers (145)(145) Graphics & Games (48) Memory & Storage (61) Networking & The Popular Culture (50) Software & Languages (60) Bell Laboratories scientist 1937 George Stibitz uses relays for a Hewlett-Packard is founded demonstration adder 1939 Hewlett and Packard in their garage workshop “Model K” Adder David Packard and Bill Hewlett found their company in a Alto, California garage. Their first product, the HP 200A A Called the “Model K” Adder because he built it on his Oscillator, rapidly became a popular piece of test equipm “Kitchen” table, this simple demonstration circuit provides for engineers. Walt Disney Pictures ordered eight of the 2 proof of concept for applying Boolean logic to the design of model to test recording equipment and speaker systems computers, resulting in construction of the relay-based Model the 12 specially equipped theatres that showed the movie I Complex Calculator in 1939. That same year in Germany, “Fantasia” in 1940. engineer Konrad Zuse built his Z2 computer, also using telephone company relays. The Complex Number Calculat 1940 Konrad Zuse finishes the Z3 (CNC) is completed Computer 1941 The Zuse Z3 Computer The Z3, an early computer built by German engineer Konrad Zuse working in complete isolation from developments elsewhere, uses 2,300 relays, performs floating point binary arithmetic, and has a 22-bit word length. The Z3 was used for aerodynamic calculations but was destroyed in a bombing raid on Berlin in late 1943. Zuse later supervised a reconstruction of the Z3 in the 1960s, which is currently on Operator at Complex Number Calculator (CNC) display at the Deutsches Museum in Munich.
    [Show full text]
  • In the United States District Court for the District of Delaware
    Case 1:19-cv-01548-LPS Document 277 Filed 04/08/20 Page 1 of 97 PageID #: 6849 IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE UNJTED STATES OF AMERICA Plaintiff, v. C.A. No. 19-1548-LPS SABRE CORP., REDACTED PUBLIC SABRE GLBL INC., VERSION FARELOGIXINC., and (RELEASED APRIL 8, SANDLER CAPITAL PARTNERS V, L.P., 2020) Defendants. David C. Weiss, Laura D. Hatcher, and Shamoor Anis, UNITEDSTATES DEPARTMENT OF JUSTICE, Wilmington, DE Julie S. Elmer, Scott A. Westrich, Sarah P. McDonough, Robert A. Lepore, Aaron Comenetz, Brian E. Hanna, Craig W. Conrath,Dylan M. Carson, Rachel A. Flipse, Michael T. Nash, Jeremy P. Evans, Vittorio Cottafavi,Seth J. Wiener, John A. Holler, Grant A. Bermann, and Katherine A. Celeste, UNITED STATES DEPARTMENT OF JUSTICE, Washington, DC Attorneys forPlaintiff United States of America Joseph 0. Larkin and Veronica A. Bartholomew, SKADDEN, ARPS,SLATE, MEAGHER & FLOM LLP, Wilmington, DE Tara L. Reinhart and Steven C. Sunshine, SKADDEN, ARPS, SLATE, MEAGHER & FLOM LLP, Washington, DC Matthew M. Martino, Michael H. Menitove, and Evan R. Kreiner, SKADDEN, ARPS, SLATE, MEAGHER & FLOM LLP, New York, NY Attorneys forDefendants Sabre Corporation and Sabre GLBL Inc. Case 1:19-cv-01548-LPS Document 277 Filed 04/08/20 Page 2 of 97 PageID #: 6850 Daniel A. Mason, PAUL, WEISS, RIFKIND, WHARTON & GARRISON LLP, Wilmington, DE Kenneth A. Gallo, Jonathan S. Kanter, Joseph J. Bia!, and Daniel J. Howley, PAUL, WEISS, RIFKIND, WHARTON & GARRISON LLP, Washington, DC Attorneys for Defendants Farelogix Inc. and Sandler Capital Partners V, L.P. OPINION April 7, 2020 Wilmington, Delaware Case 1:19-cv-01548-LPS Document 277 Filed 04/08/20 Page 3 of 97 PageID #: 6851 INTRODUCTION The United States Department of Justice ("DOJ" or "government") filed this expedited antitrust action seeking to permanently enjoin the proposed acquisition by Defendants Sabre Corporation and Sabre GLBL 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]
  • 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]