DOCSLIB.ORG

IBM PE for AIX and Linux V5 R1: Installation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM PE for AIX and Linux V5 R1: Installation Parallel Environment for AIX and Linux Installation Ve r s i o n 5 Release 1 SC23-6666-00 Parallel Environment for AIX and Linux Installation Ve r s i o n 5 Release 1 SC23-6666-00 Note Before using this information and the product it supports, read the information in “Notices” on page 93. First Edition (November 2008) This edition applies to version 5, release 1, modification 0 of IBM Parallel Environment for AIX (product number 5765-PEA) and version 5, release 1, modification 0 of IBM Parallel Environment for Linux (product number 5765-PEL) and to all subsequent releases and modifications until otherwise indicated in new editions. IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you can send your comments to the following address: International Business Machines Corporation Department 58HA, Mail Station P181 2455 South Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States & Canada): 1+845+432-9405 FAX (Other Countries): Your International Access Code +1+845+432-9405 ™ IBMLink (United States customers only): IBMUSM10(MHVRCFS) Internet e-mail: [email protected] If you want a reply, be sure to include your name, address, and telephone or FAX number. Make sure to include the following in your comment or note: v Title and order number of this publication v Page number or topic related to your comment 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 International Business Machines Corporation 1993, 2008. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables . vii About this information . .ix Who should read this information . .ix How this information is organized . .ix Conventions and terminology used in this information . .x Abbreviated names . .xi Prerequisite and related information . .xi How to send your comments . xii National language support (NLS) . xii Functional restrictions for PE 5.1 . xiii Summary of changes . xiii Changes for PE 5.1 . xiii Chapter 1. Introducing PE 5.1 . .1 PE components . .1 Chapter 2. Planning to install the PE software . .3 PE for AIX installation requirements . .3 PE for AIX hardware requirements . .3 PE for AIX software requirements . .3 Disk space requirements for AIX installation . .6 PE for Linux installation requirements . .6 PE for Linux hardware requirements . .6 PE for Linux software requirements . .6 Disk space requirements for Linux installation . .10 PE Limitations . .10 Information for the system administrator . .10 Software compatibility within workstation clusters . .11 Node resources . .11 Deciding which nodes require which PE filesets or RPMs, or additional software . .12 Enabling xinetd for Linux installation . .12 File systems . .12 User IDs on remote nodes . .13 PE for AIX user authorization . .13 POE security method configuration . .13 Cluster based security configuration . .13 AIX-based security (compatibility) . .14 PE for Linux user authorization . .14 Tuning your Linux system for more efficient parallel job performance . .15 Running large POE jobs and IP buffer usage (PE for AIX only) . .16 Chapter 3. Installing the Parallel Environment . .17 Installing the PE for AIX software . .17 About installing PE for AIX with CSM . .17 About installing PE for AIX on an IBM Power Systems cluster . .17 Migration installation . .18 When to install the rsct.lapi.rte fileset . .19 When to install the rsct.lapi.bsr fileset . .19 When to install the rsct.core.sec fileset . .19 When to install the loadl.so (LoadLeveler) fileset . .19 View the readme file before installation . .19 PE for AIX installation procedure summary . .20 Install the PE for AIX filesets step-by-step . .20 © Copyright IBM Corp. 1993, 2008 iii Performing PE for AIX post installation tasks (optional) . .28 Enabling the barrier sychronization register (BSR) . .28 Installing the PE for Linux software . .28 Installing PE for Linux manually . .29 Installing PE for Linux using the pe_install.sh script . .31 Performing PE for Linux post installation tasks (optional) . .35 Resolving installation errors . .36 Chapter 4. Migrating and upgrading PE . .39 Migrating and upgrading PE for AIX . .39 PE for AIX migration overview . .39 AIX compatibility . .40 Coexistence . .40 Migration support . .40 AIX support . .40 MPI library support . .41 Barrier synchronization register (BSR) support . .41 LAPI support . .41 Fortran 90 compile time type-checking support . .41 Online documentation . .42 Migrating and upgrading PE for Linux . .42 PE for Linux migration overview . .42 Installing an upgrade . .43 Coexistence . .44 Migration support . .45 LAPI support . .45 Fortran 90 compile time type-checking support . .45 Chapter 5. Performing installation-related tasks . .47 Performing PE for AIX installation-related tasks . .47 Removing a software component . .47 Recovering from a software vital product database error . .47 Customizing the message catalog . .48 Installing AFS . .48 Performing PE for Linux installation-related tasks . .49 Finding installed components . .49 Removing a software component . .50 Customizing the message catalog . .51 Chapter 6. Understanding how installing PE alters your system . .53 Understanding how installing PE for AIX alters your system . .53 How installing the POE fileset alters your system . .53 How installing PDB alters your system . .57 How installing the online documentation alters your system . .57 Understanding how installing PE for Linux alters your system . .58 How installing the PE license RPM alters your system . .58 How installing the PE and LAPI RPMs alters your system . .59 Chapter 7. Additional information for the system administrator . .63 Using the /etc/poe.limits file . .63 Entries in the /etc/poe.limits file . .63 How the Partition Manager daemon handles the /etc/poe.limits file . .64 Description of /etc/poe.security . .64 Configuring the Parallel Environment coscheduler . .65 POE coscheduling parameters and limits . .65 AIX dispatcher tuning (PE for AIX only) . .68 Enabling Remote Direct Memory Access (RDMA) . .69 Enabling RDMA for use with the IBM High Performance Switch (PE for AIX only) . .70 Enabling RDMA for use with the InfiniBand interconnect . .71 Configuring InfiniBand for User Space without LoadLeveler (PE for AIX only) . .72 iv IBM PE for AIX and Linux V5 R1: Installation Compiling and installing the NRT API samples . .72 Chapter 8. Syntax of commands for running installation and deinstallation scripts . .75 PE for AIX installation.
Load more

Recommended publications
  • Supporting Operating System Installation | 3
    cc01SupportingOperatingSystemInstallation.indd01SupportingOperatingSystemInstallation.indd PagePage 1 08/10/1408/10/14 4:334:33 PMPM martinmartin //208/WB01410/XXXXXXXXXXXXX/ch01/text_s208/WB01410/XXXXXXXXXXXXX/ch01/text_s Supporting Operating LESSON 1 System Installation 70-688 EXAM OBJECTIVE Objective 1.1 – Support operating system installation. This objective may include but is not limited to: Support Windows To Go; manage boot settings, including native virtual hard disk (VHD) and multi-boot; manage desktop images; customize a Windows installation by using Windows Preinstallation Environment (PE). LESSON HEADING EXAM OBJECTIVE Using a Troubleshooting Methodology Viewing System Information Using the Event Viewer Supporting Windows To Go Support Windows To Go Creating and Deploying a Windows To Go Workspace Drive Booting into a Windows To Go Workspace Managing Boot Settings Manage boot settings, including native virtual hard disk (VHD) and multi-boot Using BCDEdit and BCDBoot Configuring a Multi-Boot System Manage boot settings, including native virtual hard disk (VHD) and multi-boot Configuring a Native VHD Boot File Manage boot settings, including native virtual hard disk (VHD) and multi-boot Understanding VHD Formats Installing Windows 8.1 on a VHD with an Operating System Present Installing Windows 8.1 on a VHD Without an Operating SystemCOPYRIGHTED Present MATERIAL Managing Desktop Images Manage desktop images Capturing Images Modifying Images using DISM Customizing a Windows Installation by Using Windows PE Customize a Windows
    [Show full text]
  • Chapter 8 SYSTEM RECOVERY and DIAGNOSTIC TRICKS
    09_0789736896_08.qxd 4/26/07 2:02 PM Page 259 Chapter 8 SYSTEM RECOVERY AND DIAGNOSTIC TRICKS Backup and Restore Center omputers die. It’s true. They overheat; they get old and run Cdown. A lightning strike creeps up the wires into your box. They call them terminals for a reason. It’s because their lifespan ■ Backup and Restore Center is terminal (okay, not really, but you take my point). The differ- ■ ence with a computer is that you have the ability to back up your The System Rating data, settings, and preferences and restore them to the same ■ Windows System machine with new hardware or an entirely new machine. Assessment Tool ■ Problem Reports and Solutions IN THIS CHAPTER ■ Reliability and Performance Monitor ■ Memory Diagnostics Tool ■ ReadyBoost and SuperFetch ■ Vista Recovery: Advanced Boot Options, WinRE, and WinPE 09_0789736896_08.qxd 4/26/07 2:02 PM Page 260 260 Tricks of the Windows Vista Masters The Backup and Restore Center Even novice users can open the Backup and Restore Center (shown in Figure 8.1) and work their way through the wizards. To find it you can type Backup and Restore Center from the Start orb search pane, or you can open the All Programs folder, go to Maintenance, and select it from there to start the wizards. FIGURE 8.1 The Backup and Restore Center is an easy console for novice users to work with. From within the center you can do the following: ■ Back up your data files (or schedule your files to be backed up at regular intervals to ensure data protection).
    [Show full text]
  • Programming with Haiku
    Programming with Haiku Lesson 4 Written by DarkWyrm All material © 2010 DarkWyrm Source Control: What is It? In my early days as a developer on the Haiku project I had troubles on occasion because I had to use a source control manager (SCM). I didn't understand it and I didn't want to take the time to learn about it from some tutorial online. I wanted to be able to write code with as few hurdles as possible. How I wish that I'd understood source control then. Source control, also known as revision control or version control, is a tool or set of tools which facilitates development on a single codebase by many people at once. This is done by recording the changes that are made by each person and ensuring that one person's changes cannot be applied at the same time as another's. Most also provide for working on a separate copy of the main sources, called a branch. Using an SCM forces your workflow to have some structure, which is actually a good thing for those who have a hard time getting organized, provided that they are willing to work with it. Day-to-day coding involves checking out others' updates and checking in your own. On occasion, a change must be undone, called reverting a change. Sometimes a feature is large enough that it necessitates working over the course of several check-ins, called commits. In these cases, a branch is created so that the development of the feature benefits from source control without disturbing others' work.
    [Show full text]
  • Volume 43 August, 2010
    Volume 43 August, 2010 Xfce 4.6.2: Linux IS Ready For The Desktop Alternate OS: Haiku, Part 2 Xfce Settings Manager, Part 3 Command Line Computer Xfce 4.6.2: Interface Intro: Part 11 Languages A to Z: Modula2 Customize Your Xfwm Theme Video Encoding: Step­By­Step Game Zone: World Of Goo Xfce 4.6.2: Customize Thunar's Context Menu Firefox Add­ons: Inkscape Tutorial: Clipping Ob1jects Xmarks Marks The Spot OpenOffice 3.2: Calc And much more inside! TTaabbllee OOff CCoonntteennttss 3 Welcome From The Chief Editor 4 Linux IS Ready For The Desktop 5 Screenshot Showcase 6 Xfce 4.6.2: Xfce Settings Manager, Part 3 12 Screenshot Showcase The PCLinuxOS name, logo and colors are the trademark of 13 Testimonial: Greetings From A New PCLinuxOS User Texstar. 14 Xfce 4.6.2: Customize Your Xfwm Theme The NEW PCLinuxOS Magazine is a monthly online publication containing PCLinuxOS­related materials. It is 18 Double Take & Mark's Quick Gimp Tip published primarily for members of the PCLinuxOS community. The Magazine staff is comprised of volunteers 19 Command Line Interface Intro: Part 11 from the PCLinuxOS community. 28 Screenshot Showcase Visit us online at http://www.pclosmag.com 29 ms_meme's Nook: Linux Time 30 Xfce 4.6.2: Customize Thunar's Context Menu This release was made possible by the following volunteers: 33 Screenshot Showcase Chief Editor: Paul Arnote (parnote) Assistant Editors: Andrew Strick (Stricktoo), Meemaw 34 OpenOffice 3.2: Calc Consultants: Archie Arevalo, Tim Robinson Artwork: Sproggy, Timeth, Mark Szorady 37 Testimonial: PCLinuxOS ­ An Accidental Discovery 38 Alternate OS: Haiku, Part 2 Magazine Layout: parnote, Meemaw, ms_meme, Stricktoo HTML Layout: Galen Seaman 41 Video Encoding: Step­By­Step Staff: 43 Screenshot Showcase/Disclaimer Neal Brooks ms_meme Galen Seaman Mark Szorady 44 Computer Languages A to Z: Modula2 Patrick Horneker Darrel Johnston 46 Screenshot Showcase Guy Taylor Meemaw Andrew Huff Gary L.
    [Show full text]
  • Operating System Structures Outlook
    Operating System Structures Outlook Oppgerating-System Services System Call Perspective on Services OtiOperating-StSystem SttStructure Operat ing -System Im pl em en tati on , Generation, and Boot 2 Operating-System Services Services can be provided at different levels Command interpreter Command interpreter Shell: read and interpret control statements Process creation and management, I/O handling , secondary-storage management, System programs main memory management, file- system access, protection, netkitworking, … Or a mouse-based window and menu system System call API System Programs See Windows Systemsteuerung for examples Ressources System Call API E.g. File Open/Read/Write/Close- Interface Ressources e.g. buttons, … 4 Oppgyerating System Service Classes Services intended for the user Uitf(CLIbthGUI)User interface (CLI, batch, GUI) Program execution I//pO operations File-system manipulation Process communications (shared memory, message passing) Error detection (appropriate OS action for errors , debugging support) Services ensuring efficient operation of the system itself Resource allocation for multiple users or jobs at the same time e. g. CPU, RAM , File storage , I /O Accounting for billing or statistics Protection and security Essential Components? 5 Process management Process = Program in execution CildCompiler, word-processittking program, system task A process requires resources CPU time, memory , files , I/O devices Processes may run concurrently Operating system is responsible for Creating and deleting
    [Show full text]
  • Application of Software Components in Operating System Design
    CHARLES UNIVERSITY IN PRAGUE FACULTY OF MATHEMATICS AND PHYSICS DOCTORAL THESIS Martin Děcký Application of Software Components in Operating System Design Department of Distributed and Dependable Systems Supervisor of the Doctoral Thesis: Doc. Ing. Petr Tůma, Dr. Study Programme: Computer Science Specialization: I2 Software Systems Prague 2015 ii Acknowledgements The text of this doctoral thesis captures my original thoughts related to the HelenOS microkernel multiserver operating system. The text describes my overall inluence on the design of HelenOS and also my individual contributions to the implementation of HelenOS. That being written, it is completely necessary to acknowledge that no human is an island and (almost) all ideas are always extensions and recombination of previous ideas. The current source code of HelenOS in its mainline branch [42] comprises of more than 287,000 physical lines of code (see Figure 7.2). These 287,000 physical lines of code were contributed by more that 50 individuals and organizations (including myself) over the entire history of HelenOS and its direct ancestors since 2001. The size of the code would be even higher if we would also count in all the original code that can be found in the numerous feature branches of HelenOS [41] and the code in standalone patches that still wait for their inal review and merging into the main- line branch. For the sake of simplicity, we also ignore the code that was once written, but later refactored, replaced or removed. Assessing my own personal contribution to the HelenOS mainline branch can be done in a straight- forward way by examining the source code repository.
    [Show full text]
  • Ebook - Informations About Operating Systems Version: September 3, 2016 | Download
    eBook - Informations about Operating Systems Version: September 3, 2016 | Download: www.operating-system.org AIX Operating System (Unix) Internet: AIX Operating System (Unix) AmigaOS Operating System Internet: AmigaOS Operating System Android operating system Internet: Android operating system Aperios Operating System Internet: Aperios Operating System AtheOS Operating System Internet: AtheOS Operating System BeIA Operating System Internet: BeIA Operating System BeOS Operating System Internet: BeOS Operating System BSD/OS Operating System Internet: BSD/OS Operating System CP/M, DR-DOS Operating System Internet: CP/M, DR-DOS Operating System Darwin Operating System Internet: Darwin Operating System Debian Linux Operating System Internet: Debian Linux Operating System eComStation Operating System Internet: eComStation Operating System Symbian (EPOC) Operating System Internet: Symbian (EPOC) Operating System FreeBSD Operating System (BSD) Internet: FreeBSD Operating System (BSD) Gentoo Linux Operating System Internet: Gentoo Linux Operating System Haiku Operating System Internet: Haiku Operating System HP-UX Operating System (Unix) Internet: HP-UX Operating System (Unix) GNU/Hurd Operating System Internet: GNU/Hurd Operating System Inferno Operating System Internet: Inferno Operating System IRIX Operating System (Unix) Internet: IRIX Operating System (Unix) JavaOS Operating System Internet: JavaOS Operating System LFS Operating System (Linux) Internet: LFS Operating System (Linux) Linspire Operating System (Linux) Internet: Linspire Operating
    [Show full text]
  • Design and Implementation of an Overlay File System for Cloud-Assisted Mobile Apps
    IEEE TRANSACTION ON CLOUD COMPUTING 1 Design and Implementation of an Overlay File System for Cloud-Assisted Mobile Apps Nafize R. Paiker, Jianchen Shan, Cristian Borcea, Narain Gehani, Reza Curtmola, Xiaoning Ding Abstract—With cloud assistance, mobile apps can offload their resource-demanding computation tasks to the cloud. This leads to a scenario where computation tasks in the same program run concurrently on both the mobile device and the cloud. An important challenge is to ensure that the tasks are able to access and share the files on both the mobile and the cloud in a manner that is efficient, consistent, and transparent to locations. Existing distributed file systems and network file systems do not satisfy these requirements. Current systems for offloading tasks either do not support file access for offloaded tasks or do not offload tasks with file access. The paper addresses this issue by designing and implementing an application-level file system called Overlay File System (OFS). To improve efficiency, OFS maintains and buffers local copies of data sets on both the cloud and the mobile device. OFS ensures consistency and guarantees that all the reads get the latest data. It combines write-invalidate and write-update policies to effectively reduce the network traffic incurred by invalidating/updating stale data copies and to reduce the execution delay when the latest data cannot be accessed locally. To guarantee location transparency, OFS creates a unified view of the data that is location independent and is accessible as local storage. We overcome the challenges caused by the special features of mobile systems on an application-level file system, like the lack of root privilege and state loss when application is killed due to the shortage of resource and implement an easy to deploy prototype of OFS.
    [Show full text]
  • Comparison of Operating System Complexity
    Comparison of Operating System Complexity Dan•Simon Myrland [email protected] ABSTRACT It is plainly obvious that computer operating systems are growing increasingly complex every year, and have been for some time now. In the early days of UNIX a PDP11 with ¼ Mb of ram and 30 Mb of diskspace served its 100 users well, whereas today a computer with 10,000 times more resources is not even adequate for a single user. The increased complexity does not only tax our hardware but also our minds. Whereas Dennis Ritchie and Ken Thompson at Bell•Labs wrote the entire UNIX operating system and userland in a matter of weeks in the late 60’s, you would be hard pressed to find a developer today that can finish a company webpage within a year. Naturally you can do a lot more with a computer today then you could in the 70’s, but at what cost? This article does not give a definitive answer to the correct balance between providing the necessary features and keeping things simple, instead it simply analyses the complexity of operating systems, and their various components. Such analysis is illuminating in itself and can provide hints to the above question. Although commented, proprietary systems are not studied in detail here since it would be illegal to do so. Finally, only UNIX•like operating systems are analyzed. In practice very few viable non•UNIX exist, and comparing the handful that do with UNIX•like systems, would be comparing apples and oranges. Table of Contents CHAPTERS 1. Preliminary information 1 2.
    [Show full text]
  • Acronis® Backup & Recovery 10® 11 User's Guide
    Acronis® Disk Director® 11 Home Update 2 User's Guide Copyright © Acronis, Inc., 2000-2011. All rights reserved. "Acronis", "Acronis Compute with Confidence", "Acronis Recovery Manager", "Acronis Secure Zone", Acronis True Image, Acronis Try&Decide, and the Acronis logo are trademarks of Acronis, Inc. Linux is a registered trademark of Linus Torvalds. VMware and VMware Ready are trademarks and/or registered trademarks of VMware, Inc. in the United States and/or other jurisdictions. Windows and MS-DOS are registered trademarks of Microsoft Corporation. All other trademarks and copyrights referred to are the property of their respective owners. Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Distribution of this work or derivative work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. 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. Third party code may be provided with the Software and/or Service. The license terms for such third- parties are detailed in the license.txt file located in the root installation directory. You can always find the latest up-to-date list of the third party code and the associated license terms used with the Software and/or Service at http://kb.acronis.com/content/7696. 2 Copyright © Acronis, Inc. Table of contents 1 Introducing Acronis® Disk Director® 11 Home .........................................................................6 2 Installation and upgrade ........................................................................................................8 2.1 Hardware requirements ...........................................................................................................
    [Show full text]
  • How to REVERSE MALWARE on MACOS Without Getting Infected
    How to REVERSE MALWARE ON MACOS Without Getting Infected Phil Stokes Sponsored by TABLE OF CONTENTS Foreword . 3 Author’s Note . 5 Introduction . 6 Part One . 7 How To Set Up A Safe Environment To Test Malware . 7 Isolate Your macOS Guests! . 8 Tools For Testing Malware On macOS . 10 How To Find Malware Samples For macOS . 1 1 macOS Malware File Analysis – First Steps . 13 How To Check The Code Signature . 14 Application Bundle Structure . 15 How to Gather File Metadata . 16 Review: Where We Are So Far . 18 Part Two . 19 What is a Mach-O Binary? . 19 Exploring Segments & Sections . 20 The Power of Pulling Strings . .22 Using Otool To Examine A Binary . 23 Compiling Indicators of Compromise . .26 Review: Where We Are So Far . 28 Part Three . 29 How to Run Malware Blocked by Apple . .29 Using LLDB to Examine Malware . 30 Launching a Process in LLDB . .32 How to Read Registers in LLDB . 35 How to Exit the LLDB Debugger . 37 Next Steps with macOS Reverse Engineering . .38 Conclusion . 39 How to Reverse Malware on macOS without Getting Infected 2 Foreword By Patrick Wardle I'm strangely fascinated by malware. At a young age, tales of programs that could autonomously infect systems across the globe all the while stealthily avoiding detection seemed like the closest thing to "life" in cyberspace. I craved more insight into these malicious creations, seeking answers to questions such as: "How does malware infect computer systems?" "To remain undetected, what stealth mechanism does the malware employ?" "How can we generally detect such threats to ensure users remain protected?" A job in the "Malicious Code Analysis" branch within the National Security Agency (NSA) gave me insight to many of these questions through the analysis of sophisticated "nation-state" malware designed to penetrate US government networks.
    [Show full text]
  • Earth Explorer Ground Segment File Format Standard
    Ground Segment File Format Standard Doc. No.: PE-TN-ESA-GS-0001 Issue: 1.4 Date: 13 June 2003 Page: 1 Earth Explorer Ground Segment File Format Standard Prepared by: Earth Observation Programs System Support Division Checked by: P. Viau • ESTEC Noordwijk The Netherlands • Ground Segment File Format Standard Doc. No.: PE-TN-ESA-GS-0001 Issue: 1.4 Date: 13 June 2003 Page: 2 Change Record Issue Date Page Section Req’t Description of Change 0.5 3 Oct 2001 All initial draft Issue, limited distribution 0.6 30 Oct 2001 All draft issue, distributed for comments 0.9 9 Nov 2001 All draft issue, for Ground Segment Requ. Review 1.0 1 May 2002 All updated after comments from all reviewers 1.1 24 May 2002 All clarified file naming consolidated Fixed Header content added binary records description in XML Variable header 1.2 12 Jul 2002 All consolidated binary records description in XML Variable Header (arrays, structures) added ASCII guideline on usage of time reference corrected variable XML structure representation clarified empty tags usage corrected syntax for lists tags 1.3 18 Oct 2002 All All cleaned up terminology: standard (not guidelines) 2.2 added GOCE Master ICD as Reference Document 3, 4 clarified file naming vs packaging 3, 4 added ZIP as preferred packaging/compression tool 6.3 added 4-bytes alignment for binary data 7.1 corrected typos in Fixed Header example 4 changed time format in file names (if used) 1.4 13 Jun 2003 All All small clarifications (see change bars) 5.2 added validation schema reference for non-XML data 7.2.3 removed record structure description from Variable Header Ground Segment File Format Standard Doc.
    [Show full text]