Sun Enterprise Systems Interface 1.0 Installation

Total Page:16

File Type:pdf, Size:1020Kb

Sun Enterprise Systems Interface 1.0 Installation Sun Enterprise™ Systems Interface 1.0 Installation and User Guide With Release Notes and Reference Section Sun Microsystems, Inc. 901 San Antonio Road Palo Alto,CA 94303-4900 U.S.A. 650-960-1300 Part No. 806-5690-10 January 2001, Revision A Send comments about this document to: [email protected] Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. For Netscape Communicator™, the following notice applies: (c) Copyright 1995 Netscape Communications Corporation. All rights reserved. Sun, Sun Microsystems, the Sun logo, docs.sun.com, Sun Enterprise, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements. Federal Acquisitions: Commercial Software-Government Users Subject to Standard License Terms and Conditions. DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, Californie 94303 Etats-Unis. Tous droits réservés. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd. La notice suivante est applicable à Netscape Communicator™: (c) Copyright 1995 Netscape Communications Corporation. Tous droits réservés. Sun, Sun Microsystems, le logo Sun, docs.sun.com, Sun Enterprise, et Solaris sont des marques de fabrique ou des marques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun. CETTE PUBLICATION EST FOURNIE "EN L’ETAT" ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y COMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU’ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NE S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU. Please Recycle Contents Preface xi How This Book Is Organized xi Using UNIX Commands xii Typographic Conventions xiii UNIX Shell Prompts xiii Related Documentation xiv Ordering Sun Documentation xiv Accessing Sun Documentation Online xiv Sun Welcomes Your Comments xv 1. Release Notes 1 General Issues 1 Minimum Hardware Requirement 1 Supported Platforms 1 PCI I/O Board Limitation 2 Known Software Bugs 2 Bug ID 4373467 - prtdiag Command Does Not Show the ESI Board 2 2. Overview 3 Uses for the TCP/IP Interface Software 3 iii Uses for the Tape Emulation Software 4 Features of the Sun ESI 1.0 Software 4 Requirements for Using Sun ESI 1.0 Software 4 External Documentation 5 For Operating Channel and Devices 5 For Operating TCP/IP 5 3. Installing Sun ESI 1.0 Software 7 Gathering Configuration Information for TCP/IP Interface Software 7 Gathering Configuration Information for Tape Emulation Software 9 Sample Sun ESI Configuration Worksheets 10 Installing the Sun ESI 1.0 Software 11 4. Configuring and Testing TCP/IP Interface Software 15 Configuring the TCP/IP Interface Software 15 Determining Data Transfer Properties 15 Identifying Control Unit Addressing Parameters 16 Defining the Sun ESI Configuration File 17 Administering the Sun ESI 1.0 Software 17 Using the Sun ESI Administration Program 18 Initial Configuration and Testing of the TCP/IP Interface 18 Ensuring That Changes Take Effect in the Sun ESI Configuration File 20 Disabling or Restoring the Automatic Sun ESI Configuration 22 Configuring the TCP/IP Interface Software for Multiple Interfaces 22 Creating a Network Configuration Persistent Across System Boots 24 Removing a TCP/IP Network Interface 25 5. Configuring, Testing, and Using Tape Emulation Software 27 Configuring Tape Emulation Software 27 Identifying Control Unit Addressing Parameters 27 iv Sun Enterprise Systems Interface 1.0 Installation and User Guide • January 2001 Defining the Channel Configuration File 28 Administering the Sun ESI Software 29 Initial Configuration and Testing of Tape Emulation Devices 29 Transferring Files 30 Messages from the Mainframe 31 Mount Message 31 Verification Message 32 Dismount Command 32 System Error Message 32 A. Reference Section 35 Reference Manual (man) Pages 35 changet(1) 35 chanput(1) 35 chanadm(1M) 35 chan.conf(4) 36 chanip(7D) 36 chantape(7D) 36 esi(7D) 36 B. Troubleshooting 57 Using Diagnostics 57 Operating the Sun ESI Diagnostics 58 Indicating Errors 58 Obtaining Traces 59 C. Using Dynamic Reconfiguration (DR) With Sun ESI 1.0 Software 61 Suspending the Operating System and Sun ESI Boards 61 Removing a Sun ESI Board from the System 61 v Adding a Sun ESI Board to the System 63 D. Configuring Mainframe Information 67 Configuring Mainframe for TCP/IP Interface and Tape Emulation Using IOCP Macros 68 Defining IOCP Macros for Configuring the Mainframe 69 CHPID 69 CNTLUNIT 70 IODEVICE 71 Configuring Mainframe for TCP/IP Interface and Tape Emulation Using HCD 72 Mapping IOCP Macros to HCD 72 Defining Devices Using HCD 73 Configuring the TCP.PROFILE.TCPIP Data Set 89 Registering the Missing Interrupt Handler (MIH) 89 E. Configuring Multiple Images 91 F. Configuring Multiple Sun ESI Boards 93 G. Using JCL Scripts for Tape Emulation Software 95 vi Sun Enterprise Systems Interface 1.0 Installation and User Guide • January 2001 Tables TABLE 3-1 Summary of Configuration Information for the TCP/IP Interface 8 TABLE 3-2 Sample Sun and Mainframe Configuration Details Worksheet 10 TABLE 3-3 Sample IP Addresses Worksheet 10 vii viii Sun Enterprise Systems Interface 1.0 Installation and User Guide • January 2001 Figures FIGURE E-1 Illustration of a Multiple Image Configuration 92 FIGURE F-1 Example of IBM TCP/IP Data Set Addressing 94 ix x Sun Enterprise Systems Interface 1.0 Installation and User Guide • January 2001 Preface The Sun Enterprise Systems Interface 1.0 Installation and User Guide describes how to install, configure, and use the Sun Enterprise™ Systems Interface (ESI) software that supports the Sun Enterprise Systems Interface board. The manual includes Release Notes in Chapter <$elemparanumonly and Reference Manual pages in Appendix <$elemparanumonly<$elemtext. This document is intended for the user who installs, configures, and uses Enterprise Systems Interface 1.0 software to transfer files to a Sun server from a mainframe and from a mainframe to a Sun server. This user should have a working knowledge of UNIX® systems, particularly those based on the Solaris™ operating environment. The document is also of interest to the mainframe system programmer who is configuring the mainframe for use with the Sun server. This user should be an experienced mainframe professional with basic TCP/IP administration skills. How This Book Is Organized The Sun Enterprise Systems Interface 1.0 Installation and User Guide is organized as follows: Chapter <$elemparanumonly contains Release Notes. Chapter <$elemparanumonly is an overview of the Sun Enterprise Systems Interface 1.0 software.
Recommended publications
  • Status and Projections of the NAS Program Frank R
    https://ntrs.nasa.gov/search.jsp?R=19870015491 2020-03-20T10:46:12+00:00Z View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by NASA Technical Reports Server NASA Technical Memorandum 88339 . , Status and Projections of the NAS Program Frank R. Bailey EECGECTIOIS CP f Avail: NTlS P87-24924 CSCL 09B 63 Unclad 0080153 July 1986 National Aeronautics and Space Administration ~~ ~ NASA Technical Memorandum 88339 Status and Projections of the NAS Program Frank R. Bailey, Ames Research Center, Moffett Field, California July 1986 NASA National Aeronautics and Space Adminlstratlon Ames Research Center Moffett Field. California 94035 STATUS AND PROJECTIONS OF THE NAS PROGRAM by Dr. F. Ron Bailey to be presented at the SYMPOSIUM ON FUTURE DIRECTIONS OF COMPUTATIONAL MECHANICS ASME Winter Annual Meeting December 7-12, 1986 Anaheim, California ABSTRACT NASA's Numerical Aerodynamic Simulation (NASI Program has completed devel- opment of the initial operating configuration of the NAS Processing System Net- work (NPSN). This is the first milestone in the continuing and pathfinding effort to provide state-of-the-art supercomputing for aeronautics research and development. The NPSN, available to a nation-wide community of remote users, provides a uniform UNIX 1 environment over a network of host computers ranging from the new Cray-2 supercomputer to advanced scientific workstations. This system, coupled with a vendor-independent base of common user interface and network software, presents a new paradigm for supercomputing environments. Presented here is the background leading to the NAS Program, its programmatic goals and strategies, technical goals and objectives, and the development activ- ities leading to the current NPSN configuration.
    [Show full text]
  • Einführung in Z/OS Und OS/390
    Einführung in z/OS und OS/390 Dr. rer. nat. Paul Herrmannn Prof. Dr.-Ing. Wilhelm G. Spruth WS 2006/2007 Teil 3 z/OS Betriebssystem es 0101 ww6 wgs 09-99 System z und S/390 Betriebssysteme z/OS IBM große Installationen (OS/390, MVS) z/VSE IBM mittelgroße Installationen z/VM IBM Virtualisierung, Software Entwicklung TPF IBM spezialisierte Transaktionsverarbeitung UTS 4 Amdahl based on System V, Release 4 (SVR4) OSF/1 Hitachi Open System Foundation Unix z/Linux Public Domain Alle System z bzw. S/390 Betriebssysteme sind Server Betriebssysteme, optimiert für den Multi-User Betrieb es 0521z ww6 wgs 09-99 Transaction Processing Facility TPF 13. Oktober 2006. Die Firma Worldspan, ein weltweiter Anbieter von Reise-Reservierungs- systemen, hat sich für den Einsatz von sechs IBM System z9 Enterprise Class (EC) Mainframe-Servern entschieden. Worldspan will damit sein Angebot an elektronischen Datendiensten erweitern, um circa 700 Anbietern von Reiseangeboten und Millionen von Reisenden weltweit eine gemeinsame Plattform anbieten zu können. Worldspan setzt die neuen IBM System z9 EC Server ein, um sowohl Reisebüros als auch Anbietern von Online-basierten Reisediensten die Möglichkeit zur Nutzung des weltweiten Global Distribution System (GDS) zu geben, über das zum Beispiel die Bestellung und Buchung von Reiseprodukten von Flugzeugtickets, Hotels, Mietwagen und andere Reisedienstleistungen durchgeführt wird. Durch die Nutzung der Software „IBM Transaction Processing Facility“ (TPF) ist Worldspan in der Lage, 17.000 Kundenanfragen pro Sekunde auf
    [Show full text]
  • Joseph S. Mertz Jr. EDUCATION
    Jan 2020 Joseph S. Mertz Jr. H. John Heinz III College & Dietrich College of Humanities and Social Sciences Carnegie Mellon University Pittsburgh, PA 15213-3890 Phone: (412) 268-2540 Email: [email protected] EDUCATION: 1995 Carnegie Mellon University Ph.D. in Engineering and Public Policy 1983 University of Southern California M.S. in Computer Science 1982 Pennsylvania State University B.S. in Computer Science ACADEMIC APPOINTMENTS: Carnegie Mellon University 2018 – present: Director - Information Systems Program 2015 – present: Teaching Professor Joint 50/50 appointment: H. John Heinz III College Dietrich College of Humanities & Social Sciences Information Systems Program 2010 – 2015: Associate Teaching Professor Joint 50/50 appointment: H. John Heinz III College Dietrich College of Humanities & Social Sciences Information Systems Program 2005 – 2010: Associate Teaching Professor Joint 50/50 appointment: H. John Heinz III College School of Computer Science Spring 2009: Associate Teaching Professor Carnegie Mellon Qatar Computer Science Spring 2008: Associate Teaching Professor Carnegie Mellon Qatar Computer Science 2002 – 2005: Associate Teaching Professor Joint 50/50 appointment: Mertz-CV H. John Heinz III School of Public Policy & Management School of Computer Science 1996 – 2002: Co-Director Center for University Outreach 1994 – 1996: Post Doctoral Fellow Center for Innovation in Learning 1988 – 1995: Graduate Research Assistant Department of Engineering & Public Policy University of Puerto Rico 1986 – 1987: Visiting Professor Department of Electrical & Computer Engineering Illinois Benedictine College 1984: Adjunct Instructor Computer Science AWARDS: Mark Gelfand Service Award for Educational Outreach – 2012 Annual University honor for sustained, effective community service with academic coursework to enhance learning, and teach social responsibility. Nominated for the Martcia Wade Teaching Award – 2012 H.
    [Show full text]
  • How Attackers Break Programs, and How to Write Programs More Securely
    How Attackers Break Programs, and How To Write Programs More Securely Matt Bishop Department of Computer Science University of California at Davis Davis, CA 95616-8562 United States of America email: [email protected] www: http://seclab.cs.ucdavis.edu/~bishop phone: +1 (530) 752-8060 © 2002 by Matt Bishop This page deliberately left blank. That is, this page would have been blank except that we had to put the notice "this page deliberately left blank" on it. Otherwise, you might have seen the blank page and worried that someone left a page out of your booklets. So, we put a note on the blank page to assure you that no-one forgot to put something on this page; indeed, we intended for it to be blank. But we could not live up to our intentions, for the reason stated above, so we couldn't put a blank page in here. We had to put a page with some writing on it. So we couldn't put the notice "this page deliberately left blank" because it's not true and, if we couldn't tell when a page is blank, you'd doubt the veracity of everything we did. So we wrote this paragraph to ... oh, heck, forget it. Table of Contents sections slides Overview..................................... 1— 13 Attacking Programs ........................... 14—123 Overview .......................14 — 20 Users and Privilege ...............21 — 29 Environment ....................30 — 48 Buffer Overflow ..................49 — 70 Numeric Overflow ................71 — 76 Validation and Verification .........77 — 92 Race Conditions..................93—112 Denial of Service ............... 113—121 Environment .................. 122—123 Writing Better Programs ......................124—379 Overview ....................
    [Show full text]
  • 17. Websphere Application Server
    17. WebSphere Application Server 17.1 z/OS as a Unix System 17.1.1 Unix Betriebssysteme Welche Server-Betriebssysteme findet man in der Praxis ? • Windows, verschiedene Varianten • Unix, verschiedene Varianten • i-Series, OS/400 • zSeries Betriebssysteme – z/OS, z/VM, z/VSE, TPF Welche wesentlichen Unix Varianten existieren ? • HP/UX • SunSolaris • IBM AIX • Siemens Sinix Unix Systeme sind weitestgehend, • MacOS (BSD) aber nicht 100 % kompatibel • Linux, einschließlich zLinux • z/OS Unix System Services Führende Unix Großrechner sind: • Integrity Superdome von HP mit Itanium Prozessoren und dem HP-UX Betriebssystem • M9000 bzw. SPARC M5-32 Server von Oracle mit Sparc Prozessoren und dem Solaris Betriebssystem. Ein verwandtes Produkt wird von der Firma Fujitsu unter dem Namen „SPARC Enterprise Server“ vertrieben. • System p von IBM mit PowerPC Prozessoren und dem AIX Betriebssystem Neben den proprietären Unix Dialekten ist auf diesen Rechnern auch Linux verfügbar. Performance Unix versus z/OS Die I/O Leistung eines Rechners wird gemessen in der Anzahl von I/O Operationen pro Sekunde unter realistischen Betriebsbedingungen. Konkrete Untersuchungen sind nie veröffentlicht worden, aber es wird allgemein angenommen, dass die z/OS I/O Leistung vielleicht um einen Faktor 3 - 10 höher als die I/O Leistung von großen Unix Rechnern wie Superdome und M9000 ist. 17-1 17.1.2 Was definiert ein Unix System ? Unix wurde ursprünglich von Ken Thompson und Dennis Ritchie an den Bell Telephone Laboratories für Rechner der Digital Equipment Corporation (DEC) entwickelt und 1971 erstmalig im praktischen Betrieb eingesetzt. Schon bald entstanden (fast) kompatible Implementierungen für andere Rechner. Aus Bemühungen um einen einheitlichen Unix Standard entstand die Portable Operating System Interface (POSIX).
    [Show full text]
  • Les Routeurs Multicast
    Raccorder son réseau d’entreprise à l’Internet Alexandre Fenyö, Frédéric Le Guern, Samuel Tardieu To cite this version: Alexandre Fenyö, Frédéric Le Guern, Samuel Tardieu. Raccorder son réseau d’entreprise à l’Internet. Editions Eyrolles, 1997, 9782212089516. hal-01649131 HAL Id: hal-01649131 https://hal.archives-ouvertes.fr/hal-01649131 Submitted on 3 Jul 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution - NonCommercial - ShareAlike| 4.0 International License Remerciements Nous tenons tout particulierement` a` remercier Philippe DAX, Nadine RICHARD et Ahmed SERHROUCHNI pour les precieux´ conseils qu’ils nous ont prodigues´ durant la redaction´ de cet ouvrage ainsi que pour leur patience lors des multiples relectures. Les noms d’utilisateurs fictifs presents´ dans les exemples de ce livre nous ont et´ e´ gracieu- sement pretˆ es´ par Luc BEURTON et Stoned ELIPOT, qui nous ont egalement´ aides´ par leurs pertinentes contributions. Le chapitre sur le travail cooperatif´ a ben´ efici´ e´ de l’aide de Yan PUJANTE, auteur d’un me-´ moire de recherche sur le sujet. Nous tenons egalement´ a` remercier Bruno BEAUGRAND, Raphael¨ LUTA et Philippe MEU- NIER qui ont eu la gentillesse de nous procurer les documentations techniques dont nous avions besoin.
    [Show full text]
  • The Long Road to 64 Bits
    DOI:10.1145/1435417.1435431 Double, double toil and trouble —Shakespeare, Macbeth, Act 4, Scene 1 BY JOHN MASHEY The Long Road To 64 Bits SHAKESpeare’S WORDS OFTEN cover circumstances beyond his wildest dreams. Toil and trouble accompany major computing transitions, even when people plan ahead. Much of tomorrow’s software will still be driven by decades-old decisions. Past decisions have unanticipated side effects that last decades and can be difficult to undo. ranging from high-level strategies down For example, consider the overly to programming specifics. long, often awkward, and sometimes contentious process by which 32-bit Fundamental Problem (late 1980s) microprocessor systems evolved into Running out of address space is a long 64/32-bitters needed to address larger tradition in computing, and often quite storage and run mixtures of 32- and 64- predictable. Moore’s Law grew DRAM bit user programs. Most major general- approximately four times bigger every purpose CPUs now have such versions, three to four years, and by the mid- so bits have “doubled,” but “toil and 1990s, people were able to afford 2GB trouble” are not over, especially in soft- to 4GB of memory for midrange micro- ware. processor systems, at which point sim- This example illustrates the interac- ple 32-bit addressing (4GB) would get tions of hardware, languages (especial- awkward. Ideally, 64/32-bit CPUs would ly C), operating system, applications, have started shipping early enough standards, installed-base inertia, and (1992) to have made up the majority of industry politics. We can draw lessons the relevant installed base before they Chronology: Multiple E K Interlocking RANS IBM S/360 F EN 32-bit, with 24-bit B Threads addressing (16MB total) BY H P of real (core) memory HOTOGRA P 1964 1965 JANUary 2009 | VOL.
    [Show full text]
  • Validated Products List: Programming Languages, Database Language
    NISTIR 469 (Supersedes NISTIR 4623) VALIDATED PRODUCTS LIST 1991 No. 4 Programming Languages Database Language SQL Graphics ®OSIP Judy B. Kailey POSIX Editor U.S. DEPARTMENT OF COMMERCE National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 October 1991 (Supersedes July 1991 issue) U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director — QC 100 .U56 NIST //4690 1991 V C.2 NISTIR 4690 (Supersedes NISTIR 4623) - ' J JF VALIDATED PRODUCTS LIST 1991 No. 4 Programming Languages Database Langucige SQL Graphics GOSIP Judy B. Kailey POSIX Editor U.S. DEPARTMENT OF COMMERCE National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 October 1991 (Supersedes July 1991 issue) U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director FOREWORD The Validated Products List (formerly called the Validated Processor List) is a collection of registers describing implementations of Federal Information Processing Standards (FIPS) that have been tested for conformance to FIPS. The Validated Products List also contains information about the organizations, test methods and procedures that support the validation programs for the FIPS identified in this document. The Validated Products List is updated quarterly. TABLE OF CONTENTS 1. INTRODUCTION 1-1 1.1 Purpose 1-1 1.2 Document Organization 1-1 1.2.1 Programming Languages 1-1 1.2.2 Database Language SQL 1-2 1.2.3 Graphics 1-2 1.2.4 GOSIP 1-2 1.2.5 POSIX 1-2 1.2.6 FIPS Conformance Testing Products 1-2 2.
    [Show full text]
  • Amdahl 580 Series
    70C-Q.Ht.tM-'l" Computers Amdahl 580 Series MANAGEMENT SUMMARY Amdahl Corporation's 5890 Series is posi­ UPDATE: As a manufacturer of IBM plug-compatible tioned as a price/performance alternative to products, Amdahl has scaled profitable peaks andfallen into the IBM 3090 Series. The older Amdahl 580 some less than profitable valleys. At the moment, Amdahl is models are now in "limited new produc­ perched on another peak. The volume shipment ofAmdahl tion," according to Amdahl. 5890-300 mainframes, which compete against the IBM 3090, in addition to the sale ofdouble-capacity 6380E disks MODELS: 5840, 5850, 5860, 5867, 5868, made 1986 a financially satisfying year for Amdahl, to say 5870, 5880, and 5890-190E, -200E, the least. After coming off a very profitable 1986, Amdahl -300E, -400E, and -600E. responded to IBM's January 3090 liE" model announce­ CONFIGURATION: One, two, three, or four ments with the February introduction of a new three-way CPUs, up to 512MB of main memory, and up 5890-400E processor and the announcement ofperformance to 128 I/O channels. enhancements to existing 5890 models. Similar to IBM, COMPETITION: IBM 4381, IBM 308X, Amdahl also appended an liE" to the end ofeach ofits new IBM 3090, NAS AS/XL Series. and existing 5890 IBM-compatible machines. In January, PRICE: Prices range from $1,270,000 to Amdahl also announced a new 5890-190 uniprocessor $12,220,000. which has since been upgraded to a 5890.. ']90E. The new Amdahl 5890-190E, the first single-processor offering in the model line, establishes a new 5890 entry point for Amdahl CHARACTERISTICS 580 users contemplating a move to Amdahfs latest main­ frame generation.
    [Show full text]
  • Multithreading the Sunos Kernel
    BeyondMultiprocessing: Multithreadingthe SUnOSKernel t. 4. Fyt4olg S, R. Kleimaq S. Børton,R. Faulkner,A. Shivalingiah, M. Smith,D. Stein,J. Voll, M. Weeks,D. Williams- SunSoft,[nc. ABSTRACT Preparingthe SUnOSiSVR4kernel for today'schallenges: symmetric multiprocessing, multi-th¡eadedapplications, real-time, and multimedia,led to the incorporationof several innovativetechniques. In particular,the kernelwas re-structuredaround threads. Threads are usedfor most asynchronousprocessing, including interrupts. The resultingkernel is fully preemptibleand capableof real-timeresponse. The combinationprovides a robustbase for highly concurrent,responsive operation. Introduction having only a small data structure and a stack. Switchingbetween When we started to investigateenhancements kernelthreads does not requirea changeof virtual memory to the SunOSkernel to supportmultiprocessors, we addressspace information, so it is relatively realized that we wanted to go further than merely inexpensive.Kernel threadsare fully preemptible addinglocks to the kernel and keepingthe userpro- and may be scheduledby any of the scheduling cessmodel unchanged.It was importantfor the ker- classesin the system,including the real-time(fixed priority) nel to be capableof a high degreeof concurrencyon class. Sinceall other exe- cution entities tightly coupled symmetricmultiprocessors, but it are built using kernel th¡eads,they representa fully preemptible, was also a goal to supportmore thanone threadof real-time"nucleus" within the kernel. controlwithin a userprocess. These threads must be capableof executingsystem calls and handlingpage Kernel th¡eads use synchronizationprimitives faults independently. On multiprocessorsystems, that supportprotocols for preventingpriority inver- theseth¡eads of control must be capableof running sion, so a thread'spriority is determinedby which concurently on different processors.[Powell 1991] activitiesit is impedingby holdinglocks as well as describedthe user-visiblethread architecture.
    [Show full text]
  • Unix System Services
    Betriebssysteme it-Akademie Bayern z/OS und OS/390 Lehrgang 2009 Prof. Dr.-Ing. Wilhelm G. Spruth Teil 12 z/OS Unix System Services bs 1001 ww6 © copyright W. G. Spruth, 10-2000 wgs 03-95 Unix Welche Betriebssysteme findet man in der Praxis ? • Windows, verschiedene Varianten • Unix, verschiedene Varianten • i-Series OS/400 • zSeries Betriebssysteme – z/OS, zVM, zVSE, TPF Welche wesentlichen Unix Varianten existieren ? • HP/UX • SunSolaris • IBM AIX • Siemens Sinix • MacOS (BSD) • Linux, einschließlich zLinux • z/OS Unix System Services Literatur OS/390 Unix System Services. IBM Form No. SC28- 1891-8 Jürgen Gulbins: “Unix”. Springer Verlag , 3. Auflage, 1988. ISBN 3-540-19248-4 Gutes Handbuch, um mit den einzelnen Unix Shell befehlen zu arbeiten. History of Unix Operating Systems z/OS vs. Unix OS/390 mehrere 1000 E/A Operationen / s Unix mehrere 100 E/A Operationen / s Native Unix Betriebssysteme für S/390 Amdahl UTS (Universal Time Sharing System) Marktführer, < 300 Installationen Hitachi HI-OSF/1-M IBM AIX/ESA (nicht mehr verfügbar) z/OS Unix System Services früher als Open Edition MVS (OMVS) bezeichnet 1100 Unix API´s es 0519z ww6 wgs 09-99 The work on Portable Operating Systems Interface (Posix) started out as an effort to standardize UNIX and was performed by a work group under IEEE (Institute of Electrical and Electronic Engineers). What they defined was an application programming interface which could be applied not only to UNIX systems but to other operating systems, like OS/390. Posix is now a set of standards that define common interfaces across operating systems.
    [Show full text]
  • AUUGN Volume 11, Number 3 June 1990
    AUUGN Volume 11, Number 3 June 1990 The Australian UNIX* systems User Group Newsletter Volume 11 Number 3 June 1990 CONTENTS AUUG General Information .......................... 3 Editorial ................................ 4 AUUG Institutional Members ........................ 6 Letters tothe Editor ................. ACSnet Survey .......................... 10 SESSPOOLE Information ...................... 13 Call For Papers: AFUU Convention UNIX ’91 .............. 14 AUUG Book Club - Reviews & Order Form ............... 17 Perth Summer’90 Technical Meeting Report ................ 23 Using UNIX as a Persistent Programming Environment (From Summer’90 Victoria) . 25 UNIX System V Release 4 and OSF/1 (From Summer’90 Sydney) ....... 30 Optimizing The B5FS File System .................... 38 Open Buzzwords And NPA’s .................. 46 Bulgeria In Turmoil ......................... 48 USENIX Association News For AUUG Members ............. 5O AUUGN Back Issues ........................ 54 WAUG Information ................. ¯ . 55 AUUG Membership Information .................. 56 AUUG Forms .......................... 57 AUUGN 1 Vol 11 No 3 Copyright © 1990 AUUG Incorporated. All rights reserved. AUUGN is the journal of the Australian UNIX1 systems User Group (AUUG Incorporated). Copying without fee is permitted provided that copies are made without modification, and are not made or distributed for commercial advantage. Credit to AUUGN and the author must be given. Abstracting with credit is permitted. No other reproduction is permitted without prior consent of AUUG Incorporated. 1 UNIX is a registered trademark of AT&T in the USA and other countries. Vol 11 No 3 2 AUUGN AUUG General Information Memberships and Subscriptions Membership, Change of Address, and Subscription forms can be found at the end of this issue. All correspondence concerning membership of the AUUG should be addressed to:- The AUUG Membership Secretary P.O. Box 366 Phone: (02) 361 5994 Kensington, N.S.W.
    [Show full text]