HP 3000 Manuals HP 3000 Manuals
900 Series HP 3000 Computer Systems Getting System Information Programmer's Guide HP Part No. 32650-90018 Printed in U.S.A. Edition Second Edition E0692
________________________________________________________________________ |The information contained in this document is subject to change | |without notice. | | | |Hewlett-Packard makes no warranty of any kind with regard to this | |material, including, but not limited to, the implied warranties of | |merchantability or fitness for a particular purpose. Hewlett-Packard | |shall not be liable for errors contained herein or for direct, | |indirect, special, incidental, or consequential damages in connection | |with the furnishing or use of this material. | | | |Hewlett-Packard assumes no responsibility for the use or reliability | |of its software on equipment that is not furnished by Hewlett-Packard.| | | |This document contains proprietary information that is protected by | |copyright. All rights are reserved. Reproduction, adaptation, or | |translation without prior written permission is prohibited, except as | |allowed under the copyright laws. | ________________________________________________________________________ Copyright (c) 1992 by Hewlett-Packard Company ________________________________________________________________________ |Use, duplication, or disclosure by the U.S. Government is subject to | |restrictions as set forth in subparagraph (c) (1) (ii) of the Rights | |in Technical Data and Computer Software clause at DFARS 252.227-7013. | |Rights for non-DoD U.S. Government Departments and agencies are as set| |forth in FAR 52.227-19 (c) (1,2). | | | |Hewlett-Packard Company | |3000 Hanover Street | |Palo Alto, CA 94304 U.S.A. | ________________________________________________________________________ Restricted Rights Legend Printed 1992 Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document; therefore, do not expect a one-to-one correspondence between product releases and document editions. Edition Date Software Version --------------------------------------------------------------------------------------- First Edition November 1987 A.01.00 Update 1 July 1988 A.10.00 Update 2 December 1988 A.20.00 Second Edition June 1992 B.40.00 Preface MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX. You can continue to use MPE XL system documentation, although it may not refer to features added to the operating system to support POSIX (for example, hierarchical directories). Finally, you may encounter references to MPE V, which is the operating system for HP 3000s not based on the PA-RISC architecture. MPE V software can be run on PA-RISC (Series 900) HP 3000s in what is known as compatibility mode. About This Manual This manual is written for MPE/iX systems programmers and experienced system administrators. It describes how you can access various types of system information on MPE/iX. This manual presupposes that you are familiar with using the MPE/iX operating system. You should use this manual with the MPE/iX Commands Reference Manual, Volumes 1 and 2 (32650-90003 and 32650-90364) and the MPE/iX Intrinsics Reference Manual (32650-90028). The reference manuals provide detailed information about each command and intrinsic. Organization of This Manual This manual contains the following chapters: Chapter 1 Introduction describes the tasks that are covered in this manual and the types of information available on the system. Chapter 2 Getting File Information discusses common file system tasks that require you to obtain and use file system information, and outlines the system features that you use to obtain it. Chapter 3 Getting Job and Session Information describes how to get information about your job or session, and explains what commands and intrinsics you can use for this purpose. Chapter 4 Getting Process Information briefly outlines the various process handling commands and intrinsics available on the MPE/iX system. Chapter 5 Getting Time and Date Information discusses the time and date functions available on the system, and indicates how you can use them to obtain the information that you need in the format that best serves your purposes. Chapter 6 Getting Input and Output Information describes how to get information that describes the status of your input and output devices using MPE/iX system commands. Chapter 7 Getting System Administration Information discusses commonly performed system administration tasks and describes how to collect information using commands and system utilities. Chapter 8 System Logging describes the system logging facility used on MPE/iX and illustrates the log record formats produced by this facility. Chapter 9 Error Management describes the error management intrinsics available on MPE/iX and how you can use them to read errors from the process error stack or to display error messages from the system error catalog. How to Use This Manual If you are in the process of familiarizing yourself with MPE/iX, you should read chapter 1 first; otherwise, you should consult the chapter that describes the type of information that you want to obtain. Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm com_mand comamnd italics In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND filename bold italics In a syntax statement, a word in bold italics represents a parameter that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND(filename) punctuation In a syntax statement, punctuation characters (other than brackets, braces, vertical bars, and ellipses) must be entered exactly as shown. In the following example, the parentheses and colon must be entered: (filename):(filename) underlining Within an example that contains interactive dialog, user input and user responses to prompts are indicated by underlining. In the following example, "yes" is the user's response to the prompt: Do you want to continue? >> yes { } In a syntax statement, braces enclose required elements. When several elements are stacked within braces, you must select one. In the following example, you must select either ON or OFF: COMMAND { ON } { OFF} [ ] In a syntax statement, brackets enclose optional elements. In the following example, OPTION can be omitted: COMMAND filename [OPTION] When several elements are stacked within brackets, you can select one or none of the elements. In the following example, you can select OPTION or parameter or neither. The elements cannot be repeated. COMMAND filename [ OPTION ] [ parameter] Conventions (continued) [...] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...] In the example below, you only use the comma as a delimiter if parameter is repeated; no comma is used before the first occurrence of parameter: [parameter][,...] |...| In a syntax statement, horizontal ellipses enclosed in vertical bars indicate that you can select more than one element within the immediately preceding pair of brackets or braces. However, each particular element can only be selected once. In the following example, you must select A, AB, BA, or B. The elements cannot be repeated. { A} |...| { B} ... In an example, horizontal or vertical ellipses indicate where portions of an example have been omitted. In a syntax statement, the space symbol shows a required blank. In the following example, parameter and parameter must be separated with a blank: (parameter) (parameter) The symbol indicates a key on the keyboard. For example, RETURN represents the carriage return key or Shift represents the shift key. CTRLcharacterCTRLcharacter indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously.