HP 3000 Manuals HP 3000 Manuals
HP RPG/XL Utilities-Part 3 SIGEDITOR SIGEDITOR HP Part No. 30318-90006 Printed Oct 1989
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 prior written consent of Hewlett-Packard Company. Copyright Æ 1989 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 edition does not change. The software product part number printed alongside the date indicates the version and update 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 on one correspondence between product updates and manual updates. First Edition October 1989 30318A.00.04 Preface to RPG SIGEDITOR This is the reference manual for Hewlett-Packard's SIGEDITOR. SIGEDITOR is a menu-driven forms design utility used by RPG programmers to construct forms. This manual assumes that you are an experienced RPG programmer using SIGEDITOR. In this manual, the term user refers to the person entering data into the forms that you have designed. This manual contains the following: Chapter 1 Gives an overview of SIGEDITOR. A short tutorial introduces you to the menu and the basic functions. All topics in this chapter are explained in detail in chapter 2. Chapter 2 Describes in detail how to use SIGEDITOR and gives examples. This chapter explains forms specifications, fields, and advanced editing techniques. Chapter 3 Gives step-by-step guides to specific tasks. If you are not familiar with SIGEDITOR, you can use this chapter as a quick guide to these tasks. Chapter 4 Describes how RPG programmers use forms generated by SIGEDITOR. Appendix A Lists and describes the SIGEDITOR error messages. Appendix B Summarizes the SIGEDITOR keys. Appendix C Describes how to calculate the self-check field. Additional Documentation For more information on RPG, see the HP RPG/XL Reference Manual (part number 30318-90003) and PROCMON/3000 (part number 99941-90001). Unsupported Devices SIGEDITOR does not support these HP terminals: * 264X Series * 2621A/B * 2703A * 2625A * 3XXX Series 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 italics Within syntax statements, a word in italics represents a formal parameter or argument that you must replace with an actual value. In the following example, you must replace filename with the name of the file you want to release: RELEASE filename punctuation Within syntax statements, punctuation characters (other than brackets, braces, vertical parallel lines, and ellipses) must be entered exactly as shown. { } Within syntax statements, braces enclose required elements. When several elements within braces are stacked, you must select one. In the following example, you must select ON or OFF: {ON } SETMSG {OFF} [ ] Within syntax statements, brackets enclose optional elements. In the following example, brackets around ,TEMP indicate that the parameter and its delimiter are optional: PURGE {filename} [,TEMP] When several elements with brackets are stacked, you can select any one of the elements or none. In the following example, you can select devicename or deviceclass or neither: SHOWDEV [devicename] [deviceclass] Conventions (continued) NOTATION DESCRIPTION [...] Within syntax statements, a horizontal ellipsis enclosed in brackets indicates that you can repeatedly select elements that appear within the immediately preceding pair of brackets or braces. In the following example, you can select itemname and its delimiter zero or more times. Each instance of itemname must be preceded by a comma: [,itemname][...] If a punctuation character precedes the ellipsis, you must use that character as a delimiter to separate repeated elements. However, if you select only one element, the delimiter is not required. In the following example, the comma cannot precede the first instance of itemname: [itemname][,...] |...| Within syntax statements, a horizontal ellipsis enclosed in parallel vertical lines indicates that you can select more than one element that appears within the immediately preceding pair of brackets or braces. However, each element can be selected only one time. In the following example, you must select ,A or ,B or ,A,B or ,B,A : {,A} {,B}|...| If a punctuation character precedes the ellipsis, you must use that character as a delimiter to separate repeated elements. However, if you select only one element, the delimiter is not required. In the following example, you must select A or B or AB or BA. The first element cannot be preceded by a comma: {A} {B}|,...| ... Within examples, horizontal or vertical ellipses indicate where portions of the example are omitted. Å Within syntax statements, the space symbol Å shows a required blank. In the following example, you must separate modifier and variable with a blank: SET[(modifier)]Å(variable); underlining User input is underlined. For example: PROMPT?response In a syntax statement, brackets, braces or ellipses are underlined if you must enter them. For example: COMMAND [[ParameterA]] = ParameterB Conventions (continued) NOTATION DESCRIPTION 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. CTRLchar CTRLchar indicates a control character. For example, CTRLY 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.