COBOL/400

Naveen Kumar / Romi Rimesh 16/06/2008 -----------------------------------------------------------------------------------

COBOL 400
Structure of COBOL program: A COBOL Program consists of following 4 divisions:

IDENTIFICATION DIVISION ENVIRONMENT DIVISION DATA DIVISION PROCEDURE DIVISION

All the divisions must appear in the same order as shown above.

-1-

COBOL/400

COBOL - DIVISION1
Identification Division It names the program and may include the date the program was written, the date of compilation, and other such documentary information about the program.

-2-

COBOL/400

Identification Division
PROGRAM-ID. AUTHOR. INSTALLATION. DATE-WRITTEN. DATE-COMPILED. SECURITY. | | | |

Optional |

Coding Example:
IDENTIFICATION DIVISION. PROGRAM-ID. TESTPGM. AUTHOR. PROGRAMMER NAME. INSTALLATION. TCS. DATE-WRITTEN. 15/02/02. DATE-COMPILED. 15/02/02.

-3-

COBOL/400

COBOL - DIVISION2
Environment Division
Configuration Section Input-Output Section.

The Configuration Section is optional. When specified, it can describe the computer on which the source program is compiled and the computer on which the object program is executed.

-4-

COBOL/400

Environment Division
Configuration Section SOURCE-COMPUTER OBJECT-COMPUTER SPECIAL-NAMES Input-Output Section File-Control. I-O-Control

-5-

COBOL/400

COBOL - DIVISION2

Configuration Section can:

Relate IBM-defined environment-names to user-defined mnemonic names Specify a substitution for the currency sign Interchange the functions of the comma and the period in PICTURE clauses and numeric literals

-6-

COBOL/400

Configuration Section
Coding Example: ENVIRONMENT DIVISION. CONFIGURATION SECTION. SOURCE-COMPUTER. IBM-AS400. OBJECT-COMPUTER. IBM-AS400. SPECIAL-NAMES. TOP IS TOP-OF-PAGE.

-7-

COBOL/400

Input-Output Section
The Input-Output Section

Define each file to be used Identify its external storage medium

Assign the file to one or more input/ output devices

Specify information needed for efficient transmission of data between the external medium and the COBOL program

-8-

COBOL/400

Input-Output Section
File-Control Paragraph Names and associates the files with the external media.

A COBOL/400 program can process:

Data Base Files:
Physical Files Logical Files

Device Files:
Display Files Tape Files Printer Files Diskette Files ICF Files

-9-

COBOL/400

Input-Output Section
Coding Example1: INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT DISPLAY-FILE
ASSIGN TO WORKSTATION-TESTDSPF ORGANIZATION IS TRANSACTION ACCESS IS DYNAMIC RELATIVE KEY IS RRN FILE STATUS IS FILE-STATUS.

- 10 -

COBOL/400

Input-Output Section
Coding Example2: INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT PHY-FILE1
ASSIGN TO DATABASE-PHYSICAL1 ORGANIZATION IS INDEXED ACCESS IS DYNAMIC RECORD KEY IS EXTERNALLY-DESCRIBED-KEY FILE STATUS IS WS-PHY-FILE1-STATUS.

- 11 -

COBOL/400

Input-Output Section
SELECT Paragraph Makes association between the file and the external medium It consists of 3 parts: Device File Name Attribute

- 12 -

COBOL/400

SELECT Paragraph
DEVICE:

Specifies the type of Device that the file will use It can be changed at run-time
List of Different Devices: Device File WORKSTATION Display File DATABASE Externally described Database File DISK Program described Database file FORMATFILE Externally described Printer file PRINTER Program described Printer file TAPEFILE Tape File DISKETTE Diskette File

- 13 -

COBOL/400

SELECT Paragraph
FILE-NAME: 1 thru 10 char. system name of the actual external file For Database files, a member name can not be specified in the COBOL program. If a particular member is to be specified, the OVRDBF command must be used at execution time to specify the member name The file-name can be changed at execution time with the TOFILE parameter of the OVRxxxF command

- 14 -

COBOL/400

SELECT Paragraph
ATTRIBUTE: This part can be SI SI indicates that a separate indicator area has been specified in the DDS for the FORMATFILE or WORKSTATION file

- 15 -

COBOL/400

SELECT Paragraph
Device File Name Default SI File-name Optional N/A N/A Optional

WORKSTATION DATABASE DISK FORMATFILE PRINTER TAPE FILE DISKETTE

Required

Optional

Required Required Required QPRINT N/A Optional QTAPE Optional QDKT

N/A
N/A

- 16 -

COBOL/400

Input-Output Section
ORGANIZATION Clause For Database files, it indicates the use of the file in the program (permanent logical structure of the file) 4 types of organization: Sequential Indexed Relative Transaction

- 17 -

COBOL/400

Input-Output Section
SEQUENTIAL ORGANIZATION
The physical order in which the records are placed in the file determines the sequence of records The relationships among records in the file do not change, except that the file can be extended There are no keys. Both database files and device files can have sequential organization

- 18 -

COBOL/400

Input-Output Section
INDEXED ORGANIZATION Each record in the file has an embedded key called a key data item that is associated with an index An index provides a logical path to the data records, according to the contents of the associated embedded record key data items Only database files can have indexed organization

- 19 -

COBOL/400

Input-Output Section
RELATIVE ORGANIZATION Each record area is identified by a relative record number; the access method stores and retrieves a record, based on its relative record number Relative files must be assigned to DISK or DATABASE

- 20 -

COBOL/400

Input-Output Section
TRANSACTION ORGANIZATION Work station and data communication files can have TRANSACTION organization

- 21 -

COBOL/400

Input-Output Section
ACCESS MODE Clause It defines the manner in which the records of the file are made available for processing If the ACCESS MODE clause is not specified, sequential access is assumed

- 22 -

COBOL/400

Input-Output Section
ACCESS MODE Clause Sequential Access Mode
Sequential Organization Indexed Organization Relative Organization

Random Access Mode

Indexed Organization Relative Organization

Dynamic Access Mode

Indexed Organization Relative Organization

- 23 -

COBOL/400

Input-Output Section
ACCESS MODE Clause Sequential-Access Mode: Allows reading and writing records of a file in a serial manner; the order of reference is implicitly determined by the position of a record in the file Random-Access Mode: Allows reading and writing records in a programmer-specified manner; the control of successive references to the file is expressed by specifically defined keys supplied by the user Dynamic-Access Mode: Allows a specific I/O request to determine the access mode. Therefore, records may be processed sequentially and/or randomly

- 24 -

COBOL/400

Input-Output Section
RECORD KEY Clause It must be specified for an indexed file Each record in the file must have a unique record key value EXTERNALLY-DESCRIBED-KEY specifies that the key(s) for this file are same that are externally described in DDS WITH DUPLICATES phrase can be specified for files assigned to DATABASE

- 25 -

COBOL/400

Input-Output Section
RECORD KEY Clause Note: An error will be encountered at run-time, if
DUPLICATES is specified in COBOL program and file was created with UNIQUE specified in DDS DUPLICATES is not specified in COBOL program and file was created allowing non unique keys

- 26 -

COBOL/400

Input-Output Section
RELATIVE KEY Clause It specifies the relative record number for a specific logical record within a relative file. The POSITION parameter on the OVRDBF command can be used to set the file position indicator. This causes processing to begin with a record other than the first record.

- 27 -

COBOL/400

Input-Output Section
FILE-STATUS Clause It monitors the execution of each input-output request for the file In some cases it indicates the I-O errors It must be defined in Data Division

- 28 -

COBOL/400

Input-Output Section
I-O-Control Paragraph It is specified when checkpoints are to be taken and the storage areas to be shared by different files This paragraph is optional in a COBOL program

- 29 -

COBOL/400

Input-Output Section
SAME AREA Clause It specifies that two or more files, that do not represent sort or merge files, are to use the same main storage area during processing The files named in a SAME AREA clause need not have the same organization or access The SAME AREA clause is syntax checked, but is treated as documentation

- 30 -

COBOL/400

Input-Output Section
SAME RECORD AREA Clause It specifies that two or more files are to use the same main storage area for processing the current logical record. All of the files may be open at the same tim A logical record in the shared storage area is considered to be both of the following:
A logical record of each opened output file in the clause A logical record of the most recently read input file in the clause

This clause allows transfer of data from one file to another with no explicit data manipulation because the I/O record areas of named files are identical, and all are available to the user

- 31 -

COBOL/400

Input-Output Section
SAME SORT AREA Clause This clause optimizes the storage area assignment to a given SORT statement When the SAME SORT AREA clause is specified, at least one file-name specified must name a sort file. Files that are not sort files may also be specified

- 32 -

COBOL/400

Input-Output Section
SAME SORT AREA Clause The following rules apply:
More than one SAME SORT AREA clause may be specified. However, a given sort file must not be named in more than one such clause If a file that is not a sort file is named in both a SAME AREA clause and in one or more SAME SORT AREA clauses, all the files in the SAME AREA clause must also appear in that SAME SORT AREA clause Files named in a SAME SORT AREA clause need not have the same organization or access Files named in a SAME SORT AREA clause that are not sort files do not share storage with each other unless the user names them in a SAME AREA or SAME RECORD AREA clause

- 33 -

COBOL/400

Input-Output Section
SAME SORT-MERGE AREA Clause This clause optimizes the storage area assignment to a given SORT or MERGE statement When the SAME SORT-MERGE AREA clause is specified, at least one file-name specified must name a sort or merge file. Files that are not sort or merge files may also be specified

- 34 -

COBOL/400

Input-Output Section
SAME SORT-MERGE AREA Clause The following rules apply:
More than one SAME SORT-MERGE AREA clause may be specified. However, a given sort or merge file must not be named in more than one such clause If a file that is not a sort or merge file is named in both a SAME AREA clause and in one or more SAME SORT-MERGE AREA clauses, all the files in the SAME AREA clause must also appear in that SAME SORT-MERGE AREA clause Files named in a SAME SORT-MERGE AREA clause need not have the same organization or access Files named in a SAME SORT-MERGE AREA clause that are not sort or merge files do not share storage with each other unless the user names them in a SAME AREA or SAME RECORD AREA clause

- 35 -

COBOL/400

Input-Output Section
COMMITMENT CONTROL Clause This clause specifies the files that will be placed under commitment control when they are opened. These files will be affected by the COMMIT and ROLLBACK statements The COMMIT statement allows the synchronization of changes to database records while preventing other jobs from modifying those records until the COMMIT is complete The ROLLBACK statement provides a method of canceling changes made to database files when those changes should not be made permanent

- 36 -

COBOL/400

Input-Output Section
COMMITMENT CONTROL Clause This clause can specify only files assigned to a device type of DATABASE Files under commitment control may have an organization of sequential, relative or indexed, and may have any access mode valid for a particular organization The system locks records contained in files under commitment control when these records are accessed. Records remain locked until released by a COMMIT or ROLLBACK statement

- 37 -

COBOL/400

COBOL - DIVISION3
Data Division The Data Division of a COBOL source program describes, in a structured manner, all the data to be processed by the object program This section outlines the structure of the Data Division and explains the types of data and how they are related in a COBOL program

- 38 -

COBOL/400

Data Division
File Section Describes externally stored data (including sort-merge files)

Working-Storage Section Describes internal data

Linkage Section Describes data made available by another program.

- 39 -

COBOL/400

Data Division
Coding Example: DATA DIVISION. FILE SECTION. FD DISPLAY-FILE. 01 DISPLAY-REC COPY DD-ALL-FORMATS OF TESTDSPF. FD PHY-FILE1. 01 PHY-FILE1-RCD. COPY DDS-ALL-FORMATS OF PHYSICAL1. FD PHY-FILE2. 01 PHY-FILE2-REC. COPY DDSR-ALL-FORMATS OF PHYSICAL2.

- 40 -

COBOL/400

Data Division
WORKING-STORAGE SECTION. FD DISPLAY-FILE. 01 PHYSICAL2-PARMS. 05 PHYSICAL2-PRODCD 05 PHYSICAL2-INV 05 PHYSICAL2-STATUS 88 PHYSICAL2-NONE-FOUND 88 PHYSICAL2-ALL-VERIFIED 88 PHYSICAL2-UNVERIFIED 77 ERR-MESSAGE

PIC X(04). PIC S9(03). PIC X(01). VALUE "0". VALUE "1". VALUE "2". PIC X(80) VALUE SPACES.

- 41 -

COBOL/400

Data Division
LINKAGE SECTION. 01 FUNCTION-MEMBER. 05 FUNCTION-CODE 88 END-OF-PGM 88 ENTRY-OPERATION 88 VERIFY-OPERATION 05 MEMBER-CODE 88 ENTRY-MEMBER 88 CLUSTER-MEMBER 01 USER-ID 01 JOB-NUMBER

PIC X. VALUE SPACES. VALUE "E". VALUE "V". PIC X. VALUE "E". VALUE "C". PIC X(10). PIC X(10).

- 42 -

COBOL/400

File Section
For all files except sort/merge, the File Section must contain an FD (File Description) entry For each sort or merge file, the File Section must contain an SD (Sort Description) entry

- 43 -

COBOL/400

File Section
file-description-entry
Represent the highest level of organization in the File Section Provide information about the physical structure and identification of a file, and gives the recordname(s) associated with that file

- 44 -

COBOL/400

File Section
record-description-entry A set of data description entries that describe the particular record(s) contained within a particular file More than one record description entry may be specified; each is an alternative description of the same record storage area Data areas described in the File Section are not available for processing unless the file containing the data area is open The initial value of a data item in the File Section is undefined

- 45 -

COBOL/400

File Section
file-name Must follow the level indicator (FD or SD), and must be the same as that specified in the associated SELECT clause The file-name must be unique within this program One or more record description entries must follow the file-name. When more than one record description entry is specified, each entry implies a redefinition of the same storage area The clauses that follow file-name are optional; they may appear in any order

- 46 -

COBOL/400

File Section
BLOCK CONTAINS Clause Specify the size of the physical records If the records in the file are not blocked, the clause may be omitted This clause is always active for tape files, but is syntax-checked only for diskette files

- 47 -

COBOL/400

File Section
RECORDS Specify the number of logical records contained in each physical record Maximum record size is 32766; maximum block size is 32766

- 48 -

COBOL/400

File Section
RECORD CONTAINS Clause Specify the number of character positions for fixed length records

- 49 -

COBOL/400

File Section
RECORD CONTAINS Clause Specify the number of character positions for fixed length records When the record length determined from the record description entries does not match the length specified in the RECORD CONTAINS clause, the former will be used

- 50 -

COBOL/400

File Section
LABEL RECORDS Clause Indicate the presence or absence of labels If it is not specified for a file, label records for that file must conform to the system label specifications Generally treated as documentation
STANDARD Labels conforming to system specifications exist for this file OMITTED No labels exist for this file Note: The LABEL RECORDS clause is an obsolete element and is to be deleted from the next revision of the ANSI Standard

- 51 -

COBOL/400

File Section
VALUE OF Clause Describe an item in the label records associated with this file The clause is syntax checked, then treated as documentation

Note: The VALUE OF clause is an obsolete element and will be deleted Standard

from the next revision of the ANSI

- 52 -

COBOL/400

Data Types
File Data (External Data) File data is contained in files

Program Data (Internal Data) Program data is created by the program itself

- 53 -

COBOL/400

Data Types
Data Relationships The relationships among all data to be used in a program are defined in the Data Division, through a system of level indicators and level-numbers A level indicator, with its descriptive entry, identifies each file in a program. Level indicators represent the highest level of any data hierarchy with which they are associated; FD is the file description level indicator and SD is the sort-merge file description level indicator A level-number, with its descriptive entry, indicates the properties of specific data

- 54 -

COBOL/400

Data Types
Levels of Data After a record has been defined, it can be subdivided to provide more detailed data references A system of level-numbers specifies the organization of elementary and group items into records. Special level- numbers are also used; they identify data items used for special purposes

- 55 -

COBOL/400

Data Types
A level-number is a 1- or 2-digit integer between 01 and 49, or one of three special level-numbers: 66, 77, or 88 The following level-numbers are used to structure records: 01 Specify the record itself, and is the most inclusive levelnumber possible. A level-01 entry may be either a group item or an elementary item 02-49Specify group and elementary items within a record

- 56 -

COBOL/400

Data Types
Special Level-Numbers Special level-numbers identify items that do not structure a record. The special level-numbers are: 66 Identifies items that must contain a RENAMES clause; previously defined data items such items regroup

77 Identifies data item description entries independent WorkingStorage or Linkage Section items that are not subdivisions of other items, and are not sub-divided themselves 88 Identifies any condition-name entry that is associated value of a conditional variable with a particular

- 57 -

COBOL/400

Data Types
BLANK WHEN ZERO Clause Specify that an item contains nothing but spaces when its value is zero Specify only for elementary numeric or numeric-edited items These items must be described, either implicitly or explicitly, as USAGE IS DISPLAY. When this clause is specified for a numeric item, the item is considered a numeric-edited item Must not be specified for level-66 or level-88 items Not allowed for items described with the USAGE IS INDEX clause or the USAGE IS POINTER clause

- 58 -

COBOL/400

Data Types
JUSTIFIED Clause Override standard positioning rules for a receiving item of the alphabetic or alphanumeric categories May be specified only at elementary level. JUST is an abbreviation for JUSTIFIED, and has the same meaning. RIGHT is an optional word and has no effect on the execution of the program Cannot be specified for numeric, numeric-edited, or alphanumeric-edited items Must not be specified with level-66 (RENAMES) and level-88 (condition-name) entries

- 59 -

COBOL/400

Data Types
Coding Example:
01 WS-DATE628-PARMS. 05 CVTDATE 05 RTNDATE 05 DTERR

PIC X(6) JUSTIFIED RIGHT. PIC X(8). PIC X.

- 60 -

COBOL/400

Data Types
LIKE Clause Define the PICTURE, USAGE, and SIGN characteristics of a data item by copying them from a previously defined data item Make the length of the data item you define different from the length of the original item Cause the new data item to inherit specific characteristics from the existing data item. These characteristics are the PICTURE, USAGE, SIGN, and BLANK WHEN ZERO attributes of the existing item

- 61 -

COBOL/400

Data Types
Coding Example:
01 EMPLOYEE-RECORDS PIC 1. 88 MORE-EMPLOYEE-RECORDS 88 NO-MORE-EMPLOYEE-RECORDS 01 NEW- EMPLOYEE -REC. 05 NEW-EMPLOYEE-RECORD

VALUE B"1". VALUE B"0".

LIKE

EMPLOYEE-RECORD.

01 WS-CNT1 01 WS-CNT2

PIC S9(3). Like WS-CNT1.

- 62 -

COBOL/400

Data Types
PICTURE Clause Specify the general characteristics and editing requirements of an elementary item Must be specified for every elementary item except an index data item or the subject of the RENAMES clause The PICTURE character-string may contain a max of 30 chars

- 63 -

COBOL/400

Data Types
Coding Example:
LINKAGE SECTION. 01 FROMDATE. 05 FROMMM 05 FROMDD 05 FROMYY 01 TODATE. 05 TOMM 05 TODD 05 TOYY 01 DAYS 01 STATUS-CODE

PIC 99. PIC 99. PIC 99. PIC 99. PIC 99. PIC 99. PIC S9(7) COMP-3. PIC 1.

- 64 -

COBOL/400

Data Types
REDEFINES Clause To use different data description entries to describe the same computer storage area

- 65 -

COBOL/400

Data Types
Coding Example:
01 TODAYS-DATE. 05 DATE-YY PIC XX. 05 DATE-MM 05 DATE-DD 01 TODAYS-DATE-HOLD

PIC XX. PIC XX. REDEFINES TODAYS-DATE

PIC 9(6).

01 01

TODAYS-DATE PIC X(6). TODAYS-DATE-HOLD 05 DATE-YY PIC XX. 05 DATE-MM 05 DATE-DD

REDEFINES TODAYS-DATE. PIC XX. PIC XX.

- 66 -

COBOL/400

Data Types
RENAMES Clause Specify alternative, possibly overlapping, groupings of elementary data items The special level-number 66 must be specified for data description entries that contain the RENAMES clause One or more RENAMES entries can be written for a logical record

- 67 -

COBOL/400

Data Types
Coding Example:
INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT EMPLOYEE ASSIGN TO DATABASE-EMPLOYEE ACCESS IS DYNAMIC RECORD KEY IS EMPID FILE STATUS IS WS-EMPLOYEE-STATUS. FILE SECTION. FD EMPLOYEE 01 EMP-REC. COPY DDS-EMPREC OF EMPLOYEE. 66 EMPID RENAMES EMPNO IN EMP-REC THRU DOJ IN EMP-REC.

ORGANIZATION IS INDEXED

- 68 -

COBOL/400

Data Types
Coding Example:
MOVE WS-EMPNO TO EMPNO OF EMP-REC. MOVE WS-DOJ TO DOJ OF EMP-REC. IF WS-EMPNO > ZERO THEN SET ONE-EMPOYEE TO TRUE. START EMPLOYEE KEY NOT < EMPID INVALID KEY MOVE Invalid Emp No. TO WS-ERR.MSG END-START.

- 69 -

COBOL/400

Data Types
SIGN Clause Specify the position and mode of representation of the operational sign for a numeric entry

- 70 -

COBOL/400

Data Types
USAGE Clause Specify for an entry at any level. However, if it is specified at the group level, it applies to each elementary item in the group

- 71 -

COBOL/400

Data Types
Coding Example:
01 EMPLOYEE-WORK-FIELDS. 05 EMPLOYEE-FILE-STATUS 05 EMPLOYEE-END-OF-PAGE 05 EMPLOYEE-SALARY

PIC X(2). PIC X(1) VALUE "N". PIC 9(7) USAGE PACKED-DECIMAL VALUE ZERO.

01 EMPLOYEE-WORK-FIELDS. 05 EMPLOYEE-FILE-STATUS 05 EMPLOYEE-RRN

PIC X(2). PIC 9(5) USAGE IS COMP.

01

RECORD-COUNT

PIC S9(10)V9(5) COMP-3 VALUE 0.

- 72 -

COBOL/400

Data Types
Computational Items Value used in arithmetic operations Must be numeric The maximum length of a computational item is 18 decimal digits

- 73 -

COBOL/400

Data Types
BINARY

Specified for binary data items

PACKED-DECIMAL

Specified for internal decimal items

COMPUTATIONAL or COMP

Specified for internal decimal items

COMPUTATIONAL-3 or COMP-3 (internal decimal)

This is the equivalent of PACKED-DECIMAL

COMPUTATIONAL-4 or COMP-4 (binary)

This is the equivalent of BINARY

- 74 -

COBOL/400

Data Types
VALUE Clause Specify the initial contents of a data item or the value(s) associated with a condition-name Use of the VALUE clause differs depending on the Data Division section in which it is specified; In the File and Linkage sections, the VALUE clause must be used only in condition-name entries; in the Working-Storage Section, the VALUE clause may be used in condition-name entries, or in specifying the initial value of any data item The data item assumes the specified value at the beginning of program execution. If the initial value is not explicitly specified, it is unpredictable

- 75 -

COBOL/400

Working-Storage Section
The Working-Storage Section describes data records that are not part of external data files but are developed and processed internally The Working-Storage Section contains record description entries and data description entries for independent data items, called data item description entries

- 76 -

COBOL/400

Working-Storage Section
record-description-entry
Data entries in the Working-Storage Section that bear a definite hierarchic relationship to one another must be grouped into records structured by level number

- 77 -

COBOL/400

Working-Storage Section
data-item-description-entry
Independent items in the Working-Storage Section that bear no hierarchic relationship to one another need not be grouped into records, provided that they do not need to be further subdivided. Instead, they are classified and defined as independent elementary items. Each is defined in a separate data-item description entry that begins with either the level number 77 or 01

- 78 -

COBOL/400

Working-Storage Section
The initial value of any data item in the Working-Storage Section, except an index data item, is specified by associating a VALUE clause with the item The initial value of any index data item, or of any data item not associated with a VALUE clause, is undefined

- 79 -

COBOL/400

Linkage Section
Describe data made available from another program Record description entries and data item description entries in the Linkage Section provide names and descriptions, but storage within the program is not reserved because the data area exists elsewhere Any data description clause may be used to describe items in the Linkage Section, with one exception: the VALUE clause may not be specified for items other than level-88 items

- 80 -

COBOL/400

Linkage Section
Coding Example:
LINKAGE SECTION. 01 FROMDATE. 05 FROMMM PIC 99. 05 FROMDD PIC 99. 05 FROMYY PIC 99. 01 TODATE. 05 TOMM PIC 99. 05 TODD PIC 99. 05 TOYY PIC 99. 01 DAYS PIC S9(7) COMP-3. 01 STATUS-CODE PIC 1.

- 81 -

COBOL/400

COBOL - DIVISION4
Procedure Division Consists of optional declaratives, and procedures that contain sections and/or paragraphs, sentences, and statements

- 82 -

COBOL/400

Procedure Division
Procedure Division Header The USING Phrase Required only if the object program is to be invoked by a CALL statement and that statement includes a USING phrase Makes data items defined in a calling program available to a called subprogram Each USING identifier must be defined as a level-01 or level-77 item in the Linkage Section of the called subprogram Must not contain a REDEFINES clause Maximum number of data-names - 30

- 83 -

COBOL/400

Procedure Division
Declaratives Provide one or more special-purpose sections that are executed when an exceptional condition occurs When Declarative Sections are specified, they must be grouped at the beginning of the Procedure Division, and the entire Procedure Division must be divided into sections

- 84 -

COBOL/400

Procedure Division
Procedures Within the Procedure Division, a procedure consists of:
A section or a group of sections A paragraph or group of paragraphs

A procedure-name is a user-defined name that identifies a section or a paragraph

- 85 -

COBOL/400

Procedure Division
Section A section header optionally followed by one or more paragraphs Section-header A section-name followed by:
the keyword SECTION an optional segment-number a separator period

- 86 -

COBOL/400

Procedure Division
Section-name A user-defined word that identifies a section If referenced, a section-name must be unique within the program in which it is defined

- 87 -

COBOL/400

Procedure Division
Paragraph A paragraph-name followed by a separator period, optionally followed by one or more sentences Paragraph-name A user-defined word that identifies a paragraph

- 88 -

COBOL/400

Procedure Division
Sentence One or more statements terminated by a separator period Statement A syntactically valid combination of identifiers and symbols beginning with a COBOL verb

- 89 -

COBOL/400

Procedure Division
Identifier A syntactically correct combination of a data name In any Procedure Division reference, the contents of an identifier must be compatible with the class specified through its PICTURE clause, or results are unpredictable

- 90 -

COBOL/400

Procedure Division
Coding Example:
PROCEDURE DIVISION. DECLARATIVES. ERROR-IT SECTION. USE AFTER STANDARD ERROR PROCEDURE ON INPUT-DATA. ERROR-ROUTINE. IF CHECK-IT = "30" ADD 1 TO DECLARATIVE-ERRORS. END DECLARATIVES.

- 91 -

COBOL/400

Procedure Division
Common Phrases There are several phrases common to arithmetic and data manipulation statements; these phrases are described below CORRESPONDING Phrase Allows ADD, SUBTRACT, and MOVE operations to be performed on elementary data items of the same name if the group items to which they belong are specified Both identifiers following the key word CORRESPONDING must name group items

- 92 -

COBOL/400

Procedure Division
Coding Example:
MOVE CORRESPONDING DATE-YYMMDD TO DATE-WITH-SLASHES.

01 DATE-YYMMDD. 05 YY 05 MM 05 DD 01 DATE-WITH-SLASHES. 05 MM 05 SLASHA 05 DD 05 SLASHB 05 YY

PIC XX. PIC XX. PIC XX.

PIC XX. PIC X VALUE "/". PIC XX. PIC X VALUE "/". PIC XX.

- 93 -

COBOL/400

Procedure Division
GIVING Phrase The value of the identifier that follows the word GIVING is set equal to the calculated result of the arithmetic operation Because this identifier is not involved in the computation, it may be a numeric edited item

- 94 -

COBOL/400

Procedure Division
Coding Example:
SUBTRACT SUB1 FROM SUB2 GIVING RESULT. DIVIDE NUM1 BY 10 GIVING RESULT.

- 95 -

COBOL/400

Procedure Division
ROUNDED Phrase After decimal point alignment, the number of places in the fraction of the result of an arithmetic operation is compared with the number of places provided for the fraction of the resultant identifier When the size of the fractional result exceeds the number of places provided for its storage, truncation occurs unless ROUNDED is specified. When ROUNDED is specified, the least significant digit of the resultant identifier is increased by 1 when-ever the most significant digit of the excess is greater than or equal to 5

- 96 -

COBOL/400

Procedure Division
Coding Example:
DIVIDE NUM1 BY 10 GIVING RESULT ROUNDED. COMPUTE RESULT ROUNDED = NUM1 * NUM2.

- 97 -

COBOL/400

Procedure Division
SIZE ERROR Phrases A size error condition can occur in three different ways:
When the absolute value of the result of an arithmetic evaluation, after decimal point alignment, exceeds the largest value that can be contained in the result field When division by zero occurs In an exponential expression, when
Zero raised to the exponent Zero Zero raised to a negative exponent A negative number raised to a fractional exponent

The size error condition applies only to final results, not to any intermediate results

- 98 -

COBOL/400

Procedure Division
Coding Example:
ADD 1 TO NUM1 ON SIZE ERROR MOVE 0 TO NUM1

- 99 -

COBOL/400

Procedure Division
Input-Output Statements Transfer data to and from files stored on external media Control low-volume data that is obtained from or sent to an input/output device Common Processing Facilities Applied to more than one input-output statement:
Status key INVALID KEY condition INTO/FROM identifier phrase File position indicator

- 100 -

COBOL/400

Procedure Division
Status Key If the FILE STATUS clause is specified in the FILE-CONTROL entry, a value is placed in the specified status key (the 2-character data item named in the FILE STATUS clause) during execution of any request on that file, which indicates the status of that request The value is placed in the status key before execution of any EXCEPTION/ERROR declarative or INVALID KEY/AT END phrase associated with the request

- 101 -

COBOL/400

Procedure Division
Coding Example:
ENVIRONMENT DIVISION. INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT PROJECT-FILE ASSIGN TO DATABASE_PROJECT ORGANIZATION IS INDEXED ACCESS MODE IS DYNAMIC RECORD KEY IS EXTERNALLY-DESCRIBED-KEY FILE STATUS IS WS-PROJECT-FILE-STATUS.

DATA DIVISION. WORKING-STORAGE SECTION. 01 WS-PROJECT-FILE-STATUS 88 WS-IO-SUCCESSFUL 88 WS-END-OF-FILE 88 WS-INVALID-KEY 88 WS-IO-ERROR

PIC XX. VALUE "00" THRU "09". VALUE "10" THRU "19". VALUE "20" THRU "29". VALUE "30" THRU "99".

- 102 -

COBOL/400

Procedure Division
INVALID KEY Condition Can occur during execution of a START, READ, WRITE, REWRITE, or DELETE statement When occurs, the input-output statement that caused the condition is unsuccessful

- 103 -

COBOL/400

Procedure Division
Coding Example:
READ PROJECT RECORD INVALID KEY MOVE "N" TO PROJECT-RECORD-FOUND NOT INVALID KEY MOVE "Y" TO PROJECT-RECORD-FOUND END-READ. IF WS-PROJECT-FILE-STATUS >= "30" MOVE "N" TO PROJECT-RECORD-FOUND END-IF.

- 104 -

COBOL/400

Procedure Division
INTO/FROM Identifier Phrase Valid for READ, RETURN, RELEASE, REWRITE, and WRITE statements The identifier specified must be the name of an entry in the Working-Storage Section or the Linkage Section, or of a record description for another previously opened file Record-name/file-name and identifier must not refer to the same storage area The INTO phrase may be specified in a READ or RETURN statement The FROM phrase may be specified in a RELEASE, REWRITE, or WRITE statement

- 105 -

COBOL/400

Procedure Division
Coding Example:
READ PROJECT RECORD INTO WS-PROJECT FORMAT IS "PROJECT1" INDICATORS ARE WS-INDICATOR-TABLE END-READ. REWRITE SUBFILE PROJECT-RCD FROM WS-PROJECT1SFL-O FORMAT IS PROJECT11SFL" INDICATORS ARE WS-INDICATOR-TABLE INVALID KEY CONTINUE END-REWRITE.

- 106 -

COBOL/400

Procedure Division
Procedure Division Statements ACCEPT Statement Transfer data into the specified identifier No editing or error checking of the incoming data

- 107 -

COBOL/400

Procedure Division
Coding Example:
ACCEPT SYSTEM-DATE FROM DATE. ACCEPT SYSTEM-TIME FROM TIME.

- 108 -

COBOL/400

Procedure Division
ACQUIRE Statement Acquire a program device for a TRANSACTION file

- 109 -

COBOL/400

Procedure Division
ADD Statement Sum two or more numeric operands and stores the result

- 110 -

COBOL/400

Procedure Division
Coding Example:
ADD 1 TO PROJECT-COUNTER.

- 111 -

COBOL/400

Procedure Division
CALL Statement Transfer control from one object program to another within the run unit Pass control to the first non-declarative instruction of the called subprogram Called subprograms themselves can contain CALL statements, but a called subprogram that contains a CALL statement that directly or indirectly calls the calling program gives unpredictable results

- 112 -

COBOL/400

Procedure Division
Coding Example:
CALL "XXXVALIDDT" USING DATE-CHECK.

- 113 -

COBOL/400

Procedure Division
CANCEL Statement Ensure that the next time the referenced subprogram is called it will be entered in its initial state Close all open files Operate only on the program specified, and not on any program that may have been called by the canceled program No action is taken when a CANCEL statement is executed, naming a program that has not been called in the run unit, or that names a program that was called and subsequently canceled. In either case, control passes to the next statement If names a program that does not exist in the library list, an error message is issued

- 114 -

COBOL/400

Procedure Division
Coding Example:
CANCEL "XXXVALIDDT.

- 115 -

COBOL/400

Procedure Division
CLOSE Statement Terminate the processing of volumes and files, with optional rewind and/or lock or removal, where applicable Terminate the processing of volumes and files, with optional rewind and/or lock or removal, where applicable If the file is in an open status and the execution of a CLOSE statement is unsuccessful, the EXCEPTION/ERROR procedure (if specified) for this file is executed If a CLOSE statement for an open file is not processed before a STOP RUN for this run unit, the file is implicitly closed

- 116 -

COBOL/400

Procedure Division
Coding Example:
CLOSE PROJECT.

- 117 -

COBOL/400

Procedure Division
COMMIT Statement Provide a way of synchronizing changes to data base records while preventing other jobs from modifying those records until the COMMIT is performed All record locks held by the job since the last commitment boundary for files under commitment control are released and the records become available to other jobs Only affect files under commitment control If a COMMIT is executed and there are no files opened under commitment control, the COMMIT statement has no effect and no commitment boundary is established

- 118 -

COBOL/400

Procedure Division
COMPUTE Statement

Assign the value of an arithmetic expression to one or more data items

With the COMPUTE statement, arithmetic operations can be combined without the restrictions on receiving data items imposed by the rules for the ADD, SUBTRACT, MULTIPLY, and DIVIDE statements

- 119 -

COBOL/400

Procedure Division
Coding Example:
COMPUTE RESULT = NUM1 - 1.

- 120 -

COBOL/400

Procedure Division
CONTINUE Statement Allow to specify a no operation statement Indicate that no executable instruction is present May be used anywhere a conditional statement Has no effect on the execution of the program

- 121 -

COBOL/400

Procedure Division
Coding Example:
READ PROJECT INVALID KEY CONTINUE END-READ.

- 122 -

COBOL/400

Procedure Division
DELETE Statement Remove a record from an indexed or relative file For indexed files, the key may then be reused for record addition For relative files, the space is then available for a new record with the same RELATIVE KEY value File must be open in I-O mode Record is logically removed from the file and can no longer be accessed

- 123 -

COBOL/400

Procedure Division
Coding Example:
DELETE PROJECT-FILE RECORD INVALID KEY MOVE "N" TO WS-PROJRCT-RECORD-FOUND NOT INVALID KEY MOVE "Y" TO WS-PROJECT-RECORD-FOUND END-DELETE

- 124 -

COBOL/400

Procedure Division
DISPLAY Statement Transfer the contents of each operand to the output device Contents are displayed on the output device in the order, left to right, in which the operands are listed

- 125 -

COBOL/400

Procedure Division
Coding Example:
DISPLAY IO-ERR-MSG UPON CNSL. DISPLAY USER-MSG.

SPECIAL-NAMES. SYSTEM-CONSOLE IS CNSL.

- 126 -

COBOL/400

Procedure Division
DIVIDE Statement Divide one numeric data item into or by one or more others, and sets the values of data items equal to the quotient and remainder

- 127 -

COBOL/400

Procedure Division
Coding Example:
DIVIDE WS-HOURS BY 24 GIVING WS-DAYS REMAINDER WS-REMAINDER-HOURS.

- 128 -

COBOL/400

Procedure Division
EVALUATE Statement Provide a shorthand notation for a series of nested IF statements

- 129 -

COBOL/400

IF (MENU-INPUT = 0") THEN PERFORM INIT-PROC ELSE IF (MENU-INPUT >= "1") AND (MENU-INPUT <= "9") THEN PERFORM PROCESS-PROC ELSE IF (MENU-INPUT = "R") THEN PERFORM READ-PARMS ELSE IF (MENU-INPUT = "X") THEN PERFORM CLEANUP-PROC ELSE PERFORM ERROR-PROC END-IF END-IF END-IF END-IF.

EVALUATE MENU-INPUT WHEN 0" PERFORM INIT-PROC WHEN "1" THRU "9" PERFORM PROCESS-PROC WHEN "R" PERFORM READ-PARMS WHEN "X" PERFORM CLEANUP-PROC WHEN OTHER PERFORM ERROR-PROC END-EVALUATE.

- 130 -

COBOL/400

Procedure Division
EXIT Statement Provide a common end point for a series of paragraphs

- 131 -

COBOL/400

Procedure Division
Coding Example:
200-PROCESS. IF PROJECT-FOUND = Y" PERFORM 250-PARA1 ELSE PERFORM 260-PARA2 END-IF. 200-EXIT. EXIT.

- 132 -

COBOL/400

Procedure Division
EXIT PROGRAM Statement Specify the end of a called program and returns control to the calling program When there is no next executable statement in a called program, an implicit EXIT PROGRAM statement is executed

- 133 -

COBOL/400

Procedure Division
Coding Example:
END-OF-JOB. IF NO-PROJ-ERROR THEN CLOSE PROJECT. IF NO-DISPLAY-ERROR THEN CLOSE DISPLAY-FILE. EOJ-EXIT. EXIT PROGRAM. STOP RUN.

- 134 -

COBOL/400

Procedure Division
GOBACK Statement Function like the EXIT PROGRAM statement when it is coded as part of a program that is a subprogram in a COBOL run unit, and like the STOP RUN statement when coded in a program that is a main program in a COBOL run unit Specify the logical end of a program

- 135 -

COBOL/400

Procedure Division
Coding Example:
PROCEDURE DIVISION USING LINK-PARMS. 100-MAIN. IF PROJECT-FOUND = Y" PERFORM 150-PARA1 ELSE PERFORM 250-PARA2 END-IF. GOBACK. 100-EXIT. EXIT.

- 136 -

COBOL/400

Procedure Division
GO TO Statement Transfer control from one part of the Procedure Division to another Three types of GO TO statements: 1. Unconditional 2. Conditional 3. Altered (Obsolete)

- 137 -

COBOL/400

Procedure Division
Coding Example:
IF PROJECT1 NOT = PROJECT2 THEN GO TO 220-READ-NEXT-PROJECT END-IF

- 138 -

COBOL/400

Procedure Division
IF Statement Evaluate a condition and provides for alternative actions in the object program, depending on the evaluation

- 139 -

COBOL/400

Procedure Division
Coding Example:
IF (MENU-INPUT >= "1") AND (MENU-INPUT <= "9") THEN PERFORM PROCESS-PROC ELSE IF (MENU-INPUT = "R") THEN PERFORM READ-PARMS END-IF END-IF.

- 140 -

COBOL/400

Procedure Division
INITIALIZE Statement Sets selected categories of data fields to predetermined values Functionally equivalent to one or more MOVE statements

- 141 -

COBOL/400

Procedure Division
Coding Example:
INITIALIZE PROJECT1-FIELD1. INITIALIZE PROJECT1.

- 142 -

COBOL/400

Procedure Division
INSPECT Statement Specify that characters in a data item are to be counted (tallied) or replaced or both Count the occurrence of a specific character (alphabetic, numeric, or special character) in a data item Fill all or portions of a data item with spaces or zeros Translate characters from one collating sequence to another

- 143 -

COBOL/400

Procedure Division
Coding Example:
INSPECT WS-PAGE-IN-ERROR REPLACING LEADING ZEROS BY SPACES. INSPECT PROJECT1-FIELD1 TALLYING WS-SPACE-CNTR FOR ALL .

- 144 -

COBOL/400

Procedure Division
MERGE Statement Combine two or more identically sequenced files (that is, files that have already been sorted according to an identical set of ascending/ descending keys) on one or more keys and makes records available in merged order to an output procedure or output file May appear anywhere in the Procedure Division except in a Declarative Section

- 145 -

COBOL/400

Procedure Division
MOVE Statement Transfer data from one area of storage to one or more other areas

- 146 -

COBOL/400

Procedure Division
Coding Example:
MOVE NUM1 TO NUM2 MOVE "MISSING OR INVALID VALUE" TO WS-ERROR-MESSAGE.

- 147 -

COBOL/400

Procedure Division
MULTIPLY Statement Multiplies numeric items and sets the values of data items equal to the results

- 148 -

COBOL/400

Procedure Division
Coding Example:
MULTIPLY NUM1 BY NUM2 GIVING RESULT.

- 149 -

COBOL/400

Procedure Division
OPEN Statement Initiate the processing of files Vary depending on the type of file:
Sequential files Indexed files Relative files Transaction files

- 150 -

COBOL/400

Procedure Division
Sequential files At least one of the phrases, INPUT, OUTPUT, I-O, or EXTEND, must be specified with the OPEN keyword The INPUT, OUTPUT, I-O, and EXTEND phrases may appear in any order Indexed and Relative Files At least one of the phrases, INPUT, OUTPUT, or I-O, must be specified with the OPEN keyword. The INPUT, OUTPUT, and I-O phrases may appear in any order Transaction Files A TRANSACTION file must be opened in the I-O mode

- 151 -

COBOL/400

Procedure Division
Coding Example:
OPEN I-O FILE1. OPEN INPUT FILE2, FILE3. OPEN OUTPUT FILE4.

- 152 -

COBOL/400

Procedure Division
PERFORM Statement Transfer control explicitly to one or more procedures and implicitly returns control to the next executable statement after execution of the specified procedure(s) or imperative statements is completed 4 PERFORM statement formats:
1. 2. 3. 4. Basic PERFORM TIMES phrase PERFORM UNTIL phrase PERFORM VARYING phrase PERFORM

- 153 -

COBOL/400

Procedure Division
Coding Example:
PERFORM 110-INITIALIZATION. PERFORM 300-LOAD-PROJECTS VARYING CNT1 FROM 1 BY 1 UNTIL CNT1 > PROJECT-COUNT END-PERFORM.

- 154 -

COBOL/400

Procedure Division
READ Statement Make a record available to the program Associated file must be open in INPUT or I-O mode For sequential access, the READ statement makes the next logical record from a file available to the object program For random access, the READ statement makes a specified record from a direct-access file available to the object program

- 155 -

COBOL/400

Procedure Division
Coding Example:
READ PROJECT-FILE INVALID KEY SET INVALID-PROJ TO TRUE END-READ. READ PROJECT-FILE-L NEXT RECORD AT END PERFORM 300-END-OF-FILE-PROCESSING END-READ . READ PROJECT-FILE AT END SET END-OF-FILE TO TRUE END-READ.

- 156 -

COBOL/400

Procedure Division
RELEASE Statement Transfer records from an input/output area to the initial phase of a sorting operation Can only be used within the range of an input procedure associated with a SORT statement

- 157 -

COBOL/400

Procedure Division
RETURN Statement Transfer records from the final phase of a sort or merge operation to an OUTPUT PROCEDURE Can be used only within the range of an output procedure associated with a SORT or MERGE statement

- 158 -

COBOL/400

Procedure Division
REWRITE Statement Logically replace an existing record in a direct-access file Associated direct-access file must be open in I-O mode

- 159 -

COBOL/400

Procedure Division
REWRITE Statement for Sequential Files When the access mode is sequential, the last prior input/output statement executed for this file must be a successfully executed READ statement. When the REWRITE statement is executed, the record retrieved by that READ statement is logically replaced The INVALID KEY phrase must not be specified for a file with sequential organization An EXCEPTION/ERROR procedure may be specified

- 160 -

COBOL/400

Procedure Division
REWRITE Statement for Indexed Files When the access mode is sequential, the record to be replaced is specified by the value contained in the prime RECORD KEY. When the REWRITE statement is executed, this value must equal the value of the prime record key data item in the last record read from this file The INVALID KEY phrase must be specified if an applicable USE AFTER STANDARD EXCEPTION procedure is not specified for the associated file-name

- 161 -

COBOL/400

Procedure Division
REWRITE Statement for Relative Files For relative files in sequential access mode, the INVALID KEY phrase must not be specified An EXCEPTION/ERROR procedure may be specified The INVALID KEY phrase must be specified in the REWRITE statement for relative files in the random or dynamic access mode, and for which an appropriate USE AFTER STANDARD EXCEPTION procedure is not specified When the access mode is random or dynamic, the record to be replaced is specified in the RELATIVE KEY data item If the file does not contain the record specified, an invalid key condition exists, and, if specified, the INVALID KEY imperative-statement is executed

- 162 -

COBOL/400

Procedure Division
Coding Example:
REWRITE PROJECT-RCD INVALID KEY CONTINUE END-REWRITE. REWRITE SUBFILE PROJECT-RCD FROM WS-LIST1SFL-O FORMAT IS "LIST1SFL" INDICATORS ARE WS-INDICATOR-TABLE INVALID KEY CONTINUE END-REWRITE.

- 163 -

COBOL/400

Procedure Division
ROLLBACK Statement Provide a way to cancel one or more changes to data-base records when the changes should not remain permanent Any changes made to files under commitment control since the last commitment boundary are removed from the database A commitment boundary is the previous occurrence of a ROLLBACK or COMMIT statement If no COMMIT or ROLLBACK has been issued, the commitment boundary is the first OPEN of a file under commitment control

- 164 -

COBOL/400

Procedure Division
Removal of changes takes place for all files under commitment control in the job, and not just for files under commitment control in the COBOL program that issues the ROLLBACK All record locks held by the job for files under commitment control are released and the records become available to other jobs Has no effect on files not under commitment control If a ROLLBACK is executed and there are no files under commitment control, the ROLLBACK is ignored A ROLLBACK, when executed, leaves files in the same open or closed state as before execution

- 165 -

COBOL/400

Procedure Division
SEARCH Statement Search a table for an element that satisfies the specified condition, and adjusts the associated index to indicate that element

- 166 -

COBOL/400

Procedure Division
Coding Example:
SEARCH PROJECT-TABLE AT END DISPLAY "TABLE OVERFLOW" SEARCH PROJECT-TABLE VARYING PROJECT-TABLE-INDEX

- 167 -

COBOL/400

Procedure Division
SET Statement Establish reference points for table handling operations by doing one of the following:
1. 2. 3. Placing values associated with table elements into indexes associated with index-names Incrementing or decrementing an occurrence number Setting the status of an external switch to ON or OFF

4.
5.

Moving data to condition names to make conditions true

Setting addresses of pointer data items

- 168 -

COBOL/400

Procedure Division
Coding Example:
SET PARM-ERROR-FOUND TO TRUE. READ PROJECT-RECORD AT END SET NO-MORE-RECORDS TO TRUE END-READ.

- 169 -

COBOL/400

Procedure Division
SORT Statement Accept records from one or more files, sorts them according to the specified key(s), and makes the sorted records available either through an OUTPUT PROCEDURE or in an output file

- 170 -

COBOL/400

Procedure Division
START Statement Provide a means of positioning within an indexed or relative file for subsequent sequential record retrieval This positioning is achieved by comparing the key values of records in the file with the value you place in the RECORD KEY portion of a files record area (for an indexed file), or in the RELATIVE KEY data item (for a relative file) prior to execution of the START statement

- 171 -

COBOL/400

Procedure Division
Coding Example:
START PROJECT-FILE KEY IS NOT LESS THAN EXTERNALLY-DESCRIBED-KEY INVALID KEY SET NO-MORE-RECORDS TO TRUE END-START.

- 172 -

COBOL/400

Procedure Division
STOP Statement Halts execution of the object program either permanently or temporarily

- 173 -

COBOL/400

Procedure Division
STRING Statement String together the partial or complete contents of two or more data items or literals into one single data item One STRING statement can be written instead of a series of MOVE statements

- 174 -

COBOL/400

Procedure Division
Coding Example:
STRING LASTNAME DELIMITED BY " " "," DELIMITED BY SIZE FIRSTNAME DELIMITED BY SIZE INTO USERNAME. STRING MM, "/", DD, "/", YY DELIMITED BY SIZE INTO CURR-DATE.

- 175 -

COBOL/400

Procedure Division
SUBTRACT Statement Subtract one numeric item, or the sum of two or more numeric items, from one or more numeric items, and stores the result

- 176 -

COBOL/400

Procedure Division
Coding Example:
SUBTRACT 1 FROM NUM1 SUBTRACT 1 FROM NUM1 GIVING RESULT.

- 177 -

COBOL/400

Procedure Division
UNSTRING Statement Cause contiguous data in a sending field to be separated and placed into multiple receiving fields One UNSTRING statement can be written instead of a series of MOVE statements

- 178 -

COBOL/400

Procedure Division
Coding Example:
UNSTRING NAME INTO NAME1 NAME2 NAME3. 01 NAME PIC X(60).

- 179 -

COBOL/400

Procedure Division
WRITE Statement Release a logical record for an output or input/output file When the WRITE statement is executed
the associated indexed or relative file must be open in OUTPUT, I-O, or EXTEND mode the associated sequential file must be open in OUTPUT or EXTEND mode

- 180 -

COBOL/400

Procedure Division
Coding Example:
WRITE ERROR-LINE FROM ERROR-REPORT-LINE AFTER ADVANCING 2 LINES END-WRITE. WRITE PROJECT-RECORD END-WRITE. WRITE PROJECT-RECORD FORMAT IS "LIST1CMD" INDICATORS ARE WS-INDICATOR-TABLE INVALID KEY CONTINUE END-WRITE.

- 181 -

COBOL/400

COBOL/400 Compiler Limits

Language Element Data Division Length of: COBOL/400 Limit

Working-Storage Section group item Linkage Section group item Elementary item

3 000 000 bytes 3 000 000 bytes 3 000 000 bytes

Procedure Division Number of:

GO TO proc-name IF nesting levels CALL parameters SORT-MERGE input files SORT-MERGE keys 255 30 30 31 30

- 182 -

COBOL/400

COBOL/400 Compiler Limits

Language Element COBOL/400 Limit

General Number of Files Number of characters to identify:

Library-name Program-name Text-name

99
10 10 10

Environment Division Number of:

SELECT file-names 99

- 183 -

COBOL/400

COBOL/400 Compiler Limits

Language Element Data Division Length of: COBOL/400 Limit

Working-Storage Section group item Linkage Section group item Elementary item

3 000 000 bytes 3 000 000 bytes 3 000 000 bytes

Procedure Division Number of:

GO TO proc-name IF nesting levels CALL parameters SORT-MERGE input files SORT-MERGE keys 255 30 30 31 30

- 184 -

COBOL/400

Thank You