HP 3000 Manuals HP 3000 Manuals
User Logging Programmer's Guide Printed in U.S.A. 900 Series HP 3000 Computer Systems HP Part No. 32650-90027 Edition U0788 Printed Nov 1987
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. Copyright Æ 1987, 1988 by HEWLETT-PACKARD COMPANY Printing History New editions are complete revisions of the manual. Update packages, which are issued between editions, contain additional and replacement pages to be merged into the manual by the customer. The date on the title page and back cover of the manual changes only when a new edition is published. When an edition is reprinted, all the prior updates to the edition are incorporated. No information is incorporated into a reprinting unless it appears as a prior update. The software code printed alongside the date indicates the version level of the software product at the time the manual edition or update was issued. Many product updates and fixes do not require manual changes, and conversely, manual corrections may be done without accompanying product changes. Therefore, do not expect a one-to-one correspondence between product updates and manual updates. First Edition November 1987 A.01.00 Update #1 July 1988 A.10.00 Documentation MapPreface The User Logging Programmer's Guide describes the MPE XL User Logging Facility. It explains the differences between user logging in MPE XL and MPE VE Operating Systems. Serial Logging, disc logging, and application design are discussed. The manuals listed below have been referenced in this manual and provide additional information: MPE XL Commands Reference Manual (32650-90003) MPE XL Intrinsics Reference Manual (32650-90028) MPE VE System Operations and Resource Management Reference Manual (32033-90005) This manual contains the following information: Chapter 1 Introduction introduces the subject matter contained in this manual, the types of applications you would want to use User Logging for, and the differences between MPE V/E and MPE XL. Chapter 2 User Logging Intrinsics introduces the programmatic use of its special intrinsics. Chapter 3 User Logging Commands introduces the commands that may be used at a system level to perform User Logging functions. Chapter 4 The User Logging Process explains the media to be used, how to create necessary files, and how to control the logging process. Chapter 5 User Logging in an Application explains, in detail, the use of the User Logging intrinsics. Chapter 6 Recovery explains the recovery process and how to use the different logging records. Appendix A Suggested User Logging Procedure gives a basic outline of what information is required to implement a User Logging procedure. Appendix B Record Formats explains the contents of the logging records. Appendix C User Logging Error Codes lists all error codes returned by User Logging intrinsics. 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: show job ShoJob SHOW_JOB boldface Within syntax statements, a parameter in boldface 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); NOTE: All syntax parameters within text are italicized. ... 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 NOTATION DESCRIPTION --------------------------------------------------------------------------------------- [[ ]] 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 press 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/M010467/DOCMAP43c50.gif)