HP 3000 Manuals HP 3000 Manuals
900 Series HP 3000 Computer Systems MPE/iX Commands Reference Manual Volume II HP Part No. 32650-90364 Printed in U.S.A. Edition Fourth E0796
________________________________________________________________________ |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 which 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) 1996 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 | |for DoD agencies, Computer Software Restricted Rights clause at FAR | |52.227-19 for other agencies. | | | |Hewlett-Packard Company | |3000 Hanover Street | |Palo Alto, CA 94304 U.S.A. | ________________________________________________________________________ Restricted Rights Legend Printed 1996 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 June 1992 B.04.00 Second Edition April 1994 C.50.00 Third Edition January 1995 C.50.00 Fourth Edition July 1996 C.55.00 Preface The fourth edition of the MPE/iX Commands Reference Manual Volume II (32650-90364) is a part of a two volume set. Volume I provides command descriptions alphabetically from A through L. Volume II provides command descriptions alphabetically from M through X. Both Volume I and Volume II of this manual are written for all users of the 900 Series HP 3000. 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 unde 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 3000's, not based on the PA-RISC architecture. MPE V software can be run on the PA-RISC (Series 900) HP 3000's in what is known as compatibility mode. Organization of This Manual The MPE/iX Commands Reference Manual Volume II (32650-90364) is organized into one chapter and seven appendices. A description of the chapter and appendix follows: Chapter 2 Command Definitions is a continuation of Chapter 2 in Volume I, and documents each MPE/iX command in alphabetical order from M through X. Appendix A Predefined Variables in MPE/iX lists all valid MPE/iX predefined variables. Appendix B Expression Evaluator Functions lists functions available for use by the expression evaluator and an explanation of their use. Appendix C Terminal and Printer Types provides information on supported MPE/iX terminal and printer types and how they differ from supported MPE V/E terminal and printer types. Appendix D Subsystem Formal File Designators lists the formal file designators associated with parameters for specific commands. Appendix E MPE/iX File Codes provides information on system-defined file codes and defines the reserved integer and mnemonic values. Appendix F Wildcard Characters lists all of the available wildcard characters for use with MPE/iX. How to Use This Manual Chapter 2 of this manual is an alphabetical listing of MPE/iX commands. This volume is a continuation of chapter 2 in Volume I and documents commands that begin with M through X. If you know which command to use, turn directly to that command definition in chapter 2. If not, turn to chapter 1 in Volume 1, which lists commands by task. After you determine which command to use, turn to the appropriate volume and command definition in chapter 2. For supplemental information on command syntax and use refer to the MPE/iX General User's Reference Manual (32650-90002). 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 command 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. CTRLcharacter CTRLcharacter indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously.