Tru64 UNIX Guide to the POSIX Threads Library

Total Page:16

File Type:pdf, Size:1020Kb

Tru64 UNIX Guide to the POSIX Threads Library Tru64 UNIX Guide to the POSIX Threads Library Order Number: AA–RH9RB–TE April 2000 This guide reviews the principles of multithreaded programming, as reflected in the IEEE® POSIX® 1003.1-1996 standard, and provides implementation guidelines and reference information for the Compaq® Multithreading Run-Time Library. Revision/Update Information: This guide supersedes the Guide to DECthreads, printed July 1999. Product Version: Tru64 UNIX Version 5.0A or higher Compaq Computer Corporation Houston, Texas © 2000 Compaq Computer Corporation. All rights reserved. COMPAQ and the Compaq logo are registered in the U.S. Patent and Trademark Office. Tru64 and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. Microsoft is a registered trademark of Microsoft Corporation. UNIX is a registered trademark and The Open Group is a trademark of The Open Group in the U.S. and other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this publication is subject to change without notice and is provided "as is" without warranty of any kind. The entire risk arising out of the use of this information remains with recipient. In no event shall Compaq be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption or loss of business information), even if Compaq has been advised of the possibility of such damages. The foregoing shall apply regardless of the negligence or other fault of either party and regardless of whether such liability sounds in contract, negligence, tort, or any other theory of legal liability, and notwithstanding any failure of essential purpose of any limited remedy. The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty. This document is available on CD–ROM. This document was prepared using VAX DOCUMENT Version 2.1. Contents Preface ..................................................... xvii Part I POSIX Threads Library Overview and Programming Guidelines 1 Introducing Multithreaded Programming 1.1 Advantages of Using Threads ........................... 1–1 1.2 Overview of Threads .................................. 1–2 1.3 Thread Execution . ................................... 1–4 1.4 Functional Models for Multithreaded Programming .......... 1–5 1.4.1 Boss/Worker Model ................................. 1–5 1.4.2 Work Crew Model ................................. 1–6 1.4.3 Pipelining Model .................................. 1–6 1.4.4 Combination of Functional Models . ................... 1–7 1.5 Programming Issues for Multithreaded Programs . .......... 1–7 1.6 POSIX Threads Libraries and Interfaces ................... 1–8 1.6.1 The pthread Multithreading Interface .................. 1–10 1.6.1.1 Optionally Implemented POSIX.1 Routines . .......... 1–22 1.6.2 Thread-Independent Services Interface ................. 1–23 1.6.3 Undocumented and Obsolete Interfaces ................. 1–26 1.6.3.1 The cma Interface . ........................... 1–26 1.6.3.2 The d4 (DCEthread) Interfaces . ................... 1–27 2 Objects and Operations 2.1 Threads and Synchronization Objects . ................... 2–1 2.2 Attributes Objects . ................................... 2–2 2.3 Thread Operations . ................................... 2–2 2.3.1 Creating a Thread ................................. 2–3 iii 2.3.2 Setting the Attributes of a New Thread . ................ 2–3 2.3.2.1 Setting the Inherit Scheduling Attribute ............. 2–4 2.3.2.2 Setting the Scheduling Policy Attribute .............. 2–4 2.3.2.2.1 Techniques for Setting the Scheduling Policy Attribute . ................................ 2–5 2.3.2.2.2 Comparing Throughput and Real-Time Policies ..... 2–6 2.3.2.2.3 Portability of Scheduling Policy Settings . ....... 2–6 2.3.2.3 Setting the Scheduling Parameters Attribute . ....... 2–7 2.3.2.4 Setting the Stacksize Attribute .................... 2–8 2.3.2.5 Setting the Stack Address Attribute ................ 2–8 2.3.2.6 Setting the Guardsize Attribute .................... 2–9 2.3.2.7 Setting the Contention Scope Attribute .............. 2–9 2.3.3 Terminating a Thread .............................. 2–11 2.3.3.1 Cleanup Handlers .............................. 2–14 2.3.4 Detaching and Destroying a Thread .................... 2–14 2.3.5 Joining With a Thread .............................. 2–15 2.3.6 Scheduling a Thread ............................... 2–16 2.3.6.1 Calculating the Scheduling Priority . ................ 2–16 2.3.6.2 Effects of Scheduling Policy ....................... 2–17 2.3.7 Canceling a Thread ................................ 2–19 2.3.7.1 Thread Cancelation Implemented Using Exceptions .... 2–19 2.3.7.2 Thread Return Value After Cancelation .............. 2–19 2.3.7.3 Controlling Thread Cancelation .................... 2–20 2.3.7.4 Deferred Cancelation Points ...................... 2–21 2.3.7.5 Cleanup from Deferred Cancelation . ................ 2–21 2.3.7.6 Cleanup from Asynchronous Cancelation ............. 2–22 2.3.7.7 Example of Thread Cancelation Code ............... 2–23 2.4 Synchronization Objects ................................ 2–26 2.4.1 Mutexes . ........................................ 2–26 2.4.1.1 Normal Mutex . ................................ 2–27 2.4.1.2 Default Mutex . ................................ 2–27 2.4.1.3 Recursive Mutex ............................... 2–27 2.4.1.4 Errorcheck Mutex .............................. 2–28 2.4.1.5 Mutex Operations .............................. 2–28 2.4.1.6 Mutex Attributes ............................... 2–29 2.4.2 Condition Variables ................................ 2–30 2.4.3 Condition Variable Attributes ........................ 2–35 2.4.4 Read-Write Locks . ................................ 2–36 2.4.4.1 Thread Priority and Writer Precedence for Read-Write Locks ........................................ 2–36 2.4.4.2 Initializing and Destroying a Read-Write Lock . ....... 2–37 2.4.4.3 Read-Write Lock Attributes ....................... 2–37 2.5 Process-Shared Synchronization Objects . ................ 2–37 iv 2.5.1 Programming Considerations ......................... 2–38 2.5.2 Process-Shared Mutexes . ........................... 2–38 2.5.3 Process-Shared Condition Variables . ................... 2–38 2.5.4 Process-Shared Read-Write Locks . ................... 2–39 2.6 Thread-Specific Data .................................. 2–39 3 Programming with Threads 3.1 Designing Code for Asynchronous Execution ................ 3–1 3.1.1 Avoid Passing Stack Local Data ....................... 3–2 3.1.2 Initialize Objects Before Thread Creation ............... 3–2 3.1.3 Do Not Use Scheduling As Synchronization .............. 3–3 3.2 Memory Synchronization Between Threads ................. 3–4 3.3 Sharing Memory Between Threads ....................... 3–4 3.3.1 Using Static Memory ............................... 3–5 3.3.2 Using Stack Memory ............................... 3–5 3.3.3 Using Dynamic Memory . ........................... 3–6 3.4 Managing a Thread’s Stack . ........................... 3–6 3.4.1 Sizing the Stack ................................... 3–7 3.4.2 Using Stack Overflow Warning and Stack Guard Areas . 3–7 3.4.3 Diagnosing Stack Overflow Errors . ................... 3–8 3.5 Scheduling Issues . ................................... 3–8 3.5.1 Real-Time Scheduling . ........................... 3–8 3.5.2 Priority Inversion .................................. 3–9 3.5.3 Dependencies Among Scheduling Attributes and Contention Scope ........................................... 3–9 3.6 Using Synchronization Objects ........................... 3–10 3.6.1 Distinguishing Proper Usage of Mutexes and Condition Variables ........................................ 3–10 3.6.2 Avoiding Race Conditions . ........................... 3–10 3.6.3 Avoiding Deadlocks ................................ 3–11 3.6.4 Signaling a Condition Variable ........................ 3–11 3.6.5 Static Initialization Inappropriate for Stack-Based Synchronization Objects . ........................... 3–13 3.7 Granularity Considerations . ........................... 3–13 3.7.1 Determinants of a Program’s Granularity ............... 3–14 3.7.1.1 Alpha Processor Granularity . ................... 3–15 3.7.1.2 VAX Processor Granularity ....................... 3–15 3.7.2 Compiler Support for Determining the Program’s Actual Granularity . ................................... 3–16 3.7.3 Word Tearing . ................................... 3–16 3.7.4 Alignments of Members of Composite Data Objects ........ 3–17 v 3.7.5 Avoiding Granularity-Related Errors . ................ 3–17 3.7.5.1 Changing the Composite Data Object’s Layout . ....... 3–18 3.7.5.2 Maintaining the Composite Data Object’s Layout ...... 3–18 3.7.5.3 Using One Mutex Per Composite Data Object . ....... 3–19 3.7.6 Identifying Possible Word-Tearing Situations Using Visual Threads . .......................................
Recommended publications
  • Migration Specialties International, Inc. Freeaxp™
    Migration Specialties International, Inc. 217 West 2nd Street, Florence, CO 81226-1403 +1 719-784-9196 E-mail: [email protected] migrationSpecialties.com Continuity in Computing FreeAXP™ SPD V2.n – 11-FEB-2016 Digital Emulator Collection Software Product Description FreeAXP is a virtual AlphaServer 400 designed to be hosted on a Windows x86 and x64 systems. This highly portable product offers the following key features: • OpenVMS, Digital UNIX, and Tru64 UNIX support • Simple configuration • Commercial and hobbyist licensing • VM host support • Optional support contracts Best of all, the product is free! FreeAXP is designed to virtualize legacy Alpha hardware. The product is binary compatible with real Alpha hardware, allowing the resident operating system and software to be ported to FreeAXP without modification or the need for source code. For all intents and purposes, FreeAXP offers a simple way to upgrade existing Alpha systems to new hardware. FreeAXP supports 32 – 128MB of virtual memory, up to seven storage devices, including a physical CD/DVD-ROM, two 100Mb NICs, one virtual serial console, and one virtual serial port. FreeAXP provides an introduction to Migration Specialties legacy Alpha virtualization products. It is designed for hobbyist and non-critical system use. Clients requiring additional performance and capabilities should look at Migration Specialties Avanti commercial Alpha replacement solutions. FreeAXP is provided free of charge without warranty or official support. FreeAXP Home Page: http://migrationspecialties.com/FreeAXP.html Migration Specialties believes the information in this publication is accurate as of its publication date; such information is subject to change without notice. Migration Specialties is not responsible for any inadvertent errors.
    [Show full text]
  • Oracle Application Server Installation Guide for Hp Tru64 UNIX
    Oracle® Application Server Installation Guide 10g Release 2 (10.1.2) for hp Tru64 UNIX B25859-01 February 2007 Oracle Application Server Installation Guide 10g Release 2 (10.1.2) for hp Tru64 UNIX B25859-01 Copyright © 2007, Oracle. All rights reserved. Primary Author: Megan Ginter, Divya Shankar Contributors: Maria Cheng, Rupesh Das, Kriti Dutta, Ranjan Dutta, Xinyang Gao, Hiroaki Hiratsuka, Sunil Jain, Yongqing Jiang, Prashanth Joshi, Michael Moon, Sambit Nanda, Edsel delos Reyes, Janelle Simmons, Abhay Singh, Shashidhara Varamballi The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • CHARON-AXP/DS/ES/GS for Linux 64
    Document: 60-15-046-003 CHARON-AXP/DS/ES/GS for Linux 64 bit Product version: 4.4; Build 147-01 Description CHARON-AXP/DS/ES/GS are members of the CHARON cross-platform hardware virtualization product family. CHARON-AXP creates the virtual replica of the original AlphaServer hardware inside a standard 64 bit x86 compatible computer system. It will run the original Alpha binary code, including operating systems like OpenVMS and Tru64 UNIX, their layered products, and applications. CHARON-AXP/DS/ES/GS for Linux 64 bit is designed to replace the following AlphaServer computer systems by its virtual equivalent running on a Windows host platform: CHARON-AXP product Hardware to replace CHARON-AXP/DS10 AlphaServer DS10, DS15 better performance. The constant improvements Stromasys makes to the CHARON products, together with CHARON-AXP/DS20 AlphaServer DS20, DS25 rapidly developing faster hardware, will further shift the CHARON-AXP/ES40 AlphaServer ES40, ES45, ES47 balance to favor cross-platform virtualization. CHARON-AXP/GS80 AlphaServer GS80, GS60, ES80 For the reference, the table below shows performance CHARON-AXP/GS160 AlphaServer GS140, GS160 measurements of the original AlphaServer hardware using CHARON-AXP/GS320 AlphaServer GS320, GS1280 the standard SPEC2000 benchmark. Those numbers are Most of the original AlphaServer hardware is virtualized, available online from official SPEC2000 web page. allowing the OpenVMS or Tru64 operating system and all Single CPU benchmark SPEC2000 INT SPEC2000 FP software that is running in that environment to remain AlphaServer 4100 5/533 176 176 working as always. Very little changes to the original AlphaServer DS10 6/500 300 383 software (operating system, layered products, or AlphaServer DS20 6/677 425 455 applications) are required, their management routines stay AlphaServer ES40 6/500 299 382 the same.
    [Show full text]
  • SDE 3.0.1 System Requirements
    SDE 3.0.1 System Requirements This PDF contains system requirements information, including hardware requirements, best performance configurations, and limitations, for SDE 3.0.1. Compaq/Digital Tru64 UNIX V4.0b o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 Compaq/Digital Tru64 UNIX V4.0c o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 Compaq/Digital Tru64 UNIX V4.0d o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 HP HP-UX 10.20 (700 series, 8x7 series) o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 HP HP-UX 11.0 (700 series, 8x7 series) o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 IBM AIX 4.1.5.0 o IBM DB2 Common Server 2.1.2 o IBM DB2 Universal Database (UDB) 5.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 IBM AIX 4.2.1.0 o IBM DB2 Universal Database (UDB) 5.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 IBM AIX 4.3.0.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 PC-Intel Windows NT 4.0 o Microsoft SQL Server 6.5 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 SGI IRIX 6.2 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 SGI IRIX 6.3 o Oracle 8 (32 bit) Enterprise
    [Show full text]
  • Tru64 UNIX Compaq C Language Reference Manual
    Tru64 UNIX Compaq C Language Reference Manual Order Number: AA–RH9NC–TE August 2000 This document is the language reference manual for Compaq C. Revision Update Information: This revised manual supersedes the DEC C Language Reference Manual (Order No. AA–RH9NB–TE). Software Version: Compaq C for Tru64 UNIX Version 5.1 or higher Compaq C Version 6.2 for OpenVMS Systems Compaq C Version 6.2 for Linux Alpha Compaq Computer Corporation Houston, Texas First Printing, February 1991 Revised, November 1992 Revised, November 1995 Revised, March 1996 Revised, May 1997 Revised, February 1998 Revised, December 1998 Revised, November 1999 Revised, April 2000 Revised, July 2000 Copyright 2000 Compaq Computer Corporation COMPAQ, VAX, and the Compaq logo Registered in U.S. Patent and Trademark Office. Tru64, Alpha, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. UNIX is a trademark of The Open Group. All other product names mentioned herein may be trademarks or registered trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this publication is subject to change without notice and is provided "as is" without warranty of any kind. The entire risk arising out of the use of this information remains with recipient. In no event shall Compaq be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption or loss of business information), even if Compaq has been advised of the possibility of such damages.
    [Show full text]
  • Operating Systems
    PHYS-4007/5007: Computational Physics Course Lecture Notes Appendix A Dr. Donald G. Luttermoser East Tennessee State University Version 7.0 Abstract These class notes are designed for use of the instructor and students of the course PHYS-4007/5007: Computational Physics I taught by Dr. Donald Luttermoser at East Tennessee State University. Appendix A. Operating Systems A. A Brief History of Operating Systems. 1. A simple definition of a operating system is the suite of programs that make the hardware usable. The operating system manages the CPU, disks, and I/O devices. 2. Manipulation of the operating system was typically one of the hardest aspects of learning to use computers which is why the “GUI (Graphic User Interface) mentality” has taken hold of the modern computers — the user no long needs to talk to the op- erating system, the GUI does it for you! (Which is actually a “pain-in-the-butt” if you need to actually talk to the operating system!) 3. We now follow the history of operating systems and programming languages that are important in the scientific community, starting in the 1940s: a) Early computers had no operating system (e.g., the IBM 604). b) The computer was told what to do with a low-level set of commands =⇒ assembly language. c) The IBM 604 could undertake 60 program steps before using punch cards as a backing store. d) Often, the user had to manipulate toggle switches to input the code for the mainframe. 4. The 1950s saw the advent and rapid changes in the capability of operating systems.
    [Show full text]
  • IBM Visualage Pacbase Version 3.0 Delivers a Remodeled Environment for E-Business
    Software Announcement February 20, 2001 IBM VisualAge Pacbase Version 3.0 Delivers a Remodeled Environment for e-business Overview Using VisualAge Pacbase, organizations will: At a Glance VisualAge Pacbase is a • repository-based application Progressively move to the most VisualAge Pacbase offers: advanced technologies and development (AD) offering designed • for enterprise-wide scalability, extend existing assets to the Life-cycle coverage of AD needs reliability, and performance. world of e-business from analysis and design to production of all types of B2B, • Benefit from a multiplatform VisualAge Pacbase Version 3.0 B2C, and B2E applications that approach to ensure portability offers extended capabilities: are portable on IBM and and scalability of applications non-IBM platforms • The e-business information model while protecting previous IT has been restructured to facilitate investments • Model-driven development and visual programming to improve the implementation of new • Take advantage of a powerful and technologies. productivity and enable secure industrial-strength developers to focus on business • The new Developer Workbench solution to bring enterprise level issues provides a single user-friendly computing to their application Java -based interface to drive environment • Reusability of components traditional and e-business during the development process development. Key Prerequisites and consistency during the life-cycle of applications • The coverage of e-business needs • Server is improved through additional • Ability to extend legacy capabilities such as integration of − Mainframe: MVS or applications to the world of existing COBOL applications, OS/390 CICS , MVS or e-business, and create low-cost server components testing, and OS/390 IMS , IBM VSE/CICS; Web-enabled systems support for Enterprise JavaBean Bull GCOS7, GCOS8; Unisys 2200 series For ordering, contact: (EJB) session components.
    [Show full text]
  • ICS 143 - Principles of Operating Systems
    ICS 143 - Principles of Operating Systems Lectures 3 and 4 - Processes and Threads Prof. Nalini Venkatasubramanian [email protected] Some slides adapted from http://www-inst.eecs.berkeley.edu/~cs162/ Copyright © 2010 UCB. Note that some slides are also adapted from course text slides © 2008 Silberschatz Outline ■ Process Concept ❑ Process Scheduling ❑ Operations on Processes ❑ Cooperating Processes ■ Threads ■ Interprocess Communication Process Concept ■ An operating system executes a variety of programs ■ batch systems - jobs ■ time-shared systems - user programs or tasks ■ Job, task and program used interchangeably ■ Process - a program in execution ■ process execution proceeds in a sequential fashion ■ A process contains ■ program counter, stack and data section Process =? Program main () main () Heap { { …; …; } } Stack A() { A() { A main … … } } Program Process ■ More to a process than just a program: ❑ Program is just part of the process state ❑ I run Vim or Notepad on lectures.txt, you run it on homework.java – Same program, different processes ■ Less to a process than a program: ❑ A program can invoke more than one process ❑ A web browser launches multiple processes, e.g., one per tab Process State ■ A process changes state as it executes. new admitted exit terminated interrupt ready running Scheduler I/O or dispatch event I/O or completion event wait waiting Process States ■ New - The process is being created. ■ Running - Instructions are being executed. ■ Waiting - Waiting for some event to occur. ■ Ready - Waiting to be assigned to a processor. ■ Terminated - Process has finished execution. Process Control Block ■ Contains information associated with each process ■ Process State - e.g. new, ready, running etc. ■ Process Number – Process ID ■ Program Counter - address of next instruction to be executed ■ CPU registers - general purpose registers, stack pointer etc.
    [Show full text]
  • Chapter 4: Threads
    Chapter 4: Threads Operating System Concepts with Java – 8th Edition 14.1 Silberschatz, Galvin and Gagne ©2009 Chapter 4: Threads n Overview n Multithreading Models n Thread Libraries n Threading Issues n Operating System Examples n Windows XP Threads n Linux Threads Operating System Concepts with Java – 8th Edition 14.2 Silberschatz, Galvin and Gagne ©2009 Objectives n To introduce the notion of a thread — a fundamental unit of CPU utilization that forms the basis of multithreaded computer systems n To discuss the APIs for the Pthreads, Win32, and Java thread libraries n To examine issues related to multithreaded programming Operating System Concepts with Java – 8th Edition 14.3 Silberschatz, Galvin and Gagne ©2009 Single and Multithreaded Processes Operating System Concepts with Java – 8th Edition 14.4 Silberschatz, Galvin and Gagne ©2009 Multithreaded Server Architecture Operating System Concepts with Java – 8th Edition 14.5 Silberschatz, Galvin and Gagne ©2009 Benefits n Responsiveness l Allows a program continue running if part of it is blocked or its is performing a lengthy operation n Resource Sharing l Threads share the memory and the resources of the parent process n Economy l In Solaris, creating a process is 30 times slower than creating a thread, context switching is 5 times slower. n Scalability l Multithreading on a multi-CPU machine increase parallelism Operating System Concepts with Java – 8th Edition 14.6 Silberschatz, Galvin and Gagne ©2009 Multicore Programming n Multicore systems putting pressure on programmers, challenges include l Dividing activities 4 Find area that can be divided into separate, concurrent tasks l Balance 4 Ensure concurrent tasks perform equal work of equal value l Data splitting 4 Data accessed must be divided to run on speparate cores.
    [Show full text]
  • Alphaserver DS20E / Alphastation DS20E Systems
    AlphaServer DS20E AlphaStation DS20E Reference Guide Order Number: ER-K8F6W-UA. D01 This manual is for managers and operators of Compaq AlphaServer DS20E / AlphaStation DS20E systems. Compaq Computer Corporation Revised, August 2000 © 2000 Compaq Computer Corporation. COMPAQ, the Compaq logo, and AlphaServer Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P. Linux is a registered trademark of Linus Torvalds in several countries. UNIX is a registered trademark of The Open Group in the U.S. and other countries. All other product names mentioned herein may be trademarks of their respective companies. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is subject to change without notice. Contents Preface ........................................................................................................................xi Chapter 1 System Overview 1.1 System Enclosures ................................................................................ 1-2 1.2 System Parts (Front/Side View)............................................................ 1-4 1.3 System Parts (Rear View) ..................................................................... 1-6 1.4 Operator Control Panel......................................................................... 1-8 1.5 System Board ...................................................................................... 1-10 1.6 Server Feature Module ......................................................................
    [Show full text]
  • Intelligent Event Module for HP Tru64 UNIX
    ™ ® ® ® Intelligent Event Module for HP TRU64 UNIX INTELLIGENT EVENT MODULE BASICS To Download the IEM 1. Install the license for the HP Tru64 UNIX IEM. To The HP Tru64 UNIX Intelligent Event Module (IEM) obtain this license, contact your TDi Solutions Team enables you to automate real-time monitoring of Manager ( ). AlphaServer® platforms running on the Tru64® UNIX® [email protected] 5.1 operating system and capture the critical 2. Move to the TDi web site information you need for effective enterprise (www.tditx.com/support_iemdownloads.asp). management. 3. On the Product Downloads page, locate and click ® The HP Tru64 UNIX IEM provides ConsoleWorks with HP Tru64 UNIX. a watch-list of text messages, including error codes, system warnings, and status alerts, produced by Tru64 4. In the Connect to support2.tditx.com dialog box, UNIX. ConsoleWorks watches for these messages, enter your User name and Password, and click OK. called Events, in the data streams of your managed To obtain a User name and Password, contact TDi systems. Support ([email protected]). Events 5. Save the file (cw_iem-hp_t64u-0000.bin) to a directory accessible from your client workstation. When ConsoleWorks detects an Event, it alerts you to the Event as it is happening, records the circumstances surrounding the Event, and automatically performs the To Import the IEM default or customer-configured responses associated with that Event. 1. On the ConsoleWorks main menu, click Admin > Database > Import IEM. Scans 2. On the Import IEM page, click Browse. IEMs come with Events pre-arranged in logical groupings, called Scans™. Working with a Scan—or a 3.
    [Show full text]
  • The Solaris™ Operating System
    Migrating From Tru64 UNIX to the Solaris™ Operating System Ken Pepple, Brian Down, David Levy Sun BluePrints™ OnLine—March 2005 http://www.sun.com/blueprints Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95045 U.S.A. 650 960-1300 Part No. 819-2274-10 Edition: March 2005 Copyright 2003—2005 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, California 95045 U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. 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. Sun, Sun Microsystems, the Sun logo, Sun BluePrints, SunSolve, SunSolve Online, docs.sun.com, JumpStart, N1, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
    [Show full text]