Application Programming Guide

Total Page:16

File Type:pdf, Size:1020Kb

Application Programming Guide Airline Control System Version 2 IBM Application Programming Guide Release 4.1 SH19-6948-20 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page xiii. 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, 2016. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures .................................... ix Tables .................................... xi Notices ................................... xiii Programming interface information ........................... xiii Trademarks ................................... xiv About this book ................................ xv Who should read this book .............................. xv How this book is organized .............................. xv ALCS services .................................. xvi TPF compatibility ................................. xvii Note on the example code .............................. xvii Chapter 1. Overview of ALCS .......................... 1 1.1 What ALCS provides ............................... 1 1.2 Agent sets ................................... 2 1.3 Functions performed by ALCS ............................ 2 1.4 Processing a message ............................... 3 1.5 Using information from previous messages ........................ 6 1.6 Application programs in ALCS ............................ 6 1.7 Direct access files ................................ 8 1.7.1 Fixed-file records ............................... 8 1.7.2 Pool-file records ............................... 9 1.7.3 Chains of pool-file records ........................... 10 1.7.4 Recovering long-term pool-file records ....................... 11 1.7.5 Application global area............................. 12 1.7.6 General files and general data sets ......................... 12 1.7.7 Virtual file access............................... 13 1.8 Sequential files ................................. 13 1.9 Communication with users, other systems, and other applications ................ 13 1.10 ALCS applications ............................... 14 Chapter 2. Communication ........................... 15 2.1 Communication facilities .............................. 15 2.2 Receiving input messages ............................. 16 2.3 Validating input data ............................... 18 2.4 Sending response messages to the originating terminal.................... 18 2.5 Sending unsolicited messages ............................ 18 2.6 Message formats ................................ 19 2.7 APPC communication calls and conversation services .................... 19 2.7.1 ZSTAT message counts and data collection statistics ................... 19 2.7.2 Program preparation ............................. 19 2.7.3 Including CPI-C calls in application programs ..................... 19 2.7.4 Including APPC/MVS calls in application programs ................... 21 2.7.5 APPC/MVS calls with asynchronous notification of completion ............... 23 2.7.6 Ending the conversation ............................ 24 2.8 Message Queue Interface (MQI) ........................... 25 2.8.1 ZSTAT message counts and data collection statistics ................... 26 2.8.2 Program preparation ............................. 26 2.8.3 Including MQI calls in application programs ..................... 26 2.8.4 MQI calls with asynchronous notification of completion.................. 27 2.8.5 Closing MQI objects.............................. 30 © Copyright IBM Corp. 2003, 2016 iii 2.9 Optimized Local Adapters (OLA) for WebSphere Application Server ............... 30 2.9.1 WAS Bridge ................................ 30 2.9.2 ZSTAT message counts and data collection statistics ................... 31 2.9.3 Program preparation ............................. 31 2.9.4 Including OLA calls in application programs ..................... 31 2.9.5 Testing the return code ............................. 32 2.9.6 Unregistering and releasing connection handles .................... 32 2.10 3270 Screen mapping support............................ 32 2.11 TCP/IP support ................................ 33 Chapter 3. Data in ALCS ............................ 37 3.1 Using direct access files .............................. 37 3.1.1 File addresses ................................ 37 3.1.2 Standard record header............................. 38 3.2 Reading and writing DASD records .......................... 39 3.2.1 Reading DASD records............................. 40 3.2.2 Writing DASD records ............................. 41 3.2.3 Sequential files ............................... 42 3.3 Serialization .................................. 42 3.3.1 Serialization - forcing exclusive access to resources ................... 44 3.3.2 Serializing access to the application global area..................... 45 3.3.3 SYNCC monitor-request macro and global C function ................... 51 3.3.4 ALCS services for accessing DASD records ...................... 52 3.3.5 Summary of ALCS services for DASD processing .................... 53 3.3.6 Offline access to general files and general data sets ................... 54 3.4 Using sequential files ............................... 54 3.4.1 System sequential files ............................. 55 3.4.2 Real-time sequential files ............................ 55 3.4.3 General sequential files............................. 55 3.4.4 Several entries using the same general sequential file................... 55 3.4.5 ALCS services for sequential file processing ...................... 57 3.4.6 Summary of ALCS services for sequential files ..................... 57 3.5 Global records and fields.............................. 58 3.5.1 Global directories .............................. 58 3.5.2 Keypointing global records ........................... 59 3.5.3 Logical global records ............................. 59 3.5.4 Using globals - attention ............................ 60 3.5.5 Global area serialization ............................ 61 3.5.6 C functions for processing globals ......................... 62 3.5.7 How a C language application program accesses the global area ............... 62 3.5.8 ALCS services for global area handling ....................... 64 3.6 Global area protection............................... 64 3.6.1 Global area protect key............................. 65 3.6.2 Using global area protection ........................... 65 3.7 Using Structured Query Language (SQL) ........................ 66 3.7.1 Preparation................................. 67 3.7.2 Making SQL calls .............................. 67 3.7.3 Distributing application logic across several programs .................. 68 3.8 Designing databases for use with ALCS......................... 68 3.8.1 Performance and design ............................ 68 3.8.2 TPF Database Facility (TPFDF) .......................... 69 3.8.3 Portability ................................. 69 3.9 Organizing data................................. 70 3.9.1 Standard structures .............................. 70 3.9.2 TPF Database Facility (TPFDF) .......................... 70 3.10 Record classes ................................. 70 3.10.1 Fixed files ................................. 71 3.10.2 Pool files ................................. 71 3.10.3 Short-term pool file ............................. 72 3.10.4 Long-term pool file ............................. 72 3.10.5 Choosing which class of record to use ....................... 72 iv Airline Control System Version 2: Application Programming Guide 3.11 Protecting data................................. 73 3.12 Commit and backout .............................. 74 3.12.1 Single-phase commit ............................. 74 3.12.2 Two-phase commit .............................. 75 3.12.3 ALCS commit and backout services ........................ 75 3.12.4 Keeping a transaction log ........................... 75 3.12.5 Sequential update technique .......................... 75 3.12.6 Why ALCS does not provide a synchpoint manager................... 77 3.12.7 Other considerations ............................. 78 3.13 Utility programs ................................ 78 Chapter 4. The entry control block (ECB) and other entry storage .......... 81 4.1 Format of the ECB ................................ 81 4.2 ECB work areas 1 and 2 .............................. 82 4.2.1 Work area fields ............................... 83 4.3 ECB local program work area ............................ 84 4.4 ECB data levels and storage levels .......................... 85 4.4.1 ECB data levels ............................... 85 4.4.2 ECB storage levels .............................. 86 4.5 Entry origin fields ................................ 87 4.6 User register save areas .............................. 87 4.6.1
Recommended publications
  • On-Line Computing with a Hierarchy of Processors
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science December 1968 On-Line Computing With a Hierarchy of Processors Richard P. Morton University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Richard P. Morton, "On-Line Computing With a Hierarchy of Processors", . December 1968. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-69-13. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/804 For more information, please contact [email protected]. On-Line Computing With a Hierarchy of Processors Abstract Time shared computer systems have been based upon the two techniques of multiprogramming and swapping. Multiprogramming is based on restricting each program to a portion of the total computer memory. Swapping requires considerable overhead time for loading and unloading programs. To alleviate the size restriction due to multiprogramming, segmentation is employed, resulting in fact in vastly increased swapping. A new system architecture is proposed for time shared computing that alleviates the high overhead or program size restriction. It utilizes a hierarchy of processors, where each processor is assigned tasks on the basis of four factors: interactive requirements, frequency of use, execution time, and program length. In order to study the hierarchical approach to system architecture, the Moore School Problem Solving Facility (MSPSF) was built and used. The study of the manner of operation and the reactions of the users clarified and defined the Hierarchy of Processors system architecture. The Moore School Problem Solving Facility was implemented on second generation equipment, the IBM 7040, and therefore it is not possible to adequately compare the efficiency with third generation computers operating in a swapping mode.
    [Show full text]
  • Data Definition Language
    1 Structured Query Language SQL, or Structured Query Language is the most popular declarative language used to work with Relational Databases. Originally developed at IBM, it has been subsequently standard- ized by various standards bodies (ANSI, ISO), and extended by various corporations adding their own features (T-SQL, PL/SQL, etc.). There are two primary parts to SQL: The DDL and DML (& DCL). 2 DDL - Data Definition Language DDL is a standard subset of SQL that is used to define tables (database structure), and other metadata related things. The few basic commands include: CREATE DATABASE, CREATE TABLE, DROP TABLE, and ALTER TABLE. There are many other statements, but those are the ones most commonly used. 2.1 CREATE DATABASE Many database servers allow for the presence of many databases1. In order to create a database, a relatively standard command ‘CREATE DATABASE’ is used. The general format of the command is: CREATE DATABASE <database-name> ; The name can be pretty much anything; usually it shouldn’t have spaces (or those spaces have to be properly escaped). Some databases allow hyphens, and/or underscores in the name. The name is usually limited in size (some databases limit the name to 8 characters, others to 32—in other words, it depends on what database you use). 2.2 DROP DATABASE Just like there is a ‘create database’ there is also a ‘drop database’, which simply removes the database. Note that it doesn’t ask you for confirmation, and once you remove a database, it is gone forever2. DROP DATABASE <database-name> ; 2.3 CREATE TABLE Probably the most common DDL statement is ‘CREATE TABLE’.
    [Show full text]
  • Origins of Operating Systems OS/360 Martin Grund
    Origins of Operating Systems OS/360 Martin Grund HPI Table of Contents ● IBM System 360 ● Functional Structure of OS/360 ● Virtual Machine Time Sharing Juni 2006 Origins of Operating Systems - OS/360 2 Martin Grund Welcome to Big Blue Juni 2006 Origins of Operating Systems - OS/360 3 Martin Grund IBM System 360 ● In 1964 IBM announced the IBM-360 family for computers ● All machines, despite their differences, had the same user instruction set ● Different operating systems available for these machines ● Only midrange and high-end system run OS/360 ● IBM introduced the new term of hardware architecture ● In 1970 IBM announced System 370 with hardware virtual memory support Juni 2006 Origins of Operating Systems - OS/360 4 Martin Grund IBM System 360 ● High-end machines established 32 bit as standard for computers ● Virtual Memory Support – hardware support for dynamic address translation ● Within ten years S/360 achieved standard status ● Flashback prices: ● 1970 – $279/MB hard disk ● 1980 - $35/MB hard disk | $50.000 /MB DRAM Juni 2006 Origins of Operating Systems - OS/360 5 Martin Grund IBM System 360 Specials ● Introduced 8bit entities ● Introduction of 32 or 64 bit floating point words based on a hexadecimal base ● Variable length strings using length field in the first byte ● All registers are universal registers – accumulators as well as address registers ● Registers use 32 bit, 24 bit for addressing -> 16MB Juni 2006 Origins of Operating Systems - OS/360 6 Martin Grund IBM S/360 - Pictures Juni 2006 Origins of Operating Systems -
    [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]
  • 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]
  • 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]
  • IBM Application System/400 System/38-Compatible COBOL User's Guide and Reference
    IBM IBM Application System/400 SC09-1814-00 System/38-Compatible COBOL User’s Guide and Reference Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page xv. First Edition (June 1994) This edition applies to the System/38-Compatible feature of the IBM* ILE* COBOL/400* licensed program, (Program 5763-CB1), Version 3 Release 0 Modification 5, and to all subsequent releases and modifications until otherwise indi- cated in new editions. Make sure you are using the proper edition for the level of the product. Order publications through your IBM representative or the IBM branch serving your locality. Publications are not stocked at the address given below. A form for readers’ comments is provided at the back of this publication. If the form has been removed, you may address your comments to: IBM Canada Ltd. Laboratory Information Development 2G/345/1150/TOR 1150 Eglinton Avenue East, North York, Ontario, Canada M3C1H7 You can also send your comments by facsimile (attention: RCF Coordinator), or you can send your comments elec- tronically to IBM. See "Communicating your Comments to IBM" for a description of the methods. This page imme- diately precedes the Readers' Comment Form at the back of this publication. When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1994. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
    [Show full text]
  • Preparation of Papers for AIAA Technical Conferences
    NASA KSC – Internship Final Report Unit Testing and Remote Display Development Nicholas Costa Kennedy Space Center Computer Science USRA Summer Session 18 07 2014 NASA Center 1 18/7/2014 NASA KSC – Internship Final Report Unit Testing and Remote Display Development Nicholas Costa Denison University, Granville, Ohio, Abstract The Kennedy Space Center is currently undergoing an extremely interesting transitional phase. The final Space Shuttle mission, STS-135, was completed in July of 2011. NASA is now approaching a new era of space exploration. The development of the Orion Multi- Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) launch vehicle that will launch the Orion are currently in progress. An important part of this transition involves replacing the Launch Processing System (LPS) which was previously used to process and launch Space Shuttles and their associated hardware. NASA is creating the Spaceport Command and Control System (SCCS) to replace the LPS. The SCCS will be much simpler to maintain and improve during the lifetime of the spaceflight program that it will support. The Launch Control System (LCS) is a portion of the SCCS that will be responsible for launching the rockets and spacecraft. The Integrated Launch Operations Applications (ILOA) group of SCCS is responsible for creating displays and scripts, both remote and local, that will be used to monitor and control hardware and systems needed to launch a spacecraft. It is crucial that the software contained within be thoroughly tested to ensure that it functions as intended. Unit tests must be written in Application Control Language (ACL), the scripting language used by LCS.
    [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]
  • Rise of the Intelligent Machines in Healthcare March 2, 2016
    Rise of the Intelligent Machines in Healthcare March 2, 2016 Kenneth A. Kleinberg, FHIMSS Managing Director, Research & Insights The Advisory Board Company Conflict of Interest Kenneth A. Kleinberg, MA Has no real or apparent conflicts of interest to report. Agenda • Roundtable Learning Objectives • Overview of Intelligent Computing • Use in Other Industries • Uses in Health Care • Challenges and Futures • Roundtable Questions/Discussion • Summary/Wrap-Up Learning Objectives • Identify what advances in intelligent computing are having the greatest effect on other industries such as transportation, retail, and financial services, and how these advances could be applied to healthcare • Compare the types of technological approaches used in intelligent computing, such as inferencing, constraint-based reasoning, neural networks, and machine learning, and the types of problems they can address in healthcare • Identify examples of the application of intelligent computing in healthcare and the Internet of Things (IoT) that are already deployed or are in development and the benefits they provide, such as robotic assistants, smart pumps, speech interfaces, scheduling systems, and remote diagnosis • Recognize the workflow, workforce, and cultural changes that will need to occur in a world of intelligent machines, such as the morphing or elimination of job roles, comparisons of human to computer performance, and the reliance, risks and benefits of use of intelligent systems • Discuss the IT implications and how healthcare industry professionals can
    [Show full text]