HP 3000 Manuals HP 3000 Manuals
Trap Handling Programmer's Guide Printed in U.S.A. 900 Series HP 3000 Computer Systems HP Part No. 32650-90026 Edition E1288 Printed Dec 1988
________________________________________________________________________ |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 AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard | |shall not be liable for errors contained herein or for incidental or | |consequential damages in connection with the furnishing, performance | |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. No part of this document may be | |photocopied,reproduced or translated to another language without the | |prior written consent of Hewlett-Packard Company. | ________________________________________________________________________ Æ 1988 by HEWLETT-PACKARD COMPANY Printing History The following table lists the various printings of the manual, together with the respective release date for each edition. The software code (Product VUF) printed alongside the release date indicates the version level of the software product at the time the manual edition was issued. Many product updates and fixes do not require manual changes. Therefore, do not expect a one-to-one correspondence between product updates and manual editions. Edition Number Release Date Product VUF --------------------------------------------------------------------------------------- First Edition November 1987 A.01.00 Second Edition December 1988 A.20.00 Documentation MapPreface The Trap Handling Programmer's Guide explains how you can develop your own routines to handle interrupt events and thereby recover from errors and avoid a process abort. Chapter 1 Overview defines traps and trap handling; summarizes trap handling on MPE XL. Chapter 2 MPE XL Arithmetic Traps provides an overview of and reference information on the arithmetic trap handling intrinsics; describes the use of these intrinsics; includes example programs. Chapter 3 MPE XL Code-related Traps provides information regarding how the MPE XL trap subsystem handles code-related traps. Chapter 4 MPE XL CONTROL-Y Traps provides an overview of, and reference information on, the CONTROL-Y trap handling intrinsics; describes the use of these intrinsics; includes example programs. Chapter 5 MPE XL Software Library Traps provides an overview of, and reference information on, the software library trap handling intrinsic; describes the use of this intrinsic; includes example programs. Chapter 6 MPE XL Software System Traps provides an overview of, and reference information on, the software system trap handling intrinsic; describes the use of this intrinsic; includes example programs. Appendix A MPE XL Trap Subsystem Error Messages lists the MPE XL Trap Subsystem Error Messages. For each message, a cause and recovery action are listed. Appendix B MPE XL Trap Subsystem Escape Codes lists the MPE XL trap subsystem escape codes in decimal and hexadecimal and supplies the meanings for those codes. Appendix C Intrinsic Numbers lists the MPE XL system intrinsics and their associated numbers (used in handling software system traps). Appendix D Debugging Traps discusses how to debug code-related and arithmetic traps. Conventions NOTATION DESCRIPTION UPPERCASE Within syntax statements, characters in uppercase must be entered in exactly the order shown, though you can enter them in either uppercase or lowercase. For example: SHOWJOB Valid entries:showjob ShowJob SHOWJOB Invalid entries:shojwob ShoJob SHOW_JOB boldface italics Within syntax statements, a parameter in boldface italics is required. In the following example, you must specify the pin parameter: ACTIVATE (pin,allow); italics Within syntax statements, a parameter in italics is optional. In the following example, you are not required to specify the allow parameter: ACTIVATE (pin,allow); ... Within examples, horizontal or vertical ellipses indicate where portions of the example are omitted. shading Within an example of interactive dialog, shaded characters indicate user input or responses to prompts. In the following example, OMEGA is the user's response to the NEW NAME prompt: NEW NAME? OMEGA [[ ]] The symbol [[ ]] indicates a key on the terminal's keyboard. For example, [[CTRL]] indicates the Control key. [[CTRL]] char [[CTRL]] char indicates a control character. For example, [[CTRL]] Y means you have to simultaneously the Control key and the Y key on the keyboard. base prefixes The prefixes %, #, and $ specify the numerical base of the value that follows: %num specifies an octal number. #num specifies a decimal number. $num specifies a hexadecimal number. When no base is specified, decimal is assumed. Bit (bit:length) When a parameter contains more than one piece of data within its bit field, the different data fields are described in the format Bit (bit:length), where bit is the first bit in the field and length is the number of consecutive bits in the field. For example, Bits (13:3) indicates bits 13, 14, and 15: most significant least significant |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| | 0| | | | | | | | | | | | |13|14|15| |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| Bit (0:1) Bits(13:3)
![[]](../../pic3k/M010457/DOCMAP43c50.gif)