DOCSLIB.ORG

Hierarchical File System Usage Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Hierarchical File System Usage Guide Hierarchical File System Usage Guide Learn how to manage HFS data Optimize HFS performance Set up sysplex sharing Nigel Morton Toru Yamazaki Rama Ayyar Dirk Gutschke Barry Kadleck Masato Miyamoto ibm.com/redbooks International Technical Support Organization SG24-5482-01 Hierarchical File System Usage Guide September 2000 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix C, “Special notices” on page 307. Second Edition (September 2000) This edition applies to Version 1, Release 5 of DFSMS/MVS, Program Number 5695-DF1 for use with Version 2 Release 7 of OS/390 or higher. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1999, 2000. All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures ......................................................ix Tables ...................................................... xiii Preface ......................................................xv The team that wrote this redbook ...................................... xv Commentswelcome................................................xvii Chapter 1. Introduction to the Hierarchical File System................1 1.1HFSoverview...............................................1 1.2StructureofanHFSdataset....................................2 1.2.1 HFS track capacities on a 3380 and 3390 volume ................2 1.2.2 Index structure of an HFS data set ...........................4 1.2.3 Index updates through shadow writes . ......................10 1.2.4Syncprocess..........................................11 1.3 New enhancements . .......................................13 1.3.1 DFSMS/MVS 1.5 enhancements ............................14 1.3.2 OS/390 2.9 enhancements ................................14 1.3.3Non-SMSHFSdatasets..................................15 1.3.4 DFSORT support of HFS data sets ..........................15 Chapter 2. Introduction to OS/390 UNIX System Services .............17 2.1 Required USS operation level to use HFS. ......................17 2.1.1Minimummode.........................................17 2.1.2Sockets-onlymode......................................18 2.1.3Full-functionmode.......................................18 2.2 UNIX System Services and related address spaces .................19 2.3UNIXfilesystemoverview....................................20 2.3.1UNIXfilesystemstructure.................................20 2.3.2 Recommended file system structure . ......................22 2.4HFSandUNIXSystemServicessecurity.........................24 2.4.1UNIXfilesecurityoverview................................24 2.4.2 UNIX users and superuser ................................24 2.4.3 UNIX groups ...........................................25 2.4.4UNIXfilesecuritywiththeOS/390SecurityServer(RACF)........29 Chapter 3. HFS externals .......................................33 3.1SMSconsiderations.........................................33 3.1.1BasicSMSterms........................................33 3.1.2DefiningSMSconstructsforHFSdatasets....................35 3.1.3Dataclass.............................................36 3.1.4Storageclass..........................................37 3.1.5 Management class ......................................39 3.1.6Storagegroup..........................................42 3.1.7ACSroutines...........................................46 3.2Non-SMSconsiderations......................................51 3.2.1 Non-SMS availability management ..........................52 3.2.2 Non-SMS space management. ............................54 3.3 HFS PARMLIB and command enhancements ......................56 3.3.1BPXPRMxxoptions......................................56 3.3.2TSOMOUNTcommand..................................63 © Copyright IBM Corp. 1999, 2000 iii 3.3.3TSOUNMOUNTcommand............................... 64 3.3.4SETOMVSsystemcommand..............................66 3.3.5confighfsshellcommand................................. 68 3.3.6DisplayingtheSYNCintervalsettings....................... 72 3.4 Requirements and restrictions . .............................. 73 3.4.1 Restrictions for executable files (object modules) .............. 74 3.4.2 Additional dependencies, issues, restrictions, and requirements . 74 Chapter 4. Allocating and mounting HFS data sets.................. 77 4.1AllocatinganHFS.......................................... 77 4.1.1Multi-volumeallocationconsiderations....................... 78 4.1.2Guaranteedspaceconsiderations.......................... 78 4.1.3SMSdefinitionexamples................................. 82 4.1.4UsingISPF........................................... 83 4.1.5UsingDDstatementinabatchjob.......................... 86 4.1.6 Miscellaneous allocation methods . ......................... 87 4.1.7UsingISHELL......................................... 89 4.1.8SummaryofHFSdatasetallocations....................... 91 4.2MountinganHFS........................................... 91 4.2.1 Before mounting HFS data sets . ......................... 92 4.2.2 TSO MOUNT and UNMOUNT commands . ................... 93 4.2.3ISPFISHELL.......................................... 95 4.2.4 OMVS mountx and unmountx shell commands . ..............98 4.2.5 After mounting HFS data sets ............................. 98 4.2.6AddingMOUNTStatementstoBPXPRMxx................... 99 4.2.7 Status of mounted HFS data sets . ......................... 99 Chapter 5. Managing HFS data sets ............................. 103 5.1DFSMSdssdumpandrestore................................ 103 5.1.1Dumpprocessing...................................... 103 5.1.2Restoreprocessing.................................... 114 5.2DFSMShsmbackupandmigration............................. 115 5.2.1CommonDFSMShsmfunctions........................... 115 5.2.2Backupprocessing.................................... 118 5.2.3RecoveryandrestoreofHFSdatasets..................... 123 5.2.4 Migrating and recalling an HFS data set . .................. 125 5.3Recoveringfilesanddirectories............................... 126 5.3.1 Copytree utility........................................ 127 5.3.2Consistencycheckingofafilesystem...................... 129 5.4 Additional space management topics. ........................ 130 5.4.1 Releasing unused space . ............................. 130 5.4.2DeletingorremovinganHFSdataset...................... 131 5.4.3TransportinganHFS................................... 132 5.5IncreasingthesizeofanHFSdataset......................... 132 5.5.1IncreasingthefilesystemsizeusingDFSMSdss.............. 133 5.5.2 IDCAMS ALTER to add candidate volumes .................. 137 5.5.3 USS confighfs command to change file system size ........... 139 5.6Displayingthefilesystemsize................................ 143 5.6.1UsingthedfUNIXcommand............................. 143 5.6.2UsingtheUNIXconfighfscommand........................ 145 5.6.3ISPFdatasetinformation............................... 146 5.6.4TSOISHELL—filesystemattributes...................... 147 5.6.5ISMFdatasetinformation............................... 148 iv Hierarchical File System Usage Guide 5.7MovinganddisplayingtheownershipforasharedHFS.............148 5.8 Installing service to products in the HFS .........................150 5.9 Snapshot and DFSMSdss COPY considerations. ................150 Chapter 6. Tivoli Storage Manager...............................153 6.1 Introduction to Tivoli Storage Manager ..........................153 6.1.1 Why use Tivoli Storage Manager?..........................153 6.1.2 Tivoli Storage Manager components . .....................154 6.2 Installing the Tivoli Storage Manager USS client . ................155 6.2.1Orderingtheclientsoftware..............................155 6.2.2Initialinstallation.......................................155 6.2.3Customizingtheclient...................................155 6.2.4 Using the Tivoli Storage Manager client .....................158 6.2.5TSMserverconsiderations...............................162 6.2.6HFSfilesharingconsiderations............................163 6.3 Data management strategies . ................................163 6.3.1 DFSMSdss and Tivoli Storage Manager .....................163 6.3.2Disasterrecoveryconsiderations...........................164 6.4Performanceconsiderations..................................164 6.4.1Tuning...............................................164 6.4.2 Reorganizing HFS for performance .........................165 Chapter 7. Sharing and serialization for HFS data sets ..............167 7.1Serializationconsiderations..................................170 7.1.1 ENQ usage for shared HFS (OS/390 2.9 and higher) . ..........171 7.1.2SerializationbyDFSMSdss...............................173 7.2Sharingconsiderations(OS/3902.8andbelow)...................174 7.2.1 Mount integrity (write protection) enhancements ...............175 7.3 HFS sysplex sharing (OS/390 2.9 and above).....................179 7.3.1Functionshipping......................................179 7.3.2Sysplexsharingconsiderations............................182
Load more

Recommended publications
  • Sequence Listings Webinar Suzannah K. Sundby Carl Oppedahl
    Suzannah K. Sundby Canady + Lortz LLP Sequence Listings Webinar January 9, 2018 – Updated Version Carl Oppedahl Oppedahl Patent Law Firm LLC DISCLAIMER These materials and views expressed today reflect only the personal views of the author and do not necessarily represent the views of other members and clients of the author’s organizations. These materials are public information and have been prepared solely for educational purposes to contribute to the understanding of U.S. intellectual property law. While every attempt was made to ensure that these materials are accurate, errors or omissions may be contained therein, for which any liability is disclaimed. These materials and views are not a source of legal advice and do not establish any form of attorney-client relationship with the authors and their law firms. Why are some sequence errors not identified by Checker? Is “SEQ ID NO” required before sequences in Specifications? Do you recommend using the PatentIn Software? How do you correct sequence listing errors in PCTs? What about the new WIPO ST.26 Standard? Is Checker worthwhile? How can I easily edit sequence listings generated by others? Can I use other software to generate sequence listings? How do I file sequence listings using EFS-Web and ePCT? How long does it take the USPTO to review and approve? Any risk TYFNIL of using certain sequence descriptors? Help! IT locked down my computer… what do I do? Any sequence listing tips? Why Practitioners Should Know and Do Usually lack of time to send to outside vendors Last minute changes to applications (apps) containing sequences (seqs) Particularly, changes to claims Not hostage to staff/vendors, overtime, etc.
    [Show full text]
  • Copy on Write Based File Systems Performance Analysis and Implementation
    Copy On Write Based File Systems Performance Analysis And Implementation Sakis Kasampalis Kongens Lyngby 2010 IMM-MSC-2010-63 Technical University of Denmark Department Of Informatics Building 321, DK-2800 Kongens Lyngby, Denmark Phone +45 45253351, Fax +45 45882673 [email protected] www.imm.dtu.dk Abstract In this work I am focusing on Copy On Write based file systems. Copy On Write is used on modern file systems for providing (1) metadata and data consistency using transactional semantics, (2) cheap and instant backups using snapshots and clones. This thesis is divided into two main parts. The first part focuses on the design and performance of Copy On Write based file systems. Recent efforts aiming at creating a Copy On Write based file system are ZFS, Btrfs, ext3cow, Hammer, and LLFS. My work focuses only on ZFS and Btrfs, since they support the most advanced features. The main goals of ZFS and Btrfs are to offer a scalable, fault tolerant, and easy to administrate file system. I evaluate the performance and scalability of ZFS and Btrfs. The evaluation includes studying their design and testing their performance and scalability against a set of recommended file system benchmarks. Most computers are already based on multi-core and multiple processor architec- tures. Because of that, the need for using concurrent programming models has increased. Transactions can be very helpful for supporting concurrent program- ming models, which ensure that system updates are consistent. Unfortunately, the majority of operating systems and file systems either do not support trans- actions at all, or they simply do not expose them to the users.
    [Show full text]
  • Chrooting All Services in Linux
    LinuxFocus article number 225 http://linuxfocus.org Chrooting All Services in Linux by Mark Nielsen (homepage) About the author: Abstract: Mark works as an independent consultant Chrooted system services improve security by limiting damage that donating time to causes like someone who broke into the system can possibly do. GNUJobs.com, writing _________________ _________________ _________________ articles, writing free software, and working as a volunteer at eastmont.net. Introduction What is chroot? Chroot basically redefines the universe for a program. More accurately, it redefines the "ROOT" directory or "/" for a program or login session. Basically, everything outside of the directory you use chroot on doesn't exist as far a program or shell is concerned. Why is this useful? If someone breaks into your computer, they won't be able to see all the files on your system. Not being able to see your files limits the commands they can do and also doesn't give them the ability to exploit other files that are insecure. The only drawback is, I believe it doesn't stop them from looking at network connections and other stuff. Thus, you want to do a few more things which we won't get into in this article too much: Secure your networking ports. Have all services run as a service under a non-root account. In addition, have all services chrooted. Forward syslogs to another computer. Analyze logs files Analyze people trying to detect random ports on your computer Limit cpu and memory resources for a service. Activate account quotas. The reason why I consider chroot (with a non-root service) to be a line of defense is, if someone breaks in under a non-root account, and there are no files which they can use to break into root, then they can only limit damage to the area they break in.
    [Show full text]
  • The Linux Kernel Module Programming Guide
    The Linux Kernel Module Programming Guide Peter Jay Salzman Michael Burian Ori Pomerantz Copyright © 2001 Peter Jay Salzman 2007−05−18 ver 2.6.4 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at http://opensource.org/licenses/osl.php. This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose. The author encourages wide distribution of this book for personal or commercial use, provided the above copyright notice remains intact and the method adheres to the provisions of the Open Software License. In summary, you may copy and distribute this book free of charge or for a profit. No explicit permission is required from the author for reproduction of this book in any medium, physical or electronic. Derivative works and translations of this document must be placed under the Open Software License, and the original copyright notice must remain intact. If you have contributed new material to this book, you must make the material and source code available for your revisions. Please make revisions and updates available directly to the document maintainer, Peter Jay Salzman <[email protected]>. This will allow for the merging of updates and provide consistent revisions to the Linux community. If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the Linux Documentation Project (LDP).
    [Show full text]
  • Use of Seek When Writing Or Reading Binary Files
    Title stata.com file — Read and write text and binary files Description Syntax Options Remarks and examples Stored results Reference Also see Description file is a programmer’s command and should not be confused with import delimited (see [D] import delimited), infile (see[ D] infile (free format) or[ D] infile (fixed format)), and infix (see[ D] infix (fixed format)), which are the usual ways that data are brought into Stata. file allows programmers to read and write both text and binary files, so file could be used to write a program to input data in some complicated situation, but that would be an arduous undertaking. Files are referred to by a file handle. When you open a file, you specify the file handle that you want to use; for example, in . file open myfile using example.txt, write myfile is the file handle for the file named example.txt. From that point on, you refer to the file by its handle. Thus . file write myfile "this is a test" _n would write the line “this is a test” (without the quotes) followed by a new line into the file, and . file close myfile would then close the file. You may have multiple files open at the same time, and you may access them in any order. 1 2 file — Read and write text and binary files Syntax Open file file open handle using filename , read j write j read write text j binary replace j append all Read file file read handle specs Write to file file write handle specs Change current location in file file seek handle query j tof j eof j # Set byte order of binary file file set handle byteorder hilo j lohi j 1 j 2 Close
    [Show full text]
  • Serverless Network File Systems
    Serverless Network File Systems Thomas E. Anderson, Michael D. Dahlin, Jeanna M. Neefe, David A. Patterson, Drew S. Roselli, and Randolph Y. Wang Computer Science Division University of California at Berkeley Abstract In this paper, we propose a new paradigm for network file system design, serverless network file systems. While traditional network file systems rely on a central server machine, a serverless system utilizes workstations cooperating as peers to provide all file system services. Any machine in the system can store, cache, or control any block of data. Our approach uses this location independence, in combination with fast local area networks, to provide better performance and scalability than traditional file systems. Further, because any machine in the system can assume the responsibilities of a failed component, our serverless design also provides high availability via redundant data storage. To demonstrate our approach, we have implemented a prototype serverless network file system called xFS. Preliminary performance measurements suggest that our architecture achieves its goal of scalability. For instance, in a 32-node xFS system with 32 active clients, each client receives nearly as much read or write throughput as it would see if it were the only active client. 1. Introduction A serverless network file system distributes storage, cache, and control over cooperating workstations. This approach contrasts with traditional file systems such as Netware [Majo94], NFS [Sand85], Andrew [Howa88], and Sprite [Nels88] where a central server machine stores all data and satisfies all client cache misses. Such a central server is both a performance and reliability bottleneck. A serverless system, on the other hand, distributes control processing and data storage to achieve scalable high performance, migrates the responsibilities of failed components to the remaining machines to provide high availability, and scales gracefully to simplify system management.
    [Show full text]
  • Of Friday 13 June 2008 Supplement No. 1 Birthday Honours List — United Kingdom
    05-06-2008 13:04:14 [SO] Pag Table: NGSUPP PPSysB Job: 398791 Unit: PAG1 Number 58729 Saturday 14 June 2008 http://www.london-gazette.co.uk B1 [ Richard Gillingwater. (Jun. 14, 2008). C.B.E. Commander of the Order of the British Empire, 2008 Birthday Honours, No. 58729, Supp. No. 1, PDF, p. B7. London Gazette. Reproduced for educationaly purposes only. Fair Use relied upon. ] Registered as a newspaper Published by Authority Established 1665 of Friday 13 June 2008 Supplement No. 1 Birthday Honours List — United Kingdom CENTRAL CHANCERY OF Dr. Philip John Hunter, C.B.E., Chief Schools THE ORDERS OF KNIGHTHOOD Adjudicator. For services to Education. Moir Lockhead, O.B.E., Chief Executive, First Group. St. James’s Palace, London SW1 For services to Transport. 14 June 2008 Professor Andrew James McMichael, F.R.S., Professor of Molecular Medicine and Director, Weatherall The Queen has been graciously pleased, on the occasion Institute of Molecular Medicine, University of Oxford. of the Celebration of Her Majesty’s Birthday, to signify For services to Medical Science. her intention of conferring the honour of Knighthood William Moorcroft, Principal, TraVord College. For upon the undermentioned: services to local and national Further Education. William Desmond Sargent, C.B.E., Executive Chair, Better Regulation Executive, Department for Business, Enterprise and Regulatory Reform. For services to Knights Bachelor Business. Michael John Snyder. For services to Business and to the City of London Corporation. Paul Robert Stephenson, Q.P.M., Deputy Commissioner, Dr. James Iain Walker Anderson, C.B.E. For public and Metropolitan Police Service.
    [Show full text]
  • IBM Systems, Consult the Latest IBM System/370, 30Xx, and 4300 Processors Bibliography, GC20-0001, for the Editions That Are Applicable and Current
    ---- MVS/Extended Architecture Licensed --------- --- ---,--------- --- Data Facility Product: Program ( Planning Guide c- Order Number Data Facility Product Version 1 GC26-4040-3 5665-284 Release 1.2 o I~ourth Edition (.January 1987) This is a major revision of, and makes obsolete, GC26-4040-2. This edition applies to Version I Release 1.2 of MVSiExtended Architecture Data Facility Product, Licensed Program 5665-284, and to ariy subsequent releases until otherwise indicated in new editions or technical newsletters. The changes for this edition are summarized under "Summary of Changes" following the preface. Specific changes are indicated by' a vertical bar to the left of the change. These bars will be deleted at any subsequent republication of the page affected. Editorial changes that have no technical significance are not noted. Changes are made periodically to this publication; before using this publication in connection with the operation of IBM systems, consult the latest IBM System/370, 30xx, and 4300 Processors Bibliography, GC20-0001, for the editions that are applicable and current. References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IHM operates. Any reference to an IBM licensed program in this publication is not intended .to state or imply that only IHM's program may be used. Any functionally equivalent program may be used instead. Requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. If you request publications from the address given below, your order will be delayed because publications are not stocked there.
    [Show full text]
  • File Handling in Python
    hapter C File Handling in 2 Python There are many ways of trying to understand programs. People often rely too much on one way, which is called "debugging" and consists of running a partly- understood program to see if it does what you expected. Another way, which ML advocates, is to install some means of understanding in the very programs themselves. — Robin Milner In this Chapter » Introduction to Files » Types of Files » Opening and Closing a 2.1 INTRODUCTION TO FILES Text File We have so far created programs in Python that » Writing to a Text File accept the input, manipulate it and display the » Reading from a Text File output. But that output is available only during » Setting Offsets in a File execution of the program and input is to be entered through the keyboard. This is because the » Creating and Traversing a variables used in a program have a lifetime that Text File lasts till the time the program is under execution. » The Pickle Module What if we want to store the data that were input as well as the generated output permanently so that we can reuse it later? Usually, organisations would want to permanently store information about employees, inventory, sales, etc. to avoid repetitive tasks of entering the same data. Hence, data are stored permanently on secondary storage devices for reusability. We store Python programs written in script mode with a .py extension. Each program is stored on the secondary device as a file. Likewise, the data entered, and the output can be stored permanently into a file.
    [Show full text]
  • 11.7 the Windows 2000 File System
    830 CASE STUDY 2: WINDOWS 2000 CHAP. 11 11.7 THE WINDOWS 2000 FILE SYSTEM Windows 2000 supports several file systems, the most important of which are FAT-16, FAT-32, and NTFS (NT File System). FAT-16 is the old MS-DOS file system. It uses 16-bit disk addresses, which limits it to disk partitions no larger than 2 GB. FAT-32 uses 32-bit disk addresses and supports disk partitions up to 2 TB. NTFS is a new file system developed specifically for Windows NT and car- ried over to Windows 2000. It uses 64-bit disk addresses and can (theoretically) support disk partitions up to 264 bytes, although other considerations limit it to smaller sizes. Windows 2000 also supports read-only file systems for CD-ROMs and DVDs. It is possible (even common) to have the same running system have access to multiple file system types available at the same time. In this chapter we will treat the NTFS file system because it is a modern file system unencumbered by the need to be fully compatible with the MS-DOS file system, which was based on the CP/M file system designed for 8-inch floppy disks more than 20 years ago. Times have changed and 8-inch floppy disks are not quite state of the art any more. Neither are their file systems. Also, NTFS differs both in user interface and implementation in a number of ways from the UNIX file system, which makes it a good second example to study. NTFS is a large and complex system and space limitations prevent us from covering all of its features, but the material presented below should give a reasonable impression of it.
    [Show full text]
  • Reference Guide
    Reference Guide Scyld ClusterWare Release 5.10.1-5101g0000 December 18, 2013 Reference Guide: Scyld ClusterWare Release 5.10.1-5101g0000; December 18, 2013 Revised Edition Published December 18, 2013 Copyright © 1999 - 2013 Penguin Computing, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without the prior written permission of Penguin Computing, Inc.. The software described in this document is "commercial computer software" provided with restricted rights (except as to included open/free source). Use beyond license provisions is a violation of worldwide intellectual property laws, treaties, and conventions. Scyld ClusterWare, the Highly Scyld logo, and the Penguin Computing logo are trademarks of Penguin Computing, Inc.. Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Infiniband is a trademark of the InfiniBand Trade Association. Linux is a registered trademark of Linus Torvalds. Red Hat and all Red Hat-based trademarks are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks and copyrights referred to are the property of their respective owners. Table of Contents Preface .....................................................................................................................................................................................v
    [Show full text]
  • BEA TUXEDO Reference Manual Section 5 - File Formats and Data Descriptions
    BEA TUXEDO Reference Manual Section 5 - File Formats and Data Descriptions BEA TUXEDO Release 6.5 Document Edition 6.5 February 1999 Copyright Copyright © 1999 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.
    [Show full text]