HP 3000 Manuals HP 3000 Manuals
HP COBOL II/XL Migration Guide Printed in U.S.A. 900 Series HP 3000 HP Part No. 31500-90004 Edition E1088 Printed Oct 1988
Æ 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 dates on the title page change only when a new edition or a new update is published. No information is incorporated into a reprinting unless it appears as a prior update; the edition does not change when an update is incorporated. 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 31500A.00.12 Second Edition October 1988 31500A.01.006 Preface This document describes how to convert COBOL II/V programs into HP COBOL II/XL programs that run on 900 Series HP 3000 computers. It is written for experienced COBOL programmers. Manual Description This guide contains the following chapters: * Chapter 1 introduces the migration process. * Chapter 2 outlines the differences between COBOL II/V and COBOL II/XL by listing the new features of COBOL II/XL, those features missing from COBOL II/XL, and features that have changed. * Chapter 3 describes how to convert COBOL II/V programs to COBOL II/XL programs given the differences listed in Chapter 2. * Chapter 4 explains how to convert data files that were developed for COBOL II/V programs into data files that will work with COBOL II/XL programs. * Chapter 5 provides several examples relating to COBOL migration. * Chapter 6 includes a "cookbook" style checklist that you can use as a migration guideline. * Appendix A discusses error messages that you may receive while migrating a COBOL program and explains how you can correct the problem. Related Manuals The following manuals provide additional information that will help you to migrate COBOL II/V programs to COBOL II/XL. MPE V to MPE XL: Getting Started (30367-90002)--This manual generally describes what you need to know to move from an MPE V system to an MPE XL system. An Introduction to MPE XL for MPE V Programmers (30367-90005)--This guide concentrates on explaining the differences (such as new and changed intrinsics) between MPE V and MPE XL. It updates the MPE V Programmer's manual. HP COBOL II Reference Manual (31500-90001)--This is a generic reference manual that fully describes the COBOL II language for programming on HP computers. HP COBOL II/XL Reference Manual Supplement (31500-90005)--This supplement describes system-dependent information about programming in HP COBOL II/XL. HP COBOL II/XL Programmer's Guide (31500-90002)--This manual presents selected programming topics, such as statement interaction and native mode debugging. HP COBOL II Quick Reference Guide (31500-90003)--This summarizes the HP COBOL II programming language. Acknowledgment At the request of the American National Standards Institute (ANSI), the following acknowledgment is reproduced in its entirety: Any organization interested in reproducing the COBOL standard and specifications in whole or in part, using ideas from this document as the basis for an instruction manual or for any other purpose, is free to do so. However, all such organizations are requested to reproduce the following acknowledgment paragraphs in their entirety as part of the preface to any such publication (any organization using a short passage from this document, such as in a book review, is requested to mention "COBOL" in acknowledgment of the source, but need not quote the acknowledgment): COBOL is an industry language and is not the property of any company or group of companies, or of any organization or group of organizations. No warranty, expressed or implied, is made by any contributor or by the CODASYL Programming Language Committee as to the accuracy and functioning of the programming system and language. Moreover, no responsibility is assumed by any contributor, or by the committee, in connection therewith. The authors and copyright holders of the copyrighted material used herein have specifically authorized the use of this material in whole or in part, in the COBOL specifications. Such authorization extends to the reproduction and use of COBOL specifications in programming manuals or similar publications. FLOW-MATIC (trademark of Sperry Rand Corporation), Programming for the Univac++ I and II, Data Automation Systems copyrighted 1958, 1959, by Sperry Rand Corporation; IBM Commercial Translator Form No. F 28-8013, copyrighted 1959 by IBM, FACT, DSI 27A5260-2760, copyrighted 1960 by Minneapolis-Honeywell. Conventions NOTATION DESCRIPTION UPPERCASE Within syntax statements, characters in uppercase must be entered in exactly the order shown. Uppercase words that are underlined are keywords that are always required when the clause or statement in which they appear is used in your program. Uppercase words that are NOT underlined are optional, and may be included or omitted at will. They have no effect on program execution and serve only to make source program listings more readable and easy to understand. [FILE STATUS IS stat-item]. STATUS must be entered, FILE may be either included or omitted as you wish. italics Within syntax statements, a word in italics represents a formal parameter, argument, or literal 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, when several elements within braces are stacked, you must select one. In the following equivalent examples, you 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 not required: PURGE filename [,TEMP] When several elements within brackets are stacked, you can select any one of the elements or none. In the following equivalent examples, can select devicename or deviceclass or neither: [devicename] SHOWDEV [deviceclass] (cont.) underlining in dialog When it is necessary to distinguish user input from computer output, the input is underlined. Example: NEW NAME? ALPHA [ ]... Brackets followed by a horizontal ellipsis indicates that a previous bracketed element may be repeated zero or more times, or that elements have been omitted from the description. [WITH DUPLICATES ]... The ellipsis shows that the preceding clause may be repeated indefinitely. { }... Braces followed by a horizontal ellipses indicates that the item within braces may be repeated one or more times, or that elements have been omitted from the description. Å 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); These symbols are used in conditional statements to < represent the keywords LESS THAN, GREATER THAN, EQUAL TO, > LESS THAN OR EQUAL TO, GREATER THAN OR EQUAL TO, and NOT = EQUAL TO, respectively. Although these symbols represent <= keywords, they are NOT underlined. >= <> ; The semicolon is used only to improve readability and is always optional. , The comma is also used only to improve readability, and is always optional. . The period is a terminator or delimiter that is always required where shown; it must always be entered at the end of every division name, section name, paragraph name, and sentence. ^ The caret is occasionally used in examples to represent an implied decimal point in computer memory. Shading New COBOL'85 features, accessible through the ANSI85 entry point, are shaded.