DOCSLIB.ORG

IBM AIX Version 7.1 Differences Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM AIX Version 7.1 Differences Guide Front cover IBM AIX Version 7.1 Differences Guide AIX - The industrial strength UNIX operating system AIX Version 7.1 Standard Edition enhancements An expert’s guide to the new release Richard Bassemir Thierry Fauck Chris Gibson Brad Gough Murali Neralla Armin Röll Murali Vaddagiri ibm.com/redbooks International Technical Support Organization IBM AIX Version 7.1 Differences Guide December 2010 SG24-7910-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. First Edition (December 2010) This edition applies to AIX Version 7.1 Standard Edition, program number 5765-G98. © Copyright International Business Machines Corporation 2010. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . ix Tables . xi Notices . xiii Trademarks . xiv Preface . xv The team who wrote this book . xv Now you can become a published author, too! . xvii Comments welcome. xviii Stay connected to IBM Redbooks . xviii Chapter 1. Application development and debugging . 1 1.1 AIX binary compatibility . 2 1.2 Improved performance using 1 TB segments . 2 1.3 Kernel sockets application programming interface . 5 1.4 UNIX08 standard conformance . 6 1.4.1 stat structure changes. 8 1.4.2 open system call changes. 9 1.4.3 utimes system call changes . 9 1.4.4 futimens and utimensat system calls . 10 1.4.5 fexecve system call . 10 1.5 AIX assembler enhancements . 10 1.5.1 Thread Local Storage (TLS) support. 10 1.5.2 TOCREL support. 11 1.6 Malloc debug fill. 11 1.7 proc_getattr and proc_setattr enhancements . 12 1.7.1 Core dump enhancements . 13 1.7.2 High resolution timers . 14 1.8 Disabled read write locks . 14 1.9 DBX enhancements . 17 1.9.1 Dump memory areas in pointer format . 17 1.9.2 dbx environment variable print_mangled . 18 1.9.3 DBX malloc subcommand enhancements . 19 1.10 ProbeVue enhancements . 20 1.10.1 User function probe manager for Fortran . 21 1.10.2 User function exit probes . 22 1.10.3 Module name support in user probes . 23 © Copyright IBM Corp. 2010. All rights reserved. iii 1.10.4 ProbeVue support for pre-compiled C++ header files. 24 1.10.5 Associative array data type . 24 1.10.6 Built-in variables for process- and thread-related information. 25 1.10.7 Interval probes for profiling programs . 27 Chapter 2. File systems and storage. 29 2.1 LVM enhancements . 30 2.1.1 LVM enhanced support for solid-state disks . 30 2.2 Hot files detection in JFS2. 35 Chapter 3. Workload Partitions and resource management . 43 3.1 Trusted kernel extension loading and configuration . 44 3.1.1 Syntax overview . 44 3.1.2 Simple example monitoring. 45 3.1.3 Enhancement of the lspwar command . 47 3.1.4 mkwpar -X local=yes|no parameter impact . 47 3.2 WPAR list of features . 50 3.3 Versioned Workload Partitions (VWPAR) . 50 3.3.1 Benefits . 50 3.3.2 Requirements and considerations. 50 3.3.3 Creation of a basic Versioned WPAR AIX 5.2 . 51 3.3.4 Creation of an AIX Version 5.2 rootvg WPAR. 60 3.3.5 Content of the vwpar.52 package . 65 3.3.6 Creation of a relocatable Versioned WPAR . 67 3.3.7 SMIT interface. 68 3.4 Device support in WPAR. 68 3.4.1 Global device listing used as example . 68 3.4.2 Device command listing in an AIX 7.1 WPAR. 69 3.4.3 Dynamically adding a Fibre Channel adapter to a system WPAR . 72 3.4.4 Removing of the Fibre Channel adapter from Global . 74 3.4.5 Reboot of LPAR keeps Fibre Channel allocation . 74 3.4.6 Disk attached to Fibre Channel adapter . 77 3.4.7 Startwpar error if adapter is busy on Global . 79 3.4.8 Startwpar with a Fibre Channel adapter defined. 79 3.4.9 Disk commands in the WPAR . 82 3.4.10 Access to the Fibre Channel attached disks from the Global . 83 3.4.11 Support of Fibre Channel devices in the mkwpar command. 84 3.4.12 Config file created for the rootvg system WPAR. 92 3.4.13 Removing an FC-attached disk in a running system WPAR. 93 3.4.14 Mobility considerations . 93 3.4.15 Debugging log . 94 3.5 WPAR RAS enhancements. 95 3.5.1 Error logging mechanism aspect. 95 iv IBM AIX Version 7.1 Differences Guide 3.5.2 Goal for these messages . 96 3.5.3 Syntax of the messages . 96 3.6 WPAR migration to AIX Version 7.1 . 98 Chapter 4. Continuous availability. 113 4.1 Firmware-assisted dump . 114 4.1.1 Default installation configuration . 114 4.1.2 Full memory dump options . 115 4.1.3 Changing the dump type on AIX V7.1. 116 4.1.4 Firmware-assisted dump on POWER5 and earlier hardware . 120 4.1.5 Firmware-assisted dump support for non-boot iSCSI device . 121 4.2 User key enhancements . 122 4.3 Cluster Data Aggregation Tool . 123 4.4 Cluster Aware AIX . 129 4.4.1 Cluster configuration . 130 4.4.2 Cluster system architecture flow . 142 4.4.3 Cluster event management . 143 4.4.4 Cluster socket programming . 144 4.4.5 Cluster storage communication configuration . 147 4.5 SCTP component trace and RTEC adoption . 150 4.6 Cluster aware perfstat library interfaces . 152 Chapter 5. System management . 159 5.1 Processor interrupt disablement . 160 5.2 Distributed System Management . 161 5.2.1 The dpasswd command . 162 5.2.2 The dkeyexch command . ..
Load more

Recommended publications
  • Using Restricted Transactional Memory to Build a Scalable In-Memory Database
    Using Restricted Transactional Memory to Build a Scalable In-Memory Database Zhaoguo Wang†, Hao Qian‡, Jinyang Li§, Haibo Chen‡ † School of Computer Science, Fudan University ‡ Institute of Parallel and Distributed Systems, Shanghai Jiao Tong University § Department of Computer Science, New York University Abstract However, the correctness of the resulting code is complex to reason about and relies on the processor’s (increasingly The recent availability of Intel Haswell processors marks the complex) memory model. transition of hardware transactional memory from research Recently, Intel has shipped its 4th-generation Haswell toys to mainstream reality. DBX is an in-memory database processor with support for Hardware Transactional Mem- that uses Intel’s restricted transactional memory (RTM) to ory [16]. This opens up a third possibility to scaling multi- achieve high performance and good scalability across multi- core software. Instead of relying on fine-grained locking core machines. The main limitation (and also key to practi- and atomic operations, one can synchronize using hardware cality) of RTM is its constrained working set size: an RTM transactions, which offer a programming model that is ar- region that reads or writes too much data will always be guably even more straightforward than mutual exclusion. aborted. The design of DBX addresses this challenge in sev- The promise is that the resulting implementation is much eral ways. First, DBX builds a database transaction layer on simpler and easier-to-understand while still retaining the top of an underlying shared-memory store. The two layers performance benefits of fine-grained locking. use separate RTM regions to synchronize shared memory Does hardware transactional memory actually deliver its access.
    [Show full text]
  • Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Programming Languages Supported by GCC ............ 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .........................
    [Show full text]
  • Oracle Solaris Studio 12.3 Debugging a Program With
    Oracle® Solaris Studio 12.3: Debugging a ProgramWith dbx Part No: E21993 December 2011 Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx Sun™ Studio 11 Sun Microsystems, Inc. www.sun.com Part No 819-3683-10 November 2005, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright © 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties. 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 in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, and JavaHelp are trademarks or registered trademarks 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 architecture developed by Sun Microsystems, Inc. This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.
    [Show full text]
  • Operating RISC: UNIX Standards in the 1990S
    Operating RISC: UNIX Standards in the 1990s This case was written by Will Mitchell and Paul Kritikos at the University of Michigan. The case is based on public sources. Some figures are based on case-writers' estimates. We appreciate comments from David Girouard, Robert E. Thomas and Michael Wolff. The note "Product Standards and Competitive Advantage" (Mitchell 1992) supplements this case. The latest International Computerquest Corporation analysis of the market for UNIX- based computers landed on three desks on the same morning. Noel Sharp, founder, chief executive officer, chief engineer and chief bottle washer for the Superbly Quick Architecture Workstation Company (SQAWC) in Mountain View, California hoped to see strong growth predicted for the market for systems designed to help architects improve their designs. In New York, Bo Thomas, senior strategist for the UNIX systems division of A Big Computer Company (ABCC), hoped that general commercial markets for UNIX-based computer systems would show strong growth, but feared that the company's traditional mainframe and mini-computer sales would suffer as a result. Airborne in the middle of the Atlantic, Jean-Helmut Morini-Stokes, senior engineer for the UNIX division of European Electronic National Industry (EENI), immediately looked to see if European companies would finally have an impact on the American market for UNIX-based systems. After looking for analysis concerning their own companies, all three managers checked the outlook for the alliances competing to establish a UNIX operating system standard. Although their companies were alike only in being fictional, the three managers faced the same product standards issues. How could they hasten the adoption of a UNIX standard? The market simply would not grow until computer buyers and application software developers could count on operating system stability.
    [Show full text]
  • A Short User Manual for Dbx
    A Short User Manual for dbx \dbx" is the name of the debugger that is available for use on many Unix systems. This document is intended to list the most common dbx commands and briefly explain how to use them. It is not a complete description of dbx but should be a sufficient reference to get started. For a more detailed description or to find out about other commands and options, execute the command % man dbx or from within dbx use the 'help' command (recommended). Subjects covered below: let (dbx) be the prompt while in dbx mode: a) Compiling your code for use with the debugger [ cc with -g flag] b) Starting the debugger [ \%dbx executable ] c) Getting help while using the debugger [ (dbx) help ] d) Running your program in the debugger [ (dbx) run ] e) Setting breakpoints in the program [ (dbx) stop ] f) Listing the breakpoints that are set [ (dbx) status ] g) Removing a breakpoint [ (dbx) delete ] h) Stepping through the program [ (dbx) step, (dbx) next ] i) Jumping ahead to the next breakpoint [ (dbx) cont ] j) Examining the values of variables [ (dbx) print ] k) Listing a portion of the source code [ (dbx) list ] l) Leaving the debugger [ (dbx) quit ] To use dbx to debug your C programs you need to follows the procedure: 1. Compiling your code for use with the debugger: You must use the -g flag when compiling your code. For example: % cc -g myfile.c will create an a.out executable suitable for dbx. 2. Starting the debugger: Give the 'dbx' command along with the name of the exe- cutable you wish to examine.
    [Show full text]
  • The Rise & Development of Illumos
    Fork Yeah! The Rise & Development of illumos Bryan Cantrill VP, Engineering [email protected] @bcantrill WTF is illumos? • An open source descendant of OpenSolaris • ...which itself was a branch of Solaris Nevada • ...which was the name of the release after Solaris 10 • ...and was open but is now closed • ...and is itself a descendant of Solaris 2.x • ...but it can all be called “SunOS 5.x” • ...but not “SunOS 4.x” — thatʼs different • Letʼs start at (or rather, near) the beginning... SunOS: A peopleʼs history • In the early 1990s, after a painful transition to Solaris, much of the SunOS 4.x engineering talent had left • Problems compounded by the adoption of an immature SCM, the Network Software Environment (NSE) • The engineers revolted: Larry McVoy developed a much simpler variant of NSE called NSElite (ancestor to git) • Using NSElite (and later, TeamWare), Roger Faulkner, Tim Marsland, Joe Kowalski and Jeff Bonwick led a sufficiently parallelized development effort to produce Solaris 2.3, “the first version that worked” • ...but with Solaris 2.4, management took over day-to- day operations of the release, and quality slipped again Solaris 2.5: Do or die • Solaris 2.5 absolutely had to get it right — Sun had new hardware, the UltraSPARC-I, that depended on it • To assure quality, the engineers “took over,” with Bonwick installed as the gatekeeper • Bonwick granted authority to “rip it out if itʼs broken" — an early BDFL model, and a template for later generations of engineering leadership • Solaris 2.5 shipped on schedule and at quality
    [Show full text]
  • Debugging a Program with Dbx
    Debugging a Program With dbx A Sun Microsystems, Inc. Business 901 San Antonio Road Palo Alto, , CA 94303-4900 Part No: 805-4948 Revision A, February 1999 USA 650 960-1300 fax 650 969-9131 Debugging a Program With dbx Part No: 805-4948 Revision A, February 1999 Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. 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. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and in other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a). Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • IBM System Storage Open Systems Tape Encryption Solutions
    Front cover IBM System Storage Open Systems Tape Encryption Solutions Understanding tape encryption and Tivoli Key Lifecycle Manager Version 2 Planning for and installing hardware and software Configuring and managing the tape encryption solution Alex Osuna Luciano Cecchetti Edgar Vinson ibm.com/redbooks International Technical Support Organization IBM System Storage Open Systems Tape Encryption Solutions December 2010 SG24-7907-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2010) This edition applies to Tivoli Key Lifecycle Manager (TKLM) Version 2. © Copyright International Business Machines Corporation 2010. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team who wrote this book . .x Become a published author . xi Comments welcome. xi Stay connected to IBM Redbooks . xii Chapter 1. Introduction to tape encryption. 1 1.1 IBM System Storage tape drives. 2 1.2 How tape data encryption works . 4 1.3 What to encrypt . 6 1.4 Why use tape data encryption. 7 1.4.1 Why encrypt data in the drive . 7 1.4.2 Fundamental to encryption: Policy and key management . 7 1.4.3 Summary. 8 1.5 Concepts of tape data encryption . 8 1.5.1 Symmetric key encryption. 9 1.5.2 Asymmetric key encryption . 11 1.5.3 Hybrid encryption . 14 1.5.4 Digital certificates . 15 1.6 Simplifying key management with TKLM . 20 1.6.1 Encryption as a critical business process .
    [Show full text]
  • Chapter 4 Introduction to UNIX Systems Programming
    Chapter 4 Introduction to UNIX Systems Programming 4.1 Introduction Last chapter covered how to use UNIX from from a shell program using UNIX commands. These commands are programs that are written in C that interact with the UNIX environment using functions called Systems Calls. This chapter covers this Systems Calls and how to use them inside a program. 4.2 What is an Operating System An Operating System is a program that sits between the hardware and the application programs. Like any other program it has a main() function and it is built like any other program with a compiler and a linker. However it is built with some special parameters so the starting address is the boot address where the CPU will jump to start the operating system when the system boots. Draft An operating system typically offers the following functionality: ● Multitasking The Operating System will allow multiple programs to run simultaneously in the same computer. The Operating System will schedule the programs in the multiple processors of the computer even when the number of running programs exceeds the number of processors or cores. ● Multiuser The Operating System will allow multiple users to use simultaneously in the same computer. ● File system © 2014 Gustavo Rodriguez-Rivera and Justin Ennen,Introduction to Systems Programming: a Hands-on Approach (V2014-10-27) (systemsprogrammingbook.com) It allows to store files in disk or other media. ● Networking It gives access to the local network and internet ● Window System It provides a Graphical User Interface ● Standard Programs It also includes programs such as file utilities, task manager, editors, compilers, web browser, etc.
    [Show full text]
  • Open Technology Development (OTD): Lessons Learned & Best Practices for Military Software
    2011 OTD Lessons Learned Open Technology Development (OTD): Lessons Learned & Best Practices for Military Software 2011-05-16 Sponsored by the Assistant Secretary of Defense (Networks & Information Integration) (NII) / DoD Chief Information Officer (CIO) and the Under Secretary of Defense for Acquisition, Technology, and Logistics (AT&L) This document is released under the Creative Commons Attribution ShareAlike 3.0 (CC- BY-SA) License. You are free to share (to copy, distribute and transmit the work) and to remix (to adapt the work), under the condition of attribution (you must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work)). For more information, see http://creativecommons.org/licenses/by/3.0/ . The U.S. government has unlimited rights to this document per DFARS 252.227-7013. Portions of this document were originally published in the Software Tech News, Vol.14, No.1, January 2011. See https://softwaretechnews.thedacs.com/ for more information. Version - 1.0 2 2011 OTD Lessons Learned Table of Contents Chapter 1. Introduction........................................................................................................................... 1 1.1 Software is a Renewable Military Resource ................................................................................ 1 1.2 What is Open Technology Development (OTD) ......................................................................... 3 1.3 Off-the-shelf (OTS) Software Development
    [Show full text]
  • Using and Porting the GNU Compiler Collection
    Using and Porting the GNU Compiler Collection Richard M. Stallman Last updated 14 June 2001 for gcc-3.0 Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001 Free Software Foundation, Inc. For GCC Version 3.0 Published by the Free Software Foundation 59 Temple Place - Suite 330 Boston, MA 02111-1307, USA Last printed April, 1998. Printed copies are available for $50 each. ISBN 1-882114-37-X Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. Short Contents Introduction......................................... 1 1 Compile C, C++, Objective C, Fortran, Java ............... 3 2 Language Standards Supported by GCC .................. 5 3 GCC Command Options ............................. 7 4 Installing GNU CC ............................... 111 5 Extensions to the C Language Family .................. 121 6 Extensions to the C++ Language ...................... 165 7 GNU Objective-C runtime features .................... 175 8 gcov: a Test Coverage Program ...................... 181 9 Known Causes of Trouble with GCC ................... 187 10 Reporting Bugs.................................
    [Show full text]