DOCSLIB.ORG

Open System Services Management and Operations Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open System Services Management and Operations Guide Open System Services Management and Operations Guide Abstract This guide describes how to manage and operate the HP NonStop™ operating system Open System Services (OSS) environment. Product Version OSS Monitor T8622H02, T8622G12 Supported Release Version Updates (RVUs) This guide supports G06.27 and all subsequent G-series RVUs and H06.06 and all subsequent H-series RVUs until otherwise indicated by its replacement publication. Part Number Published 527191-004 May 2006 Document History Part Number Product Version Published 527191-002 OSS Monitor T8622H01, T8622G11 July 2005 527191-003 OSS Monitor T8622H01, T8622G12 September 2005 527191-004 OSS Monitor T8622H02, T8622G12 May 2006 Open System Services Management and Operations Guide Glossary Index Figures Tables What’s New in This Guide xiii Guide Information xiii New and Changed Information xiii About This Guide xv What This Guide Is About xv Who Should Read This Guide? xv What This Guide Does Not Cover xv What Is in This Guide? xvi Related Reading, Training, and Services xvii Unsupported Utilities xix Acknowledgment xx Notation Conventions xx 1. Introducing Open System Services The Operating System Environments 1-1 Management Tools 1-2 Management and Operations Tasks 1-3 OSS File System Concepts 1-5 OSS Files 1-6 The /G Directory 1-7 The /E Directory 1-7 The /dev Directory 1-8 Components to Be Managed 1-9 Input/Output Utilities 1-9 OSS Security 1-9 OSS File-System Components 1-10 Interprocess Communication Facilities 1-11 Hewlett-Packard Company—527191-004 i Contents 2. Operating the OSS Environment 2. Operating the OSS Environment Starting and Stopping the OSS Environment 2-1 Possible Ways to Start the OSS File System 2-1 Automatic Startup Service 2-2 Possible Ways to Stop the OSS File System 2-3 Manually Stopping the OSS File System and the OSS Environment 2-3 Manually Restarting the OSS File System and the OSS Environment 2-6 Managing the OSS Subsystem 2-6 Starting the OSS Monitor 2-7 Stopping the OSS Monitor 2-15 Obtaining Information About the OSS Subsystem 2-15 Changing the OSS Subsystem Configuration 2-18 Enabling the Automatic Startup Service 2-18 Removing the OSS File System 2-19 Monitoring OSS Processes 2-20 Monitoring OSS Processes From the OSS Environment 2-21 Monitoring OSS Processes From the Guardian Environment 2-21 Managing OSS Processes 2-22 Making OSS Application Processes Persistent with the Kernel Subsystem 2-23 Managing OSS Process Scheduling 2-30 Managing OSS Process Processor Use 2-33 Managing OSS Interprocess Communication Facilities 2-34 Scheduling Periodic Tasks 2-34 Using the cron Process 2-35 Using the NetBatch Product 2-38 3. Understanding the OSS File System OSS Pathnames 3-1 Using Pathnames for Remote Files 3-5 Using the Local Root Directory as a Pathname 3-5 OSS File Components 3-7 OSS Catalog Files 3-7 OSS Data Files 3-7 Relating OSS Files, Filesets, and Disk Volumes 3-8 OSS File Size Considerations 3-8 Fileset Size Considerations 3-9 OSS Configuration Files 3-10 Open System Services Management and Operations Guide—527191-004 ii Contents 4. Managing Servers 4. Managing Servers Introducing the OSS Servers 4-1 The OSS Name Servers 4-2 The OSS Message-Queue Server 4-2 The OSS Sockets Local Server 4-4 The OSS Transport Agent Servers 4-4 The Terminal Helper Servers 4-4 The Network Services Servers and Tools 4-5 Configuration Files 4-7 Configuration Files Used for the OSS Name Servers 4-7 Configuration Database Files Used for the OSS Message-Queue Server 4-19 Configuration Database Files Used for the OSS Sockets Local Server 4-20 Configuration Database Files Used for the OSS Transport Agent Servers 4-23 Configuration Files for the Network Services Servers and Tools 4-24 Adding a Server 4-28 Configuring a Server 4-29 Configuring an OSS Name Server 4-29 Configuring the OSS Message-Queue Server 4-30 Configuring the OSS Sockets Local Server 4-30 Configuring the OSS Transport Agent Servers 4-31 Configuring Network Services Servers, Tools, and Applications 4-31 Starting a Server 4-36 Starting an OSS Name Server 4-36 Starting the OSS Message-Queue Server 4-37 Starting the OSS Sockets Local Server 4-37 Starting an OSS Transport Agent Server 4-38 Starting a Network Services Server 4-38 Obtaining Information About a Server 4-39 Determining Whether a Server Is Running 4-39 Determining the Current Configuration of a Server 4-41 Determining Usage and Configuration of Network Services Servers 4-42 Stopping a Server 4-43 Stopping a Specific OSS Name Server 4-43 Stopping the OSS Message-Queue Server 4-44 Stopping the OSS Sockets Local Server 4-44 Stopping an OSS Transport Agent Server 4-45 Stopping a Network Services Server 4-45 Open System Services Management and Operations Guide—527191-004 iii Contents 4. Managing Servers (continued) 4. Managing Servers (continued) Reconfiguring a Server 4-46 Reconfiguring an OSS Name Server 4-46 Reconfiguring the OSS Message-Queue Server 4-47 Reconfiguring the OSS Sockets Local Server 4-48 Reconfiguring a Network Services Server 4-49 Removing a Server 4-49 Removing an OSS Name Server 4-49 Removing a Network Services Server 4-50 Troubleshooting a Server 4-50 5. Managing Filesets Creating a Fileset 5-1 Creating a Unique Fileset 5-1 Creating a Storage Pool 5-6 Starting (Mounting) or Restarting Filesets 5-7 Automatic Restart of Filesets During OSS Monitor Startup 5-8 Automatic Restart of Filesets by the Automatic Startup Service 5-9 Automatic Restart of Filesets After OSS Name Server Failure 5-10 Automatic Restart of OSS Name Servers After Processor Failure 5-10 Potential Problems During Automatic Restart of Filesets 5-10 Auditing a Fileset 5-12 Using the AUDITENABLED Attribute 5-12 Audited SCF Operations 5-12 Obtaining Information About a Fileset 5-13 Checking the Current Configuration of a Fileset 5-13 Checking the Current State of a Fileset 5-13 Stopping (Unmounting) a Fileset 5-13 Reconfiguring a Fileset 5-14 Changing the Operating Parameters of a Fileset 5-14 Changing OSS File Caching for the Disks of a Fileset 5-18 Changing the Physical Makeup of a Fileset 5-21 Checking and Repairing Fileset Integrity 5-24 When Do You Need to Check Fileset Integrity? 5-24 FSCK Log File 5-25 Inconsistencies Checked by FSCK 5-29 Generated Catalog Files 5-33 What Happens When Diagnosis Appears to Fail? 5-33 Deleting a Fileset 5-34 Open System Services Management and Operations Guide—527191-004 iv Contents 5. Managing Filesets (continued) 5. Managing Filesets (continued) Renaming a Fileset 5-34 Updating Existing Fileset Configurations 5-35 Removing Older Configuration Files 5-35 Moving a Directory Hierarchy to Its Own Fileset 5-36 Cleaning Up a Fileset 5-37 Troubleshooting Filesets 5-39 Managing and Repairing Fileset Catalog Files 5-40 Upgrading OSS Catalog Files 5-40 Moving and Removing OSS Catalog Files 5-41 6. Managing OSS Files Obtaining Information About OSS Files 6-1 Interpreting Guardian Filenames for OSS Files 6-2 Using the OSS gname Command 6-2 Using the OSS pname Command 6-3 Using FUP INFO on OSS Regular Files 6-3 Installing New Product Files 6-4 Using COPYOSS 6-6 Using PINSTALL 6-8 Removing Obsolete OSS Files and Directories 6-9 Updating the whatis Database Files 6-10 Backing Up and Restoring OSS Files 6-11 Considerations 6-12 Backing Up the OSS Environment Using a Version of Backup/Restore 6-14 Backing Up User Files 6-15 Backing Up OSS Files to Other Expand Nodes 6-22 OSS Files and Backup/Restore Utilities (T9074) 6-23 Restoring User Files 6-24 Redirecting OSS Standard Files 6-27 Controlling the Maximum Number of Files 6-30 7. Managing Terminal Access How Users Gain Access to the OSS Environment 7-1 Configuring Telserv Access 7-2 Configuring the Telserv TACL Service 7-2 Configuring a Telserv Direct Service 7-3 Configuring FTP Access 7-5 Open System Services Management and Operations Guide—527191-004 v Contents 8. Managing Security 8. Managing Security Common and Unique Characteristics of OSS and UNIX Security 8-1 Administrative Files and Directories 8-1 Administrative Tools 8-4 Users and Groups 8-6 Components of OSS Security Management 8-8 Managing Users and Groups 8-9 Differences Between OSS and UNIX User and User-Group Configuration 8-9 How Users Gain Access to the OSS Environment 8-10 User and User-Group Attributes 8-12 Assigning an Initial Working Directory 8-13 Assigning an Initial Program 8-17 Hints and Suggestions 8-19 OSS Security Auditing 8-23 Audit Records for OSS Objects 8-23 Auditing of OSS Shell Commands 8-26 Protecting Your System 8-26 OSS Shell Commands Useful for Security Administration 8-26 Use of suid Scripts 8-27 Preventing Security Problems 8-28 Identifying Attempts to Break Security 8-29 9. Managing With the Shell OSS Management With the Shell 9-1 Customizing the OSS Shell 9-2 Setting Up a Default .profile File 9-2 Setting Up an /etc/profile File 9-2 Localizing Software 9-5 Localizing Reference Pages 9-7 Monitoring the OSS Environment With the Shell 9-8 Slow Performance 9-8 Overuse of Resources 9-8 Controlling the Growth of Directories 9-8 Defragmenting Disks 9-9 Compressing Files 9-10 Executing Remote Shell Commands 9-10 Parsing Command Options With the getopts Command 9-11 Open System Services Management and Operations Guide—527191-004 vi Contents 10.
Load more

Recommended publications
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • NOAA Technical Report NOS NGS 60
    NOAA Technical Report NOS NGS 60 NAD83 (NSR2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Rockville, MD August 2008 NOAA Technical Report NOS NGS 60 NAD 83(NSRS2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Silver Spring, MD August 2008 U.S. DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration National Ocean Service Contents Overview ........................................................................................................................ 1 Part I. Background .................................................................................................... 5 1. North American Datum of 1983 (1986) .......................................................................... 5 2. High Accuracy Reference Networks (HARNs) .............................................................. 5 3. Continuously Operating Reference Stations (CORS) .................................................... 7 4. Federal Base Networks (FBNs) ...................................................................................... 8 5. National Readjustment .................................................................................................... 9 Part II. Data Inventory, Assessment and Input ....................................... 11 6. Preliminary GPS Project Analysis ................................................................................11 7. Master File .....................................................................................................................11
    [Show full text]
  • A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability
    A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2014-172 http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-172.html October 11, 2014 Copyright © 2014, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica UC Berkeley UC Berkeley Carnegie Mellon University UC Berkeley ABSTRACT Even though our work does not provide new active mea- We present a retrospective and longitudinal study of Internet surement techniques or new datasets, we believe that there is value in this retrospective analysis on several fronts. First, it latency and path stability using three large-scale traceroute provides a historical and longitudinal perspective of Internet datasets collected over several years: Ark and iPlane from path properties that are surprisingly lacking in the measure- 2008 to 2013 and a proprietary CDN’s traceroute dataset spanning 2012 and 2013. Using these different “lenses”, we ment community today. Second, it can help us revisit and revisit classical properties of Internet paths such as end-to- reappraise classical assumptions about path latency and sta- end latency, stability, and of routing graph structure.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Misleading Stars: What Cannot Be Measured in the Internet?
    Noname manuscript No. (will be inserted by the editor) Misleading Stars: What Cannot Be Measured in the Internet? Yvonne-Anne Pignolet · Stefan Schmid · Gilles Tredan Abstract Traceroute measurements are one of the main in- set can help to determine global properties such as the con- struments to shed light onto the structure and properties of nectivity. today’s complex networks such as the Internet. This arti- cle studies the feasibility and infeasibility of inferring the network topology given traceroute data from a worst-case 1 Introduction perspective, i.e., without any probabilistic assumptions on, e.g., the nodes’ degree distribution. We attend to a scenario Surprisingly little is known about the structure of many im- where some of the routers are anonymous, and propose two portant complex networks such as the Internet. One reason fundamental axioms that model two basic assumptions on is the inherent difficulty of performing accurate, large-scale the traceroute data: (1) each trace corresponds to a real path and preferably synchronous measurements from a large in the network, and (2) the routing paths are at most a factor number of different vantage points. Another reason are pri- 1/α off the shortest paths, for some parameter α 2 (0; 1]. vacy and information hiding issues: for example, network In contrast to existing literature that focuses on the cardi- providers may seek to hide the details of their infrastructure nality of the set of (often only minimal) inferrable topolo- to avoid tailored attacks. gies, we argue that a large number of possible topologies Knowledge of the network characteristics is crucial for alone is often unproblematic, as long as the networks have many applications as well as for an efficient operation of the a similar structure.
    [Show full text]
  • PAX A920 Mobile Smart Terminal Quick Setup Guide
    PAX A920 QUICK SETUP GUIDE PAX A920 Mobile Smart Terminal Quick Setup Guide 2018000702 v1.8 1 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE PAX A920 Mobile Terminal Intelligence of an ECR in a handheld point of sale. The PAX A920 is an elegantly designed compact secure portable payment terminal powered by an Android operating system. The A920 comes with a large high definition color display. A thermal printer and includes NFC contactless and electronic signature capture. Great battery life for portable use. 2018000702 v1.8 2 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 1 What’s in The Box The PAX A920 includes the following items in the box. 2018000702 v1.8 3 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 2 A920 Charging Instructions Before starting the A920 battery should be fully charged by plugging the USB to micro USB cord to a PC or an AC power supply and then plug the other end with the micro USB connector into the micro USB port on the left side of the terminal. Charge the battery until full. Note: There is a protective cover on the new battery terminals that must be removed before charging the battery. See Remove and Replace Battery section. 2018000702 v1.8 4 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 3 A920 Buttons and Functions Front Description 6 1 2 7 3 8 9 4 5 2018000702 v1.8 5 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 3.1 A920 Buttons and Functions Front Description 1.
    [Show full text]
  • HP Integrity Nonstop Operations Guide for H-Series and J-Series Rvus
    HP Integrity NonStop Operations Guide for H-Series and J-Series RVUs HP Part Number: 529869-023 Published: February 2014 Edition: J06.03 and subsequent J-series RVUs and H06.13 and subsequent H-series RVUs © Copyright 2014 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Intel, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. Motif, OSF/1, Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks, and IT DialTone and The Open Group are trademarks of The Open Group in the U.S. and other countries. Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc.
    [Show full text]
  • PAX-It! TM Applications the Paxcam Digital USB 2.0 Camera System
    Digital Imaging Workflow for Industrial From the Makers of PAX-it! TM Applications The PAXcam Digital USB 2.0 Camera System l Affordable camera for microscopy, with an easy-to-use interface l Beautiful, high-resolution images; true color rendition l Fully integrated package with camera and software l USB 2.0 interface for the fastest live digital color preview on the market l Easy-to-use interface for color balance, exposure & contrast control, including focus indicator tool l Adjustable capture resolution settings (true optical resolution -- no interpolation) l Auto exposure, auto white balance and manual color adjustment are supported l Create and apply templates and transparencies over the live image l Acquire images directly into the PAX-it archive for easy workflow l Easy one-cable connection to computer; can also be used on a laptop l Adjustable region of interest means smaller file sizes when capturing images l PAXcam interface can control multiple cameras from the same computer l Stored presets may be used to save all camera settings for repeat conditions Capture Images Directly to PAX-it Image Database Software Includes PAXcam Video Agent for motion video capture l Time lapse image capture l Combine still images to create movie files l Extract individual frames of video clips as bitmap images Live preview up to 40 fps PAX-it! l File & retrieve images in easy-to-use cabinet/folder structure l Store images, video clips, documents, and other standard digital file types l Images and other files are in a searchable database that you
    [Show full text]
  • [Linux] - Unix/Linix Commands
    [Linux] - Unix/Linix Commands 1. $ ssh username@servername command used to login to server 2$ pwd it prints present working directory 3$ ls -l listing the files in present directory 4$ cd..takes you to previous Dir 5$ mkdir <directory>will create directory 6$ mkdir -p /home/user1/d1/d2/d3will create all the non-existing Dir’s 7$ vi <file_name>opens file for reading/editing 8$ cat <file_name>display contents of file 9$ more <file_name>displays page by page contents of file 10$ grep <pattern> file_namechecks pattern/word in file name specified 11$ head <file_name>shows first 10 lines of file_name 12$ touch <file_name>creates a zero/dummy file 13$ ln file1 file2 creates link of file1 to file2 14$ cp <file1> <file2>Copy a file 15$ mv <file1> <file2>Move/rename a file or folder 16$ clearclears the scree 17$ whoDisplays logged in user to the system. 18$ file <file_name>shows what type of file it is like 19$wwill display more info abt the users logged in 20$ ps -efshows process 21$ which <file_name>shows if the file_name/command exists and if exists display the path 22$ rm <file_name>will delete file specified$ rm * Delete all the files in the present directory (BE CAREFUL WHILE GIVING THIS COMMAND) 23$ find . -type f -print -exec grep -i <type_ur_text_here> {} \;this is recursive grep$ find / - name <file_name> -print 24$ tail <file_name>shows last 10 lines of fileuse tail -f for continous update of file_name 25$ chmod 777 <file_name>changes file_name/directory permissions use –R switch for recursive 26$ chown owner:group <file_name>changes
    [Show full text]
  • CICS and IPCS
    CICS and IPCS Andre Clark Staff CICS L2 Support Agenda § Dump types § Some basic IPCS commands § CICS Verbexit DFHPDxxx § Common System Area (CSA) § Storage Manager (SM) § Transaction Manager (XM) § Dispatcher (DS) § Kernel (KE) § Loader domain (LD) § Program domain (PG) § Lock Manager (LM) § Enqueue domain (NQ) § Application domain (AP) § Task Summary (TK) § Trace (TR) 3 IPCS Primary Menu ------------------- IPCS PRIMARY OPTION MENU --------------------------------- OPTION ===> ******************** 0 DEFAULTS - Specify default dump and options * USERID - USASSC1 1 BROWSE - Browse dump data set * 2 ANALYSIS - Analyze dump contents * 3 UTILITY - Perform utility functions * TIME - 16:46 4 INVENTORY - Inventory of problem data * PREFIX - USASSC1 5 SUBMIT - Submit problem analysis job to batch * TERMINAL- 3278 6 COMMAND - Enter subcommand, CLIST or REXX exec * PF KEYS - 24 T TUTORIAL - Learn how to use the IPCS dialog ******************** X EXIT - Terminate using log and list defaults Enter END command to terminate IPCS dialog F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=MORE F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=CURSOR 4 IPCS Default Menu ------------------------- IPCS Default Values --------------------------------- Command ===> You may change any of the defaults listed below. The defaults shown before any changes are LOCAL. Change scope to GLOBAL to display global defaults. Scope ==> BOTH (LOCAL, GLOBAL, or BOTH) If you change the Source default, IPCS will display the current default Address Space for the new source and will ignore any data entered in the Address Space field. Source ==> DSNAME('USASSC1.SHAREFC.DUMP') Address Space ==> ASID(X'0044') Message Routing ==> NOPRINT TERMINAL Message Control ==> FLAG(WARNING) NOCONFIRM VERIFY Display Content ==> MACHINE REMARK REQUEST NOSTORAGE SYMBOL Press ENTER to update defaults.
    [Show full text]
  • Freebsd and Netbsd on Small X86 Based Systems
    FreeBSD and NetBSD on Small x86 Based Systems Dr. Adrian Steinmann <[email protected]> Asia BSD Conference in Tokyo, Japan March 17th, 2011 1 Introduction Who am I? • Ph.D. in Mathematical Physics (long time ago) • Webgroup Consulting AG (now) • IT Consulting Open Source, Security, Perl • FreeBSD since version 1.0 (1993) • NetBSD since version 3.0 (2005) • Traveling, Sculpting, Go AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 2 Focus on Installing and Running FreeBSD and NetBSD on Compact Flash Systems (1) Overview of suitable SW for small x86 based systems with compact flash (CF) (2) Live CD / USB dists to try out and bootstrap onto a CF (3) Overview of HW for small x86 systems (4) Installation strategies: what needs special attention when doing installations to CF (5) Building your own custom Install/Maintenance RAMdisk AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 3 FreeBSD for Small HW Many choices! – Too many? • PicoBSD / TinyBSD • miniBSD & m0n0wall • pfSense • FreeBSD livefs, memstick • NanoBSD • STYX. Others: druidbsd, Beastiebox, Cauldron Project, ... AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 4 PicoBSD & miniBSD • PicoBSD (1998): Initial import into src/release/picobsd/ by Andrzej Bialecki <[email protected]
    [Show full text]
  • Using IPCS with MVS/ESA Version 5
    SYSTEM BY TOM BRYANT STRATEGIES MVS/XA/ESA Problem Solving: Part I — Using IPCS With MVS/ESA Version 5 PCS for MVS/ESA Version 5 has come a long way since I first used it in 1983 at the prompting of an exuberant IBM customer engineer. IPCS IPCS for MVS/ESA continues to move toward a fully panel-driven environment, although in Version 5 offers many Isome situations, I find using IPCS commands easier. capabilities, including the ability to scan for unformatted storage dumps. This article Future articles will examine the environ- easily in batch mode as well as in an ISPF mental record editing and printing program foreground session. I also wanted a CLIST examines the many (EREP), one-page MVS/XA/ESA abend that was well-documented with easy-to-use facilities of IPCS, analysis, advanced SVCDUMP analysis, parameters. Finally, I wanted a CLIST that slip traps and GTF tracing, and standalone does not hang onto dump directory and IPCS and includes some dump analysis. print dataset allocations when completed, as of the author’s favorite IPCS stands for Interactive Problem the IBM BLSCDDIR CLIST does. Control System, although most people IPCS commands. (myself included) use it just for looking at IPCS CLISTS FOR MVS/ESA unformatted storage dumps. IPCS will process VERSION 4.3 AND ABOVE SVCDUMPs which are dumps usually pro- The #IPCSTJB CLIST is the mainline duced with the abend (SVC 13) issued by your CLIST that you execute to establish an IPCS program or the system. Other unformatted session (see Figure 1). If you are invoking dumps that IPCS will produce include an #IPCSTJB for the first time, the NEW CLIST application unformatted dump allocated keyword parameter indicates that you will through the SYSMDUMP DD statement and dynamically create a VSAM dump directory the standalone dump produced by the stand- using the value of the VOL CLIST keyword alone dump program.
    [Show full text]