Open-Source Software on IBM I Your Questions Answered
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
1994 Hearings on Software Patents
United States Patent and Trademark Office Public Hearing on Use of the Patent System to Protect Software-Related Inventions Transcript of Proceedings Wednesday, January 26, 1994 Thursday, January 27, 1994 9:00 a.m. to 5:00 p.m. Before Bruce A. Lehman Assistant Secretary of Commerce and Commissioner of Patents and Trademarks Location: San Jose Convention Center 408 Almaden Avenue San Jose, California UNITED STATES PATENT AND TRADEMARK OFFICE Public Hearing on Patent Protection for Software-Related Inventions San Jose, California -- January 26-27, 1994 Table of Participants Before: Bruce A. Lehman Assistant Secretary of Commerce and Commissioner of Patents and Trademarks United States Patent and Trademark Office The Panel: Ginger Lew General Counsel-Designate United States Department of Commerce Lawrence Goffney Assistant Commissioner for Patents-Designate United States Patent and Trademark Office Micheal K. Kirk Assistant Commissioner for External Affairs United States Patent and Trademark Office Jeffrey P. Kushan Attorney-Advisor United States Patent and Trademark Office Recording Technicians: Karl Henderscheid Support Office Services 52 Second Street, Third Floor San Francisco, CA 94104 (415) 391-4578 Trascriber: Milton Hare Rogershare Transcribers 541 Maud Avenue San Leandro, CA 94577 (510) 357-8220 - ii - UNITED STATES PATENT AND TRADEMARK OFFICE Public Hearing on Patent Protection for Software-Related Inventions San Jose, California -- January 26-27, 1994 Witnesses January 26, 1994 January 27, 1994 Mr. Clark Mr. Fiddler VideoDiscovery Wind River Systems Mr. Poppa Mr. Warren StorageTek Autodesk, Inc. Mr. Ryan Ms. O'Hare Intellectual Property Owners, Inc. Mr. Glenn Mr. LeFaivre Intellectual Property Section of the State Bar of California Apple Computer Mr. -
CA Top Secret for Z/OS Control Options Guide
CA Top Secret® for z/OS Control Options Guide r15 Ninth Edition This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. -
File System Design Approaches
File System Design Approaches Dr. Brijender Kahanwal Department of Computer Science & Engineering Galaxy Global Group of Institutions Dinarpur, Ambala, Haryana, INDIA [email protected] Abstract—In this article, the file system development design The experience with file system development is limited approaches are discussed. The selection of the file system so the research served to identify the different techniques design approach is done according to the needs of the that can be used. The variety of file systems encountered developers what are the needed requirements and show what an active area of research file system specifications for the new design. It allowed us to identify development is. The file systems researched fell into one of where our proposal fitted in with relation to current and past file system development. Our experience with file system the following four categories: development is limited so the research served to identify the 1. The file system is developed in user space and runs as a different techniques that can be used. The variety of file user process. systems encountered show what an active area of research file 2. The file system is developed in the user space using system development is. The file systems may be from one of the FUSE (File system in USEr space) kernel module and two fundamental categories. In one category, the file system is runs as a user process. developed in user space and runs as a user process. Another 3. The file system is developed in the kernel and runs as a file system may be developed in the kernel space and runs as a privileged process. -
Systems Management Performance Reference Information 7.1
IBM IBM i Systems management Performance reference information 7.1 IBM IBM i Systems management Performance reference information 7.1 Note Before using this information and the product it supports, read the information in “Notices,” on page 267. This edition applies to IBM i 7.1 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. © Copyright IBM Corporation 1998, 2010. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Reference information for Performance 1 Disk Watcher data files: QAPYDWSTAT ... 237 Collection Services data files ......... 1 Disk Watcher data files: QAPYDWTDER ... 239 Collection Services data files containing time Disk Watcher data files: QAPYDWTRC .... 240 interval data ............. 1 Data files: File abbreviations ........ 244 Collection Services data files: Field data for CL commands for performance ....... 244 configuration database files........ 221 Intelligent Agents ............ 247 Collection Services database files: Field data for Intelligent Agent concepts ........ 247 trace database files .......... 229 Developing agents........... 250 Collection Services data files: System category Set up your agent environment ...... 252 and file relationships .......... 229 Managing agents ........... 260 Collection Services data files: Task type extender 231 Disk -
OS Structures and System Calls
COS 318: Operating Systems OS Structures and System Calls Kai Li Computer Science Department Princeton University (http://www.cs.princeton.edu/courses/cos318/) Outline Protection mechanisms OS structures System and library calls 2 Protection Issues CPU Kernel has the ability to take CPU away from users to prevent a user from using the CPU forever Users should not have such an ability Memory Prevent a user from accessing others’ data Prevent users from modifying kernel code and data structures I/O Prevent users from performing “illegal” I/Os Question What’s the difference between protection and security? 3 Architecture Support: Privileged Mode An interrupt or exception (INT) User mode Kernel (privileged) mode • Regular instructions • Regular instructions • Access user memory • Privileged instructions • Access user memory • Access kernel memory A special instruction (IRET) 4 Privileged Instruction Examples Memory address mapping Flush or invalidate data cache Invalidate TLB entries Load and read system registers Change processor modes from kernel to user Change the voltage and frequency of processor Halt a processor Reset a processor Perform I/O operations 5 x86 Protection Rings Privileged instructions Can be executed only When current privileged Level (CPR) is 0 Operating system kernel Level 0 Operating system services Level 1 Level 2 Applications Level 3 6 Layered Structure Hiding information at each layer Layered dependency Examples Level N THE (6 layers) . MS-DOS (4 layers) . Pros Level 2 Layered abstraction -
CA Top Secret R16 Security Target
CA Top Secret r16 Security Target ST Version: 1.0 August 18, 2017 3333 Warrenville Road Suite 800 Lisle, IL 60532 Prepared By: Cyber Assurance Testing Laboratory 304 Sentinel Drive, Suite 100 Annapolis Junction, MD 20701 Security Target CA Top Secret r16 Table of Contents 1 Security Target Introduction ................................................................................................................. 6 1.1 ST Reference ................................................................................................................................. 6 1.1.1 ST Identification ................................................................................................................... 6 1.1.2 Document Organization ........................................................................................................ 6 1.1.3 Terminology .......................................................................................................................... 7 1.1.4 Acronyms .............................................................................................................................. 8 1.1.5 References ............................................................................................................................. 9 1.2 TOE Reference .............................................................................................................................. 9 1.3 TOE Overview ............................................................................................................................. -
CICS Essentials Auditing CICS – a Beginner’S Guide
CICS Essentials Auditing CICS – A Beginner’s Guide Julie-Ann Williams Mike Cairns Martin Underwood Craig Warren ii CICS ESSENTIALS Foreword by Brian Cummings A thorough Audit Guide for CICS is something that is long overdue. This document provides a wealth of information about CICS, its operations, and its various resources and capabilities along with audit guidelines and recommendations. Various documents on AuditNet and other sources have taken a stab at parts or all of CICS, but are likely not up to date or sufficiently complete. CICS largely remains an environment that holds its mysteries against auditors and security officers alike. The results of poor understanding can lead to dangerous levels of unidentified risk to the applications and sensitive information of entities that use the power of CICS for critical business applications. Unlike any other environment, CICS security implementations fail in the first place because all of the security control is often only focused on transactions. Transactions are many levels of resources removed from the data files and data bases they query or update. In the end, we see the greatest level of security established for the least sophisticated technical users – end business users, and the least security facing the most technically sophisticated – the CICS sub-system programmer and the CICS Application programmer. For example, it is typical to leave FCT resources unsecured and to allow the CICS regions to have total rights to the data sets they access. This condition gives sub-system and application programmers full-reign to use CICS utilities to inherit the CICS regions’ authorities and gain full access to freely browse and update data. -
402197 350 System Manual.Book
350 Cable Survey System System Manual Covers DeepView Software Version 5.x.x and Firmware Version 3.7 TSS (International) Ltd 1, Garnett Close Greycaine Industrial Estate Watford, Herts, WD24 7GL Telephone +44 (0)1923 470800 Facsimile +44 (0)1923 470842 24 hr Customer Support +44 (0)7899 665603 e-mail: [email protected] The information in this Manual is subject to change without notice and does not represent a commitment on the part of TSS (International) Ltd Document P/N 402197 Issue 2.4 abcdef January 2008 1 9 9 3 THE QUEEN'S AWARD FOR EXPORT ACHIEVEMENT Contents CAUTIONARY NOTICE This System Manual contains full installation and operating instructions and is an important part of the 350 System. This Manual should remain easily available for use by those who will install, operate and maintain the System. WARNINGS and CAUTIONS Where appropriate, this Manual includes important safety information. Safety infor- mation appears as WARNING and CAUTION instructions. You must obey these instructions: ❐ WARNING instructions alert you to a potential risk of death or injury to users of the 350 System. ❐ CAUTION instructions alert you to the potential risk of damage to the 350 System. For your convenience, the Table of Contents section includes copies of all the WARNING and CAUTION instructions contained in this Manual. Technical Support and contact information TSS (International) Ltd 1 Garnett Close, Greycaine Industrial Estate, Watford, Herts, WD24 7GL Tel: +44 (0)1923 470800 Fax: +44 (0)1923 470842 Out of UK Hours Technical Helpline: +44 (0)7899 -
Alpha Release of the Data Service
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 777533. PROviding Computing solutions for ExaScale ChallengeS D5.2 Alpha release of the Data service Start / 01 November 2017 Project: PROCESS H2020 – 777533 Duration: 36 Months Dissemination1: Public Nature2: R Due Date: 31 January 2019 Work Package: WP 5 Filename3 PROCESS_D5.2_Alpha_release_of_the_Data_service_v1.0.docx ABSTRACT During the first 15 months of its implementation, PROCESS has progressed from architecture design based on use cases’ requirements (D4.1) and through architecture validation again based on use cases (D4.2) towards initial implementations of computing services (D6.1) and data services - effort presented here in the deliverable D5.2. In D5.2 we provide an initial demonstrator of the data services, which works in cooperation with the computation services demonstrated in D6.1. The demonstrator is based on the design of the PROCESS data infrastructure described in D5.1. The implementation and initial integration of the infrastructure are based on use case requirements, formulated here as custom application-specific services which are part of the infrastructure. The central, connecting component of the data infrastructure is LOBCDER. It implements a micro-infrastructure of data services, based on dynamically provisioned Docker containers. Additionally to LOBCDER and use case-specific services, the data infrastructure contains generic data and metadata- handling services (DISPEL, DataNet). Finally, Cloudify integrates the micro-infrastructure and the orchestration components of WP7. 1 PU = Public; CO = Confidential, only for members of the Consortium (including the EC services). 2 R = Report; R+O = Report plus Other. -
Bladecenter Interoperability Guide
Front cover BladeCenter Interoperability Guide Quick reference for BladeCenter Includes internal components and interoperability external connectivity Covers software compatibility Discusses storage interoperability Ilya Krutov David Watts Note: Before using this information and the product it supports, read the information in “Notices” on page iii. Last update on 24 February 2015 This edition applies to: BladeCenter E BladeCenter H BladeCenter HT BladeCenter S BladeCenter HS12 type 8028 BladeCenter HS22 BladeCenter HS22V BladeCenter HS23 (E5-2600) BladeCenter HS23 (E5-2600 v2) BladeCenter HS23E BladeCenter HX5 BladeCenter PS700/701/702 BladeCenter PS703/704 © Copyright Lenovo 2015. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract Contents Notices . iii Trademarks . iv Preface . .v Authors. .v Comments welcome. vi Do you have the latest version?. vi Chapter 1. Chassis interoperability. 1 1.1 Server to chassis compatibility . 2 1.1.1 HS22 chassis support . 3 1.1.2 HS22V chassis support. 4 1.1.3 HS23 (E5-2600) chassis support . 5 1.1.4 HS23 (E5-2600 v2) chassis support . 6 1.1.5 HS23E chassis support. 7 1.1.6 HX5 chassis support . 8 1.1.7 PS700 chassis support . 9 1.2 I/O module to chassis interoperability . 10 1.2.1 SAS, InfiniBand, Pass-thru, and interconnect modules interoperability . 10 1.2.2 Ethernet I/O module interoperability . 11 1.2.3 Fibre Channel I/O module interoperability. 12 1.3 I/O module to adapter interoperability . 13 1.3.1 I/O module bay to adapter mappings . 13 1.3.2 Ethernet I/O modules and adapters . -
Hands-On Linux Administration on Azure
Hands-On Linux Administration on Azure Explore the essential Linux administration skills you need to deploy and manage Azure-based workloads Frederik Vos BIRMINGHAM - MUMBAI Hands-On Linux Administration on Azure Copyright © 2018 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing or its dealers and distributors, will be held liable for any damages caused or alleged to have been caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. Commissioning Editor: Vijin Boricha Acquisition Editor: Rahul Nair Content Development Editor: Nithin George Varghese Technical Editor: Komal Karne Copy Editor: Safis Editing Project Coordinator: Drashti Panchal Proofreader: Safis Editing Indexer: Mariammal Chettiyar Graphics: Tom Scaria Production Coordinator: Deepika Naik First published: August 2018 Production reference: 1310818 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78913-096-6 www.packtpub.com mapt.io Mapt is an online digital library that gives you full access to over 5,000 books and videos, as well as industry leading tools to help you plan your personal development and advance your career. -
IBM System X and Bladecenter Business Partner Guidebook Titles of Interest
July 2011 CLICK HERE to check for updates Your Road Map to Success with IBM IBM System x System x and and BladeCenter BladeCenter Business Partner Guidebook Over 100,000 copies downloaded! Edited by Jim Hoskins IBM System x and BladeCenter Business Partner Guidebook Titles of Interest More IBM Titles of Interest • IBM Information Infrastructure Business Partner Guidebook • Exploring IBM SOA Technology & Practice • Exploring IBM Accelerators for WebSphere Portal Top Internet Business Titles • 101 Ways to Promote Your Web Site • 3G Marketing on the Internet • Protect Your Great Ideas for Free! • And many more… For more information, visit us at maxpress.com or email us at [email protected]. IBM System x and BladeCenter Business Partner Guidebook Twentieth Edition Your Road Map to Success with IBM System x and BladeCenter Edited by Jim Hoskins (version 20.0e) 605 Silverthorn Road Gulf Breeze, FL 32561 maxpress.com Notices Production Manager: Jacquie Wallace Cover Designer: Lauren Smith This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in rendering professional services. If legal, accounting, medical, psychological, or any other expert assistance is required, the services of a competent professional person should be sought. ADAPTED FROM A DECLARATION OF PRIN- CIPLES OF A JOINT COMMITTEE OF THE AMERICAN BAR ASSOCIATION AND PUBLISHERS. Copyright 2011 by Maximum Press. All rights reserved. Published simultaneously in Canada. Reproduction or translation of any part of this work beyond that permitted by Section 107 or 108 of the 1976 United States Copyright Act without the permission of the copyright owner is unlawful.