COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series

701

702

703

704

705

706

707

708

709

710

17 HP Extensions to ISO COBOL

This section lists the HP extensions to ISO/ANSI COBOL, grouping them according to the sections

of this manual that explain them; that is:

• Source Program Organization and Format

• Language Elements

• Data Fundamentals

• Environment Division

• Data Division

• Procedure Division Verbs

These HP extensions are explained in other sections, and are not repeated in this section:

• HP Reserved Words (page 743)

• Chapter 18: HP COBOL CRE Support (page 709)

• Chapter 48: Run-Time Diagnostic Messages (page 1178)

Compiler Directives are HP extensions to ISO COBOL.

HP extensions for using SQL/MP with HP COBOL are explained in the SQL/MP Programming

Manual for COBOL.

HP extensions for using SQL/MX with HP COBOL are explained in the SQL/MX Programming

Manual for C and COBOL.

Source Program Organization and Format

The only HP extension to ISO/ANSI COBOL that affects source program organization or format

is Tandem reference format, which features:

• 132 columns

• Continuation of a nonnumeric literal without including trailing spaces

• No sequence number area or identification field (comment lines instead)

For more information on Tandem reference format, see Reference Format for Source Program Lines

(page 44).

Language Elements

The HP extensions to ISO/ANSI COBOL that are language elements are:

• HP COBOL requires at least one character in a COBOL word to be either a letter or a hyphen;

COBOL requires a letter.

• In HP COBOL, using a COBOL word as a library-name does not interfere with its concurrent

use as the name of an entity in another category; however, library-names must be unique

among themselves.

• COBOL limits the forms of system-names to those permitted for user-defined names. HP COBOL

relaxes this restriction. The use of each particular system-name is limited to contexts appropriate

for its category. The few minor restrictions on duplicate usages of system-names are discussed

in SPECIAL-NAMES Paragraph (page 105).

Source Program Organization and Format 705