COBOL-64 Software System

COBOL 64 Software Syste~
By K. A. Alexander
A Data Becker Product

Published by
~bacus Software
Copyright Notice
Abacus Software makes this package available for use on a single
computer only. It is unlawful to copy any portion of this software
package onto any medium for any purpose other than backup. It is
unlawful to give away or resell copies of this package. Any
unauthorized distribution of this product deprives the authors of
their deserved royalties. For use on multiple computers, please
contact Abacus Software to make such arrangements.
Warranty
Abacus Software makes no warranties, expressed or implied as to
the fitness of this software package for any particular purpose. In
no event will Abacus software be liable for consequential damages.
Abacus Software will replace any copy of the software which is
unreadable if returned within 30 days of purchase. Thereafter, there
will be a nominal charge for replacement.
First printing March 1986

Printed in U.S.A.
Copyright O 1984 K.A. ALEXANDER
Civic Center Office Plaza
25882 Orchard Lake Road, Suite
Farmington Hills MI. 480 18
Copyright O 1986 Abacus Software, Inc.
P.O. Box 7219
Grand Rapids, MI 495 10
PREFACE
It is assumed that the readers of this manual are familiar with the
Commodore 64 computer and general programming techniques.
The names used in this publication are not of individuals living or
otherwise. Any similarity or likeness of the names used in this
publication with the names of any individuals, living or otherwise,
is purely coincidental and not intentional.
Abacus Software believes that the information described in this
manual is accurate and reliable, and much care has been taken in its
preparation. However, no responsibility, financial or otherwise, is
accepted for any consequences arising out of the use of this
material. The information contained herein is subject to change.
ACKNOWLEDGEMENT
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,
Flow-matic (trademark of Sperry Rand Corporation).
Programming for the UNIVAC I and 11,Data Automation Systems
copyrighted 1958, 1959, by Sperry Rand Corporation; IBM
Commercial Translator Form Number F 28-8013, copyrighted
1959 by IBM;FACT, DSI 27A5260-2760, copyrighted 1960 by
Minneapolis-Honeywell,
rF*. 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.
n
TABLE OF CONTENTS
Chapter 1 - Introduction
Chapter 2 - The Nature of COBOL IN GENERAL
Chapter 3 - COBOL Advantages
Chapter 4 - COBOL 64 Implementation Notes
Chapter 5 - Hardware Consideration
Chapter 6 - COBOL 64 Source Language
Section 1--Program Organization
Section 2--Language Concepts
Section 3--Editing Format
Section 4--IDENTIFICATION DIVISION
Section 5--ENVIRONMENT DIVISION
Section &-DATA DIVISION
Section 7--PROCEDURE DIVISION
ACCEPT
ACCEPT- 1-KEY
ADD
CLOSE
DEBUG-BREAK
DEBUG-TRACE-OFF
DEBUG-TRACE-ON
DISPLAY
DIVIDE
EXIT
FILTER-NUMERIC
GOT0
IF
MOVE
MULTIPLY
OPEN
PERFORM
READ
SET
STOP RUN
SUBTRACT
WRITE
Chapter 7 -- Start Uptoperating Instructions
Chapter 8 -- Main Menu
CRUNCH
DEBUG
START-PROG
RESUME-PROG
SINGLE-ON
SINGLE-OFF
EXIT
BREAK 1
BREAK 2
BREAK 3
OF'TIONS
TRACE-ON-LINE
TRACE-OFF-LINE
TRACE-FAST
TRACE-SLOW
TRACE-ON
TRACE-OFF
RESET-OPTIONS
EDIT
COBOL 64 Statements
DIRECTORY
LIST
DELETE
SYNTAX
AUTO
SAVE
RESEQUENCE
PRINT-ON
PRINT-OFF
EXIT
GET
NEW-NAME
NEW-PROGIEDIT
PRINT-ON
PRINT-OFF
RUN
SAVE
APPENDIX A - Sample Program/Exercises
APPENDIX B - Reserved Words
APPENDIX C - Language Summary
APPENDIX D - Sample Programs
Abacus Software COBOL 64
CHAPTER 1
n INTRODUCTION
This manual provides a complete description of the COBOL 64

System as implemented for use on the Commodore 64 computer or
equivalent. The COBOL 64 programming language is designed
along the guidelines of the American National Standards Institute
(ANSI) X3.23- 1974.
The language is an easy to learn subset of the ANSI 1974 standard
Level 1 with appropriate extensions to utilize COMMODORE 64
features as well as providing high level program debugging
capabilities. With COBOL 64 there is no need for the user to be
concerned with machine language, memory addressing or
hexadecimal notation. All debugging is performed at the source
language (symbolic) level as opposed to the machine language
level.
A The COBOL 64 software system is a combination of an Editor,
Compiler, Interpreter and Symbolic Debugger. These features have
been designed with ease of learning and ease of use in mind to
provide a powerful programming development tool for general
business applications.
Commodore 64 is a registered trademark of Commodore Business
Machines, Inc.
CHAPTER 2
THE NATURE OF COBOL IN GENERAL cc.llr
COBOL is the most widespread commercial programming language

in use today. The reasons for its vast success will be discussed
below.
The word COBOL is an abbreviation for Common Business
Qriented Language. It is a Business Oriented computer language
designed for commercial applications. The rules governing the use
of the language make it applicable for commercial problems.
COBOL is a computer language that is common to many
computers. That is most computers can process a COBOL program
with minor variations.
The universality of COBOL, therefore, allows computer users
greater flexibility. A company is free to use computers of different
manufacturers while retaining a single programming language.
Similarly, conversion from one model computer to a more
advanced or newer one presents no great problem. Computers of a
future generation will also be equipped to use COBOL.
Since its creation in 1959, the COBOL language has undergone
extensive refinement in an effort to make it more standardized The
American National Standards Institute (ANSI), an association of
computer manufacturers and users, has developed an industry-wide
standard COBOL.
Thus the meaning of the word COBOL suggests two of its basic
advantages. It is common to most computers, and it is
commercially oriented. There are, however, additional reasons
why it is such a popular language.
COBOL is an English-like language. All instructions are coded
using English words rather than complex codes. To add two
numbers together, for example, we use the word ADD. Another
example of a COBOL statement is:
MULTIPLY HOURS-WORKED BY HOURLY-WAGE GIVING GROSS-WAGES
The rules for programming in COBOL conform to many of the

rn rules for writing in English, making it a relatively simple language
to learn. It, therefore, becomes significantly easier to train
programmers. In addition, COBOL programs are written and
tested in far less time than programs written in other computer
languages.
Thus the English-like quality of COBOL makes it easy to write
programs. Similarly, this quality makes COBOL programs easier
to read. Such programs can generally be understood by non-data
processing personnel. The business executive who knows little
about computers can better understand the nature of a programming
job simply by reading a COBOL program.
CHAPTER 3
COBOL ADVANTAGES
The long list of COBOL advantages is derived chiefly from its

intrinsic quality of permitting the programmer to state the problem
solution in English prose, and thus provide automatic program and
system documentation. When users adopt well-chosen data-names
before attempting to program a system, maximum documentational
advantages of the language described herein are obtained.
To a computer user, COBOL 64 offers the following major
advantages:
1. Expeditious means of program implementation providing a
high degree of programmer productivity.
2. Accelerated programmer training and simplified retraining
requirements. m
3. Reduced conversion costs when changing from a computer
of one manufacturer to that of another.
4. Significant ease of program modification/enhancements
due to the high level of readability.
5. Documentation which facilitates nontechnical management
participation in data processing activities.
6. A comprehensive source program diagnostic capability
which includes tracing, break points and single step
features.
CHAPTER 4
COBOL 64 IMPLEMENTATION NOTES
A program written in COBOL 64, called a source program, is

accepted as input by the COBOL 64 software system. The system
verifies that each source statement is syntactically c o m t , and then
converts them into an intermediate condensed representation.
'The intermediate program can then be executed on the Commodore
64 System using the COBOL 64 Interpreter. The interpreter causes
the system hardware to perform the operations specified by the
intermediate program and thus the source program.
-
CHAPTER 5
HARDWARE CONSIDERATIONS
COMMODORE 64 Computer or equivalent (BASIC V2)

One to four Commodore 1541 disk drives or equivalent
One optional Commodore 1525 printer or equivalent
CHAPTER 6
e
SECTION 1 PROGRAM ORGANIZATION
COBOL 64 SOURCE PROGRAM DIVISIONS
Every COBOL 64 source program must contain these four

divisions in the following order:
IDENTIFICATION
ENVIRONMENT
DATA
PROCEDURE
The IDENT IF ICAT ION D Iv IS ION identifies the program. In
addition to required information, the programmer may include such
optional pieces of information as the date written and programmer's
A name for documentation purposes. This division is completely
machine-independent.
The ENVIRONMENT D IVIs ION specifies the equipment being
used. It contains computer descriptions and some information
about the files the program will use.
The D A T A D IvI S I ON contains not only file and record
descriptions describing the data files that the program manipulates
or creates, but also the individual logical records which comprise
these files. The characteristics or properties of the data are
described in relation to a standard data format rather than an
equipment-oriented format. Therefore, this division is to a large
extent, computer-independent. While compatibility among
computers cannot be absolutely assured, careful planning in the
data layout will permit the same data descriptions, with minor
modification, to apply to more than one computer.
F
The PROCEDURE DIVISION specifies user-supplied steps for
computer execution. These steps are expressed in terms of
meaningful English words, statements, sentences, and paragraphs.
This division of a COBOL 64 program is often referred to as the
"program". In reality, it is only part of the total program, and alone

is insufficient to describe the entire program. This is true because
repeated references must be made (either explicitly or implicitly) to
information appearing in the other divisions. This division, more n
than any other, allows the user to express thoughts in meaningful
English. Concepts of verbs to denote actions, and sentences to
describe procedures are basic, as is the use of conditional
statements to provide alternative paths of action.
REQUIRED HEADERS
The standard for COBOL 64 requires that a program consist of

certain divisions, sections, and fixed paragraph names known as
headers.
The following elements are the minimum required for a COBOL 64
program:
IDENTIFICATION DIVISION.
PROGRAM-ID. MINIMUM.
ENVIRONMENT DIVISION.
CONFIGURATION SECTION.
SOURCE-COMPUTER C64.
OBJECT-COMPUTER C64.
DATA DIVISION.
PROCEDURE DIVISION.
STARTUP.
STOP RUN.
- SECTION 2
GENERAL
LANGUAGE CONCEPTS
As stated in Section 1, COBOL 64 is a language based on English

and is composed of words, statements, sentences, and paragraphs.
The following paragraphs define the rules to be followed in the
creation of this language. The use of the different constructs
formed from the created words is covered in subsequent sections of
this document.
LANGUAGE DESCRIPTION NOTATION
A nearly universal form of notation exists for COBOL reference

manuals. This manual uses that notation as described in the
paragraphs that follow.
m
The apostrophe ( I ) is used to delimit characters with specific
meaning. Other than its use in this manual as a delimiter, it has no
specific use in the COBOL language.
KEYWORDS
All underlined upper-case words are key words and are
required when utilizing related functions. Omissions of
key words will cause error conditions at compilation time.
An example of key words follows:
-
IF data-name IS [m]rNUMERIC I
The key words are I F , NOT, NUMERIC, and

ALPHABETIC.
OPTIONAL WORDS
All upper case words not underlined are optional words
included for readability only and may be included or
excluded in the source program. In the preceding example,
the optional word is IS.
GENERIC TERMS
All lower-case words represent generic terms which are
used to represent COBOL words, literals, P I C T U R E
charac ter-strings, comment-entries, or a complete
syntactical entry that must be supplied in that format
position by the programmer. Where generic terms are
repeated in a general format, a number or letter appendage
to the term serves to identify that term for explanation or
discussion.
Identifier-1 and identifier-2 are generic terms in this
example: Ca
MOVE identifier-1 TO identifier-2
BRACES
The following symbols are braces: { } . When words or

phrases are enclosed in braces, a choice of one of the
entries must be made. In the previous example in the
subsection titled Keywords, either N U M E R I C or
ALPHABETIC must be included in the statement.
BRACKETS
The following symbols are brackets: [ ] . Words and
phrases enclosed in brackets represent optional portions of .rg,
a statement. A programmer wishing to include the optional
feature may do so by including the entry shown between
brackets. Otherwise, the optional portion may be omitted.
[NOT] in the example titled Keywords, is optional.
LEVEL-NUMBERS
When specific level-numbers appear in data description
entry formats those specific level-numbers are required
when such entries are used in a COBOL 64 program. In
this document, the form 0 1, 0 2, . . . ,0 9 is used to
indicate level-numbers 1 through 9.
ELLIPSIS
The presence of the ellipsis (three consecutive
periods(. . .) within any format indicates the position at
which repetition may occur at the programmer's option.
The portion of the format that may be repeated is defined in
the following paragraph.
The ellipsis applies to the words between the determined
pair of delimiters. Given the ellipsis in a clause or
statement format, scanning right to left, determine the right
bracket or right brace immediately to the left of the ...;
continue scanning right to left and determine the logically
matching left bracket or left brace.
CHARACTER SET
The COBOL 64 character set for the COBOL 64 System
consists of the following 46 characters:
0 through 9
A through Z
blank or space
+ plus sign
- minus sign or hyphen
* asterisk
/ slash
$ currency sign
. period or decimal point
quotation mark
( left parenthesis
) right parenthesis
CHARACTERS USED FOR WORDS Ar

The character set for words consists of the following 37
characters:
0 through 9
A through Z
- (hyphen)
PUNCTUATION CHARACTERS
The following characters may be used for program
punctuation:
quotation mark
( left parenthesis
) right parenthesis
space or blank
. period
EDITING CHARACTERS
The COBOL 64 System accepts the following characters in
editing:
$ currency sign
* asterisk (check protect)
, cornrna
/ slash
B space or blank insert
0 zero insert
+ plus sign
- minus sign
CR credit
DB debit
z zero suppress
. period
1~ LANGUAGE STRUCTURE
The individual characters of the language are concatenated
to form character-strings and separators. A separator may
be concatenated with another separator or with a
character-string.
A character-string may only be concatenated with a
separator. The concatenation of character-strings and
separators forms the text of a source program.
SEPARATORS
A separator is a string of one or more punctuation
characters. The rules for formation of separators are:
m 1. The punctuation character space is a separator. Anywhere

a space is used as a separator, more than one space may be
used.
2. The punctuation character period is a separator when
immediately followed by a space.
3. The punctuation character quotation mark is a separator.

An opening quotation mark must be immediately preceded
by the separator space, a closing quotation mark must be
immediately followed by one of the separators space or
period followed by a space. Quotation marks may appear
only in balanced pairs delimiting nonnumeric literals except
when the literal is continued.
4. The punctuation characters right and left parentheses are
separators. Parentheses may appear only in balanced pairs
of left and right parentheses delimiting subscripts or
indices. The right parentheses must be followed by a
space.
5. The separator space may optionally immediately follow any
separator except the opening quotation mark. In this case,
a following space is considered as part of the nonnumeric
literal and not as a separator.
Any punctuation character which appears as part of the
specification of a P I CTURE character-string or numeric
literal is not considered as a punctuation character, but
rather as a symbol used in the specification of that
P I CTURE character-string or numeric literal. P I CTURE
character-strings are delimited only by the separators space
or period followed by a space.
The rules established for the formation of separators do not
apply to the characters which comprise the contents of
nonnumeric literals, comment-entries, or comment lines.
CHARACTER-STRINGS
A character-string is a character of sequence of contiguous
characters which forms a COBOL 64 word, literal,
P I C T U R E character-string, or comment-entry. A
character-string is delimited by separators. AI
DEFINITION OF WORDS
A COBOL 64 word is created from a combination of not

more than 30 characters, selected from the following:
0 through 9
A through Z
- (hyphen)
A word is ended by a valid separator. A word may not
begin or end with a hyphen. (A literal constitutes an
exception to these rules, as explained in a paragraph
entitled Literals in this section.) A word must begin with
an alphabetic character.
A user-defined word is a COBOL 64 word that must be
supplied by the user to satisfy the format of a clause or
statement.
m
TYPES OF WORDS
COBOL 64 contains the following word types:
nouns (user-defined words)
verbs
reserved words.
NOUNS
Nouns are divided into special categories:
The length of a noun must not exceed 30 characters. For

purposes of readability, a noun may contain one or more
hyphens. However, the hyphen must neither begin nor
end the noun (this does not apply to literals).
All nouns within a given category must be unique, because
no other noun in the same source program has identical
spelling or punctuation. All user-defined words must
begin with an alphabetic character.
n
File-Name
A file-name is a noun assigned to designate a set of data
items. The contents of a file are divided into logical
records made up of any consecutive set of data items.
Record-Name
A record-name is a noun assigned to identify a logical
record. A record can be subdivided into a set of data
items, each distinguishable by a data-name.
Data-Name
r15,
A data-name is a noun assigned to identify elements within
a record or work area and is used in COBOL 64 to refer to
an element of data, or to a defined data area containing data
elements.
Index-Name
An index-name is a word that names an index associated
with a specific table (refer to Indexing in this section). An
index is a register, the contents of which represent the
character position of the first character of an element of a
table with respect to the beginning of the table.
Paragraph-Name
A paragraph-name is a word which names a paragraph in
thePROCEDUREDIVISION.
Verbs
A verb in COBOL 64 is a single word that denotes action,
such as ADD, WRITE, or MOVE. All allowable verbs in
COBOL 64, with the exception of the word IF, are English
verbs. The usage of the COBOL 64 verbs takes place
withinthePROCEDURE DIVISION.
RESERVED WORDS
A reserved word is a COBOL 64 word that is one of a
specified list of words which may be used in COBOL 64 e
source programs, but must not appear in the programs as
user-defined words. Refer to Appendix B, Reserved
Words.
These rules apply to the entire COBOL 64 source program;
no exceptions exist for specific divisions or statements.
There are two types of reserved words:
Key words
Optional words
KEY WORDS
A key word is a word whose presence is required in a
source program. Within each format, such words are
upper-case and underlined.
Key words are of three types:
1. Verbs such as ADD and READ.
2. Required words which appear in statement and entry
formats.
3. Words which have a specific functional meaning such
as SECTION.
OPTIONAL WORDS
Optional words are included in the COBOL 64 language to
improve the readability of the statement formats. These
optional words may be included or omitted. For example, rrq
I F A I S GREATER THAN B . . .is equivalent to I F A
GREATER B . . . ; the inclusion or omission of the words
I S and THAN does not influence the logic of the statement.
LITERALS
A literal is an item of data whose value is implied by an
ordered set of characters of which the literal is composed.
There are two classes of a literal: numeric and
nonnumeric.
NUMERIC LITERAL
A numeric literal is a character-string whose characters are
selected from the digits 0 through 9, the plus sign (+), the
minus sign (-), and/or the decimal point. Numeric literals
may be from 1 to 18 digits in length. The rules for the
formation of numeric literals are as follows:
1. A numeric literal must contain at least one digit.
2. A numeric literal must not contain more than one sign
character. If a sign is used, it must appear as the
leftmost character of the literal. If the literal is
unsigned, the literal is positive.
3. A numeric literal must not contain more than one
decimal point. The decimal point is treated as an
assumed decimal point, and may appear anywhere
within the literal except as the rightmost character. If
the literal contains no decimal point, the literal is an
integer. An integer is a numeric literal which contains
no decimal point.
If a literal conforms to the rules of the formation of
numeric literals, but is enclosed in quotation marks, it
is a nonnumeric literal and is treated as such by the
system.
4. The value of a numeric literal is the algebraic quantity
represented by the characters in the numeric literal.
Every numeric literal belongs to category numeric.
Refer to the P I C T U R E clause in Section 6 for
additional information. The size of a numeric literal in
standard data format characters is equal to the number
of digits specified by the user. The following are

examples of numeric literals:
NONNUMERIC LITERAL
A nonnumeric literal may be composed of any allowable
character. The beginning and ending of a nonnumeric
literal are both denoted by a quotation mark. Any character
enclosed within quotation marks is part of the nonnumeric
literal. Subsequently, all spaces enclosed within the
quotation marks are considered part of the literal. Two
consecutive quotation marks within a nonnumeric literal
cause a single quotation mark to be inserted into the literal
string.
n
All other punctuation characters are part of the value of the
nonnumeric literal rather than separators; all nonnumeric
literals belong to category alphanumeric. Refer to the
PICTURE clause in Section 6.
A nonnumeric literal cannot exceed 120 characters.

Examples of nonnumeric literals are:
Literal on Source Program Level Literal Stored by System
"THE TOTAL P R I C E " THE TOTAL P R I C E
-
"-2080.479" -2080.479
11All 11B11 A"B
Literals that are used for arithmetic computation must be

expressed as numeric literals and must not be enclosed in
quotation marks as nonnumeric literals. For example,
4 .4 and 4 .4 are not equivalent. The system stores the
nonnumeric literal as 4 . 4, whereas the numeric literal
would be stored as 0 0 4 4 if the P I C T U R E were 9 9 9V9,
with the assumed decimal point located between the two

fours.
LOGICAL RECORD AND FILE CONCEPTS

The purpose of defining file information is to distinguish
between the physical aspects of the file and the conceptual
characteristics of the data contained within the file.
PHYSICAL ASPECTS OF A FILE

The physical aspects of a file describe the data as it appears
on the input or output media and include such features as:
1. The grouping of logical records within the physical
limitations of the file medium.
2. The means by which the file can be identified.
e
CONCEPTUAL CHARACTERISTICS OF A FILE
The conceptual characteristics of a file are the explicit
definition of each logical entity within the file itself. In a
COBOL 64 program, the input or output statements refer to
one logical record.
It is important to distinguish between a physical record and
a logical record. A COBOL 64 logical record is a group of
related information, uniquely identifiable, and treated as a
unit.
A physical record is a physical unit of information whose
size and recording mode are adapted to a particular
computer for the storage of data on a input or output
device. The size of a physical record is hardware
dependent and has no direct relationship to the size of the
file of information contained on a device.
The concept of a logical record is not restricted to file data
but is carried over into the definition of working storage.
Working storage may be grouped into logical records and

defined by a series of record description entries.
RECORD CONCEPTS
The record description consists of a set of data description
entries which describe the characteristics of a particular
record. Each data description entry consists of a
level-number followed by a data-name, if required,
followed by a series of independent clauses, as required.
CONCEPT OF LEVELS
A level concept is inherent in the structure of a logical
record. This concept arises from the need to specify
subdivisions of a record for the purpose of data reference.
Once a subdivision has been specified, it may be further
subdivided to permit more detailed data referral.
n
DATA DESCRIPTION CONCEPTS
The most basic subdivisions of a record, those not further
subdivided, are called elementary items; consequently, a
record is said to consist of a sequence of elementary items,
or the record itself may be an elementary item.
In order to refer to a set of elementary items, the
elementary items are combined into groups. Each group
consists of a named sequence of one or more elementary
items. Groups, in turn, may be combined into groups of
two or more groups. An elementary item may belong to
more than one group.
LEVEL-NTJMBERS
A system of level-numbers shows the organization of
elementary items and group items. Since records are the
most inclusive data items, level-numbers for records start
at 01. Less inclusive data items are assigned higher (not
necessarily successive) level-numbers not greater in value
than 10. There is a special level-number 77 which is an
exception to this rule. Separate entries are written in the
source program for each level-number used.
A group includes all group and elementary items following
it until a level-number less than or equal to the
level-number of that group is encountered. All items
which are immediately subordinate to a given group item
must be described using identical level-numbers greater
than the level-number used to describe that group item.
Refer to Section 6 under LEVEL-NUMBER for additional
information.
CONCEPT OF CLASSES OF DATA

The five categories of data items (refer to the P I C T U R E
clause in Section 6) are grouped into three classes:
alphabetic, numeric, and alphanumeric. For alphabetic and
numeric, the classes and categories are synonymous. The
alphanumeric class includes the categories of alphanumeric
edited, numeric edited, and alphanumeric (without editing).
Every elementary item, except for an index data item,
belongs to one of the classes and also to one of the
categories. The class of a group item is treated as
alphanumeric regardless of the class of elementary items
subordinate to that group item. Table 2-1 shows the
relationship of the class and categories of data items.
Table 2- 1. Classes of Data
LEVEL OF ITEM CLASS CATEGORY

..................................................
Alphabetic Alphabetic
- -- - *
........................................
Numeric Numeric
........................................
Elementary Numeric Edited
Alphanumeric Alphanumeric Edited
Alphanumeric
..........................................................
Alphabetic
Numeric
Nonelement ary Alphanumeric Numeric Edited
(Group) Alphanumeric Edited
Alphanumeric
..........................................................
ALGEBRAIC SIGNS
Algebraic signs fall into two categories: operational signs, n
which are associated with signed numeric data items and
signed numeric literals to indicate algebraic properties; and
editing signs, which appear on edited reports to identify the
sign of the item.
Operational signs are represented as defined under symbol
S ' of the P I C T U R E clause. Refer to the P I C T U R E
clause, General Rule 8, the ' S ' symbol in Section 6.
Editing signs are inserted into a data item through the use
of the sign control symbols of the PICTURE clause.
STANDARD ALIGNMENT RULES

The standard rules for positioning data within an
elementary item depend on the category of the receiving
item. These rules are:
1. If the receiving data item is described as numeric:
a. The data is aligned by decimal point and is moved
to the receiving character positions with zero fill or
truncation on either end as required.
b. When an assumed decimal point is not explicitly
specified, the data item is treated as if it had an
assumed decimal point immediately following the
rightmost character and is aligned as in step l a
above.
2. If the receiving data item is a numeric edited data item,
the data moved to the edited data item is aligned by
decimal point with zero fill or truncation at either end
as required within the receiving character positions of
the data item, except where editing requirements cause
replacement of the leading zeros.
3. If the receiving data item is alphanumeric (other than a
numeric edited data item), alphanumeric edited or
alphabetic, the sending data is moved to the receiving
character positions and aligned at the left-most
character position in the data item with space fill or
truncation to the right, as required.
SUBSCRIPTING
Subscripts can be used only when reference is made to an
individual element within a list or table of like elements that
have not been assigned individual data-names (refer to the
OCCURS clause in Section 6).
The subscript can be represented either by a numeric literal

that is an integer or by a data-name. The data-name must
be a numeric elementary item that represents an integer.
When the subscript is represented by a data-name, the
data-name may not be subscripted.
The subscript may be signed and, if signed, must be
positive. The lowest possible subscript value is 1. This
value points to the first element of the table. The next
sequential elements of the table are pointed to by subscripts
whose values are 2, 3, and so forth. The highest
permissible subscript value, in any particular case, is the
maximum number of occurrences of the item as specified
in the OCCURS clause.
n
At the time of execution of a statement which refers to a
subscripted table element, each subscript specified is
validated. That is, its value must not be less than one or
more than the maximum number of occurrences as
specified by the corresponding OCCURS clause. If the
subscript value is not within this range, an abnormal
termination of the program occurs.
The subscript or set of subscripts that identifies the table
element is delimited by the balanced pair of separators, left
parenthesis and right parenthesis, following the table
element data-name. The table element data-name appended
with a subscript is called a subscripted data-name or an
identifier.
When more than one subscript is required, they are written
in the order of successively less inclusive dimensions of ln4
the data organization. The maximum number of subscripts
is 3.
General Format:
data-name ( subscript-1 [ subscript-2 [ subscript-3 1 ] )
Example:
I n the following record description, to reference the first
year, TOTAL-PER-YEAR (1) is written. If data-name
YEAR contains the number of the year desired,
TOTAL-PER-YEAR (YEAR) is written. If the data item
MONTH contains the specific month desired within the
year specified by YEAR, TOTAL-PER-MONTH (YEAR
MONTH) is written.
01 YEAR-TABLE.
02 TOTAL-PER-YEAR OCCURS 10 TIMES.
05 TOTAL-PER-MONTH OCCURS 12 TIMES PIC 999.
77 YEAR PIC 99.
77 MONTH PIC 99.
*
INDEXING
References can be made to individual elements within a
table of like elements by specifying indexing for that
reference. An index is assigned to that level of the table by
using the I N D E X E D BY phrase in the definition of a table.
A name given in the I N D E X E D BY phrase is known as an
index-name and is used to refer to the assigned index. The
value of an index corresponds to the occurrence number of
an element in the associated table. An index-name can be
given a value by the execution of a SET statement.
The advantage to indexing is derived by faster execution
time when multiple references to the same table element is
required. In subscripting a multiply function is needed
each time a reference is made. In indexing the multiply
only occurs during execution of the SET statement and not
each time a reference is made.
An index-name has the same internal representation as an

index data item. If a value to be stored in an index-name or
in an index data item exceeds the largest value that can be
held in that index-name or index data item, the value is
truncated according to the rules for the occurrence of a size
error condition in an arithmetic statement without a S IZE
ERROR phrase.
An index-name assigned to one table may not be used to

index another table.
Direct indexing is specified by using an index-name in the
form of a subscript. When more than one index-name is
required, they are written in the order of successively less
inclusive dimensions of the data organization as in
subscripting.
At the time of execution of a statement which refers to an
indexed table element, the value of each direct index must
not be less than a value which corresponds to the
beginning of the first occurrence of the table element.
Also, the index must not be greater than a value which
corresponds to the beginning of the last occurrence of the
table element as specified by the corresponding OCCURS
clause. If the index value is not within this range, the
execution of the program is terminated.
Subscripting is permitted where indexing is permitted.
SECTION 3 EDITING FORMAT
C4
The rules for spacing given in the following description of
the reference format take precedence over all other rules for
spacing.
FIELD DEFINITIONS
The same format is used for all four divisions of a COBOL
64 program. These divisions must appear in proper order:
IDENTIFICATION, ENVIRONMENT, DATA, and
P ROCED U R E . The following paragraphs describe the
various fields of this coding form.
SEQUENCE AREA (Record Positions 1-6)

A sequence number, consisting of six digits in the
sequence area, must be used for each source program line.
F.
INDICATOR AREA (Record Position 7)

Column 7 has the following functions:
1. If column 7 contains an asterisk (*), the remainder of

the record is considered to be a comment and, is not
compiled.
2. If column 7 contains a slash (/), the printout is

advanced to the top of the next page before printing,
and the record is considered to be a comment record.
This feature is not available at this time.
3. The presence of a hyphen (-) indicates that the last

nonnumeric literal on the previous record is not
complete and is continued on this record beginning in
Area B (positions 12 through 80).
Nonnumeric literals can be split into two or more records.

On the initial record starting from the quotation mark, all
information through position 80 is taken as part of the
literal, and on the next record a quotation mark must be
used to indicate the start of the second part of the literal. A
AREA A (Positions 8-11)

DIVISION, SECTION, and PARAGRAPH headers must
begin in AREA A. A division header consists of the
division name (IDENTIFICATION, ENVIRONMENT,
DATA, or PROCEDURE), followed by a space, then the
word D IVI s ION followed by a period.
In the ENVIRONMENT andDATA DIVISIONS, a section
header consists of the section-name, followed by a space,
and then the word SECTION followed by a period.
A paragraph header consists of the paragraph-name
followed by a period. The first sentence of the paragraph 45
may appear on the same Line as the paragraph header.
Within the IDENTIFICATION and E N V I R O N M E N T

divisions, the section and paragraph headers are fixed and
only the headers shown in this manual are permitted.
Within the PROCEDURE D I V I S ION, the paragraph
headers are defined by the user.
Within the DATA DIVISION, the level indicator ED and

the level numbers 01 and 77 must each begin in Area A,
followed by the associated name and appropriate
descriptive information.
AREA B (Positions 12-80)

All entries which are not D I V I S I ON, SECT I ON, or
#- PARAGRAPH headers; level numbers 01 and 77, or level
indicator FD must start in Area B.
When level-numbers are to be indented, each new
level-number may begin any number of spaces to the right
of Area A.
BLANK LINES
A blank line is one that contains no entries in the Indicator
Area, Area A, and Area B. A blank line may appear
anywhere in the source program except immediately
preceding a continuation line.
PUNCTUATION
The following rules of punctuation apply in COBOL 64
source programs:
1. A sentence must be terminated by a period followed by
a space. A period must not appear within a sentence
unless it is within a nonnumeric literal or is a decimal
point in a numeric literal or P I CTURE string.
2. Two or more names in a series must be separated by a
space.
3. A space must never be embedded in a name; hyphens
are to be used instead. A hyphen must not start or
terminate a name. For example:
PAY-DAY (correct)
-PAYDAY (wrong)
SECTION 4 IDENTIFICATION DIVISION
GENERAL
The first division of the COBOL 64 source program is the
IDENTIFICATION DIVISION whose function is to
identify the source program and the resultant output. In
addition, the date the program was written and other
pertinent information can be included in the
IDENTIFICATION DIVISION.
IDENTIFICATION DIVISION STRUCTURE
-
The structure of this division follows:
IDENTIFICATIONDIVISION.
-[ - . program-name.
[AUTHOR. [comment-entry] . . .]
[INSTALLATION. [comment-entry] . . .]
.-[ [comment-entry] . . .I
[SECURITY. [comment-entry] . . .]
The following rules must be observed in the formation of
the IDENTIFICATION DIVISION:
1. The IDENTIFICATION DIVISION must begin with

the reserved words IDENTIFICATION DIVISION
followed by a period and a space.
2. All paragraph-names must begin in positions 8 through
11 (Area A). r4b
3. The comment-entry must be on the same line as the
paragraph name.
- 4. The comment-entry can consist of any combination of

words and literals allowed by the COBOL 64 Editor.
PROGRAM-ID PARAGRAPH
The PROGRAM- ID paragraph gives the name by which a
program is identified.
-
PROGRAMID.
program-name .
The following rules must be observed to form
PROGRAM-ID paragraphs.
1. The program-name must conform to the rules for
formation of a user-defined word.
2. The PROGRAM-ID paragraph contains the name of the
program and must be present in every program.
3. The program-name identifies the source program and
all listings pertaining to a particular program.
4. The program-name must be followed by a period and a
space.
SECTION 5 ENVIRONMENT DIVISION
GENERAL m
The ENVIRONMENT DIVISION is the second division of
a COBOL 64 source program. Its function is to specify the
computer being used for the program compilation, specify
the computer to be used for program execution, and
associate files with the computer hardware devices.
Furthermore, this division is also used to specify
input-output areas to be utilized for each file declared in a
program.
ENVIRONMENT DIVISION ORGANIZATION

The E N V I R O N M E N T D I V I S I O N consists of two
sections. The CONFIGURATION SECTION contains the
overall specifications of the computer. The
INPUT-OUTPUT SECTION deals with files to be used in rrr,
the object program.
ENVIRONMENT DIVISION STRUCTURE

The structure of this division follows:
. source-computer-entry
. o b ject-computer-ent ry
.-[ special-names-entry]
.- {file-control-entry ) . . . I
The following rules must be observed in the formulation of

the ENVIRONMENT DIVISION.
1. The ENVIRONMENT DIVISION must begin with the

reserved words E N V I R O N M E N T D I V I S ION
followed by a period and a space.
2. All entries must begin in Area A (columns 8 through
11).
CONFIGURATION SECTION
The CONF IGURATION SECT ION contains information
concerning the system to be used for program compilation
(SOURCE-COMPUTER), the system to be used for
program execution (OBJECT-COMPUTER), and the
SPECIAL-NAMES paragraph. The SPECIAL-NAMES
paragraph is used to define a special currency sign or
n decimal point in place of commas.
SOURCE-COMPUTER PARAGRAPH
The S O U R C E - C O M P U T E R paragraph identifies the
computer upon which the program is to be compiled.
General Format:
-
SOURCECOMPUTER.
computer-name.
Syntax Rule:
1. The computer-name must be equal to C 64 followed by
a period and a space.
rC4
Example:
SOURCE-COMPUTER. C64.
-
OBJECT-COMPUTER PARAGRAPH
The OB J E C T - C O M P U T E R paragraph identifies the
computer on which the program is to be executed.
General Format:
UTEB . computer-name .
Syntax Rules:
1. Computer-name must be equal to C 6 4 followed by a
period and a space.
SPECIAL-NAMES PARAGRAPH
The SPEC IAL-NAMES paragraph provides a means of
defining a special currency sign or the decimal point in
place of commas.
General Format:
[CLBREUCY SIGN LS literal]
[ D ~ C -W
POIN2
~ ~ Ls :OMMA1 .
SPECIAL-NAMES
Syntax Rules:
1. The literal which appears in the CURRENCY S IGN IS
literal clause is used in the P I C T U R E clause to
represent the currency symbol. The literal is limited to
a single character enclosed in quotation marks and
must not be one of the following characters:
a. Digits 0 through 9.
b. Alphabeticcharacters:~ B C D L P R S v x
z space
c. Special characters: * + - , . ; ( ) " / =
If the CURRENCY SIGN IS clause is not present, the

default value dollar sign ($) is used in the PICTURE
clause.
For example: CURRENCY SIGN IS "E"
2. The clause DECIMAL-POINT IS COMMA means that

the functions of the comma and period are exchanged
in the character-string of the PICTURE clause and in
the F ILTER-NUMERIC verb. This does not apply to
numeric literals.
INPUT-OUTPUT SECTION
The I N P U T - O U T P UT section contains information
concerning files to be used by the program, and the manner
of recording used.
FILE CONCEPTS
In the following paragraphs, concepts of File Types,
Organization, Access Mode, 1-0 Status, I N V A L I D KEY
and AT E N D are discussed pertaining to Sequential and
Relative files.
SEQUENTIAL 1 - 0
Sequential 1-0 provides a capability to access records of a
file in established sequence. The sequence is established
as a result of writing the records to the file.
n
Sequential 1-0 provides full facilities for the
F I L E - C O N T R O L and F D entries as specified in the
formats of this manual. Within the P R O C E D U R E
DIVISION, Sequential 1-0 provides full capabilities for
the CLOSE, OPEN, READ and WRITE statements.
RELATIVE 1 - 0
Relative 1-0 provides the capability to access records of a
disk file in either a random or sequential manner. Each
record in a relative file is uniquely identified by an integer
value greater than zero which specifies the record's logical
ordinal position in the file.
Relative 1-0 has full facilities for the FILE-CONTROL and

F D entries as specified in the formats of this manual. AI
Within the PROCEDURE DIVISION, the 1-0 provides
full capabilities for the CLOSE, OPEN, READ, and WRITE
statements.
ORGANIZATION
Sequential Files are organized such that each record in the
file except the first has a unique predecessor record, and
each record except the last has a unique successor record.
These predecessor-successor relationships are established
by the order of WRITE statements when the file is created.
Once established, the predecessor-successor relationships
do not change except in the case where records are added
to the end of the file.
Relative File organization is permitted only on disk storage
devices. A Relative File consists of records which are
identified by relative record numbers. The file may be
thought of as composed of a serial string of areas, each
capable of holding a logical record. Each of these areas is
denominated by a relative record number. Records are
stored and retrieved based on this number. For example,
the tenth record is the one addressed by relative record
number 10 and is in the tenth record area, whether or not
records have been written in the first through the ninth
record areas. The maximum size of a relative logical
record is 254 characters.
ACCESS MODE
The ACCESS MODE clause specifies the manner in which
records are accessed in a file. Sequential and Relative File
access methods are discussed in the following paragraphs.
SEQUENTIAL FILES
In the sequential access mode, the sequence in which
records are accessed is by the ascending order of ordinal
location within the fde.
- - - -
RELATIVE FILE
In the sequential access mode, the sequence in which
records are accessed is the ascending order of the relative *
record numbers of all records which currently exist within
the file.
In the random access mode, the sequence in which records
are accessed is controlled by the programmer. The desired
record is accessed by placing its relative record number in a
relative key data item.
1 - 0 STATUS
-
If the F I L E STATUS clause is specified in a file control
entry, a value is placed into the specZied two-character data
item during the execution of an OPEN, CLOSE, READ, Or
WRITE statement to indicate to the COBOL 64 program the
status of that input-output operation.
The usage of this feature is strongly recommended. The
testing of 1-0 status after each 1-0 statement will avoid a
good deal of confusion when debugging.
STATUS KEY 1
The leftrnost character position of the F I L E STATUS
data item is known as status key 1 and is set to a value
which indicates one of the following conditions upon
completion of the input-output operation.
VALUE CONDITION
0 Successful Completion
1 At End
2 Invalid Key
3 Perrnanent Error
9 COBOL 64-Defined Condition:
The above conditions are defined in following text.
SUCCESSFUL COMPLETION
The input-output statement was successfully executed.
AT END
The sequential READ statement is unsuccessfully executed

as a result of an attempt to read a record when no next
logical record exists in the file.
INVALID KEY
The input-output statement was unsuccessfully executed as
a result of one of the following:
1. A READ statement when the contents of the ACTUAL
KEY data item are less than 1 or greater than the ordinal
number of the last record ever written to the file, or
trying to READ a relative file record which was never
written to.
2. A WRITE statement when the contents of the ACTUAL

KEY data item are less than 1 or greater than the last
record allowed to be written because of the
specification of a maximum file size.
PERMANENT ERROR
The input-output statement was unsuccessfully executed as
the result of a boundary violation for a sequential file or as
the result of an input-output error, such as data check
parity error.
STATUS KEY 2
The rightrnost character position of the FILE STATUS
data item is known as status key 2 and is used to further m
describe the results of the input-output operations. This
character contains a value as follows:
1. If no further information is available concerning the
input-output operation, then status key 2 contains a
value of 0.
2. When status key 1 contains a value of 2 indicating an
INVALID KEY condition, status key 2 is used to
designate the case of that condition as follows:
a. A value of 3 in status key 2 indicates no record
found. An attempt is made to access a record,
identified by a key, but that record does not exist
in the file.
b. A value of 4 in status key 2 indicates a boundary
violation. An attempt was made to write beyond
the externally defined boundaries of the file.
3. When status key 1 contains a value of 9 indicating a
COBOL 64-defined condition, the value of status key
2 indicates the condition as follows:
STATUS KEY 2
VALUE CONDITION
0 This is a Commodore exception which is displayed on
the screen. See your Commodore User's Guide for
additional information.
1 Attempted to OPEN or CLOSE when file was already

opened or closed.
2 Device not present or powered on.
3 Attempted READ or W R I T E when file was not opened

or not opened properly. A READ must be opened
I N P U T or 1-0. A WRITE must be opened OUTPUT or
1-0.
4 Attempted READ when previous READ resulted in an
end of file condition.
VALID COMBINATIONS OF STATUS KEYS 1 and 2
The valid permissible combinations of the values of status
key 1 and status key 2 are shown in Table 5- 1.
TABLE 5-1. STATUS KEY COMBINATIONS
STATUS STATUS
KEY 1 KEY 2
Successful completion
AT END
I N V A L I D KEY, no record found
I N V A L I D KEY, boundary violation
Permanent error
Commodore error
OPEN CLOSE error
Devise not presentlready
READ or WRITE with OPEN error
READ after end of file
FILE-CONTROL PARAGRAPH
The F ILE-CONTROL paragraph names each file and
allows specification of other file-related information.
General Format:
FTI,F.--. { file-control-entry } ...
FILE CONTROL ENTRY

The file control entry names a file and may specify other
file-related information.
;IKPUT-OTJTPUT SECTION.
WE-CONTRL
SELF.CT filename
I Q
-MODE
I G A ~
IS SEOUENTIAI,
~ N
3
I S ~ ]
r ORGANIZATION IS RELATIVE
-MODE
[FILE
IS
YEK-[-
{ RANDOM
IS data-name-l]
-KEY
.
IS
IS data-name-2
Syntax Rules:
1. The SELECT clause must be specified first in the file
control entry. The clauses which follow the SELECT
clause may appear in any order.
2. Each file described in the DATA DIVISION must be

named only once with a file-name in the
FILE-CONTROL paragraph. Each file specified in the
file control entry must have a file description entry in
the DATA DIVISION.
3. If the ACCESS MODE clause is not specified, the
ACCESS MODE IS SEQUENTIAL clause is implied.
4. Data-name-1 must be defined in the D A T A

D I v I S I O N as a two-character data item of the
category alphanumeric and must not be defined in the
FILE S E C T I O N or the C O M M U N I C A T I O N
SECTION.
5. If no ORGAN1 ZATION IS clause is specified, the

ORGANIZATION IS SEQUENTIAL clause is
implied.
6. The RELATIVE KEY phrase may be specified only

for disk storage files.
7. Data-name-2 must not be defined in a record
description entry associated with that file-name.
8. The data item referenced by data-name-2 must be
defined as an unsigned integer.
General Rules:
1. The ASSIGN clause specifies the association of the file
referenced by file-name to a storage medium. For
Relative and Indexed Files, the storage medium must
be DISK-1541.
-
2. The O R G A N I ZATION clause specifies the logical
structure of a file. The file organization is established
at the time a file is created and cannot subsequently be
changed.
3. When the access mode of a Relative File is sequential,
records in the file are accessed in the order of
ascending relative record numbers of existing records
in the file.
4. When the F I LE STATUS clause is specified, a value
is moved by the COBOL 64 system into the data item
specified by data-name-1 after the execution of every
statement that references that file either explicitly or Aq
implicitly. This value indicates the status of execution
of the statement. Refer to 1-0 Status in this section for
5. If the access mode of a Relative File is random, the
value of the RELATIVE KEY data item indicates the
record to be accessed.
6. All records stored in a Relative File are uniquely
identified by relative record numbers. The relative
record number of a given record specifies the record's
logical ordinal position in the file. The first logical
record has a relative record number of 1, and
subsequent logical records have relative record
numbers of 2,3,4, and so forth.
-h
7. In a Relative File, the data item specified by
data-name-2 is used to communicate a relative record
number between the program and the COBOL 64
system.
SECTION 6 DATA DIVISION
GENERAL
The DATA DIVISION describes the data that the object
program is to accept as input, to manipulate, to create, or to
produce as output. Data to be processed belongs to these
three categories:
1. That which is contained in files and enters or leaves the
internal memory of the computer from a specified area
or areas.
2. That which is developed internally and placed into
intermediate or working storage, or placed into specific
format for output reporting purposes.
3. Constants which are defined by the user.
+
DATA DIVISION ORGANIZATION
The DATA DIVISION, which is one of the required
divisions in a program, is subdivided into sections. These
are FILE and WORKING-STORAGE.
The FILE SECTION defines the structure of data files.
Each file is defined by a file description entry and one or
more record descriptions. Record descriptions are written
immediately following the file description entry.
The WORKING-STORAGE SECT ION describes records
and noncontiguous data items which are not part of
external data files but are developed and processed
internally. It also describes data items whose values are
preassigned in the source program.
DATA DIVISION STRUCTURE

The following structure shows the general format of the
sections of the DATA D I V I S ION, and defines the order ba
of presentation in the source program.
-
DATA DIVISION.
-
FILE SECTION.
[file-description-entry [record-description-entry] ...] . . . 1

I]
WORKING-STORAGE SECTION.
77-level-description-entry
record-description-entry
FILE SECTION Lla
In a COBOL 64 program, the file description entry (FD)

represents the highest level of organization in the FILE
SECTION. The FILE SECTION header is followed by a
file description entry consisting of a level indicator (FD), a
file-name, and a series of independent clauses. The FD
clauses specify the size of the logical records, the presence
or absence of label records and the value of label items.
The entry is terminated by a period.
RECORD DESCRIPTION
A record description consists of a set of data description
entries which describe the characteristics of a particular
record. Each data description entry consists of a
level-number followed by a data-name (if required), "a
followed by a series of independent clauses as required.
Examples:
01 DATA-ITEM-ONE PICTURE IS X(10) .

03 LINE-COUNTER PIC 999.
A record description has a hierarchical structure and,

therefore, the clauses used with an entry may vary
considerably, depending upon whether or not it is followed
by subordinate entries. The structure of a record
description is defined in Concepts of Levels, Section 2,
while the elements allowed in a record description are
shown in the data description structure.
FILE DESCRIPTION STRUCTURE

The file description entry furnishes information concerning
the physical structure and identification pertaining to a
given file.
[FJ f ile-name
[VALUE O F F I L E - I D I S literal-11
{ record-description-entry ) . . .] ..
LABEL RECORDS
The LABEL RECORDS clause specifies whether labels are
present. da
Syntax Rules:
This clause is required. The clause is treated as
documentation only.
VALUE OF
The VALUE OF clause specifies the file identification of a
disk file.
Syntax Rules:
Literal- 1 must be a nonnumeric literal not greater than 19
characters. The first three characters must be @ 0 : if the
"replace" feature is desired. Note that relative files cannot .L"14
be "replaced. See your Commodore user's guide for
more detailed information.
General Rules:
1. For an input file, the appropriate label routine checks
to see if the disk drive contains a file name equal to the
value of literal-1.
For an output file, at the appropriate time, the value of
literal-1 is used to create the disk fde name.
Example: VALUE OF FILE-ID IS "MY-FILE"
DATA DESCRIPTION STRUCTURE

A data description entry specifies the characteristics of a
particular item of data.
General Format:
{- }
dat a-name-1
level-number
FILLER
[ [USAGE IS] INDEX ]
[ OCCURS integer-2 TIMES
[INDEXED BY index-name-1 [index-name-21 ... I
[VALUE I S literal-11
- -
[VALUE I S CHR literal-21 .
Syntax Rules:
1. The level-number may be any number from 0 1 through
10 or 77. m
2. The clauses may be written in any order with one
exception: the data-name-1 or FILLER clause must
immediately follow the level-number.
3. The P I C TURE clause must be specified for every

elementary item except an index data item, in which
case, use of this clause is prohibited. The P I C T U R E
clause and character-string must be on the same line.
General Rules:
1. The P ICTURE clauses must not be specified except for
an elementary data item.
DATA-NAME OR FILLER
A data-name specifies the name of the data being
described. The word FILLER specifies an elementary
item of the logical record that cannot be referred to
explicitly.
General Format:
{ data-name
FILLER }
Syntax Rules:
1. In the FILE and WORKING-STORAGE SECTIONS,
a data-name or the key word FILLER must be the first
word following the level-number in each data
description entry.
General Rules:
1. The key word F I L LE R may be used to name an
elementary item in a record. Under no circumstances
can a FILLER item be referred to explicitly.
2. The key word FILLER is not allowed with a level 77
item or with a VALUE clause.
LEVEL-NUMBER
The level-number shows the hierarchy of data within a
logical record. In addition, it is used to identify entries for
working storage items.
General Format:
level-number
Syntax Rules:
1. A level-number is required as the first element in each
data description entry.
2. Data description entries subordinate to an FD must
have level-numbers with the values 01 through 10.
Refer to the FD file description in the paragraph
entitled File Description Structure.
3. Data description entries in the WORKING-STORAGE

SECTION must have level-numbers with the values 01
through 10.
General Rules:
1. The level-number 01 identifies the first entry in each
record description. Less inclusive groupings are given
-
,
higher numbers (not necessarily successive) up to a
limit of 10.
2. A special level-number has been assigned to entries
where there is no real concept of level: the
level-number 77 is assigned to identify noncontiguous
working storage data items.
3. Multiple level 0 1 entries subordinate to any given level
indicator (FD) represent implicit redefinitions of the
same area.
Examples:
The following is an example of record layout which
corresponds to Figure 6-3 showing a record description "a4
and the use of level numbers.
STUDENT RECORD
STUDENT NO. NAME GRADE BIRTH DATE

LAST FIRST mth day yr
01 STUDENT-REC .
0 3 STUDENT-NO PIC 9 ( 6 ) .
0 3 STUDENT-NAME.
0 5 LAST-NAME PIC X ( 8 ) .
0 5 FIRST-NAME PIC X ( 5 ) .
0 3 GRADE PIC 9 9 .
0 3 BIRTH-DATE.
0 5 BIRTH-MONTH PIC 9 9 .
0 5 BIRTH-DAY PIC 9 9 .
0 5 BIRTH-YEAR PIC 9 9 .
Figure 6-3 Level Numbers

OCCURS
The OCCURS clause eliminates the need for separate entries
for repeated data items and supplies information required
for the application of subscripts or indices.
General Format:
QCCyE integer-2 TIMES
Syntax Rules:
1. An INDEXED BY phrase is required if the subject of
this entry, or an entry subordinate to this entry, is to be
referred to by indexing.
2. The OCCURSclause cannot be specified in a data
description entry that has an 01 or 77 level-number.
3. Index-name- 1, index-name-2,.. . must be unique
words within the program.
4. Integer-2 cannot be zero and cannot be greater than
9,999.
General Rules:
1. The OCCURSclause is used in defining tables and

other homogeneous sets of repeated data items.
Whenever the OCCURS clause is used, the data-name
which is the subject of this entry must be either
subscripted or indexed whenever it is referred to in a
statement. Further, if the data-name associated with
the OCCURSclause is the name of a group item, then
all data-names belonging to the group must be
subscripted or indexed when used as operands. Refer
to Subscripting, Indexing, and Identifier in Section 2.
2. Except for the OCCURS clause, all data description

clauses associated with an item whose description
includes an OCCURSclause apply to each occurrence
of the item described.
3. The VALUE clause is not allowed with the OCCURS

clause.
-
PICTURE
The PICTURE clause describes the general characteristics
and editing requirements of an elementary item.
General Format:
-PIC
IJ
-. P I C T U R E
1
I S character-string AI
Syntax Rules:
1. A P I C T U R E clause can be specified only at the
elementary item level.
2. A character-string consists of certain allowable
combinations of characters in the COBOL 64 character
set used as symbols. The allowable combinations
determine the category of the elementary item.
3. The maximum number of characters allowed in the
character-string is 30.
4. The P ICTURE clause must appear in every elementary

item except those items whose USAGE is declared as
INDEX.
5. PIC is an abbreviation for PICTURE.
General Rules:
rn
1. There are five categories of data that can be described
with a P I C T U R E clause; alphabetic, numeric,
alphanumeric, alphanumeric edited, and numeric
edited.
2. To define an item as alphabetic:
a. The P I CTURE character-string can only contain

the symbol ' A ' .
b. The item contents, when represented in standard
data format, must be any combination of the 26
letters of the English alphabet and the space from
the computer character set
3. To define an item as numeric:
a. The P I CTURE character-string can only contain
thesymbols ' 9 ' , ' S P , a n d ' v ' . Thenumberof
digit positions that can be described by the
P I C T U R E character-string must range from 1 to
18 inclusive.
b. If unsigned, the item contents must be a
combination of the numerals ' 0 ' , ' 1 ' , ' 2 ' ,
'3', '4', ' S f , '6', ' 7 ' , ' 8 ' , a n d ' 9 ' ; i f
signed, the item may also contain a ' + ' or ' - ' .
4. To define an item as alphanumeric:
a. The P I C T U R E character-string is restricted to

certain combinations of the symbols ' A ' , x ,
9 , and the item is treated as if the
character-string contained all x's. A P I CTURE
character-string which contains all A's or all 9's
does not define an alphanumeric item.
b. The item contents are allowable characters in the

computers.
5. To define an item as alphanumeric edited:

certain combinations of the following symbols:
l A l r l X t r 191r l B V r 1 0 1 , a n d ' / l .
1) The character-string must contain at least one

' B and at least one x ' or at least one ' 0 '
(zero) and at least one ' X ' or at least one
/ (stroke) and at least one ' x ' .
-
0 (zero) and at least one A or at least one
/ (stroke) and at least one ' A .
b. The contents are allowable characters in the
computer character set.
6. To define an item as numeric edited:

certain combinations of the symbols ' B ' , / ' r
' V V r ' Z V r 1 0 1 r '91r l r V r . r '*'r
1 1 1-1
' CR ' r ' DB ' r and the currency
symbol ($). The allowable combinations are
determined from the order of precedence of
symbols and the editing rules.
-
1) The number of digit positions that can be
represented in the P I C T U R E character-string
must range from 1 to 18 inclusive.

l o t r 1glr l / l r 1 z l r l * l r l+lr
1 1 1 1 '-'I ' C R V r ' D B t r or
r r - r
currency symbol.
b. The contents of the character positions of these

symbols that are allowed to represent a digit in
standard data format must be one of the numerals.
7. The size of an elementary item, where size means the
number of character positions occupied by the
elementary item in standard data format, is determined
by the number of allowable symbols that represent
character positions. An integer which is enclosed in
parentheses following the symbols: A ', , ,
1x1, 191, IZl, I*), IBI, I/), 101,
- , or $ indicates the number of
constkutive occumnces of the symbol. The maximum
value of this integer is 9 , 9 9 9. The following
symbols may appear only once in a given P I C T U R E :
S , V . , 'CR', and 'DB'.
8. The functions of the symbols used to describe an
elementary item are explained as follows:
'A'
Each letter A in the character-string represents a
character position which can contain only a letter of the
alphabet or a space.
IBr
Each letter B in the character-string represents a
character position into which the space character will
be inserted.
IS'
The letter S is used in a character-string to indicate
the presence of an operational sign in the internal
representation of a numeric data item. It must be the
first (leftmost) character in the character-string.
When an operational sign is specified the sign is
maintained and expected in the zone of the most
significant (leftmost) character. When the data item is
the receiving field in an arithmetic statement the four
zone bits are set to binary 0101 for negative values and
to binary 0 1 0 for positive values. When the data item
is used in an algebraic comparison or operation to

supply an algebraic value, only the most significant
zone being a binary 0101 will cause the value of the
data item to be considered negative. Only the zone
values 0100 and 0101 will qualify the data item as
being NUMERIC if tested by the NUMERIC class
condition.
'V'
The letter ' v ' is used in a character-string to indicate
the location of the assumed decimal point and may
only appear once in a character-string. The ' v ' does
not represent a character position and is not counted in
the size of the elementary item. When the assumed
decimal point is to the right of the rightmost symbol in
the string, the ' v ' is redundant.
'X'
Each letter ' x ' in the character-string is used to
represent a character position which contains any
allowable character in the character set.
*(rg
'Z'
Each letter ' z' in a character-string may only be used
to represent the leftmost leading numeric character
positions which are replaced by a space character when
the contents of that character positions are zero. Each
' z ' is counted in the size of the item.
'9'
Each numeral ' 9 ' in the character-string represents a
character position which contains a numeral and is
counted in the size of the item.
'0'
Each numeral ' 0 ' in the character-string represents a
character position into which the numeral zero is
inserted. The ' 0 ' is counted in the item.
CI
I /
Each stroke / ' in the character-string represents a

character position into which the stroke character is
inserted. The is counted in the size of the item.
I/'
1 I
I
Each comma ' , ' in the character-string represents a
character position into which the character ' , ' is
inserted. This character position is counted in the size
of the item. The insertion character ' , ' must not be
the last character in the P ICTURE character-string.
I I
When the character period ' . ' appears in the

character-string it is an editing symbol which
represents the decimal point for alignment purposes
and in addition, represents a character position into
which the character ' . ' is inserted. The character ' . '
is counted in the size of the item. For a given program
the functions of the period and comma are exchanged
if the clause DEC IMAL-POINT I S COMMA is stated
in the SPEC IAL-NAMES paragraph. In this exchange
the rules for the period apply to the comma and the
rules for the comma apply to the period when
appearing in a P I C T U R E clause. The insertion
character ' . ' must not be the last character in the
PICTURE character-string.
' + I 1 - 1
'CR' 'DB'
These symbols are used as editing sign control
symbols and when used, represent the character
position into which the editing sign control symbol
will be placed. The symbols are mutually exclusive in
any one character-string and each character used in the
symbol is counted in determining the size of the data
item.
Each asterisk ' * ' in the character-string represents a

leading numeric character position into which an
asterisk is placed when the contents of that position are
zero. Each is counted in the size of the item.
I*'
'cs'
The currency symbol ' $ ' in the character-string
represents a character position into which a currency
symbol is placed. The currency symbol in a
character-string is represented by either the dollar sign
' $ ' or by the character specified in the CURRENCY
SIGN clause in the SPECIAL-NAMES paragraph. The
currency symbol is counted in the size of the item.
EDITING RULES:
1. There are two general methods of performing editing

in the P I C T U R E clause, either by insertion or by
suppression and replacement. The four types of
insertion editing available are:
a. Simple insertion
b. Special insertion
c. Fixed insertion
d. Floating insertion
There are two types of suppression and replacement

editing:
a. Zero suppression and replacement with spaces
b. Zero suppression and replacement with asterisks
2. The type of editing which may be performed upon an

item is dependent upon the category to which the item
belongs. Table 6-1 specifies which type of editing
may be performed upon a given category:
Table 6-1. Editing for Each Item Category

Category Type of Editing
Alphabetic None
Numeric None
Alphanumeric None
Alphanumeric Edited Simple insertion 0 , B I, and ' / '
Numeric Edited All, subject to Editing Rule 3
3. Floating insertion, and editing by zero suppression and
replacement, are mutually exclusive in a PICTURE
clause. Only one type of replacement may be used
with zero suppression in a PICTURE clause.
4. Simple Insertion Editing. The , (comma), B
(space), 0 (zero), and / (stroke) are used as the
insertion characters. The insertion characters are
counted in the size of the item and represent the
position in the item into which the character is inserted.
Special Insertion Editing. The . ' (period) is used as

the insertion character. In addition to being an
insertion character it also represents the decimal point
for alignment purposes. The insertion character, used
for the actual decimal point, is counted in the size of
the item. The use of the assumed decimal point,
represented by the symbol v and the actual decimal
point, represented by the insertion character, in the
same PICTURE character-string is disallowed. The
result of special insertion editing is the appearance of
the insertion character in the item in the same position
as shown in the character-string.
6. Fixed Insertion Editing. The currency symbol and the
editing sign control symbols, + , - , ' C R 1 ,
' DB ' ,are the insertion characters. Only one currency
symbol and only one of the editing sign control
symbols can be used in a given P I C T U R E
character-string. The symbols CR ' or DB always
represent two character positions in determining the
size of the item and must represent the rightmost

character positions counted in the size of the item. The
symbol ' + ' or ' - ' when used, must be either the
leftmost or rightmost character position to be counted
in the size of the item. The currency symbol must be
the leftmost character position to be counted in the size
of the item except that it can be preceded by either a
' + ' or symbol. Fixed insertion editing results in
I-'
the insertion character occupying the same character

position in the edited item as in the P I C T U R E
character-string. Editing sign control symbols produce
the results shown in Table 6-2 depending upon the
value of the data item.
Table 6-2. Editing of Sign Control Symbols
Result
Editing Symbol in Data Item Data Item
PICTURE Character-String Positive or Zero Negative
+ -
space - e
2 spaces CR
2 spaces DB
7. Floating Insertion Editing. The currency symbol and

editing sign control symbols ' + ' or ' - ' are the
floating insertion characters and are mutually exclusive
in a given P ICTURE character-string.
Floating insertion editing is indicated in a P ICTURE
character-string by using a string of at least two of the
floating insertion characters. This string of floating
insertion characters may contain any of the fixed
insertion symbols or have fixed insertion characters
immediately to the right. These simple insertion
characters are part of the floating string. '9
The leftmost character of the floating insertion string
represents the leftmost limit of the floating symbol in
the data item. The rightmost character of the floating
string represents the rightmost limit of the floating

symbols in the data item.
The second floating character from the left represents
the leftmost limit of the numeric data that can be stored
in the data item. Nonzero numeric data may replace all
the characters at or to the right of this limit.
In a P I C T U R E character-string, there are only two

ways of representing floating insertion editing. One is
to represent any or all of the leading numeric character
positions on the left of the decimal point by the
insertion character. The other is to represent all of the
numeric character positions in the P I C T U R E
character-string by the insertion character.
If the insertion characters are only to the left of the
decimal point in the P I C T U R E character-string, the
result is that a single floating insertion character is
placed into the character position immediately
preceding either the decimal point or the first nonzero
digit in the data represented by the insertion symbol
string, whichever is farther to the left in the PICTURE
character-string. The character positions preceding the
insertion character are replaced with spaces.
If all numeric character positions in the P I C T U R E

character-string are represented by the insertion
character, the result depends upon the value of the
data. If the value is zero, the entire data item will
contain spaces. If the value is not zero, the result is
the same as when the insertion character is only to the
left of the decimal point.
To avoid truncation, the minimum size of the
P ICTURE character-string for the receiving data item
must be the number of characters in the sending data
item, plus the number of nonfloating insertion
characters being edited into the receiving data item,
plus one for the floating insertion character.
8. Zero Suppression Editing. The suppression of leading

z e m s in numeric character positions is indicated by
the use of the alphabetic character ' z ' or the character
' * ' (asterisk) as suppression symbols in a PICTURE
character-string. These symbols are mutually
exclusive in a given PICTURE character-string. Each
suppression symbol is counted in determining the size
of the item. If ' Z ' is used the replacement character is
the space, and if the asterisk is used the replacement
character will be ' * ' .
Zero suppression and replacement is indicated in a
PICTURE character-string by using a string of one or
more of the allowable symbols to represent leading
numeric character positions which are to be replaced
when the associated character position in the data
contains a zero. Any of the simple insertion characters
embedded in the string of symbols or to the immediate
right of this string are part of the string.
In a P IC T U R E character-string, there are only two
ways of representing zero suppression. One is to
represent any or all of the leading numeric character
positions to the left of the decimal point by
suppression symbols. The other is to represent all of
the numeric character positions in the P I C T U R E
character-string by suppression symbols.
If the suppression symbols appear only to the left of
the decimal point, any leading zero in the data which
corresponds to a symbol in the string is replaced by the
replacement character. Suppression terminates at the
first nonzero digit in the data represented by the
suppression symbol string or at the decimal point,
whichever is encountered first.
If all numeric character positions in the P I C T U R E

character-string are represented by suppression
symbols, and the value of the data is not zero, the
result is the same as if the suppression characters were
only to the left of the decimal point. If the value is
zero and the suppression symbol is ' z I , the entire
data item will be spaces. If the value is zero and the

suppression symbol ' * ' , the data item will be all
asterisks except for the actual decimal point.
9. The symbols ' + ' , - * ' z ' , and ' $ ' ,

when used as floating replacement characters, are
mutually exclusive within a given character-string.
10. Atleastoneofthesymbols ' A ' , X , '9'

or ' * ' , or at least two of the symbols ' + ' , ' - ' or
' cs ' must be present in a P ICTURE string.
Examples:
The following Table 6-3 demonstrates the editing function
of the PICTURE Clause. rn
Table 6-3. Editing Application of the PICTURE Clause
Source Area Receiving Area
Editing
Picture Data Picture Edited Data
USAGE
The USAGE clause specifies the format of a data item in the
computer storage.
General Format:
[USAGE IS1 INDEX
Syntax Rules:
1. An index data item can be referenced explicitly only in
a SET Statement or a relation condition.
2. The OCCURS, PICTURE, or VALUE clauses cannot be
used to describe group or elementary items described
with the USAGE I S I N D E X clause.
* General Rules:
1. An elementary item described with the USAGE I S
INDEX clause is called an index data item and contains
a value which must correspond to an occurrence
number of a table element.
The group item is considered to be a group data item
whose class is alphanumeric and may be referenced
any place in the syntax acceptable for such an item.
The size of the group item is considered to be in terms
of characters, six characters for each subordinate index
data item.
2. An index data item can be part of a group which is
referred to in an MOVE,or input-output statement, in
which case no conversion takes place.
VALUE
The VALUE clause defines the value of constants and the
initial value of working-storage items. e
General Format:
Format 1:
VAT,UE IS literal
Format 2:
VALUE IS W literal-2
Syntax Rules:
1. The VALUE clause cannot be stated for any item that
has the key word F I L L E R or one which has an
OCCURS clause or subordinate to an item which has an
OCCURS clause.
2. A signed numeric literal must have an associated

signed numeric PICTURE character-string.
3. All numeric literals in a VALUE clause of an item must

have a value which is within the range of values
indicated by the PICTURE clause, and must not have a
value which would require truncation of nonzero
digits. Nonnumeric literals in a VALUE clause of an
item must not exceed the size indicated by the
PICTURE clause.
4. Format 2 VALUE clauses must contain a PICTURE

clause with a character-string equal to one X. Literal-:!
must be an unsigned integer between 0 and 255.
General Rules:
1. The VALUE clause must not conflict with other clauses
in the data description of the item or in the data
description within the hierarchy of the item. The
following rules apply:
a. If the category of the item is numeric, the literal in
the VALUE clause must be numeric. If the literal
defines the value of a working-storage item, the
literal is aligned in the data item according to the
standard alignment rules. Refer to Standard
Alignment Rules in Section 2.
b. If the category of the item is alphabetic,
alphanumeric, alphanumeric edited or numeric
edited, all literals in the VALUE clause must be
nonnumeric literals. The literal is aligned in the
data item as if the data item had been described as
alphanumeric. (Refer to Standard Alignment
Rules in Section 2.) Editing characters in the
P I C T U R E clause are included in determining the
size of the data item (refer to the PICTURE clause
in this section) but have no effect on initialization
of the data item. Therefore, the VALUE for an
edited item is presented in an edited form.
2. Rules governing the use of the VALUE clause differ
with the respective sections of the DATA DIVISION:
a. In the FILE SECTION,the VALUE clause may

not be used.
b. In the WORKING-STORAGE SECTION the

VALUE clause is used to specify the initial value of
the data item, in which case the clause causes the
item to assume the specified value at the start of
the object program. If the VALUE clause is not
used in an item description, the initial value is
undefined.
3. The V ~ U clause
E is not allowed at the group level.
4. Format 2 is intended to provide a method of defining
special character codes which are required for display Flr
or printer commands and for testing certain keyboard
input characters such as function keys. Refer to your
Commodore User's Guide relating to CHRS codes.
For Example:
77 RETURN-CODE VALUE IS CHR 13 PIC X.
InthePROCEDURE DIVISIONwhenaDISPLAY
RETURN-CODE is executed the cursor will advance to
the next line and then position to column 1.
5. Format 2 is an extension to the ANSI COBOL-74
standard.
rllrr
WORKING-STORAGE SECTION
The WORKING-STORAGE SECTION is optional a d i s
that part of the D A T A D IV I S I ON set aside for
intermediate processing of data. The difference between
the WORKING-STORAGE a d FILE SECTIONS is that
the former deals with data that is not associated with an
input or output file. All clauses which are used in normal
input or output record descriptions can be used in a
WORKING-STORAGE record description.
WORKING-STORAGE STRUCTURE
Whereas the FILE SECT ION is composed of file
description (FD) entries and associated record description
entries, the WORKING-STORAGE SECT ION is composed -%
only of record description entries and noncontiguous
items. The WORKING-STORAGE SECT ION begins with
the section-header and a period, followed by data
description entries for noncontiguous W O R K I N G -

S T O R A G E items, and/or record description entries for
WORKING- STORAGE records.
Each WORKING-STORAGE SECTION record name and

noncontiguous item name must be unique.
General Example:
77 data-name-1
77 data-name-n
01 data-name-2
0 2 data-name-3
NONCONTIGUOUS WORKING-STORAGE
Items in WORKING-STORAGE which have no hierarchical
relationship to one another need not be grouped into
records, provided they do not need to be further
subdivided. These items are classified and defined as
noncontiguous elementary items. Each of these items is
defined in a separate data description entry which begins
with the special level-number 77.
The following record description clauses are required in
each entry:
Level-number 77
Data-name
The P ICTURE clause or the USAGE IS INDEX clause.
The OCCURS clause is not meaningful on a 77 level item

and will cause an error. Other data description clauses are
optional and can be used to complete the description of the
item if necessary.
WORKING-STORAGE RECORDS
Data elements and constants in WORKING-STORAGE
which have a definite hierarchic relationship to one another
must be grouped into records according to the rules for the
formation of record descriptions. All clauses which are
used in normal input or output record descriptions can be
used in a WORKING-STORAGE description.
INITIAL VALUES
The initial value of any item in the WORKING-STORAGE
SECTION except an index data item is specified by using
the VALUE clause with the data item. The initial value of
any index data item is unpmhctable.
CODING THE WORKING-STORAGE SECTION

Figure 6-5 illustrates the coding of the
WORKING-STORAGE SECTION
01 HDG-LINE.
0 3 FILLER PIC X(52).
0 3 DN2 PIC A(17) VALUE "SALES PERFORMANCE".
77 DISK-CONTROL PICTURE 9(8).

77 TOTAL-SALES PIC 9(11) VALUE 0.
77 SALES-QUOTA PIC 9(10).
01 STATE-TABLE.
05 STATE-KEY OCCURS 50.

10 STATE-CODE PIC 99.
10 COUNTY PIC 9.
10 CITY PIC 9.
- -
SECTION 7 PROCEDURE DIVISION
m GENERAL
The PROCEDURE DIVISION must be included in every
COBOL 64 source program. This division must contain at
least 1 paragraph.
A paragraph consists of a paragraph-name, followed by a
period and a space, followed by zero, one, or more
successive sentences. A paragraph ends immediately
before the next paragraph-name or at the end of the
PROCEDURE DIVISION.
A sentence consists of one or more statements and is

terminated by a period
A statement is a syntactically valid combination of words
and symbols beginning with a COBOL 64 verb.
The term 'identifier' is defined as the word or words
necessary to make unique reference to a data item.
EXECUTION OF THE PROCEDURE DIVISION

Execution begins with the first statement of the
PROCEDURE DIVISION. Statements are executed in the
order of appearance, except where the user indicates GO
TO or PERFORM statements.
PROCEDURE DIVISION STRUCTURE

The P R O C E D U R E DIVISION is made up of the
PROCEDURE DIVISION header and the PROCEDURE
D IVI S ION body. Descriptions of these follow:
PROCEDURE DIVISION HEADER

The PRECEDURE DIVISION is identified by and must
begin with the following header: m
PROCEDURE DIVISION BODY

The body of the PROCEDURE DIVISION must conform
to the following format.
{paragraph-name. [sentence] . . . I ...
STATEMENTS
There are two types of statements; conditional statements
and imperative statements.
e
CONDITIONAL STATEMENTS
A conditional statement specifies that the truth value of a
condition is to be determined and that the subsequent action
of the object program is dependent on this truth value.
A conditional statement is
1. An IF statement.
2. A R E A D statement that specifies the AT E N D or

I N V A L I D KEY phrase.
3. A WRITE statement that specifies the I N V A L I D KEY

phrase.
m
4. An arithmetic statement (ADD, DIVIDE, MULTIPLY,
SUBTRACT) that specifies the SIZE ERROR phrase.
5. A F ILTER-NUMERIC statement.
IMPERATIVE STATEMENTS
An imperative statement indicates a specific unconditional
action to be taken by the object program. An imperative
statement is any statement that is not a conditional
statement. An imperative statement may consist of a
sequence of imperative statements, each possibly separated
from the next by a separator. The imperative verbs are:
ACCEPT
ACCEPT-1-KEY
ADD (1)
CLOSE
DEBUG-BREAK
DEBUG-TRACE-OFF
DEBUG-TRACE-ON
DISPLAY
DIVIDE (1)
EXIT
GO
MOVE
MULTIPLY (1)
OPEN
PERFORM
READ (2)
SET
STOP
SUBTRACT (1)
WRITE (3)
The numbers in parentheses following some of the verbs

have the following meaning:
Number Meaning
1 Without the optional S IZE ERROR
phrase.
2 Without the optional AT END phrase or
INVALID KEY phrase.
3 Without the optional INVALID KEY
phrase.
When 'imperative-statement' appears in the general format

of statements, it refers to a statement that begins with an
imperative verb and specifies an unconditional action to be
taken. An imperative statement may consist of a sequence rrna
of imperative statements. Imperative statements must be
ended by a period, or an ELSE phrase associated with a
previous IF statement.
RELATION CONDITION
A relation condition causes a comparison of two operands,
each of which may be the data item referenced by an
identifier or a literal. A relation condition has a truth value
of TRUE if the relation exists between the operands. If
either of the operands is a group item, the nonnumeric
comparison rules apply.
General Format:
[=I GREATER
[=I LESS THAN
[=I EOUAI, TO
The first operand (identifier-1 or literal-1) is the subject of

the condition; the second operand (identifier-2 or literal-2)
is the object of the condition. The relation condition must
contain at least one reference to a variable.
When used, NOT and the next key word are one relational
operator that defines the comparison to be executed for
truth value; for example, NOT EQUAL is a truth test for an
unequal comparison; NOT GREATER is a truth test for an
equal or less comparison. The meaning of the relational
operators is as follows:
Relational Operator Meaning

IS [ N O T I GREATER THAN Greater than or not greater than
IS [ N O T I LESS THAN Less than or not less than
I S [ N O T ] EQUAL T O Equal to or not equal to
COMPARISON OF NUMERIC OPERANDS

For operands whose class is numeric, a comparison is
made with respect to the algebraic value of the operands.
The length of the literal in terms of number of digits
represented, is not significant. Zero is considered a unique
value regardless of the sign.
Unsigned numeric operands are considered positive for
purposes of comparison.
e
COMPARISON OF NONNUMERIC OPERANDS
For nonnumeric operands, or one numeric and one
nonnumeric operand, a comparison is made with respect to
a specified collating sequence of characters. Refer to your
Commodore User's Guide C HR $ codes for additional
information. If one of the operands is specified as
numeric, it must be an integer data item or an integer literal.
The following conditions apply:
1. If the nonnumeric operand is an elementary data item
or a nonnumeric literal, the numeric operand is treated
as though it were moved to an elementary
alphanumeric data item of the same size as the numeric
data item (in terms of standard data format characters),
and the contents of this alphanumeric data item are
compared to the nonnumeric operand. Refer to the
MOVE statement in this section.
2. If the nonnumeric operand is a group item, the numeric

operand is treated as though it were moved to a group
item of the same size as the numeric data item (in terms
of standard data format characters), and the contents of
this group item are compared to the nonnumeric
operand. Refer to the MOVE for additional information.
3. A noninteger numeric operand cannot be compared to a
nonnumeric operand.
4. The operands must be the same size.
Comparison effectively proceeds by comparing characters

in corresponding character positions starting from the high
order end and continuing until either a pair of unequal
characters is encountered or the low order end of the
operand is reached, whichever comes first. The operands
are determined to be equal if all pairs of characters compare
equally through the last pair, when the low order end is
reached.
The first encountered pair of unequal characters is
compared to determine a relative position in the collating n
sequence. The operand that contains the character that is
positioned higher in the collating sequence is considered to
be the greater operand
COMPARISONS INVOLVING INDEX-NAMES

AND/OR INDEX DATA ITEMS
Relation tests may be ma& between:
1. Two index-names. The result is the same as if the
corresponding occurrence numbers were compared.
2. An index-name and a data item (other than an index
data item) or literal. The occurrence number that
corresponds to the value of the index-name is
compared to the data item or literal.
e
3. An index data item and an index-name or another index
data item. The actual values are compared without
conversion.
The comparison of an index data item with a literal or with

any data item not specified above, is not allowed.
CLASS CONDITION
The class condition determines whether the operand is
numeric, consisting entirely of the characters '0 , 1 ' ,
2 , 3 , . . . , ' 9 ' , with or without the
operational sign, or alphabetic, consisting entirely of the
characters 'A', B , C .
. . ' Z ' , andspace.
General Format:
identifier IS INQXI 1J-

When used, NOT and the next key word specify one class
condition that defines the class test to be executed for truth
value; for example, NOT NUMERIC is a truth test for
determining that an operand is nonnumeric.
The NUMERIC test cannot be used with an item whose data

description describes the item as alphabetic or as a group
item composed of elementary items whose data description
indicates the presence of operational sign(s). If the data
description of the item being tested does not indicate the
presence of an operational sign, the item being tested is
determined to be numeric only if the contents are numeric
and an operations1 sign is not present. If the data
description of the item does indicate the presence of an
operational sign, the item being tested is determined to be
numeric only if the contents are numeric and a valid
operational sign is present.
The ALPHABETIC test cannot be used with an item whose

data description describes the item as numeric. The item
being tested is determined to be alphabetic only if the
contents consist of any combination of the alphabetic
characters ' A ' through ' z ' and the space character.
COMMON PHRASES
In the statement descriptions that follow, several phrases
appear frequently: the ROUNDED phrase and the SIZE .r.br
ERROR phrase.
In the following discussion, a resultant-identifier is that

identifier associated with a result of an arithmetic
operation.
ROUNDED PHRASE
If, after decimal point alignment, the number of places in
the fraction of the result of an arithmetic operation is
greater than the number of places provided for the fraction
of the resultant-identifier, truncation is relative to the size
provided for the resultant-identifier. When rounding is
requested, the absolute value of the resultant-identifier is
increased by adding a one into the low-order digit
whenever the absolute value of the next least significant
digit of the intermediate data item is greater than or equal to
five.
SIZE ERROR PHRASE

If, after decimal point alignment, the absolute value of a
result exceeds the largest value that can be contained in the
associated resultant-identifier, a size error condition exists.
Division by zero always causes a size error condition. The
size error condition applies only to the final results of an
arithmetic operation and does not apply to intermediate
results, except in the MULTIPLY and D I V I D E statements,
in which case the size error condition applies to the
intermediate results as well. If the ROUNDED phrase is
specified, rounding takes place before checking for size
error. When a size error condition occurs, the subsequent
action depends on whether or not the SIZE ERROR n
phrase is specified.
1. If the SIZE ERROR phrase is not specified and a size

error condition occurs, the resultant value is stored in
each of the receiving fields left truncated where
required. Values of resultant-identifier(s) for which no
size error condition occurs are unaffected by size
errors that occur for other resultant-identifier(s) during
execution of this operation.
2. V the SIZE ERROR phrase is specified and a size error

condition occurs, then the values of
resultant-identifier(s) affected by the size errors are not
altered. Values of resultant-identifier(s) size error
condition occurs are unaffected by size errors that
occur for other resultant-identifier(s)during execution
of this operation. After completion of the execution of
this operation, the imperative statement in the s I Z E
ERROR phrase is executed.
STATEMENT FORMATS
m
GENERAL RULES FOR STATEMENT FORMATS
The following paragraphs describe general rules for
statement formats.
ARITHMETIC STATEMENTS
The arithmetic statements are ADD, DIVIDE, MULTIPLY,
and SUBTRACT and have several common features:
1. The data descriptions of the operands need not be the
same; any necessary conversion and decimal point
alignment is supplied throughout the calculation.
2. The maximum size of each operand is 18 decimal
digits.
3. Each arithmetic operation is evaluated using an

intermediate data item for the result of the operation.
The contents of the intermediate data item are moved to

the resultant-identifier according to the rules for the
MOVE statement. Rounding is performed and the size
error conditon is determined only during this MOVE
operation.
INCOMPATIBLE DATA
-
Except for the class condition (refer to Class Condition in
this section), when the contents of a data item are
referenced in the PROCEDURE DIVISION and the
contents of that data item are not compatible with the class
specified for that data item by the PICTURE clause, then
the result of such a reference is undefined.
SPECIFIC VERB FORMATS

The specific verb formats, together with a detailed
discussion of the restrictions and limitations associated
with each, appear on the following pages in alphabetic lrg,
sequence.
ACCEPT
The A C C E P T statement is used to input data from the
keyboard and placed in the specified data item.
General Format:
ACCEPT identifier
Syntax Rules:
1. If the identifier describes a numeric item it must be an
integer.
General Rules:
1. The A C C E P T statement causes the transfer of data
from the keyboard. This data replaces the contents of
the data item named by the identifier.
2. The maximum number of characters that can be
transferred is 80. The R E T U R N key terminates the
transfer.
3. The A C C E P T statement causes the information

requested to be transferred to the data item specified by
identifier according to the rules of the MOVE statement.
4. As each key is entered it is displayed on the screen at
the current cursor position. The cursor control and
insert/delete keys are active.
The ACCEPT- 1- K E Y statement is used to input 1

character from the keyboard and place it in the specified
data item. This verb is an extension to ANSI COBOL-74. -4
General Format:
- -
ACCEPT identifier
This statement differs from the ACCEPT statement in that it

will enable any one key on the keyboard including function
keys. Refer to your Commodore User's Guide under
CHRScodes for each key's definition. The key entered is
not displayed.
ADD
The ADD statement causes two or more numeric operands
to be summed and the result to be stored.
General Format:
Format 1:
] ]
identifier-1 identifier-2
{liter al-1 Literal-2 ' '
lQ identifier-m [ROUNDED]
[ON SLZE ERROR imperative-statement]
Format 2:
GlVING identifier-m I - [
[ON SLZF, ERROR imperative-statement]
Syntax Rules:
1. In formats 1 and 2, each identifier must refer to an
elementary numeric item, except that in Format 2 the
identifier following the word G I V I N G must refer to
either an elementary numeric item or an elementary
numeric edited item.
2. Each literal must be a numeric literal.
General Rules:
1. Additional rules and explanation relative to this
statement are given in the appropriate paragraphs.
Refer to ROUNDED Phrase, S I Z E ERROR Phrase,
Arithmetic Statements.
2. If Format 1 is used, the values of the operands
preceding the word T O are added together, then the
sum is added to the current value of identifier-n storing
the result immediately into identifier-n.
3. If Format 2 is used, the values of the operands
preceding the word GIVING are added together, then
the sum is stored as the new value of identifier-m, the
resultant-identifier.
4. The system ensures that enough places are carried so
that significant digits are not lost during execution.
Examples: ng
Assume as initial values for each ADD : X = 2 , Y=10,

Z=15, TOT=50.
Format 1:
ADD X TO T O T . Results TOT= 52
ADD X Y Z TO TOT Results TOT=7 7
Format 2:
ADD X
ADD X
Y GIVING TOT.
Y Z G I V I N G TOT
Results TOT= 1 2
Results TOT=2 7
-
CLOSE
General Format:
n
CJIOSF, file-name
The CLOSE statement terminates the processing of a file.

General Rules:
A CLOSE statement may only be executed for a file in an
open mode. Refer to 1-0 status under the File Concepts
section.
It is very important that you CLOSE files once you have
finished using them. Closing a disk file causes the system
to properly allocate space and update the directory. If you
do not CLOSE the disk file, all of your data will be lost.
DEBUG-BREAK
This verb will cause an execution break if the program is
executing in the DEBUG Mode. Refer to the DEBUG Mode
sections. The verb is ignored if not executing in the
D E B U G Mode. This verb is an extension to the ANSI
standard.
DEBUG-TRACE-OFF
When executing in the DEBUG Mode this verb will turn off
the trace feature. Refer to the DEBUG section. This verb is
ignored if executing in the DEBUG Mode. This verb is an
extension to the ANSI standard.
-
DEBUG-TRACE-ON
This verb will cause the trace feature to be turned on if
executing in the DEBUG Mode. Refer to the DEBUG Mode
section. The verb is ignored if not executing in the DEBUG
Mode. This verb is an extension to the ANSI standard.
DISPLAY
The D I SPLAY statement causes the data items to be
displayed on the screen.
General Format:
Syntax Rules:
e
If the literal is numeric, then it must be an unsigned
integer.
General Rules:
1. The DISPLAY statement causes the contents of each
operand to be transferred to the hardware device in the
order listed.
2. The maximum number of characters that can be

transmitted is unlimited.
3. When a DISPLAY statement contains more than one

operand, the values of the operands are transferred in
the sequence in which the operands are encountered.
4. For any one data item, if a character code 13 .(a4

( R ET U R N ) is encountered the transfer will be
terminated after sending the RETURN code.
5. It is not recommended to DISPLAY an identifier which

is defined as signed numeric. This is due to the fact
that the sign character is combined with the most
n significant number of the data item.
6. The display begins at the current cursor location.
DIVIDE
The DIVIDE statement divides one numeric data item into
others and sets the values of data items equal to the
quotient.
General Formats:
Format 1:
[ON ERROR imperative-statement]
Format 2:
[ON SLZE ERROR imperative-statement]

Syntax Rules:
1. Each identifier must refer to an elementary numeric

item, except that the identifier associated with the
G I V I N G phrase must refer to either an elementary
numeric item or an elementary numeric edited item.
-
General Rules:
1. Additional rules and explanations relative to this
Refer to Arithmetic Statements, ROUNDED phrase and
the S I ZE ERROR phrase.
2. When Format 1 is used, the value of identifier-2 is
divided by either the value of identifier- 1 or literal- 1.
The value of the dividend (identifier-2) is replaced by
this quotient.
3. When Format 2 is used, the value of identifier-1 or
literal-1 is divided by the value of identifier-2 or
literal-2, and the result is stored in identifier-3.
EXIT
The EXIT statement provides a means of documenting the

logical end point for a series of paragraphs that may be
executed under the control of a PERFORM statement.
General Format:
EXIT.
Syntax Rules:
1. The EXIT statement must appear in a sentence alone.
2. The EXIT sentence must be the only sentence in the
paragraph.
General Rules: )
1. An EXIT statement serves only to enable the user to

assign a procedure-name to a given point in a program.
Such an EXIT statement has no other effect on the
execution of the program.
FILTER-NUMERIC
The F ILTER-NUMERIC statement filters and validates
alphanumeric data to numeric data format. This verb is an
extension to ANSI COBOL-74.
General Format:
ON ERROR imperative-statement
Syntax Rules:
1. Identifier-1 represents the sending area and identifier-2
represents the receiving area.
2. Identifier-2 must be defined as a numeric data item.

General Rules:
1. The contents of identifier-1 are examined. Valid n
characters are 0 through 9 and the decimal-point.
Leading and trailing space characters are also valid.
Only one decimal point character is allowed and only if
there is one or more decimal places in the receiving
fields picture. A decimal point without other
characters is invalid.
2. If the above tests are passed the size of significant data
is evaluated against the size of identifier-2. If there is
no size problem, including decimal alignment, the data
is transferred to identifier-2.
3. If any of the above tests fail the ON ERROR imperative

statement is processed.
4. The DECIMAL P O I N T I S COMMA clause apples to

this statement. e
This verb is intended to process data received from the
keyboard (ACCEPT)or other systems.
Examples: The receiving numeric PICTURE is 999V99.
Sending
Data Result
123.45 12345
1 00100
-
(all spaces) 00000
.12 00012
1 2 ERROR-embedded space
1234.5 ERROR-size
1.2345 ERROR - size
1.2.3 ERROR - more than 1 decimal point
1A2 ERROR-invalid character
ERROR-decimal point only
The GO TO statement causes control to be transferred from

one part of the PROCEDURE DMSION to another.
General Format:
Format 1:
Format 2:
GQ TO paragraph-name-1 [paragraph-name-21 ... paragraph-name-n
DEPENDING ON identifier
Syntax Rules:
1. Identifier is the name of a numeric elementary item
described without any positions to the right of the
assumed decimal point.
2. If a GO TO statement, represented by Format 1,

appears in a consecutive sequence of imperative
statements within a sentence, it must appear as the last
statement in that sequence.
General Rules:
1. When a GO TO statement, represented by Format 1 is
executed, control is transferred to paragraph-name-1.
2. When a Format 2 GO TO statement is executed,

control is transferred to the paragraph-name whose
ordinal position in the list following the GO TO
corresponds to the value of the identifier being 1, 2,
. . . , n. If the value of the identifier is anything other
than the positive or unsigned integers 1, 2, . . . ,
n, then no transfer occurs and control passes to the
next statement in the normal sequence for execution.
The IF statement causes a condition to be evaluated. The

subsequent action of the object program depends on
whether the value of the condition is TRUE or FALSE.
General Format:
Syntax Rules:
1. Statement- 1 and statement-2 must represent an
imperative statement.
2. The ELSE NEXT SENTENCE phrase may be omitted
if it immediately precedes the terminal period of the
sentence.
e
General Rules:
1. When an I F statement is executed, the following
transfers of control occur:
a. If the condition is TRUE, statement-1 is executed,

if specified. If statement-1 contains a procedure
branching statement, control is explicitly
transferred in accordance with the rules of that
statement. Refer to Categories of Statements in
this section. If statement-1 does not contain a
procedure branching statement, the ELSE phrase,
if specified, is ignored and control passes to the
next executable sentence.
b. If the condition is T R U E and the N E X T

SENTENCE phrase is specified instead of e,
statement-1, the ELSE phrase, if specified, is
ignored and control passes to the next executable
sentence.
c. If the condition is FALSE, statement-1 or NEXT

S E N T E N C E is ignored, and statement-2 if
specified, is executed. If statement-2 contains a
procedure branching statement, control is
explicitly transferred in accordance with the rules
of that statement. Refer to Categories of
Statements in this section. If statement-2 does not
contain a procedure branching statement, control
passes to the next executable sentence. If the
E L s E statement-2 phrase is not specified,
statement- 1 is ignored and control passes to the
d. If the condition is FALSE, and the ELSE NEXT
SENTENCE phrase is specified, statement- 1 is
ignored, if specified, and control passes to the
Examples:
A I F APPLE I S EQUAL TO RED

DISPLAY "GOOD"
PERFORM GOOD-APPLE
ELSE PERFORM BAD-APPLE.
I F APPLE EQUAL RED

NEXT SENTENCE
ELSE DISPLAY "BAD"
ADD 1 TO TOT-BAD-APPLES.
I F APPLE NOT EQUAL RED

ADD 1 TO TOT-BAD-APPLES.
MOVE
The MOVE statement transfers data, in accordance with the
rules of editing, to one or more data areas. -4
General Format:
-{
Syntax Rules:
identifier-
literal ) T
.
Q identifier-2 [identifier-31 ...
1. Identifier-1 and literal represent the sending area;

identifier-2, identifier-3,..., represent the receiving
area.
2. An index data item cannot appear as an operand of a
MOVE statement. Refer to the USAGE clause in Section
6.
General Rules:
1. The data designated by the literal or identifier-1 is
moved first to identifier-2, then to identifier-3, and so
on. The rules governing identifier-2 also apply to the
other receiving areas. Any subscripting or indexing
associated with identifier-2 is evaluated immediately
before the data is moved to the respective data item.
Any subscripting or indexing associated with
identifier-1 is evaluated only once, immediately before
data is moved to the first of the receiving operands.
The result of the statement:
is equivalent to:
MOVE a ( b ) TO t e m p
MOVE t e m p T O b
MOVE t e m p T O c ( b )
Temp is an intermediate result item provided by the

system.
2. Any MOVE in which the sending and receiving items

are both elementary items is an elementary move.
Every elementary item belongs to one of the following
categories: numeric, alphabetic, alphanumeric,
numeric edited, alphanumeric edited. These categories
are described in the PICTURE clause in Section 6.
Numeric literals belong to the category numeric, and
nonnumeric literals belong to the category
alphanumeric.
The following rules apply to an elementary move
between the categories:
a. A numeric edited, alphanumeric edited, or
alphabetic data item must not be moved to a
numeric or numeric edited data item.
b. A numeric literal, a numeric data item or a numeric
edited data item must not be moved to an
alphabetic data item.
c. A noninteger numeric literal or a noninteger
numeric data item must not be moved to an
alphanumeric or alphanumeric edited data item.
d. All other elementary moves are legal and are
performed accordingto the rules in General
Rule 3.
3. Any necessary conversion of data from one form of
internal representation to another takes place during
legal elementary moves, along with any editing
specified for the receiving data item:
a. When an alphanumeric edited or alphanumeric
item is a receiving item, alignment and any
necessary space filling takes place as defined
under Standard Alignment Rules in Section 2. If
the size of the sending item is greater than the size
of the receiving item, the excess characters are
truncated on the right after the receiving item is

filled. If the sending item is described as being
signed numeric, the operational sign is not moved. -
,
b. When a numeric or numeric edited item is the

receiving item, alignment by decimal point and any
necessary zero-filling takes place as defined under
the Standard Alignment Rules, except where
zeroes are replaced because of editing
requirements.
1) When a signed numeric item is the receiving

item, the sign of the sending item is placed in
the receiving item. If the sending item is
unsigned, a positive sign is generated for the
receiving item.
2) When an unsigned numeric item is the
receiving item, the absolute value of the
sending item is moved and no operational sign
is generated for the receiving item. m
3) When a data item described as alphanumeric is
the sending item, data is moved as if the
sending item were described as an unsigned
numeric integer.
c. When a receiving field is described as alphabetic,
justification and any necessary space-filling takes
place as defined under the Standard Alignment
Rules. If the size of the sending item is greater
than the size of the receiving item, the excess
characters are truncated on the right after the
receiving item is filled
Any move that is not an elementary move is treated
exactly as if it were an alphanumeric to alphanumeric
elementary move, except that there is no conversion of
data from one form of internal representation to
another. In such a move, the receiving area is filled
without consideration for the individual elementary or
group items contained within either the sending or
receiving area.
6. The validity of the various types of MOVE statements is

summarized in Table 7-4.
Table 7-4. A Valid MOVE Statement
C a t e g o r y of R e c e i v i n g D a t a I t e m
Category of Alphanumeric Numeric Integer

Sending Alphabetic Edited Numeric Noninteger
Data Item Numeric Edited
Alphanumeric
ALPHABETIC YES YES NO

ALPHANUMERIC YES YES YES
ALPHANUMERIC E D I T E D YES YES NO
NUMERIC I N T E G E R NO YES YES
NUMERIC NONINTEGER NO NO YES
NUMERIC E D I T E D NO YES NO
MULTIPLY
The M U L T I P L Y statement causes numeric data items to be
multiplied and sets the value of a data item equal to the ,
-
result.
General Format:
Format 1:
BX identif ier-2 [ROUNDED]
literal-1
[ON SlZE ERROR imperative-statement]
Format 2:
[ON ERROR imperative-statement I
Syntax Rules:
1. Each identifier must refer to a numeric elementary
item, except that in Format 2 the identifier following
the word G I V I N G must refer to either an elementary
numeric item or an elementary numeric edited item.
3. The composite of operands, determined by
superimposing all receiving data items of a given
statement, aligned on decimal points, must not exceed
18 digits. rn
General Rules:
b.r 1. Refer to ROUNDED Phrase, S I Z E ERROR Phrase in

Arithmetic Statements in this section for additional
rules and information.
literal-1 is multiplied by the value of identifier-2. The
value of the multiplier (identifier-2) is replaced by this
product.
literal-1 is multiplied by identifier-2 or literal-2 and the
result is stored in identifier-3.
OPEN
The OPEN statement initiates the processing of files. It
also performs checking of labels and other operations.
n
General Format:
Syntax Rules:
1. The 1 - 0 phrase can be used only for disk files. The
disk file must be defined with ORGAN I ZAT I O N I S
R E L A T I V E and ACCESS MODE I S RANDOM
clauses.
2. OPEN INPUT file-name must not be a printer file.

General Rules:
1. The successful execution of an OPEN statement
determines the availability of the file and results in the
file being in an open mode.
2. The execution of an OPEN statement does not affect

either the contents or availability of the file's record
area.
3. When a given file is not in an open mode, no statement
that references that file can be executed successfully.
4. A file may be opened with the INPUT, OUTPUT and

1 - 0 phrases in the same program. Following the initial
execution of an O P E N statement for a file, each
subsequent OPEN statement execution for that same
file must be preceded by the execution of a C L O S E
statement for that file.
Rb
5. Execution of the OPEN statement does not obtain or
release the first data record.
6. The beginning labels are processed as follows:
a. When the I N P U T phrase is specified, the

execution of the OPEN statement causes the labels
to be checked in accordance with conventions for
input label checking.
b. When the OUTPUT phrase is specified, the
-
execution of the OPEN statement causes the labels
to be written in accordance with conventions for
output label writing.
7. The file description entry for the file-name must be
equivalent to that used when this file was created.
8. For files being opened with the INPUT phrase, the

OPEN statement sets the current record pointer to the
first record currently existing within the file.
9. Upon successful execution of an OPEN statement with

the OUTPUT phrase specified, a file is created. At that
time the associated file contains no data records.
PERFORM
The PERFORM statement is used to transfer control
explicitly to one or more paragraphs and to return control
implicitly whenever execution of the specified paragraph is
complete
General Format:
Syntax Rules:
A- 1. The words THRU and THROUGH are equivalent.

General Rules:
1. When the PERFORM statement is executed, control is
transferred to the first statement of the paragraph
named paragraph-name- 1. This transfer of control
occurs only once for each execution of a PERFORM
statement. An implicit transfer of control to the next
executable statement following the P E R F O R M
statement is established as follows:
a. IIf paragraph-name-2 is not specified, then the
return i s after the last statement of
paragraph-name- 1.
b. If paragraph-name-2 is specified, then the return is
after the last statement of the paragraph-name-2.
2. No particular sequential relationship is required to exist
between paragraph-name-1 and paragraph-name-2.
There may be more than one logical path of program
control through the performed range of paragraphs. A

common method, though not a required one, of
documenting the terminal paragraph of a performed
range of paragraphs is through the use of the EXIT
statement.
3. An implicit return mechanism is established at the end
of a performed range of paragraphs and is activated by
the execution of a PERFORM statement. Program
control reaching an active return mechanism always
returns to the activating PERFORM statement. A return
mechanism permanently deactivates by transferring
program control back to a PERFORM statement. An
active return mechanism is temporarily deactivated by
the execution of a PERFORM statement. Program
control always passes through a nonactive return
mechanism to the next executable statement following
the PERFORM range.
4. A paragraph executed under the control of a PERFORM
statement may execute PERFORM statements. There is
no requirement that the range of paragraphs executed
under the control of the nested PERFORM statement be
declared totally within, or disjoint from, the range of
paragraphs executed by the first PERFORM statement.
The permanent deactivation of an active return
mechanism causes the last return mechanism
temporarily deactivated to again become active,
allowing overlapping PERFORM ranges, or two or
more PERFORM ranges that have a common exit point,
to logically execute the same as disjoint PERFORM
ranges.
Transferring program control, by means of a GO To

statement, from a range of paragraphs being executed
under control of a PERFORM statement does not cause the
return mechanism to be deactivated. This is allowed but
this is not considered good programming practice and -b
should be avoided! Subsequently, transferring program
control back into the PERFORM range causes control to
return to the PERFORM statement, provided that the return
mechanism is still active. Repeatedly branching from a

PERFORM range without allowing control to ever reach an
active return mechanism may cause the program to
terminate abnormally by exhausting the resources allocated
to account for return mechanisms. In such a case, the error
message PERFORM STACK ERROR is displayed
Example:
START. PERFORM PARA
PERFORM PARA THRU PARC.
ENDIT. STOP RUN.
PARA . ADD.. ..
PARB . MOVE. . . .
PARC . PERFORM PARB
The execution sequence would be:
START
PARA
PARA
PARB
PARC
PARB
ENDIT
READ
For sequential access, the READ statement makes available
the next logical record from a file. For random access, the e
READ statement makes available a specified record.
General Format:
Format 1:
READ file-name RECORD
AT ENQ imperative-statement
Format 2:
READ file-name RECORD
INVALID KEY imperat ive-statement
Syntax Rules:
1. Format 1must be used for all files in sequential access
mode.
2. Format 2 is used for files in random access mode.
General Rules:
1. The associated file must be open in the I N P U T or 1-0
mode. Refer to the OPEN statement in this section.
2. The execution of the READ statement causes the value

of the F I L E STATUS data item, if any, associated
with file-name to be updated. Refer to 1-0 Status in
Section 5. e
3. If, at the time of the execution of a Format 1 READ
statement, no next logical record exists in the file, the
AT END condition occurs, and the execution of the
READ statement is considered unsuccessful. Refer to

1-0 Status in Section 5.
4. When the AT END condition is recognized, the

following actions are taken in the specified order:
a. A value is placed into the F I LE STATUS data

item, if specified for this file, to indicate an AT
E N D condition. Refer to 1-0 Status in Section 5.
b. Control is transferred to the AT END imperative

statement.
c. The execution of the input-output statement which
caused the condition is unsuccessful.
5. Following the unsuccessful execution of any READ
statement, the contents of the associated record area
and the position of the current record pointer are
undefined.
6. When the AT END condition has been recognized, a -

Format 1 READ statement for that file must not be
executed without first executing a successful CLOSE
statement followed by the execution of a successful
OPEN statement for that file.
7. In a Relative File with access mode sequential

declared, if the RELATIVE KEY phrase is specified,
the execution of a Format 1READ statement updates the
contents of the RELATIVE KEY data item so that it
contains the relative record number of the record made
available.
8. For a Relative File with access mode random declared,
the execution of a Format 2 READ statement sets the
current record pointer and makes available the record
whose relative record number is contained in the data
item named in the RELATIVE KEY phrase for the file.
If the file does not contain such a record, the
I N V A L I D KEY condition exists and execution of the
R E A D statement is unsuccessful. Refer to the

I N V A L I D KEY condition under Invalid Key in
Section 5. -4
SET
The SET statement establishes reference points for table
handling operations by setting index-names associated with
table elements.
General Format:
identi f i e r - 3
Syntax Rules:
1. Integer-1 may be signed but must be plus.
General Rules:
1. Index-names are considered related to a given table and
are defined by being specified in the I N D E X E D BY
clause.
2. If index-name-3 is specified, the value of the index
before the execution of the SET statement should
correspond to an occurrence number of an element in
the associated table.
If index-name-1 is specified, the value of the index
after the execution of the S E T statement should
correspond to an occurrence number of an element in
the associated table. e
When a statement using the index-name to refer to a
table element is executed, the value in the index or the
value produced by relative indexing must fall within
the range specified by the OCCURS clause defining the

table. Otherwise, an abnormal termination of the
program occurs. Refer to Indexing in Section 2.
3. When a SET statement is executed, the following

actions occur:
a. Index-name-1 is set to a value causing it to refer to
the table element that corresponds in occurrence
number to the table element referenced by
index-name-3, identifier-3, or integer-1. If
identifier-3 is an index data item, or if
index-name-3 is related to the same table as
index-name-1, no conversion takes place.
b. If identifier-1 is an index data item, it may be set
equal to either the contents of index-name-3 or
identifier-3, where identifier-3 is also an index
data item. No conversion takes place in either
case.
c. If identifier-1 is not an index data item, it may be
set only to an occurrence number that corresponds
to the value of index-name-3. Neither identifier-3
nor integer-1 can be used in this case.
4. Data in Table 7-6 represents the validity of various
operand combinations in the SET statement. The
general rule reference (for example, 3b) indicates the
applicable general rule.
Table 7-6. SET Statement Combinations

Sending Item Receiving Item
Integer Data Item Index-Name Index Data Item 4-
Integer Literal NoBc ValidBa NoBb

Integer Data Item N013c Validna NoBb
Index-Name Valid/3c Valid/3a Valid/3b*
Index Data Item No13c Valid/3a* Valid/3b*
* No conversion takes place *
STOP
The STOP statement causes a permanent suspension of the
execution of the object program.
General Format:
Syntax Rules:
1. If a STOP RUN statement appears in a consecutive
sequence of imperative statements within a sentence, it
-
must appear as the last statement in that sequence.
General Rules:
1. The ending procedure established by the COBOL 64
system is instituted.
SUBTRACT
The SUBTRACT statement is used to subtract one or the
sum of two or more numeric data items from one item and
set the value of one item equal to the result.
General Format:
Format 1:
...
{ } ]
SUBTRACT identifier-1 identifier-. identifier-m
literal-1 [literal-2
[ROUNDED]
[ON ERROR imperative-statement ]
Format 2:
rn SUBTRACT
{
identifier-1
GrVING identifier-n
t }
identifier-2
[ i t ]
. . .- identifier-m
Literal-m 1
[ON ERROR imperative-statement]
Syntax Rules:
1. Each identifier must refer to a numeric elementary item
except that in Format 2, the identifier following the
word G I V I N G must refer to either an elementary
numeric item or to an elementary numeric edited item.
Abacus Sottware COBOL 64
General Rules:
1. Additional rules and explanations related to this
Refer to ROUNDED Phrase, SIZE ERROR Phrase in
Arithmetic Statements in this section.
2. In Format 1, all literals or identifiers preceding the
word FROM are added together, and this total is
subtracted from the current value of identifier-m. The
result is immediately stored into identifier-m.
3. In Format 2, all literals or identifiers preceding the
word FROM are added together, the sum is subtracted
from literal-m or identifier-m, and the result of the
subtraction is stored as the new value of identifier-m.
Examples:
Assume as initial values for each subtract;

X=2, Y=10, Z=15, TOT=50, and SUB=30.
Format 1:
SUBTRACT X FROM TOT. r e s u l t s TOT=48
SUBTRACT X Y 2 FROM TOT r e s u l t s TOT=23
Format 2:
SUBTRACT X Y FROM SUB GIVING TOT. r e s u l t s TOT=18
SUBTRACT X Y FROM Z GIVING TOT r e s u l t s TOT=3
WRITE
The W R I T E statement releases a logical record for an
output file. It can also be used for vertical positioning of
lines for a printer.
General Format:
Format 1:
E3JT.L record-name
-----
ADVANCING integer
Format 2:
UE,ITE record-name
UVATJQ KEY imperative-statement
Syntax Rules:
1. The record-name is the name of a logical record in the
FILE SECTION of the DATA DIVISION.
2. Integer-1 may not be zero.

3. Format 2 is used for Organization Relative Files.
General Rules:
1. The associated file must be open in the OUTPUT or 1-0
mode at the time of the execution of this statement.
2. The execution of a WRITE statement has no effect

upon either the contents or accessibility of the record
area.
3. The execution of the WRITE statement causes the value

of the F I L E STATUS data item, if any, associated
with the file to be updated. Refer to 1-0 Status in
Section 5. m
4. The maximum record size for a file is established when
the file is created and must not subsequently be
changed.
5. The number of character positions on a disk storage
device requkd to store a logical record in a file may or
may not be equal to the number of character positions
defined by the logical description of that record in the
program.
6. The execution of the WRITE statement releases a

logical record to the operating system.
PRINTER FILES
1. The ADVANC ING phrase allows control of the vertical
n
positioning of each line on a printed page. If the
ADVANCING phrase is not used, automatic advancing
is provided to act as if the user had specified AFTER
ADVANCING 1LINE. If the ADVANCING phrase
is used, advancing is provided as follows:
a. IIf integer-1 is specified, the page is advanced the
number of lines equal to the value of integer-1.
b. If the BEFORE phrase is used, the line is written

before the page is advanced.
2. During the transfer of data to the printer, if a character
code 13 (RETURN) is encountered the transfer is
terminated after sending the RETURN code.
DISK FILES
SEQUENTIAL FILES:
n
1. When an attempt is made to write beyond the
externally defined boundaries of a Sequential File, an
exception condition exists and the contents of the
record area are unaffected. The value of the FILE
STATUS data item, if any, of the associated file is set
to a value indicating a boundary violation. Refer to
1-0Status in Section 5.
RELATIVE FILES:
1. When a Relative File is opened in the output mode,
records may be placed into the file in one of the
following ways:
a. If the access mode is sequential, the W R I T E
statement causes a record to be released. The first
record has a relative record number of 1 and
subsequent records released have relative record
numbers of 2,3,4, and so on. If the RELATIVE
KEY data item has been specified in the file control
entry for the associated file, the relative record
number of the record just released is placed into
the RELATIVE KEY data item during execution
of the WRITE statement.
b. If the access mode is random, before the execution
of the W R I T E statement, the value of the
RELATIVE KEY data item must be initialized in
the program with the relative record number to be
associated with the record in the record area. That
record is then released by execution of the WRITE
statement.
2. When a Relative File is opened in the 1-0mode and the
access mode is random, records are to be inserted in
the associated file. The value of the RELATIVE KEY
data item must be initialized by the program with the
relative record number to be associated with the record
in the record area. Execution of a WRITE statement

then causes the contents of the record area to be
released.
3. The INVALID KEY condition exists when an attempt
is made to write beyond the externally defined
boundaries of the file.
CHAPTER 7
START UPIOPERATING INSTRUCTIONS

Connect the system as described in your Commodore
User's Guide. Now turn on the equipment in the
following order:
1. Printer (if present)
2. Computer
3. Diskdrives
4. TV or monitor
Insert the COBOL 64 diskette and type:
LOAD "COBOL 64", 8,l
followed by the RETURN key. The system loading process

will then take place. When completed, READY will appear
n on the screen. Now type:
SYS 2 0 5 1
followed by the RETURN key. The COBOL 64 System will

then start.
CHAPTER 8
MAIN MENU
The COBOL 64 Main Menu is displayed on the screen and

contains the following functions:
At this point enter the number of the function desired

followed by the RETURN key.
The following sections will describe each function in
detail. They appear in alphabetical order for easy
reference.
-
Main Menu
CRUNCH
The CRUNCH function is used to reduce the memory size of
your program file. A file must be present, refer to GET
and NEW-PROG. If the COED I T program overlay is not
present in memory, it will be automatically loaded by the
system from disk. Messages will appear on the screen
when this occurs.
While developing your program, each time you delete or
change lines the memory space for the old lines is no
longer available for new lines. This is not a problem
unless you exceed the maximum available memory. At this
time or at any time you wish to consolidate memory,
invoke this function.
The processing associated with this function includes
writing to disk a temporary file with the prefix C S
(COBOL sequential) before your file name. eg.
CSYOUR-NAME. A warning message will appear on the
screen which will allow you to remove the COBOL 64
diskette and insert your diskette. Enter any key on the
keyboard to continue. Once the temporary file is written, it
is then read back into the system. As each line is written to
disk or read back from disk, it will appear on the screen.
At the completion of this task a warning message will
appear which allows you to save the new consolidated
program on disk. The system will now return to the Main
Menu.
Main Menu
DEBUG
rn
This function directs the system to begin executing the
current program file in memory. A file must be present,
refer to G E T or NEW-PROG. The DEBUG function is
similar to the RUN function described below. In addition to
executing your program a number of powerful debug
features are provided which are intended to facilitate the
debugging of your program. All debugging in COBOL 64
is accomplished at the source (symbolic) language level.
There is no need to be concerned with machine language,
memory addressing or hexadecimal notation.
Before debugging can begin, your program is tested to
determine if it has been successfully syntaxed. If it has,
the CORD (RunIDebug) program overlay is automatically
loaded from disk if required. If your program had not
previously been syntaxed the syntax process will begin.
Refer to EDIT SYNTAX for additional details. If the
syntax process is unsuccessful the system resumes at the
main menu. If successful the system proceeds with the
CORD program overlay.
At the beginning of DEBUG Mode a "START DEBUG"

message will appear on the screen followed by the DEBUG
feature menu. At this time you may need to remove the
COBOL 64 diskette and insert your diskette if your
program is going to use the disk drive.
The following is a list of the DEBUG Menu features. Each

one is described in detail below. Enter the feature number
desired followed by the RETURN key.
l=START- PROG
2=RESUME-PROG
3=S INGLE -ON
4=SINGLE-OFF
5=EXIT
6=BREAK1
7=BREAK2
8=BREAK3
9=OPTIONS
10=TRACE-ON-LINE
11=TRACE-OFF-LINE
12=TRACE-FAST
13=TRACE-SLOW
14=TRACE-ON
15=TRACE-OFF
16=RESET-OPTIONS
START-PROG
This selection will cause your program to begin executing
at the first PROCEDURE DIVISION statement in your
program. Your program is initialized with its starting
VALUE clauses as required. To simplify debugging, all
other data items are initialized to the numeral 9. During
execution, if your program references a data item which
you did not properly initialize, the 9's will be obvious;
otherwise you would see strange characters on the screen
for a DISPLAY statement or as a function of the trace
feature.
RESUME-PROG
This selection allows you to continue execution from the
point where it was before entering the debug menu state.
This selection cannot be used when starting a program, or
n
after a STOP RUN verb, you must use the START-PROG.
SINGLE-ON
This selection turns on the "single step" feature. Single
stepping allows you to step through your program
execution one statement at a time. Once your program
begins executing (see START-PROG or RESUME-PROG)
each statement will display S=NNNNNN where N is equal to
the line number of the statement followed by the statement.
At this point depress the RETURN key to execute the next
statement. Any other key will direct the system to the
DEBUG Menu. This feature will also automatically turn on
the trace feature, refer to TRACE-ON. Comment lines are
ignored during execution.
SINGLE-OFF
The single step feature described above is turned off. The
trace feature is also turned off.
EXIT
This selection will direct the system to exit the D E B U G
Mode and proceed to the COBOL 64 Main Menu.
A selection of the break feature allows you to enter a

statement line number which when executed will cause the
system to enter the DEBUG Menu state. Note that this
occurs before execution of the statement in the selected line
number. The screen will contain a B=NNNNNN where N is
equal to the line number. The system provides for one to
three line numbers plus the verb DEBUG-BREAK which
you can place in your program as required. Comment lines
are ignored during execution.
OPTIONS
The selection of this feature directs the system to display
the current state of all DEBUG Menu options.
b4 TRACE-ON-LINE
A selection of this feature allows you to enter a statement
line number which when executed will cause the system to
turn on the trace feature. Refer to T R A C E - O N for
TRACE-OFF-LINE
A selection of this feature allows you to enter a statement
line number which when executed will cause the system to
turn off the trace feature. Refer to T R A C E - O N and
TRACE-OFF for more details.
TRACE-FAST
The TRACE-FAST feature displays all trace information at
full speed This is the default setting for the trace feature.
n
TRACE-SLOW
The TRACE-SLOW feature provides for slowing down the

speed of the trace display such that it is more readable
during execution.
TRACE-ON
The selection of the TRACE-ON feature provides for
information to be displayed during execution of your
program. The TRACE-ON feature is a default setting.
As each statement is executed the system displays a
T=NNNNNN followed by the statement; where N is equal to
the statement line number. All comment lines are ignored
during tracing. If the statement being traced has a receiving
data item such as MOVE A TO B then C= is displayed
followed by the new contents of the data item. The size of
the display is limited to 18 characters. If the receiving field
is a numeric data item the contents display is enhanced to
include the sign (+-) if present and the letter ' v ' in the
assumed decimal point position.
Example:
The picture of A is equal to S 9 9V9 9.
T=000100 MOVE +1.2 TO A

In addition to the TRACE-ON and TRACE-ON-LINE

features, the system provides a DEBUG-TRACE-ON verb
which you can insert in your program as required.
TRACE-OFF
The trace feature described above is turned off. There is also a
DEBUG-TRACE-OFF verb for this purpose which you
can insert in your program as required.
RESET-OPTIONS
The selection of this feature is used to reset all DEBUG

options to their default settings:
TRACE-ON
TRACE-FAST
Main Menu
EDIT
The E D I T function is used to enter your COBOL 64 na
statements. A set of ED I T functions are also provided to
facilitate the editing process:
DIRECTORY list the disk directory

LIST list lines on screen
DELETE delete lines
SYNTAX syntax analysis
AUTO auto line numbers
SAVE save program on disk
RE SEQUENCE renumber all lines
PRINT-ON set printer on
PRINT-OFF set printer off
EXIT exit to main menu
If the COED I T program overlay is not present in memory it
will automatically be loaded from disk by the system.
Messages will appear on the screen when this occurs.
When the START E D I T message appears on the screen
you can begin entering COBOL 64 Statements or
ED IT-Functions.
COBOL 64 Statements
Start by entering a six digit line number followed by the
remainder of your statement. Refer to the section titled
Editing Format for additional information. Each line must
be terminated by the RETURN key before it is processed by
the system. The Commodore cursor control keys are
enabled including the inservdelete keys. Refer to your
Commodore User's Guide for more details. One line on
the screen is 40 characters, a COBOL 64 line can be up to
80 characters, which would occupy 2 lines on the screen.
To replace a line you may simply type the new line with the
same line number as the line your are replacing. The
E D I T - L I ST function described below can be used to
view your text. You can, for example, list a line or series
of lines, and then type any changes needed followed by the
RETURN key. Inserting lines is accomplished by typing a
line number which falls between two existing lines.
Deleting lines is accomplished by the ED I T - D E L E T E
function described below.
While entering COBOL 64 statements some validation of
the text is performed. If an error is detected INVAL I D
E N T R Y is displayed. If this message should appear,
review the entry you have just typed and make any
necessary corrections.
Example:
If you enter -
ADD A TO 1B
the INVALID ENTRY message will appear because 1~ is

not a valid COBOL 64 word.
Additional validation (Syntax Analysis) is performed at
another h e .
DIRECTORY
The D I R E C T O R Y function will list the disk directory on
the screen. The abbreviation D I R can be used.
LIST
The LIST function has the following format:
LIST [starting-line-number] [ending-line-number]
1. If no line numbers are present then the entire file is

displayed.
2. If only one line number is entered then only that line is
displayed (if present).
3. If two line numbers are entered (at least one space
between the numbers is required) then the first number
is interpreted as the starting line and the second as the
ending line number. Note the ending line number
must be greater than or equal to the starting line
number. The lines are displayed if present.
4. The R U N / STOP key can be used to terminate the
listing process or the listing process can be paused by
holding down the SHIFT key. e
5. The LIST function can be abbreviated ' L ' .
6. Leading zeros on line numbers need not be entered.
7. An error message is displayed if invalid line numbers
are entered, such as 12x3 or more than 6 digits.
DELETE
The format and validation of DELETE is similar to LIST.
This function deletes the lines indicated. The lines are
displayed for documentation purposes.
SYNTAX
e This function performs a complete syntax analysis of your

program. Any errors found will cause the line in error to
be displayed (including the previous 7 lines) and an error
message.
For the IDENTIFICATION, ENVIRONMENT and DATA

divisions the syntax analysis process is aborted following
the first error encountered. The PROCEDURE D IVIS ION
is only syntaxed if no errors are found in the other
divisions. All errors are reported in the P R O C E D U R E
DIVISION.
This function is optional during the E D I T Mode. An

automatic syntax analysis will be forced when you select
the RUN or DEBUG Mode for any program. It has been
made available in the E D I T Mode to allow you to
selectively syntax portions of your program as you develop
it.
The syntax analysis process involves two automatic
program overlays to occur from disk, C O S Y N and
C 0S Y N P . Messages are displayed for this purpose.
Following the syntax process the C O E D I T program
overlay is automatically reloaded along with appropriate
messages appearing on the screen. This entire process
(excluding optional printer time) will take less than two
minutes, regardless of the program size.
AUTO
The AUTO function provides for automatic display of the
next line number. The AUTO function has the following
format:
AUTO [line-increment-value]
1. The line-number-value must be within the range 1 to
loo.
2. If no value is entered then the AUTO function is turned

off.
3. The line number displayed is computed by adding the
line-increment-value to the last line entered into the
system.
4. In addition to displaying the new line number, column
12 is indicated by displaying a large dot. This was La,
provided to facilitate formatting the line. If no new
text is entered in column 12, the large dot will be
automatically removed by the system before validation
begins. There is no need for you to type over it.
5. If the automatic increment should cause an overflow,
an error message is displayed and the function is
turned off.
SAVE
The SAVE function causes your program to be saved to
disk, refer to Main Menu SAVEfor additional details. It is
good practice to periodically save your program file onto
disk in case a problem with your computer or electrical
power develops. It is also good practice to save your
program on a second or third diskette in case a problem
with the diskette develops.
RESEQUENCE
- The RESEQUENCE function will renumber all lines in your

program by increments of 100.
PRINT-ON PRINT-OFF
This function forces all keyboard input and displays to the
screen to be printed on the printer. The printer must be
powered on. The feature provides for creating program
listings, documents all changes and error messages. For
example, if the PRINT-ON is entered followed by LIST
5 0 0 0 8 0 0 0, these lines are displayed on the screen and
printed on the printer. If SYNTAX is selected with the
P R I N T -ON, all error messages are printed for later
evaluation.
Printing is terminated with the PRINT-OFF function.

These functions are also available from the COBOL 64
Main Menu selection.
EXIT
The E X I T function allows for terminating the E D I T
session and returns processing to the COBOL 64 Main
Menu. If the E D I T session included changing the program
file, then a warning message appears, which will allow
files to be saved on disk. Refer to the Main Menu SAVE
function for additional details on saving a file.
Main Menu
GET
The GET function is used to get (load) an existing program
file from disk into memory. A message appears on the
screen requesting that a file name be entered. At this time
you must remove the COBOL 64 diskette and insert your
diskette. Enter the desired file name (enclosed in quotation
marks) followed by the R E T U R N key. Messages will
appear during the loading process. The system will return
to the main menu following the loading process. At this
time you may need to remove your diskette and insert the
COBOL 64 diskette, depending on your next menu
selection.
NEW-NAME
The NEW-NAME function provides for the changing of a Ca
program file name. A file must be present, refer to GET or
NEW-PROG. A message appears on the screen requesting
that the new file name be entered. Enter the new file name
(enclosed in quotation marks) followed by the RETURN
key. The system then returns to the Main Menu. This
feature is useful when using an existing program as a basis
for a new program.
NEW-PROGIEDIT
This function erases any existing program in memory and
accepts a new program name. A message appears on the
screen requesting that a file name be entered. Enter the
new program name (enclosed in quotation marks) followed
by the RETURN key. The system then proceeds as if the
ED I T function had been selected from the Main Menu.
Refer to the section on ED I T for additional information.
PRINT-ON PRINT-OFF
These features force all keyboard input and screen displays
to be printed on the printer. The printer must be powered
on. They are intended for creating program listings,
documenting all changes, menu selections, tracing and
error messages.
Printing is terminated with the PRINT-OFF function.
RUN
This function directs the system to begin executing the
current program file in memory. A file must be present,
refer to GET or NEW-PROG. Before execution can begin
your program is tested to determine if it has been
successfully syntaxed.
If it has, the CORD (RUN/DEBUG) program overlay is

automatically loaded from disk if required. At the
beginning of RUN Mode a "START RUN" message will
appear on the screen. At this time you may need to remove
the COBOL 64 diskette and insert your diskette if your
program is going to use the disk drive. Enter any key to
begin execution of your program. When your program
execution is terminated, the system will return to the Main
Menu.
If your program had not previously been successfully
syntaxed, then the syntax process will begin. Refer to
ED I T SYNTAX for additional details. If the syntax
process is unsuccessful, the system resumes at the Main
Menu. If the syntax process is successful, the system
proceeds with the CORD program overlay as described
above.
SAVE
The SAVE function provides for the saving of your
program onto disk. A file must be present, refer to GET or
N E W-PROG. Before proceeding with the SAVE, remove
the COBOL 64 diskette and insert your diskette.
Program files are saved in two parts. Each part is prefixed
by C 1 or C2 before your file name. eg., ClYOURF I L E
C 2Y OURF ILE. Screen messages will appear during the
saving process. If your file already exists on the diskette it
will automatically be overwritten by the new file.
APPENDIX A
n SAMPLE PROGRAM
The following sample program is an example of one way to write a

COBOL 64 program which performs the function of a simple
adding machine. This program is available on the COBOL 64
diskette. It is recommended that you use the program to get
familiar with the COBOL 64 system. After studying the program
listing try the exercises below:
BBOl IDEhi"..'"-'~'
itlLHi ILN L i V l 5 l O h .
988206 PROGHAM-i D. ?S-ADDI#6-PtACHikE.
Baaj0B ENY iROtiHEtiT DJ$i5!Ok.
088400 CONFI GUHAT 1% SEZT IUN.
0085BB SObRCE-COHPUiEn. Cb4.
oeasaa ~ ~ Z J E C T - C ~ ~ ~i b~4F. ~ ~ E R .
@@.73e DiijISIOR.
008806 WORKING-SiORAGE SECTIOR.
0EB90a 8 1 DISPLAY-LINE.
001688 62 DisP-SPACE P I C 1,283 ;$ALUE 3 $!
a0llfi6 3; DISP-HbMaiFi F i C !i,iZ2,iZi.99t.

?id1288 8 1 ENTRY.
a~;zae 92 E#yR.y-SABLE P I i X LCJjRS 12 TIHES,
BalJBtif i B SIGiTS t i DECitliiL POINT + 1 i U K i T I O N KEY
a j l j 0 0 77 EMiRi-SiJB P I C 99.
aelCEa 77 KEY-IN PIC X .
0817@3 77 TfiiRL P I C '59iBJY99 V A i i j i 2.
& 3 l Y E d 77 NGHERIC-ENTRY P I C SYiGjV99.
8a]?a@ 77 CLEaR-Hfihi-Cij;E $fiidi i 4 7 P I C 1,
oonaae 77 RETURN-CODE VALUE ~ H R1; PIC a.
B a z l ~ a7; R Y S - ~ N - C O ~ ~i,diiji E L ~ R13 P I C ii.
ac?na8 77 hVS-ijFF-COfiE bfi,jui CHR 146 P i c X,
8.2.2388 FfisCEijURE ijl$]SifiN,
@BiJ@ ST&RT.
4.-.-.z ar
,.Lii,< :-.-. D J j i i i A i ; .;itriR-;icfiE-CGDE
~~~~$~ "TART ASDiW flACHINE%

dP!7BB ~ET~R~-~~DE.
0 0 2 8 0 0 START-ENTRY.
002980 DISPLAY RETURN-CODE
il0388il YNTER: "
Ba3i80 NOVi " TTG ENTRY
003200 W E i TO ENTRY-SUB.
O03300 ACCEPT-LOOF.
0'83400 ACCEPT-i-KEY LEY-Iii
89350a DISPLAY KiY-ik
8936$0 1; KEY-ifi is Es;LL "+"
063708 Pskr.iRh P i i j S - i i \ THRU PLUS-KEY-EXIT

dB3800 GO TO START-ENTRii.
aajqaa I F L E f - I N EGUAL ! I - "
004000 PEHFnRM NlthUS-KEY THRU HlNUS-kEV-EXIT
804100 60 TO START-ENTRY.
804208 I F KEY-IN EQUAL 'SS"
804300 P E R F O R ~SUB-KEY
$84480 GO TO START-ENTRY.
884588 1: KEY-IN ECuAL " 7 "
804bUI PEHFORfl TOT-KEY
$84700 SO TO STAET-ENiRY.
88i8ile I F KEY-IN EQUAL "E"STO Riik.
0$4900*
80500B HDVE KEY-IN i O i t i S R Y - T k B i i i E h i H i - S B B i
005100 ADD 1 TO EHTRY-SUB
0052B8 .
I F ENTRY-SGB 1 5 & h E k X q i n A H 12LI
805308 PE'tiORN EkR

BE5400 52 ;n ~TA$T-~F,;H\
815508 ELSE 63 TO A E C E P T - ~ G ~ P .
a0560a P'US-LEY,
3a5702 i ! i T E ~ - ~ G ~ i RcdiRY ~ C 5 9 NGflE:zii-Etd;;,j
08580% ON ERROR
805980 PEAFORH iF,Z
lOb80E TO F ~ ~ S - ~ ; E ~ - E X I ; ,
pJ6188 ADD dg#i+,iC-ihS$y 70
006208 MOVE'I:Ld'(,"~ tp'!, ~ - t ~ i pi.c, i fiISP-&XBER
""',
i;iSPi8r 9''L"t'
8853'jfi ,-, , , 9 - ~ . k 2 t
"'Y'
89b558 D~SPL~F-~~HE,
8165ajj P i d S - x E Y - E i i i . E X I T ,
aabtae nrnus-KEV.
APPENDIX A
Exercises
1. Load and execute the program in RUN Mode.

a. From the Main Menu select GET file:
Enter 5 then RETURN
b. Enter the file name in quotes
Enter "ADDING then RETLTRN
At this point the ADDING program is loaded into memory.
c. Select the RUN program option
Enter 2 then RETURN
At this point the CORD program overlay will take place followed
by screen messages "START R U N and "ENTER ANY KEY TO
CONTINUE".
d. Enter any key to start the ADDING program.
e. Enter some entries such as:
Try some invalid entries such as:
1 2B 3 + (not a number)
1 2 . 3 4 5 + (too many digits after decimal point) dsa
f. To exit the program and return to the Main Menu
Enter E
2. Execute the program in DEBUG Mode.

a. From the Main Menu and with the program already
loaded into memory (Step 1 above).
Enter 3 then RETURN
Note that the CORD program overlay is not needed at this
time because it is still in memory from Step 1 above.
The DEBUG Menu is displayed at this time.
b. Proceed at this point by selecting TRACE-SLOW.
Enter 13 then RETURN.
c. Select the START-PROG option.
Enter 1 then RETURN
The program will start executing with a display of each
COBOL 64 statement as it is being executed. The trace
display will stop when the ACCEPT- 1-KEY statement is
executed (line # 003400)
d. Now enter some entries as you did in Step 1 above and
try to follow the program execution sequence.
e. Exit the program as you did in Step 1.
Enter E
The system returns to the DEBUG Menu.
f. Return to the Main Menu by selecting EXlT.
Enter 5 then RETURN
3. Try making some changes to the program so that you can

exercise the EDIT Mode. Consider changing the size of
the entry or even simpler, the "START ADDING
MACJ3INE" on line 002600.
a. From the Main Menu select EDIT Mode.

Enter 1 then RETURN
The COEDIT program overlay is then loaded into memory.
b. List the program on the screen.
Enter LIST then RETURN.
Continue changing and listing as required.
c. To exit the EDIT Mode
Enter EXIT then RETURN
Ab
Note the warning message to save the program. You
cannot use the COBOL 64 diskette because it has the write
protect tab on. Insert your own disk to save the program
or bypass the save. If you do insert your disk be sure to
replace it with the COBOL 64 diskette after the save has
been completed. Now the Main Menu is present on the
screen. Try executing your changes by following Step 1
or 2 above. This time you will observe that a Syntax
Analysis is being performed, this will occur whenever a
program is changed.
- APPENDIX B
RESERVED WORDS
All reserved words known to the COBOL 64 System are listed in
this Appendix.
ACCEPT ACCEPT-1-KEY ACCESS

ADD ADVANCING AFTER
ALPHABETIC AT AUTHOR
BEFORE BY CLOSE
COMMA CONEIGURATION CURRENCY
DATA DATE-WRITTEN DEBUG-BREAK
DEBUG-TRACE-OFF DEBUG-TRACE-ON DECIMAL-POINT
DEPENDING DISPLAY DIVIDE
DIVISION END ENVIRONMENT
EQUAL ERROR FD
FILE FILE-CONTROL FILLER
FILTER-NUMERIC FROM GIVING
6(
GO GREATER 1-0
IDENTIFICATION IF INDEX
IDEXED INPUT INPUT-OUTPUT
INSTALLATION INTO INVALID
IS KEY LABEL
LESS LINE LINES
MODE MOVE MULTIPLY
NEXT NOT NUMERIC
OBJECT-COMPUTER OCCURS OF
OMITTED ON OPEN
ORGAN1ZATION OUTPUT PERFORM
PIC PICTURE PROCEDURE
PROGRAM-ID RANDOM READ
RECORD RECORDS RELATIVE
ROUNDED RUN SECURITY
SELECT SENTENCE SEQUENTIAL
SET SIGN SIZE
#- SOURCE-COMPUTER SPECIAL-NAMES STANDARD
STATUS STOP SUBTRACT
THAN THROUGH THRU
TIMES TO VALUE
WORKING-STORAGE WRITE
APPENDIX C
LANGUAGE SUMMARY
IDENTIFICATION DIVISION
PROGRAM-ID
AUTHOR
INSTALLATION
DATE-WRITTEN
SECURITY
ENVIRONMENT DIVISION
CONFIGURATION SECTION
SOURCE-COMPUTER
OBJECT-COMPUTER
SPECIAL-NAMES
CURRENCY SIGN IS...
DECIMAL-POINT IS COMMA
INPUT-OUTPUT SECTION
FILE-CONTROL
SELECT...ASSIGN...
ORGANIZATION IS SEQUENTIAL
ACCESS MODE IS SEQUENTIAL
ORGANIZATION IS RELATIVE
ACCESS MODE IS SEQUENTIAL RELATIVE KEY IS ...
ACCESS MODE IS RANDOM RELATIVE KEY IS...
FILE STATUS IS..,
DATA DIVISION
FILE SECTION
FD
LABEL RECORDS ARE...
VALUE OF FILE-ID IS.. .
WORKING STORAGE SECTION
LEVEL-NUMBER...FILLER...
PICTURE IS...
USAGE IS...INDEX...
OCCURS...TIMES...
INDEXED BY...
VALUE IS...CHR...
LANGUAGE SUMMARY continued
PROCEDURE DIVISION
ACCEPT. ..
ACCEPT-1-KEY.. .
ADD...GIVING...ROUNDED ON SIZE ERROR...
CLOSE. ..
DEBUG-BREAK
DEBUG-TRACE-OFF
DEBUG-TRACE-ON
DISPLAY...
DIVIDE...INTO BY...GIVING...ROUNDED ON SIZE ERROR...
EXIT
FILTER-NUMERIC...
GO TO. ..DEPENDING ON...
IF...NEXT SENTENCE...ELSE...NEXT SENTENCE...
MOVE. ..
MULTIPLY ...
BY...GIVING...ROUNDED ON SIZE ERROR...
OPEN INPUT ...
OUTPUT...I-O...
PERFORM...THRU...
READ...AT END...INVALID KEY...
SET.. .
STOP RUN
SUBTRACT ...
FROM...GIVING...ROUNDED ON SIZE ERROR...
WRITE...BEFORE/AFTER ADVANCING ... LINES...INVALID KEY...
" m ~ v s m ~ ~ 3 ~ m w ~ 5 ~ ~ ~ ~ a m ~ w 6 v.: 1 1e ~v ~ &w ~~ c~ ;e ~u .m ; o. ~ e s a c u a a ~ 6 3
~ ~ E ~ W ~ ~ F ~ ~ ~ ~ ~ ~ ~ ~ ~ W B ~ ~ ~ ~ ~ ~
t.4 I:..-4 vl.i
,..I ,.I: (.J ,:..J I.., hl C...l t-..:l C.3 h, h..I C
3
. p>
. PI:, r... t C.' c c G- C- C- L' - . U ? O W G 2 C S B W B W -.
--I LO v s- I:...J ,...I .n co -4 V- m e r--J r.3
- LY 41m -4 o. ~n & UJ I+; m 4 1 m -.I G- r n P C-J r~aL-
-. --
6.,~'~FJ~~"rslocs;lcusw61~BeF.l~R1LY~6.,aLYNm~LYN~CU~~IS1w~~8)Cil
~ 1 s ~ 6 ~ ~ ~ ~ ~ 1 ~ r ~ ~ ~ 6 ~ 1 5 ; ~ ~ ~ ~ ~ ~ 6 ~ e - , ~ ~ ~
rr1 il') 7 1 -., J. A..'
.--I -..I s: 62 N T 7 1 C I T CI "1 CI rn 1 ;. 7 1 -*
--..I I . ' I .,-).
'.I : . 1
c:,
-z -., 73
r :.C I -., 7.1
... -. u -.
r- -4
2)
r c
r. 73 c
- a z c::73. CY
-* z r r 7 c;> c
. z <:: -1 C, rn
-%I >-, 7: rn 2, n 1 c rrl rn 7 1 -1 I GI z
..,I -r., -. CI C,
-n C, X I , 3 -I
r: 7.r
rZI es, c 2 m R, c:r < - r- O T u', I -4 r 1 c-J 3 7 CJ x x --4
--4 r r ~ -7, ' ~ 1
r' r r j c XI g
-, I el
' h3 P.1 z, ~ . : 1r.3 s1 r z:.15 ~1 D c-. rn r:)I -I rn L-'D c o I:, -4
-.I r- IT -.4 rn c-. r -r. I I c.2 - TI
- c
m: m x
TI? Wl <A:, c: c: r-' m -+ If> -, '7, --,
-. -
.:: T I .Z 71 -C' X? rr1 T;,CI I .-I 1 I:. I:.C Z ~ D~1 c m m &.. c r~ rl r c x I -,
- -
r, , r 1- 1 , 8 - - 7, , I 2: 1 rn , , . 8'' . -i . c-:I -+ -+ C.8 0 ZI r n 7 ; C.
r*
7 ci.~r c3 z- uy I z z I -i m 3 1 0 I,.T -. -1 CTI UI --I 7-x s -+ z CI TT
s : r - : c - : 1 7 1 CI r- .x m c,r~ rr.! u rr, o -+ ti c: 7 ' 1 f7 -I
-. L;. --I
I --I -4 C L ~r . 8 C - r- m T rn r t 7r rn r : t 7 1 rn -.cr, 2- c:, r- -ic: c:o
- +.
m u ~ t ' . ~ > o- r zi ~ : ~ r o ~ . s s . ~ I . I
E-I r n I CI r: 2 - 4 1 , . -4 -4 2 7 C:, LT>
rn ..d ,-. -+ ,z: r. -.- rn CT r crh ~8 XI '-n .x> -m -n z - T ( c? c -.i u? n~m I
.. m r
--I CJ WI -.I WI TJJ CI r r c; rn
--. o c.2 t-3 --0 XI
- --- cn I. rn a: rn C I S <: r c:
-
I 7, 7 3 I:. -. 5 : m 7:s 7 7 rr~ ~ r ' trrr r- LZ L- r 3 . T n - r r ' l r U t
.
C, - r , :I TI c':~ % ~lr c .
-. r r r- WI -
-- LC, --. -4 v"-8. UI .*: r.6 ..
II
7
-*
7 . 1
C
TI..
-. 2- I.
-4 I.
I z
- - 1 r
C- r-
r~
f'
c-7 rr1 r, C I
c-l I
- C- el I
r.. 2:.
u1 ~
-',I
; 1 - -.,
c-, c-:, r, -.- c, z I
... c-*<:
-
W, cz 3 1 r -4r-. rn c, 7, T u z m CP C I z:C? a r r ~
, . : r ; x C
2 2I WI -. P: r~7 . P; 2 . 2. n, 2;. -*
I'
r
C:;
C'
.'I.) Wl
rrq r.
x. ,-.I rm~ :c.
C. .c: CI I.. -1
- -
L IF-
1 - c-.
cn c-8
r ' m
m 2:
- . . . . - -.,
1
c:
: z:
z, rr: E I 7 -J: r . .-. 17
-.
r'l -*.-. I
- -. .
7 1 ?I' C' 3:1 T
I C' . 7.1 :t -, U S -4
1, --. mi X r. a:.- I -+ c:
:
t
c--
-.r
I
m't r
-I.'
-.b
'-1 C.-4
n
-
,-.I -.
I..,,...7
. : P
.. r , , - t
c
a
7> 7 - - , 2-: X! >.. c-9. C.!.7 --
>I. cr7r:r8 7.8 -r. :. - , I:
38 . s. LC1
::-.
-.,
-. - . - .
r n C. I... I
0:r .-." -
C' I :.: :*,
b
Ln
-I3 . .
I -.
r'I
,... : L.'
-. 7.I
-1 .-
=.Tr'l
a:,
APPENDIX D
SAMPLE PROGRAMS
88380% CLOSE DATA1

803906 i F F i L E - S i #0T EiXAL TO "8i!'
884@00 DISPLAY "CLOSE Ekq.;@*, 1.1 L.
884186 STOP RUN.

884288 GET-DATA-LOOP.
08430% DiSPLRY RVS-ON
( # r i l l
88448B t h l E R HAHE FIELD
884508 RETURN-CODE
aa4baa ACCEPT MARE-FIELD
a847a@ I F NAXE-FIELD i S NOT ALPHABETIC
a ~ j e ~ a DISPLAY 'NOT ALPHA"
884908 RETURN-CODE
8053BB 60 TO 6i T-DATA-LOOP.
885!@8 I F kkHE-FiiiD-EXIT EGiJAi TG
$85281 !!EXIT:! u~ Tfi i O ~ ~ - E ~ i T ,
'=
835388 DISPLAY RVS-ON

885400 "E#TER ADDRESS
8655%0 RETURN-'Ob" iJt
8856a3 ACCEPT a-%- urn-FiELD
60570a D ~ S P L!!DaTe
~ ~ i y / ~ ) ~ ,
885680 ACCEPY URiTE-FLAG.
885508 I F WRITE-FLAG EPUAL "Y"
i101;080 PERFORH WRiiE-ROUTINE.
886!88 GO TO GET-DATA-LOOP.
906280 #RITE-ROUTINE.
Bab38Q WRITE CATA-RECLSit.
i?Ob48B I F FILE-S. ; ui ruuAL Ti "3%"
'n:;
086588 DISPLAY "WRITE ERROR"

B$bba0 STOP RUN.
336780 HOVE " " TO DATA-RECORD.
38bfiBZ HOVE TO I H i T E - i i A E ,
#&?B@ LOOP-EXii.
9@7efia Eiii.
*cc;HFLETED
PEiHT-Dii
APPENDIX D
SAMPLE PROGRAMS
C.128REQUIRED
and C-64.READING
O ~ c . 9 r ~ ~ , ?
TRICKS & TIPS 1571 INTERNALS COMPllTER AIDED DESIGN
.m A #Lc<FnB"%cmL~co#.
Abacurmsol~warc
YC lo" a pr0grlmmg. pro em re e a e ILB 8 "8 B 0' BYB'yO"B n e

a n a l y r n Iborouqh deur8pl80n 0, all 4Urii h8lierr Ea3y and useful e l l e d n CP'M on the 128 Stmpis
BASIC Clirnrnands -8th hundreds ol Ischnlqusl mn ths operalng Syslsm slplrnallar ,>I !he mperalnp r7slsm
examples ron,.ors.mmand, ",I. r , i c * r rrro page, po8nlerr. ,he memory usage CPlM " , I " pro-
f=, much W r s I16 95 811S8C lnlslprelsrandmore 516 95 graT1, rublr#!lllald more 519 95
ANATOMY OF C - M In*'dof' su'd* lo TRICKS L ~ P FOR S C-6. c o ~ l a i o n01 BCILNCEIEYGIWEERINO ON c.84 ~ t ~ . ~ t ~ . G.~~*,I~.,..
. n.nd.aah
'- G'*nia, "O. "ma'. easy 10-"3slWrhn,~ual=dr=rssd sraphia, depth ,mr. lo mmwtsn
ssisws. l o p i o S t e p - b r n o p suds lo designmg am rnllnp
memow mKa, Com@"'mmma"'sd m p r a r s d data ,"put, anhanc.0 BASIC. chamslry, physics, b,a#ogy. aslronomy. your own adventure pa me^. wlm aln~malsd
ROM I ~ ~ ~ ~ O ~P 119.95
P ~ CP,M.
~ more,
.
2 7 5 ~ 119.95
~ - slanrono..~hn 110pp 119.95 adr.n#un pan* p.nsra~or. b o p p s?a.e5
handbook on
M A C H I N E L A N G U A G E C - 6 4 Learn ~ D ~ A N C E O
MACHIWE L A N G U A G E IOEAS F O R USE D N C.64 T b r n a s : olpur'm. WOpp Sl4.55
6510 COO. W ~ lastD progtarnr. Many ram- N,I mrsrsd a!rsrhsrs: .
"d.0 m n t r o s r . aulo e r ~ a n s . s . cdcula~mr,rsccp !,I. 6 t h
op'lon" D'n'e"" 'Or
p b s and sl8ngs lor coaplelo arromblor. ,nrerrup!s. I ~ clock,.
~ YO,~ rsai ~ Ilm.. ~ h%lr,
. dmac plannor. w ~ n d o r adrsrllslng,
monllor. L s8mulalor 20Opp 114.95 sn#nl*d BASIC, rrqr. I l O p p 114.95 other. includes lkllrps. 2OOpp S72.95 For ""4nConrsni'ncs.
conlalnsd aach o l our books Ihs.re wall-
GRAPHICS BOOK C-64 - b L relerencs C . ( 4 1 ~ ( ~ . 2 under
~ COMPILER BOOK C.64IC-128 All P u Ible on dlrkano I. saw you !#me smaclnq
C O V ~b-c
~ and a d r a n u d grwhtcs. ,,and Cornmodor., Eproncomp.,bl. p,,nl. m a d I o know about m m o , l s n : how l h s l !hem lrom I O U ~h a y b a d . ~ ~ n mns d f ~
ydms$;;r,H8~d, bAA;,c$;: ", pl .,,.,p*,d

. ul,~,l,o.: qr. work; do(i~gn'n9 and r r , t ' n q Your 0-n:
I O " ~ " ' " I machln. md. WN-h *or*'ns
bod r M n orOar8rp. :!~.OI each
I~.olol, mmmonlod M P S B O I
pnon., run.s, more. l,Dpp s,995 pnlcI
ROM I ~ ~ mar.. , ~ ~ .130. sts P, '..mPb mmp'br. ~ O ~ P119.95
P
P.O. Box 7219 Grand Raaids, MI49510 Telex 709-101 Phone (6161241-5510
= =
Call now for the name ol your nea;esl dlaler. Or to order directly by credit card, MC, AMEX of VISA call (616)
241-5510. Other software and books are available-Call and ask for your free catalog. Add $4.00 lor shipping
per order. Foreign orders add $10.00 per book. Dealer inquires welcome-1400+ nationwide.
~
For school or sollware NM just a mmpiler. but a
development. Learn C on Cornpllcruld sonwarc
Ikvclopmcnl S).sm mnplate syrlem lor d e w l o p
your Commodore wilh cur m- ing appl~cations in Pascal
deplh tulorial. Compib C pr- 9 wllh graphics and sound
grams in10 l a r l machine
language. C-128 verrim has
9 lealures. Extensive editor
$ . . + wilh search. redace. auto.
added fealurer: UnixW-llke renumber. eic. $andard J
~peralingsyslem: 60K RAM
W compiler lhal generates
disk lor la91 editing and lasl machine code. If you
compiling Linker combiner want l o learR Pascal or to
up to 10 modules: Combine
develop soltware using the
WL and C using CALL: 51K best tools available-SUPER
amilable lor d i e d code:
TWO slandard 110 libravs plus
J Pasc.1 is y w r first choice.
C-128 159.95
two addiliohi librarie-~1hl;ndionr ( i n . m s . safl. e l c l 6 20+ oraohlc
C-64 $50.05
mmmands (Itne, lill, d d , etc). cL128 f i 9 . 9 5
Easily create proferrional

OTHER TITLES AVAILABLE:
high quality chanr and T k h n i c d Analysis Sy1l.m
graphs withcut prwrammlng. Sophisticated charting and technical analysis system for
You can hmedlalely change serious investors. Charting and analyzing past history of a
Ihe scaling. labelong. axis,
stock. TAS can help pinpoint trends & patterns and predid a
bar- f i l l ~ l g .etc. to suit your
,
needs. Accepts dala lrom stock's future. Enter data from the keyboard or lrom online
CalcResult and MulliPlan linancial services. G 6 4 559.95
C.128 version has 3 X the
~ a r o l u i o nof the 'M version. P e r w ~Portfolio
l Mmagor
(YMI l o most prim.. Complete protfolio management system for the individual or
C-128 $39.95 professional investor. Easily manage your portfolios, obtain
C-64 $39.95 up-to-the-minute quotes and news, and perform selected
- analysis. Enter quotes manually or automatically through
Powerplan Warner Computer Syslems. G 6 4 $39.85
One of the most oowerful soreadsheets with intearaded
graphics. Includes menu or keyword selections, online help X~er
XPER is the lirst "exoerls v s t d for the C-128 and C-64. While
screens, field protection, windowing.trig functions and more.
ordinary data base'syst&ns are good for reproducing facts,
PowerGraph, the graphics package, 7s included to create
XPER can derive knowledge from a mountain o l facts and help
~ntegratedgraphs & charts. G 6 4 $39.95
you make experl decisions. Large capacity. Complete with
COBOL Compiler for the C-64 $39.95 editing and reporting. C.64 559.95
Ada Com~ilerfor the C-64 $39.95
~ i d e o ~ a Language
4c for the C-64 $39.95
A ~
-
~
P.O. Box 7219 Grand Rapids, MI 49510 Telex 709-101 Phone (616) 241-5510
C
-
Software
U S ~
Call now for the name of your nearest dealer. Or to order directly by credit card, MC, AMEX of VISA call
(616)
241-5510. Other software and books are available-Call and ask for your free catalog. Add $4.00 for shipping
per order. Foreign orders add $12.00 per item. Dealer inquires welcome-1400t nationwide.

COBOL-64 Software System

Uploaded by

Copyright:

Available Formats

COBOL-64 Software System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

COBOL-64 Software System

Uploaded by

Copyright:

Available Formats

COBOL 64 Software Syste~

A Data Becker Product

First printing March 1986

This manual provides a complete description of the COBOL 64

THE NATURE OF COBOL IN GENERAL cc.llr

COBOL is the most widespread commercial programming language

MULTIPLY HOURS-WORKED BY HOURLY-WAGE GIVING GROSS-WAGES

The rules for programming in COBOL conform to many of the

The long list of COBOL advantages is derived chiefly from its

COBOL 64 IMPLEMENTATION NOTES

A program written in COBOL 64, called a source program, is

COMMODORE 64 Computer or equivalent (BASIC V2)

COBOL 64 SOURCE PROGRAM DIVISIONS

Every COBOL 64 source program must contain these four

"program". In reality, it is only part of the total program, and alone

The standard for COBOL 64 requires that a program consist of

As stated in Section 1, COBOL 64 is a language based on English

LANGUAGE DESCRIPTION NOTATION

A nearly universal form of notation exists for COBOL reference

The key words are I F , NOT, NUMERIC, and

The following symbols are braces: { } . When words or

CHARACTERS USED FOR WORDS Ar

m 1. The punctuation character space is a separator. Anywhere

3. The punctuation character quotation mark is a separator.

A COBOL 64 word is created from a combination of not

The length of a noun must not exceed 30 characters. For

of digits specified by the user. The following are

A nonnumeric literal cannot exceed 120 characters.

"THE TOTAL P R I C E " THE TOTAL P R I C E

Literals that are used for arithmetic computation must be

with the assumed decimal point located between the two

LOGICAL RECORD AND FILE CONCEPTS

PHYSICAL ASPECTS OF A FILE

Working storage may be grouped into logical records and

CONCEPT OF CLASSES OF DATA

Table 2- 1. Classes of Data

LEVEL OF ITEM CLASS CATEGORY

STANDARD ALIGNMENT RULES

The subscript can be represented either by a numeric literal

An index-name has the same internal representation as an

An index-name assigned to one table may not be used to

SECTION 3 EDITING FORMAT

SEQUENCE AREA (Record Positions 1-6)

INDICATOR AREA (Record Position 7)

1. If column 7 contains an asterisk (*), the remainder of

2. If column 7 contains a slash (/), the printout is

3. The presence of a hyphen (-) indicates that the last

Nonnumeric literals can be split into two or more records.

AREA A (Positions 8-11)

Within the IDENTIFICATION and E N V I R O N M E N T

Within the DATA DIVISION, the level indicator ED and

AREA B (Positions 12-80)

SECTION 4 IDENTIFICATION DIVISION

IDENTIFICATION DIVISION STRUCTURE

1. The IDENTIFICATION DIVISION must begin with

- 4. The comment-entry can consist of any combination of

SECTION 5 ENVIRONMENT DIVISION

ENVIRONMENT DIVISION ORGANIZATION

ENVIRONMENT DIVISION STRUCTURE

The following rules must be observed in the formulation of