COBOL for the 21 st Century 11 th

COBOL for the 21 st Century 11 th edition John Wiley & Sons, Inc. Nancy Stern Hofstra University Robert A. Stern Nassau Community College James P. Ley University of Wisconsin-Stout (Emeritus) 2 -1

Chapter 2 The IDENTIFICATION and ENVIRONMENT DIVISIONs 2 -2

Chapter Objectives To familiarize you with • Basic structure of a COBOL program • General coding and format rules • IDENTIFICATION and ENVIRONMENT DIVISION entries 2 -3

Chapter Contents • Basic Structure of a COBOL Program • Coding Requirements of IDENTIFICATION DIVISION • Sections of ENVIRONMENT DIVISION • Assigning Files to Devices in ENVIRONMENT DIVISION 2 -4

CONTENTS • Basic Structure of a COBOL Program – Coding a Source Program – Coding Rules • The Main Body of a Program • Optional Entries Identification and Page and Serial Numbers • Column 7 : For Comments, Continuing Nonnumeric Literals, and Starting a New Page • Area A and B – Types of COBOL Entries

CONTENTS • Coding Requirements of the IDENTIFICATION DIVISION – Paragraphs in the IDENTIFICATION DIVISION

Basic COBOL Program Structure • Originally, each COBOL instruction coded on single line of 80 characters • Positions on line reserved for special purposes • Rules may differ for your compiler • Rigid column rules dropped in 2008 2 -7

COBOL Coding Sheet Structured COBOL Programming, Stern & Stern, 9 th Edition

Coding a Source Program • Traditional COBOL coding sheets have 20 lines with spaces set aside in columns 4 --6 for sequence numbers. • Each COBOL instruction is coded on a single line using 80 characters per line.

COBOL Coding Sheet • Used to create an initial version of the program prior to keying it into the computer

Structured COBOL Programming, Stern & Stern, 9 th Edition

COBOL Coding Sheet Structured COBOL Programming, Stern & Stern, 9 th Edition

Coding a Source Program • Every line written on the coding sheet should be keyed in with one line each on a terminal or PC keyboard. • The entire program is referred to as the COBOL source program.

Coding Rules • Columns 1 -6 and 73 -80 optional and rarely used today • Column 7 for continuation, comment, starting new page • Columns 8 -72 for COBOL program statements 2 -14

Coding Rules Column 7 * (asterisk) designates entire line as comment / (slash) forces page break when printing source listing - (dash) to indicate continuation of nonnumeric literal 2 -15

Comments in a COBOL program

2 -17

2 -18

Margin Rules • Columns 8 -72 divided into two areas – Area A - columns 8, 9, 10, 11 – Area B - columns 12 -72 • Division, section and paragraph-names must all begin in Area A – First letter of name must begin in column 8, 9, 10 or 11 – Entry may extend into Area B 2 -19

Margin Rules • All other statements, clauses, and sentences begin anywhere in Area B (column 12, 13, 14, etc. ) – Select entries in ENVIRONMENT DIVISION – Data description entries in DATA DIVISION – All PROCEDURE DIVISION instructions 2 -20

2 -21

2 -22

Areas A and B

Review of Margin Rules • Division and Section Names – Begin in Area A, end with a period – Must appear on a line with no other entries • Paragraph-names – Begin in Area A, end with period followed by space – May appear on line by themselves or with other entries 2 -24

Review of Margin Rules • Statements and Sentences – Begin in Area B – May appear on line by themselves or with other entries – Statements (e. g. , OPEN, WRITE) may end with period but not recommended – Sentences (e. g. , a paragraph made up of one or more statements) end with period followed by space 2 -25

IDENTIFICATION DIVISION • Provides identifying information about program • Divided into paragraphs • PROGRAM-ID only required paragraph • Other paragraphs optional 2 -26

IDENTIFICATION DIVISION Format IDENTIFICATION DIVISION. PROGRAM-ID. program-name. [AUTHOR. [comment-entry] …] [other optional paragraphs] 2 -27

Paragraphs in the IDENTIFICATION DIVISION. PROGRAM-ID. program-name. [AUTHOR. [comment-entry]. . . ] [INSTALLATION. [comment-entry]. . . ] [DATE-WRITTEN. [comment-entry]. . . ] [DATE-COMPILED. [comment-entry]. . . ] [SECURITY. [comment-entry]. . . ]

2 -30

Understanding Instruction Formats • Instruction formats describe syntax of all parts of COBOL language • Describe required and optional elements, ordering and punctuation • All formats in text are correct although additional options may be available 2 -31

Rules for Instruction Formats • Uppercase words are COBOL reserved words • Lowercase words are user-defined entries Example IDENTIFICATION DIVISION. PROGRAM-ID. program-name. – DIVISION is reserved word – program-name is user-defined data-name 2 -32

Rules for Instruction Formats • Underlined words are required • Punctuation if specified is required Example IDENTIFICATION DIVISION. PROGRAM-ID. program-name. – IDENTIFICATION, DIVISION required – PROGRAM-ID is required paragraph – Periods required after division header, paragraph name and program-name 2 -33

Rules for Instruction Formats • Brackets [ ] mean item is optional, braces { } mean one of enclosed items required • Ellipses (. . . ) mean entry may be repeated Example IDENTIFICATION DIVISION. PROGRAM-ID. program-name. [AUTHOR. [comment-entry] …] – AUTHOR paragraph optional – If included it may have any number of comment entries 2 -34

ENVIRONMENT DIVISION • Describes files and computer devices used to process them • Required by programs that process files • This division is machine-dependent since devices differ from computer to computer • Only division that may change if program run on different computer 2 -35

Sections of Environment Division • CONFIGURATION SECTION – Describes computer used to compile/execute program – Optional and recommended that you omit it • INPUT-OUTPUT SECTION – Describes input and output files and devices used by program – Required for all programs using files 2 -36

THE CONFIGURATION SECTION – Supplies information about the computer on which the COBOL program will be compiled and executed. SOURCE-COMPUTER: – The computer that will be used for compiling the program. OBJECT-COMPUTER: - The computer that will be used for executing or running the program. * SOURCE- COMPUTER and OBJECT-COMPUTER are coded primarily as documentation entries.

CONFIGURATION SECTION EXAMPLE

INPUT-OUTPUT SECTION • Follows CONFIGURATION SECTION (if coded) • Includes FILE-CONTROL paragraph – Contains one SELECT statement for each file used by program – Each SELECT defines a file-name and assigns device name to that file 2 -39

INPUT-OUTPUT SECTION 2 -40

INPUT-OUTPUT SECTION 2 -41

INPUT-OUTPUT SECTION Format INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT file-name-1 ASSIGN TO implementor-name-1 [ORGANIZATION IS LINE SEQUENTIAL]. 1 1 Use this clause for all PC files so each line treated as separate record. 2 -42

SELECT Statement file-names • Choose meaningful file-names – EMPLOYEE-FILE instead of E-FILE – EMP-REPORT-FILE instead or OUT-FILE • File-names are user-defined words – Words chosen by programmer to represent some element of program • Must follow rules forming user-define words 2 -43

Rules for User-Defined Words 1. 2. 3. 4. 5. 6. 1 to 30 characters Letters, digits, hyphens (-) only No embedded blanks At least one alphabetic character May not begin or end with hyphen May not be COBOL reserved word 2 -44

SELECT implementor-names • Conventions for these names vary widely among computers • Most enable use of special device names for frequently used devices Printer Disk SYSLST, SYS$OUT, PRINTER DISC or DISK and disk file-name 2 -45

SELECT implementor-names • Special device-names example Select Transaction-File Assign to Disk "Data 1". Select Report-File Assign to Printer. • Some systems use name of file stored on disk (VAX or Alpha systems) Select Sales-File Assign to "Sales 1". 2 -47

SELECT Statements for PCs • For PCs, use device names specifying – Drive on which file appears followed by a colon – Folder name if file is in a folder – Name of file • PC example Select Inventory-File Assign To "C: InventoryInv-File. dat". 2 -48

ENVIRONMENT DIVISION. CONFIGURATION SECTION. SOURCE-COMPUTER. IBM PC. OBJECT-COMPUTER. IBM PC. INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT INPUT-FILE ASSIGN TO 'input. dat' ORGANIZATION IS LINE SEQUENTIAL. SELECT PRINT-FILE ASSIGN TO PRINTER. Structured COBOL Programming, Stern & Stern, 9 th Edition 000260 000270 000280 000290 000300 000310 000320 000330 000340

ENVIRONMENT DIVISION INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT NAME-FILE ASSIGN TO C: TMPSAMPIN. TXT" ORGANIZATION IS LINE SEQUENTIAL. SELECT PRINT-FILE ASSIGN TO C: TMPSAMPOUT. TXT". SELECT SORT-FILE ASSIGN TO "C: TMPSORT. TMP".

ORGANIZATION clause for PCs • This clause describes organization of records in the file • Most PC disk files created as text files – Following data for each record, Enter key is pressed – Indicates end of the line and end of the record – If records 80 characters or less, each record appears on single line on screen or printer 2 -51

ORGANIZATION clause for PCs • Include LINE SEQUENTIAL to – Correctly read records from files when Enter key used to mark the end of each record – Create disk files with each record followed by Enter key so each record appears on separate line when printed 2 -52

ORGANIZATION clause for PCs PC Example Select Sales-File Assign to "C: Chapter 2Sales. dat" Organization is Line Sequential. 2 -53

Coding Guidelines 1. Separate divisions by blank comment line, page eject symbol or blank line 2. Code a single statement per line 3. Code paragraph-names on line by themselves 4. Be liberal in use of comments. Box lengthy comments using asterisks. 2 -54

Coding Guidelines 5. Code SELECT statements in logical order (input files first, then output files) although order not required 6. Use separate lines for SELECT, ASSIGN, ORGANIZATION clauses for readability 7. Avoid use of device-specific file-names 2 -55

COBOL 2008 Changes • Coding rules for Margins A and B will be recommended not required. • PROGRAM-ID will be only paragraph in IDENTIFICATION DIVISION. All others can be specified as comments. • Length of user-defined words will be increased from 30 to 60 characters. 2 -56

Chapter Summary • IDENTIFICATION DIVISION – Defines program name – Program name up to eight characters, letters and digits only, acceptable on all computers – PROGRAM-ID is only required paragraph, all others optional – Use comments by coding an * in column 7 2 -57

Chapter Summary • ENVIRONMENT DIVISION – Division is optional for COBOL 85 – Not needed for fully interactive programs – INPUT-OUTPUT SECTION required for any program using files – Only machine-dependent division since device specification, file-name rules vary among computers 2 -58

Copyright © 2003 John Wiley & Sons, Inc. All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for distribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein. 2 -59

QUESTIONS?

SELF-TEST Solution: 8, 9, 10, or 11; 12, 13, 14, and so on Structured COBOL Programming, Stern & Stern, 9 th Edition 1. If an entry must begin in Area A, it may begin in position _____ ; if an entry must begin in Area B, it may begin in position _____.

SELF-TEST Solution: IDENTIFICATION; ENVIRONMENT; DATA; PROCEDURE Structured COBOL Programming, Stern & Stern, 9 th Edition 2. The four divisions of a COBOL program must appear in order as _____ ; and, _____.

SELF-TEST Solution: Division, section, and paragraph-names Structured COBOL Programming, Stern & Stern, 9 th Edition 3. What entries must be coded beginning in Area A?

SELF-TEST Solution: B Structured COBOL Programming, Stern & Stern, 9 th Edition 4. Most entries such as PROCEDURE DIVISION instructions are coded in Area _____.

SELF-TEST Solution: Division names; section names Structured COBOL Programming, Stern & Stern, 9 th Edition 5. _____ and _____ must each appear on a separate line. All other entries may have several statements on the same line.

SELF-TEST Solution: IDENTIFICATION DIVISION. PROGRAM-ID. program-name. Structured COBOL Programming, Stern & Stern, 9 th Edition 6. The first two entries of a COBOL program must always be _____ and _____.

SELF-TEST Solution: period; space or blank Structured COBOL Programming, Stern & Stern, 9 th Edition 7. Each of the preceding entries must be followed by a _____ , which, in turn, must be followed by a ____.

SELF-TEST Solution: A Structured COBOL Programming, Stern & Stern, 9 th Edition 8. The first two entries of a program are both coded beginning in Area _____.

SELF-TEST Structured COBOL Programming, Stern & Stern, 9 th Edition 9. Code the IDENTIFICATION DIVISION for a program called EXPENSES for a corporation, Dynamic Data Devices, Inc. , written July 15, 1997. This program has a security classification and is available to authorized personnel only. It produces a weekly listing by department of all operating expenses.

SELF-TEST INC. Structured COBOL Programming, Stern & Stern, 9 th Edition 9. Suggested solution: IDENTIFICATION DIVISION. PROGRAM-ID. EXPENSES. AUTHOR. N. B. STERN. INSTALLATION. DYNAMIC DATA DEVICES, DATE-WRITTEN. 7/15/97. DATE-COMPILED. SECURITY. AUTHORIZED PERSONNEL ONLY.

SELF-TEST Structured COBOL Programming, Stern & Stern, 9 th Edition 10. The DATE-COMPILED paragraph usually does not include a comment entry because _____. Solution: the computer itself can supply the date of the compilation (The current date is stored in main memory. )