Cobol Lang Ref

Enterprise COBOL for z/OS
Language Reference
V ersion 3 Release 3
SC27-1408-02
Language Reference
V ersion 3 Release 3
SC27-1408-02
Note! Before using this information and the product it supports, be sure to read the general information under Notices on page 579.
Third Edition (February 2004) This edition applies to Version 3 Release 3 of IBM Enterprise COBOL for z/OS (program number 5655-G53) and to all subsequent releases and modifications until otherwise indicated in new editions. Make sure that you are using the correct edition for the level of the product. You can order publications online at www.ibm.com/shop/publications/order/, or order by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. Eastern Standard Time (EST). The phone number is (800)879-2755. The fax number is (800)445-9269. You can also order publications through your IBM representative or the IBM branch office serving your locality. Copyright International Business Machines Corporation 1991, 2004. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . ix About this document . . . . . . . . . xi
Accessing softcopy documentation and support information . . . . . . . . . . . . . . xi Accessibility . . . . . . . . . . . . . . xi Using assistive technologies . . . . . . . . xi Keyboard navigation of the user interface . . . xi Accessibility of this document . . . . . . . xii IBM extensions . . . . . . . . . . . . . xii Obsolete language elements . . . . . . . . . xii How to read the syntax diagrams . . . . . . . xiii DBCS notation . . . . . . . . . . . . . xv Acknowledgment . . . . . . . . . . . . xv Summary of changes . . . . . . . . . . . xvi Version 3 Release 3 (February 2004) . . . . . xvi Version 3 Release 2 (September 2002) . . . . xvi Version 3 Release 1 (November 2001) . . . . xvi How to send your comments . . . . . . . . xvii XML-NTEXT . . . . XML-TEXT . . . . Literals . . . . . . . Alphanumeric literals . Numeric literals . . . DBCS literals . . . . National literals . . . PICTURE character-strings Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 24 25 25 29 30 31 33 34
Chapter 4. Separators . . . . . . . . 35
Rules for separators . . . . . . . . . . . 35
Chapter 5. Sections and paragraphs . . 39

Sentences, statements, Entries . . . . Clauses . . . . Sentences . . . Statements . . . Phrases . . . . and . . . . . . . . . . entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 39 40 40 40 40
Part 1. COBOL language structure . . 1

Chapter 1. Characters . . . . . . . . . 3 Chapter 2. Character sets and code pages . . . . . . . . . . . . . . . . 5
Character encoding units . . . . . . . . . . 5
Chapter 6. Reference format . . . . . 41

Sequence number area . . . . . . . . . . Indicator area . . . . . . . . . . . . . Area A . . . . . . . . . . . . . . . Division headers. . . . . . . . . . . Section headers . . . . . . . . . . . Paragraph headers or paragraph names . . . Level indicators (FD and SD) or level-numbers (01 and 77) . . . . . . . . . . . . DECLARATIVES and END DECLARATIVES . End program, end class, and end method markers . . . . . . . . . . . . . Area B . . . . . . . . . . . . . . . Entries, sentences, statements, clauses . . . Continuation lines . . . . . . . . . . Area A or Area B . . . . . . . . . . . Level-numbers . . . . . . . . . . . Comment lines . . . . . . . . . . . Compiler-directing statements . . . . . . Debugging lines . . . . . . . . . . . Pseudo-text . . . . . . . . . . . . Blank lines . . . . . . . . . . . . . . . . . . 41 41 42 42 42 42
Chapter 3. Character-strings . . . . . . 7
COBOL words with single-byte characters COBOL words with DBCS characters . . User-defined words . . . . . . . . System-names . . . . . . . . . . Function-names . . . . . . . . . Reserved words . . . . . . . . . Figurative constants . . . . . . . Special registers . . . . . . . . . ADDRESS OF . . . . . . . . DEBUG-ITEM . . . . . . . . JNIENVPTR . . . . . . . . . LENGTH OF . . . . . . . . . LINAGE-COUNTER . . . . . . RETURN-CODE . . . . . . . . SHIFT-OUT and SHIFT-IN . . . . SORT-CONTROL . . . . . . . SORT-CORE-SIZE . . . . . . . SORT-FILE-SIZE . . . . . . . . SORT-MESSAGE . . . . . . . SORT-MODE-SIZE . . . . . . . SORT-RETURN . . . . . . . . TALLY . . . . . . . . . . . WHEN-COMPILED . . . . . . XML-CODE . . . . . . . . . XML-EVENT . . . . . . . . .
Copyright IBM Corp. 1991, 2004
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . .
. 7 . 8 . 8 . 9 . 10 . 10 . 11 . 13 . 14 . 14 . 16 . 16 . 17 . 18 . 18 . 19 . 19 . 20 . 20 . 20 . 21 . 21 . 21 . 22 . 22
. 43 . 43 . . . . . . . . . . . 43 43 44 44 46 46 46 46 47 47 47
Chapter 7. Scope of names . . . . . . 49

Types of names . . . . . . . External and internal resources . . Resolution of names . . . . . Names within programs . . . Names within a class definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 51 52 52 53
Chapter 8. Referencing data names, copy libraries, and procedure division names . . . . . . . . . . . . . . . 55 iii
Uniqueness of reference . . . . . . Qualification . . . . . . . . . Identical names . . . . . . . . References to COPY libraries . . . References to procedure division names References to data division names . . Condition-name . . . . . . . . Index-name . . . . . . . . . Index data item . . . . . . . . Subscripting . . . . . . . . . Reference modification . . . . . Function-identifier . . . . . . . Data attribute specification . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
55 55 56 56 56 57 59 60 61 61 64 66 66
ALPHABET clause . . . . . . . . . . . 109 SYMBOLIC CHARACTERS clause . . . . . . 111 CLASS clause . . . . . . . . . . . . . 112 CURRENCY SIGN clause . . . . . . . . . 112 DECIMAL-POINT IS COMMA clause . . . . . 114 REPOSITORY paragraph . . . . . . . . . 114 General rules . . . . . . . . . . . . 115 Identifying and referencing the class . . . . . 115
Chapter 16. Input-Output section . . . 117

FILE-CONTROL paragraph . . . . . . . . SELECT clause . . . . . . . . . . . . ASSIGN clause . . . . . . . . . . . . Assignment name for environment variable . Environment variable contents for a QSAM file Environment variable contents for a line-sequential file . . . . . . . . . . Environment variable contents for a VSAM file RESERVE clause . . . . . . . . . . . ORGANIZATION clause . . . . . . . . File organization . . . . . . . . . . PADDING CHARACTER clause . . . . . . RECORD DELIMITER clause . . . . . . . ACCESS MODE clause . . . . . . . . . File organization and access modes . . . . Access modes . . . . . . . . . . . Relationship between data organizations and access modes . . . . . . . . . . . RECORD KEY clause . . . . . . . . . . ALTERNATE RECORD KEY clause . . . . . RELATIVE KEY clause . . . . . . . . . PASSWORD clause . . . . . . . . . . FILE STATUS clause . . . . . . . . . . I-O-CONTROL paragraph . . . . . . . . RERUN clause . . . . . . . . . . . . SAME AREA clause . . . . . . . . . . SAME RECORD AREA clause . . . . . . . SAME SORT AREA clause . . . . . . . . SAME SORT-MERGE AREA clause . . . . . MULTIPLE FILE TAPE clause . . . . . . . APPLY WRITE-ONLY clause . . . . . . . . . . . 118 121 122 123 124
Chapter 9. Transfer of control . . . . . 69 Chapter 10. Millennium Language Extensions and date fields . . . . . . 71
Millennium Language Extensions Terms and concepts. . . . . Date field . . . . . . . Nondate . . . . . . . Century window . . . . syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 72 72 73 73
Part 2. COBOL source unit structure . . . . . . . . . . . . . 75

Chapter 11. COBOL program structure
Nested programs . . . . . . . Conventions for program-names . . . . . . . . .
. 125 125 . 126 . 126 . 127 . 129 . 130 . 130 . 131 . 131 . . . . . . . . . . . . . . 131 132 133 134 135 135 136 138 139 140 141 141 141 142
77
. 79 . 80
Chapter 12. COBOL class definition structure . . . . . . . . . . . . . . 83 Chapter 13. COBOL method definition structure . . . . . . . . . . . . . . 87
Part 3. Identification division . . . . 89

Chapter 14. Identification division . . . 91
PROGRAM-ID paragraph . . . CLASS-ID paragraph . . . . . General rules . . . . . . . Inheritance . . . . . . . FACTORY paragraph . . . . . OBJECT paragraph . . . . . . METHOD-ID paragraph . . . . Method signature . . . . . Method overloading, overriding, Optional paragraphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and hiding . . . . . . . . . . . . . . . . . . . . . . . . 94 96 97 97 97 98 98 98 98 99
Part 5. Data division . . . . . . . 143

Chapter 17. Data division overview
File section . . . . . . Working-storage section . . Local-storage section . . . Linkage section . . . . . Data units . . . . . . File data . . . . . . Program data . . . . Method data . . . . Factory data . . . . . Instance data . . . . Data relationships . . . . Levels of data . . . . Levels of data in a record Special level-numbers . Indentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . entry . . . . . . . . . . . . . . . . . . .
145
. . . . . . . . . . . . . . . 146 147 148 149 149 149 150 150 150 150 150 151 151 153 153
Part 4. Environment division . . . 101

Chapter 15. Configuration section . . 103
SOURCE-COMPUTER paragraph OBJECT-COMPUTER paragraph . SPECIAL-NAMES paragraph . . . . . . . . . . . . . . . . . . 104 . 104 . 106
iv
Language Reference
Classes and categories of data . Alignment rules . . . . . Character-string and item size . Signed data . . . . . . . Operational signs . . . . . Editing signs . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
153 154 155 156 156 156
Chapter 18. Data divisionfile description entries . . . . . . . . . 157

File section . . . . . . . . . . EXTERNAL clause . . . . . . . GLOBAL clause . . . . . . . . BLOCK CONTAINS clause . . . . . RECORD clause . . . . . . . . Format 1 . . . . . . . . . . Format 2 . . . . . . . . . . Format 3 . . . . . . . . . . LABEL RECORDS clause . . . . . VALUE OF clause . . . . . . . . DATA RECORDS clause . . . . . . LINAGE clause . . . . . . . . . LINAGE-COUNTER special register . RECORDING MODE clause . . . . CODE-SET clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 161 161 162 163 164 164 165 166 166 167 167 169 169 170
SIGN clause . . . . . . . . SYNCHRONIZED clause . . . Slack bytes . . . . . . . Slack bytes within records . . Slack bytes between records . USAGE clause . . . . . . . Computational items . . . . DISPLAY phrase . . . . . DISPLAY-1 phrase . . . . . FUNCTION-POINTER phrase . INDEX phrase . . . . . . NATIONAL phrase . . . . OBJECT REFERENCE phrase . POINTER phrase . . . . . PROCEDURE-POINTER phrase NATIVE phrase . . . . . VALUE clause . . . . . . . Format 1 . . . . . . . . Format 2 . . . . . . . . Format 3 . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
207 208 211 211 213 214 216 218 218 218 219 219 220 221 222 223 223 223 225 228
Part 6. Procedure division . . . . . 229

Chapter 20. Procedure division structure . . . . . . . . . . . . . 233
Requirements for a method procedure division The procedure division header . . . . . The USING phrase . . . . . . . . RETURNING phrase . . . . . . . . References to items in the linkage section . Declaratives . . . . . . . . . . . . Procedures . . . . . . . . . . . . Arithmetic expressions . . . . . . . . Arithmetic operators . . . . . . . . Arithmetic with date fields . . . . . . Conditional expressions . . . . . . . . Simple conditions . . . . . . . . . Class condition . . . . . . . . . . Condition-name condition . . . . . . Relation condition . . . . . . . . . Comparison of numeric and alphanumeric operands . . . . . . . . . . . . Comparison of DBCS operands . . . . Comparison of national operands . . . Sign condition . . . . . . . . . . Switch-status condition . . . . . . . Complex conditions . . . . . . . . Negated simple conditions . . . . . . Combined conditions . . . . . . . . Abbreviated combined relation conditions . Statement categories . . . . . . . . . Imperative statements . . . . . . . Conditional statements . . . . . . . Delimited scope statements . . . . . . Explicit scope terminators . . . . . . Implicit scope terminators . . . . . . Compiler-directing statements . . . . . Statement operations . . . . . . . . . CORRESPONDING phrase . . . . . . GIVING phrase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 235 236 238 238 238 239 241 242 243 246 246 247 249 250 255 259 259 261 262 262 263 263 265 268 268 270 271 271 272 272 272 272 273
Chapter 19. Data divisiondata description entry . . . . . . . . . . 171

Format 1 . . . . . . . . . . . . . Format 2 . . . . . . . . . . . . . Format 3 . . . . . . . . . . . . . Level-numbers . . . . . . . . . . . BLANK WHEN ZERO clause . . . . . . DATE FORMAT clause . . . . . . . . Semantics of windowed date fields . . . Restrictions on using date fields . . . . EXTERNAL clause . . . . . . . . . GLOBAL clause . . . . . . . . . . JUSTIFIED clause . . . . . . . . . . OCCURS clause . . . . . . . . . . Fixed-length tables . . . . . . . . ASCENDING KEY and DESCENDING KEY phrases . . . . . . . . . . . . INDEXED BY phrase . . . . . . . . Variable-length tables . . . . . . . . OCCURS DEPENDING ON clause . . . PICTURE clause . . . . . . . . . . Symbols used in the PICTURE clause . . Character-string representation . . . . Data categories and PICTURE rules . . . PICTURE clause editing . . . . . . . Simple insertion editing . . . . . . . Special insertion editing . . . . . . . Fixed insertion editing . . . . . . . Floating insertion editing . . . . . . Zero suppression and replacement editing . REDEFINES clause . . . . . . . . . REDEFINES clause considerations . . . REDEFINES clause examples . . . . . Undefined results . . . . . . . . . RENAMES clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 172 172 172 173 174 175 176 179 180 180 181 181 182 183 184 185 187 187 192 193 197 198 198 199 200 201 202 204 205 205 205
Contents
ROUNDED phrase . . . . SIZE ERROR phrases . . . . Arithmetic statements . . . Arithmetic statement operands Data manipulation statements . Input-output statements . . . Common processing facilities .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
273 274 276 276 277 277 278
Chapter 21. Procedure division statements . . . . . . . . . . . . 285

ACCEPT statement . . . . . . . . Data transfer . . . . . . . . . System information transfer . . . . DATE, DATE YYYYMMDD, DAY, DAY YYYYDDD, DAY-OF-WEEK, and TIME . ADD statement . . . . . . . . . . ROUNDED phrase . . . . . . . SIZE ERROR phrases . . . . . . . CORRESPONDING phrase (format 3) . END-ADD phrase . . . . . . . . ALTER statement . . . . . . . . . Segmentation considerations . . . . CALL statement . . . . . . . . . USING phrase . . . . . . . . . BY REFERENCE phrase . . . . . . BY CONTENT phrase . . . . . . BY VALUE phrase . . . . . . . . RETURNING phrase . . . . . . . ON EXCEPTION phrase . . . . . . NOT ON EXCEPTION phrase . . . . ON OVERFLOW phrase . . . . . . END-CALL phrase . . . . . . . CANCEL statement . . . . . . . . CLOSE statement . . . . . . . . . Effect of CLOSE statement on file types COMPUTE statement . . . . . . . . ROUNDED phrase . . . . . . . SIZE ERROR phrases . . . . . . . END-COMPUTE phrase . . . . . . CONTINUE statement . . . . . . . DELETE statement . . . . . . . . Sequential access mode . . . . . . Random or dynamic access mode . . END-DELETE phrase . . . . . . . DISPLAY statement . . . . . . . . DIVIDE statement . . . . . . . . . ROUNDED phrase . . . . . . . REMAINDER phrase . . . . . . . SIZE ERROR phrases . . . . . . . END-DIVIDE phrase . . . . . . . ENTRY statement . . . . . . . . . USING phrase . . . . . . . . . EVALUATE statement . . . . . . . END-EVALUATE phrase . . . . . Determining values . . . . . . . Comparing selection subjects and objects Executing the EVALUATE statement . EXIT statement . . . . . . . . . . EXIT METHOD statement . . . . . . EXIT PROGRAM statement . . . . . GOBACK statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 . 286 . 287 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 290 292 292 292 292 293 293 295 296 297 297 298 299 300 300 300 301 302 304 305 308 309 309 309 310 311 311 311 312 313 316 318 318 319 319 320 320 321 322 322 323 324 325 326 327 328
GO TO statement . . . . . . . . . . . Unconditional GO TO . . . . . . . . Conditional GO TO . . . . . . . . . Altered GO TO . . . . . . . . . . . MORE-LABELS GO TO . . . . . . . . IF statement . . . . . . . . . . . . . END-IF phrase . . . . . . . . . . . Transferring control . . . . . . . . . Nested IF statements . . . . . . . . . INITIALIZE statement . . . . . . . . . REPLACING phrase . . . . . . . . . INITIALIZE statement rules . . . . . . INSPECT statement . . . . . . . . . . TALLYING phrase (formats 1 and 3) . . . REPLACING phrase (formats 2 and 3) . . . BEFORE and AFTER phrases (all formats) . . CONVERTING phrase (format 4) . . . . . Data flow . . . . . . . . . . . . Example of the INSPECT statement . . . . INVOKE statement . . . . . . . . . . USING phrase . . . . . . . . . . . BY VALUE phrase . . . . . . . . . . RETURNING phrase . . . . . . . . . ON EXCEPTION phrase . . . . . . . . NOT ON EXCEPTION phrase . . . . . . END-INVOKE phrase . . . . . . . . Interoperable data types for COBOL and Java Miscellaneous argument types for COBOL and Java . . . . . . . . . . . . . . MERGE statement . . . . . . . . . . . ASCENDING/DESCENDING KEY phrase . COLLATING SEQUENCE phrase. . . . . USING phrase . . . . . . . . . . . GIVING phrase. . . . . . . . . . . OUTPUT PROCEDURE phrase . . . . . MERGE special registers . . . . . . . . Segmentation considerations . . . . . . MOVE statement . . . . . . . . . . . Elementary moves . . . . . . . . . . Moves involving file record areas. . . . . Group moves . . . . . . . . . . . MULTIPLY statement . . . . . . . . . . ROUNDED phrase . . . . . . . . . SIZE ERROR phrases . . . . . . . . . END-MULTIPLY phrase . . . . . . . . OPEN statement . . . . . . . . . . . General rules . . . . . . . . . . . Label records . . . . . . . . . . . OPEN statement notes . . . . . . . . PERFORM statement . . . . . . . . . . Basic PERFORM statement . . . . . . . END-PERFORM . . . . . . . . . . PERFORM with TIMES phrase . . . . . PERFORM with UNTIL phrase . . . . . PERFORM with VARYING phrase . . . . Varying identifiers . . . . . . . . . . Varying two identifiers . . . . . . . . Varying three identifiers . . . . . . . . Varying more than three identifiers . . . . Varying phrase rules . . . . . . . . . READ statement . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
329 329 329 330 330 331 331 332 332 333 333 334 335 338 339 340 341 343 344 345 347 347 347 349 349 349 349 351 353 353 355 356 356 357 357 358 359 360 364 364 365 366 366 366 367 369 369 370 373 373 375 375 376 377 378 379 381 381 382 383
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
Language Reference
KEY IS phrase . . . . . . . . . . . . AT END phrases . . . . . . . . . . . INVALID KEY phrases . . . . . . . . . END-READ phrase . . . . . . . . . . Multiple record processing . . . . . . . . Sequential access mode . . . . . . . . . Random access mode . . . . . . . . . . Dynamic access mode . . . . . . . . . RELEASE statement . . . . . . . . . . . RETURN statement . . . . . . . . . . . AT END phrases . . . . . . . . . . . END-RETURN phrase . . . . . . . . . REWRITE statement . . . . . . . . . . . INVALID KEY phrases . . . . . . . . . END-REWRITE phrase . . . . . . . . . Reusing a logical record . . . . . . . . . Sequential files . . . . . . . . . . . . Indexed files . . . . . . . . . . . . Relative files. . . . . . . . . . . . . SEARCH statement . . . . . . . . . . . AT END phrase and WHEN phrases . . . . NEXT SENTENCE. . . . . . . . . . . END-SEARCH phrase . . . . . . . . . Serial search . . . . . . . . . . . . . Binary search . . . . . . . . . . . . Search statement considerations . . . . . . SET statement . . . . . . . . . . . . . Format 1: SET for basic table handling . . . . Format 2: SET for adjusting indexes . . . . . Format 3: SET for external switches . . . . . Format 4: SET for condition-names . . . . . Format 5: SET for USAGE IS POINTER data items . . . . . . . . . . . . . . . Format 6: SET for procedure-pointer and function-pointer data items . . . . . . . . Format 7: SET for USAGE OBJECT REFERENCE data items . . . . . . . . . . . . . SORT statement . . . . . . . . . . . . ASCENDING/DESCENDING KEY phrase . . DUPLICATES phrase . . . . . . . . . . COLLATING SEQUENCE phrase . . . . . . USING phrase . . . . . . . . . . . . INPUT PROCEDURE phrase . . . . . . . GIVING phrase. . . . . . . . . . . . OUTPUT PROCEDURE phrase . . . . . . SORT special registers . . . . . . . . . Segmentation considerations . . . . . . . START statement . . . . . . . . . . . . KEY phrase . . . . . . . . . . . . . INVALID KEY phrases . . . . . . . . . END-START phrase . . . . . . . . . . Indexed files . . . . . . . . . . . . Relative files. . . . . . . . . . . . . STOP statement . . . . . . . . . . . . STRING statement. . . . . . . . . . . . DELIMITED BY phrase . . . . . . . . . INTO phrase . . . . . . . . . . . . POINTER phrase . . . . . . . . . . . ON OVERFLOW phrases . . . . . . . . END-STRING phrase . . . . . . . . . . Data flow . . . . . . . . . . . . .
384 384 384 385 385 385 387 388 389 391 392 392 393 394 394 394 394 394 395 396 397 397 397 397 399 401 402 402 403 404 404 405 406 407 409 410 411 411 412 413 413 414 414 415 416 416 416 417 417 417 419 420 421 421 421 421 422 422
SUBTRACT statement . . . . . . . ROUNDED phrase . . . . . . . SIZE ERROR phrases . . . . . . . CORRESPONDING phrase (format 3) . END-SUBTRACT phrase . . . . . UNSTRING statement . . . . . . . DELIMITED BY phrase . . . . . . INTO phrase . . . . . . . . . POINTER phrase . . . . . . . . TALLYING IN phrase . . . . . . ON OVERFLOW phrases . . . . . END-UNSTRING phrase . . . . . Data flow . . . . . . . . . . Example of the UNSTRING statement . WRITE statement . . . . . . . . . ADVANCING phrase. . . . . . . END-OF-PAGE phrases . . . . . . INVALID KEY phrases . . . . . . END-WRITE phrase . . . . . . . WRITE for sequential files . . . . . WRITE for indexed files . . . . . . WRITE for relative files . . . . . . XML GENERATE statement . . . . . Nested XML GENERATE or XML PARSE statements . . . . . . . . . . Operation of XML GENERATE . . . XML element name formation . . . . XML PARSE statement . . . . . . . Nested XML GENERATE or XML PARSE statements . . . . . . . . . . Control flow . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
425 427 427 427 427 428 429 430 431 431 431 432 432 434 436 438 439 440 441 441 443 443 444 447 447 449 451
. 454 . 454
Part 7. Intrinsic functions . . . . . 457

Chapter 22. Intrinsic functions . . . . 459
Specifying a function . . . . . Function definition and evaluation Types of functions . . . . . . Rules for usage . . . . . . . Arguments . . . . . . . . ALL subscripting . . . . . . Function definitions . . . . . ACOS . . . . . . . . . . ANNUITY . . . . . . . . ASIN . . . . . . . . . . ATAN . . . . . . . . . . CHAR . . . . . . . . . . COS . . . . . . . . . . CURRENT-DATE . . . . . . DATE-OF-INTEGER . . . . . DATE-TO-YYYYMMDD . . . . DATEVAL . . . . . . . . DAY-OF-INTEGER . . . . . DAY-TO-YYYYDDD . . . . . DISPLAY-OF . . . . . . . FACTORIAL. . . . . . . . INTEGER . . . . . . . . INTEGER-OF-DATE . . . . . INTEGER-OF-DAY . . . . . INTEGER-PART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 460 460 461 462 464 465 469 470 470 471 471 471 472 473 474 474 475 476 477 478 479 479 480 480
Contents
vii
LENGTH . . . . . . LOG . . . . . . . LOG10 . . . . . . LOWER-CASE . . . . MAX . . . . . . . MEAN . . . . . . MEDIAN . . . . . . MIDRANGE . . . . . MIN . . . . . . . MOD . . . . . . . NATIONAL-OF . . . NUMVAL . . . . . NUMVAL-C . . . . . ORD . . . . . . . ORD-MAX . . . . . ORD-MIN . . . . . PRESENT-VALUE . . . RANDOM . . . . . RANGE . . . . . . REM . . . . . . . REVERSE. . . . . . SIN . . . . . . . . SQRT . . . . . . . STANDARD-DEVIATION SUM . . . . . . . TAN . . . . . . . UNDATE . . . . . . UPPER-CASE . . . . VARIANCE . . . . . WHEN-COMPILED . . YEAR-TO-YYYY . . . YEARWINDOW . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
481 482 482 482 483 484 484 485 485 486 487 488 489 490 491 491 492 493 493 494 494 495 495 496 496 497 497 497 498 499 500 501
SERVICE RELOAD statement . . . SKIP statements . . . . . . . TITLE statement . . . . . . . USE statement . . . . . . . . EXCEPTION/ERROR declarative . . Precedence rules for nested programs LABEL declarative. . . . . . . DEBUGGING declarative . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
522 522 523 524 524 526 526 528
Part 9. Appendixes . . . . . . . . 531

Appendix A. IBM extensions . . . . . 533 Appendix B. Compiler limits . . . . . 545 Appendix C. EBCDIC and ASCII collating sequences . . . . . . . . 549
EBCDIC collating sequence . . US English ASCII code page . . . . . . . . . . . . . . 549 . 552
Appendix D. Source language debugging. . . . . . . . . . . . . 557

Coding debugging lines . . Coding debugging sections . DEBUG-ITEM special register Activate compile-time switch Activate object-time switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 557 558 558 558
Appendix E. Reserved words
. . . . 559
Part 8. Compiler-directing statements . . . . . . . . . . . . 503

Chapter 23. Compiler-directing statements . . . . . . . . . . . . 505
BASIS statement . . . . . . . CBL (PROCESS) statement . . . . *CONTROL (*CBL) statement . . . Source code listing . . . . . . Object code listing . . . . . . . Storage map listing . . . . . . COPY statement . . . . . . . SUPPRESS phrase . . . . . . REPLACING phrase . . . . . Replacement and comparison rules DELETE statement . . . . . . EJECT statement . . . . . . . ENTER statement . . . . . . . INSERT statement . . . . . . . READY or RESET TRACE statement REPLACE statement . . . . . . Continuation rules for pseudo-text . Comparison operation . . . . . REPLACE statement notes . . . . SERVICE LABEL statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 506 506 507 508 508 508 511 511 512 515 516 516 517 517 518 520 520 521 522
Appendix F. ASCII considerations. . . 573

Environment division . . . . . . . . . OBJECT-COMPUTER and SPECIAL-NAMES paragraphs . . . . . . . . . . . . FILE-CONTROL paragraph . . . . . . . I-O-CONTROL paragraph . . . . . . . Data division . . . . . . . . . . . . FD EntryCODE-SET clause . . . . . . Data description entries . . . . . . . . Procedure division . . . . . . . . . . . 573 . . . . . . . 573 574 574 574 575 575 575
Appendix G. Industry specifications
577
Notices . . . . . . . . . . . . . . 579
Programming interface information . Trademarks . . . . . . . . . . . . . . . . . . 580 . 580
Glossary . . . . . . . . . . . . . 581 List of resources . . . . . . . . . . 601

Enterprise COBOL for z/OS Related publications . . . . . . . . . . . . . . . . . . 601 . 601
Index . . . . . . . . . . . . . . . 603
viii
Language Reference
Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. Enterprise COBOL basic character set . . . . 4 DEBUG-ITEM subfield contents . . . . . 15 Contents of XML-EVENT and XML-TEXT or XML-NTEXT special registers . . . . . . 23 Separators . . . . . . . . . . . . . 35 Meanings of environment names . . . . 108 Types of files . . . . . . . . . . . 118 Classes and categories of functions . . . . 154 Classes and categories of data . . . . . . 154 Classes and categories of literals . . . . . 154 PICTURE clause symbol meanings . . . . 188 Data categories . . . . . . . . . . . 197 SYNCHRONIZE clause effect on other language elements . . . . . . . . . . 209 Binary and unary operators . . . . . . 242 Valid arithmetic symbol pairs . . . . . . 243 Results of using date fields in addition 244 Results of using date fields in subtraction 244 Storing arithmetic results that involve date fields when ON SIZE ERROR is specified . 246 Valid forms of the class condition for different types of identifiers . . . . . . 248 Relational operators and their meanings 251 Comparisons with date fields . . . . . . 253 Permissible comparisons for USAGE IS POINTER, NULL, and ADDRESS OF . . . 254 Permissible comparisons with numeric second operands . . . . . . . . . . 256 Permissible comparisons with alphanumeric second operands . . . . . . . . . . 257 Comparisons for index-names and index data items . . . . . . . . . . . . 259 Logical operators and their meanings 262 Combined conditionspermissible element sequences . . . . . . . . . . . . 264 Logical operators and evaluation results of combined conditions . . . . . . . . . 264 Abbreviated combined conditions: permissible element sequences . . . . . 267 Abbreviated combined conditions: unabbreviated equivalents . . . . . . . 267 Exponentiation size error conditions 275 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. How the composite of operands is determined . . . . . . . . . . . File status key values and meanings Sequential files and CLOSE statement phrases . . . . . . . . . . . . Indexed and relative file types and CLOSE statement phrases . . . . . . . . . Line-sequential file types and CLOSE statement phrases . . . . . . . . . Meanings of key letters for sequential file types . . . . . . . . . . . . . Treatment of the content of data items Interoperable Java and COBOL data types Interoperable COBOL and Java array and String data types . . . . . . . . . COBOL miscellaneous argument types and corresponding Java types . . . . . . COBOL literal argument types and corresponding Java types . . . . . . Valid and invalid elementary moves Moves involving date fields . . . . . Availability of a file . . . . . . . . Permissible statements for sequential files Permissible statements for indexed and relative files . . . . . . . . . . . Permissible statements for line-sequential files . . . . . . . . . . . . . Sending and receiving fields for format-1 SET statement . . . . . . . . . . Sending and receiving fields for format-5 SET statement . . . . . . . . . . Character positions examined when DELIMITED BY is not specified . . . . Meanings of environment-names in SPECIAL NAMES paragraph . . . . . Table of functions . . . . . . . . . Execution of debugging declaratives IBM extension language elements . . . Compiler limits . . . . . . . . . EBCDIC collating sequence . . . . . ASCII collating sequence . . . . . . Reserved words . . . . . . . . . . 276 279 . 306 . 306 . 306 . 306 342 349 . 350 . 351 . 351 362 . 364 . 370 371 . 371 . 371 . 403 . 406 . 433 . 442 . 466 529 . 533 . 545 . 549 . 552 . 559
ix
Language Reference
About this document

This document describes the COBOL language supported by IBM Enterprise COBOL for z/OS, referred to in this document as Enterprise COBOL. Use this document in conjunction with the IBM Enterprise COBOL for z/OS Programming Guide.
Accessing softcopy documentation and support information

Enterprise COBOL provides PDF and BookManager versions of the library on the product site at www.ibm.com/software/awdtools/cobol/zos/library/. You can check that Web site for the latest editions of the documents. In the BookManager version of a document, the content of some tables and syntax diagrams might be aligned improperly due to variations in the display technology. Support information is also available on the product site at www.ibm.com/software/awdtools/cobol/zos/support/.
Accessibility
| | | | | | | | Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully. The accessibility features in z/OS provide accessibility for Enterprise COBOL. The major accessibility features in z/OS enable users to: v Use assistive technology products such as screen readers and screen magnifier software. v Operate specific or equivalent features by using only the keyboard. v Customize display attributes such as color, contrast, and font size.
Using assistive technologies

| | | Assistive technology products work with the user interfaces that are found in z/OS. For specific guidance information, consult the documentation for the assistive technology product that you use to access z/OS interfaces.
Keyboard navigation of the user interface

| | | | | | | | Users can access z/OS user interfaces by using TSO/E or ISPF. For information about accessing TSO/E and ISPF interfaces, refer to the following publications: v z/OS TSO/E Primer v z/OS TSO/E Users Guide v z/OS ISPF Users Guide Volume I These guides describe how to use TSO/E and ISPF, including the use of keyboard shortcuts or function keys (PF keys). Each guide includes the default settings for the PF keys and explains how to modify their functions.
xi
Accessibility of this document

| | | | | | The English-language XHTML format of this document that is provided with IBM WebSphere Studio Enterprise Developer is accessible to visually impaired individuals who use a screen reader. To enable your screen reader to accurately read syntax diagrams, source code examples, and text that contains the period and comma picture symbols, you must set the screen reader to speak all punctuation.
IBM extensions
IBM extensions generally add features, syntax, or rules beyond those specified in the ANSI and ISO COBOL standards listed in Appendix G, Industry specifications, on page 577. Those ANSI and ISO COBOL standards are collectively referred to in this document as Standard COBOL 85. Extensions range from minor relaxation of rules to major capabilities, such as XML support, Unicode support, object-oriented COBOL for Java interoperability, and DBCS character handling. The rest of this document describes the complete language without identifying extensions. You will need to review Appendix A, IBM extensions, on page 533 and the compiler options described in the Enterprise COBOL Programming Guide if you want to use only standard language elements.
Obsolete language elements

| | Obsolete language elements are elements categorized as obsolete in Standard COBOL 85. Those elements were deleted in Standard COBOL 2002. This does not imply that Standard COBOL 85 obsolete elements will be eliminated from a future release of Enterprise COBOL. The following are language elements that Standard COBOL 85 categorized as obsolete: v ALTER statement v AUTHOR paragraph v Comment entry v DATA RECORDS clause v DATE-COMPILED paragraph v DATE-WRITTEN paragraph v DEBUG-ITEM special register v Debugging sections v ENTER statement v GO TO without a specified procedure-name v v v v INSTALLATION paragraph LABEL RECORDS clause MEMORY SIZE clause MULTIPLE FILE TAPE clause
v RERUN clause v REVERSED phrase
xii
Language Reference
v v v v v v
SECURITY paragraph Segmentation module STOP literal format of the STOP statement USE FOR DEBUGGING declarative VALUE OF clause The figurative constant ALL literal, when associated with a numeric or numeric-edited item and with a length greater than one
How to read the syntax diagrams

Throughout this document, syntax is described using the structure defined below. v Read the syntax diagrams from left to right, from top to bottom, following the path of the line. The >>- symbol indicates the beginning of a syntax diagram. The -> symbol indicates that the syntax diagram is continued on the next line. The >- symbol indicates that the syntax diagram is continued from the previous line. The ->< symbol indicates the end of a syntax diagram. Diagrams of syntactical units other than complete statements start with the >symbol and end with the -> symbol. v Required items appear on the horizontal line (the main path). Format
STATEMENT required item
Optional items appear below the main path. Format

STATEMENT optional item
v When you can choose from two or more items, they appear vertically, in a stack. If you must choose one of the items, one item of the stack appears on the main path. Format
STATEMENT required choice 1 required choice 2
If choosing one of the items is optional, the entire stack appears below the main path. Format
STATEMENT optional choice 1 optional choice 2
An arrow returning to the left above the main line indicates an item that can be repeated.
About this document
xiii
Format
STATEMENT
repeatable item
A repeat arrow above a stack indicates that you can make more than one choice from the stacked items, or repeat a single choice. v Variables appear in all lowercase letters (for example, parmx). They represent user-supplied names or values. v If punctuation marks, parentheses, arithmetic operators, or other such symbols are shown, they must be entered as part of the syntax. The following example shows how the syntax is used. Format
(1) STATEMENT identifier-1 literal-1
(2) (3) item 1
(4) TO identifier-3 ROUNDED (5) SIZE ERROR imperative-statement-1 ON END-STATEMENT (6)
item 1:
identifier-2 literal-2 arithmetic-expression-1
Notes: 1 2 3 The STATEMENT keyword must be specified and coded as shown. This operand is required. Either identifier-1 or literal-1 must be coded. The item 1 fragment is optional; it can be coded or not, as required by the application. If item 1 is coded, it can be repeated with each entry separated by one or more COBOL separators. Entry selections allowed for this fragment are described at the bottom of the diagram. The operand identifier-3 and associated TO keyword are required and can be repeated with one or more COBOL separators separating each entry. Each entry can be assigned the keyword ROUNDED. The ON SIZE ERROR phrase with associated imperative-statement-1 is optional. If the ON SIZE ERROR phrase is coded, the keyword ON is optional.
xiv
Language Reference
The END-STATEMENT keyword can be coded to end the statement. It is not a required delimiter.
DBCS notation
Double-Byte Character Set (DBCS) strings in literals, comments, and user-defined words are delimited by shift-out and shift-in characters. In this document, the shift-out delimiter is represented pictorially by the < character, and the shift-in character is represented pictorially by the > character. The single-byte EBCDIC codes for the shift-out and shift-in delimiters are X0E and X0F, respectively. The <> symbol denotes contiguous shift-out and shift-in characters. The >< symbol denotes contiguous shift-in and shift-out characters. DBCS characters are shown in this form: D1D2D3. Latin alphabet characters in DBCS representation are shown in this form: .A.B.C. The dots that precede the letters represent the hexadecimal value X42. Notes v In EBCDIC DBCS data containing mixed single-byte and double-byte characters, double-byte character strings are delimited by shift-out and shift-in characters. v In ASCII DBCS data containing mixed single-byte and double-byte characters, you do not delimit double-byte character strings by shift-out and shift-in characters.
Acknowledgment
The following extract from Government Printing Office Form Number 1965-0795689 is presented for the information and guidance of the user: Any organization interested in reproducing the COBOL report and specifications in whole or in part, using ideas taken from this report as the basis for an instruction manual or for any other purpose is free to do so. However, all such organizations are requested to reproduce this section as part of the introduction to the document. Those using a short passage, as in a book review, are requested to mention COBOL in acknowledgment of the source, but need not quote this entire section. 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 COBOL 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 there with. Procedures have been established for the maintenance of COBOL. Inquiries concerning the procedures for proposing changes should be directed to the Executive Committee of the Conference on Data Systems Languages. The authors and copyright holders of copyrighted material: v FLOW-MATIC (Trademark of Sperry Rand Corporation), Programming for the UNIVAC (R) I and II, Data Automation Systems copyrighted 1958, 1959, by Sperry Rand Corporation v IBM Commercial Translator, Form No. F28-8013, copyrighted 1959 by IBM
About this document
xv
v FACT, DSI 27A5260-2760, copyrighted 1960 by Minneapolis-Honeywell 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. Note: The Conference on Data Systems Languages (CODASYL), mentioned above, is no longer in existence.
Summary of changes
Technical changes introduced in this edition are shown below and are marked throughout this document by a vertical bar in the left margin. Other changes in this release of Enterprise COBOL for z/OS are described in the Enterprise COBOL Programming Guide. For a history of changes in OS/390 COBOL compilers, see Enterprise COBOL Compiler and Run-Time Migration Guide.
Version 3 Release 3 (February 2004)

| | | | | | | v XML support has been enhanced. A new statement, XML GENERATE, converts the content of data records to XML format. XML GENERATE creates XML documents encoded in Unicode UTF-16 or any of several single-byte EBCDIC code pages. v The XML PARSE statement supports XML files encoded in Unicode UTF-16 or any of several single-byte EBCDIC code pages. Support is not provided for ASCII code pages.
Version 3 Release 2 (September 2002)

Java interoperability support has been enhanced: v Object references of type jobjectArray are supported for interoperation between COBOL and Java. v OO applications that begin with a COBOL main factory method can be invoked with the java command.
Version 3 Release 1 (November 2001)

v Interoperation of COBOL and Java by means of object-oriented syntax, permitting COBOL programs to instantiate Java classes, invoke methods on Java objects, and define Java classes that can be instantiated in Java or COBOL and whose methods can be invoked in Java or COBOL v Ability to call services provided by the Java Native Interface (JNI) to obtain additional Java capabilities, with a copybook JNI.cpy and special register JNIENVPTR to facilitate access v XML support, including a high-speed XML parser that allows programs to consume inbound XML messages, verify that they are well formed, and transform their contents into COBOL data structures; with support for XML files encoded in Unicode UTF-16 or several single-byte EBCDIC or ASCII code pages v Support for Unicode provided by NATIONAL data type and national (N, NX) literals, intrinsic functions DISPLAY-OF and NATIONAL-OF for character conversions, and compiler options NSYMBOL and CODEPAGE v Multithreading: support of POSIX threads and asynchronous signals, permitting applications with COBOL programs to run on multiple threads within a process
xvi
Language Reference
v A 4-byte FUNCTION-POINTER data item that can contain the address of a COBOL or non-COBOL entry point, providing easier interoperability with C function pointers v Relaxed rules for using ADDRESS OF in the argument list of a CALL statement that specifies BY CONTENT or BY VALUE. Such arguments are no longer restricted to linkage section items, and now can be specified in the linkage section, working-storage section, or local-storage section. This capability facilitates interoperability with C/C++ functions that have pointer parameters. v VALUE clauses for binary data items that permit (in appropriate cases) numeric literals that have values of magnitude up to the capacity of the native binary representation, rather than being limited to the values implied by the number of 9s in the PICTURE clause v The following support is no longer provided (as documented in Enterprise COBOL Compiler and Run-Time Migration Guide): SOM-based object-oriented syntax and services Support for the VM/CMS environment
How to send your comments

Your feedback is important in helping us to provide accurate, high-quality information. If you have comments about this document or any other documentation for this product, contact us in one of these ways: v Fill out the Readers Comment Form at the back of this document, and return it by mail or give it to an IBM representative. If there is no form at the back of the document, address your comments to: IBM Corporation H150/090 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. v Use the Online Readers Comment Form at www.ibm.com/software/awdtools/rcf/. v Fax your comments to this U.S. number: (800)426-7773. Be sure to include the name of the document, the publication number of the document, the version of the product, and, if applicable, the specific location (for example, page number or section heading) of the text that you are commenting on. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
About this document
xvii
xviii
Language Reference
Part 1. COBOL language structure

Chapter 1. Characters . . . . . . . . . . . 3 Chapter 2. Character sets and code pages . . . 5 Character encoding units . . . . . . . . . . 5 Chapter 3. Character-strings . . . . . . . COBOL words with single-byte characters . . . COBOL words with DBCS characters . . . . . User-defined words . . . . . . . . . . . System-names . . . . . . . . . . . . . Function-names . . . . . . . . . . . . Reserved words . . . . . . . . . . . . Figurative constants . . . . . . . . . . Special registers . . . . . . . . . . . . ADDRESS OF . . . . . . . . . . . DEBUG-ITEM . . . . . . . . . . . JNIENVPTR . . . . . . . . . . . . LENGTH OF . . . . . . . . . . . . LINAGE-COUNTER . . . . . . . . . RETURN-CODE . . . . . . . . . . . SHIFT-OUT and SHIFT-IN . . . . . . . SORT-CONTROL . . . . . . . . . . SORT-CORE-SIZE . . . . . . . . . . SORT-FILE-SIZE . . . . . . . . . . . SORT-MESSAGE . . . . . . . . . . SORT-MODE-SIZE . . . . . . . . . . SORT-RETURN . . . . . . . . . . . TALLY . . . . . . . . . . . . . . WHEN-COMPILED . . . . . . . . . XML-CODE . . . . . . . . . . . . XML-EVENT . . . . . . . . . . . . XML-NTEXT . . . . . . . . . . . . XML-TEXT . . . . . . . . . . . . Literals . . . . . . . . . . . . . . . Alphanumeric literals . . . . . . . . . Basic alphanumeric literals . . . . . . Alphanumeric literals with DBCS characters Hexadecimal notation for alphanumeric literals . . . . . . . . . . . . . Null-terminated alphanumeric literals . . Numeric literals . . . . . . . . . . . Rules for floating-point literal values . . . DBCS literals . . . . . . . . . . . . Where DBCS literals are allowed . . . . National literals . . . . . . . . . . . Basic national literals . . . . . . . . Hexadecimal notation for national literals . Where national literals are allowed . . . PICTURE character-strings . . . . . . . . Comments . . . . . . . . . . . . . . . 7 . 7 . 8 . 8 . 9 . 10 . 10 . 11 . 13 . 14 . 14 . 16 . 16 . 17 . 18 . 18 . 19 . 19 . 20 . 20 . 20 . 21 . 21 . 21 . 22 . 22 . 24 . 24 . 25 . 25 . 25 26 . . . . . . . . . . . . 27 28 29 29 30 30 31 31 32 33 33 34 Sentences, statements, Entries . . . . Clauses . . . . Sentences . . . Statements . . . Phrases . . . . and . . . . . . . . . . entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 39 40 40 40 40
Chapter 6. Reference format . . . . . . . . 41 Sequence number area . . . . . . . . . . . 41 Indicator area . . . . . . . . . . . . . . 41 Area A . . . . . . . . . . . . . . . . 42 Division headers. . . . . . . . . . . . 42 Section headers . . . . . . . . . . . . 42 Paragraph headers or paragraph names . . . . 42 Level indicators (FD and SD) or level-numbers (01 and 77) . . . . . . . . . . . . . 43 DECLARATIVES and END DECLARATIVES . . 43 End program, end class, and end method markers . . . . . . . . . . . . . . 43 Area B . . . . . . . . . . . . . . . . 43 Entries, sentences, statements, clauses . . . . 44 Continuation lines . . . . . . . . . . . 44 Continuation of alphanumeric and national literals . . . . . . . . . . . . . . 44 Area A or Area B . . . . . . . . . . . . 46 Level-numbers . . . . . . . . . . . . 46 Comment lines . . . . . . . . . . . . 46 Compiler-directing statements . . . . . . . 46 Debugging lines . . . . . . . . . . . . 47 Pseudo-text . . . . . . . . . . . . . 47 Blank lines . . . . . . . . . . . . . 47 Chapter 7. Scope of names . . . . . . . . 49 Types of names . . . . . . . . . . . . . 49 External and internal resources . . . . . . . . 51 Resolution of names . . . . . . . . . . . 52 Names within programs . . . . . . . . . 52 Names within a class definition . . . . . . 53 Chapter 8. Referencing data names, copy libraries, and procedure division names . . . . 55 Uniqueness of reference . . . . . . . . . . 55 Qualification . . . . . . . . . . . . . 55 Qualification rules . . . . . . . . . . 56 Identical names . . . . . . . . . . . . 56 References to COPY libraries . . . . . . . 56 References to procedure division names . . . . 56 References to data division names . . . . . . 57 Simple data reference . . . . . . . . . 57 Identifier . . . . . . . . . . . . . 57 Condition-name . . . . . . . . . . . . 59 Index-name . . . . . . . . . . . . . 60 Index data item . . . . . . . . . . . . 61 Subscripting . . . . . . . . . . . . . 61 Subscripting using data-names . . . . . . 62
Chapter 4. Separators . . . . . . . . . . 35 Rules for separators . . . . . . . . . . . 35 Chapter 5. Sections and paragraphs .

. 39
Subscripting using index-names (indexing) . Relative subscripting . . . . . . . . Reference modification . . . . . . . . Evaluation of operands . . . . . . . Reference modification examples . . . . Function-identifier . . . . . . . . . . Data attribute specification . . . . . . . . Chapter 9. Transfer of control . . . . . .
. . . . . . .
63 63 64 65 65 66 66
. 69
Chapter 10. Millennium Language Extensions and date fields . . . . . . . . . . . Millennium Language Extensions syntax . . Terms and concepts. . . . . . . . . . Date field . . . . . . . . . . . . Windowed date field . . . . . . . Expanded date field . . . . . . . Year-last date field . . . . . . . . Date format . . . . . . . . . . Compatible date field . . . . . . . Nondate . . . . . . . . . . . . Century window . . . . . . . . .
. . 71 . . 71 . . 72 . . 72 . . 72 . . 72 . . 72 . . 72 . . 73 . . 73 . . 73
Language Reference
Chapter 1. Characters
The most basic and indivisible unit of the COBOL language is the character. The basic character set includes the letters of the Latin alphabet, digits, and special characters. In the COBOL language, individual characters are joined to form character-strings and separators. Character-strings and separators, then, are used to form the words, literals, phrases, clauses, statements, and sentences that form the language. The default character set used in forming character-strings and separators is shown in Enterprise COBOL basic character set (Table 1 on page 4). For certain language elements, the basic character set is extended with the IBM EBCDIC Double-Byte Character Set (DBCS). DBCS characters can be used in forming user-defined words. The content of alphanumeric literals, comment lines, and comment entries can include any of the characters from the character set used for the source code, including DBCS characters. Run-time data can include any characters from the run-time character set of the computer. The run-time character set of the computer can include alphanumeric characters, DBCS characters, and national characters. National characters are represented in UTF-16, a 16-bit encoding form of Unicode. When the NSYMBOL (NATIONAL) compiler option is in effect, literals identified by the opening delimiter N or N are national literals and can contain any single-byte or double-byte characters, or both, that are valid for the compile-time code page in effect (either the default code page or the code page specified for the CODEPAGE compiler option). Characters contained in national literals are represented as national characters at run time. For details, see COBOL words with DBCS characters on page 8, DBCS literals on page 30, and National literals on page 31.
Table 1. Enterprise COBOL basic character set Character + * / = $ , ; . ( ) > < : A-Z a-z 0-9 Meaning Space Plus sign Minus sign or hyphen Asterisk Forward slash or solidus Equal sign Currency sign1 Comma Semicolon Decimal point or period Quotation mark2 Left parenthesis Right parenthesis Greater than Less than Colon Apostrophe Alphabet (uppercase) Alphabet (lowercase) Numeric characters
1. The currency sign is the character with the value X5B, regardless of the code page in effect. The assigned graphic character can be the dollar sign or a local currency sign. 2. The quotation mark is the character with the value X7F.
Language Reference
Chapter 2. Character sets and code pages

A character set is a set of letters, numbers, special characters, and other elements used to represent information. A character set is independent of a coded representation. A coded character set is the coded representation of a set of characters, where each character is assigned a numerical position, called a code point, in the encoding scheme. The Enterprise COBOL basic character set is an example of a character set that is independent of a coded representation. ASCII and EBCDIC are examples of coded character sets, and each variation of ASCII or EBCDIC is another coded character set. Enterprise COBOL uses the term code page to refer to a coded character set. Each code page that IBM defines is identified by a code page name, for example IBM-1252, and a coded character set identifier (CCSID), for example 1252. The CODEPAGE compiler option specifies the code page that is used for the encoding of: v Source code v The content of alphanumeric and DBCS literals at run time v The content of alphanumeric and DBCS data items If you do not specify a code page, the default is code page IBM-1140, CCSID 1140. The run-time code page for national data items is UTF-16BE (big endian), CCSID 1200. A reference to UTF-16 in this document is a reference to UTF-16BE. See the Enterprise COBOL Programming Guide for details of the CODEPAGE compiler option.
Character encoding units

A character encoding unit (or encoding unit) is a single code point in a coded character set. For a single-byte EBCDIC character set, an encoding unit is a byte. For an EBCDIC double-byte character set, an encoding unit is 2 bytes. For EBCDIC and ASCII character sets, a graphic character is always represented in a single encoding unit, and users need not consider encoding units. In Unicode UTF-16, a character encoding unit consists of 2 bytes. Many UTF-16 characters are represented in one encoding unit. Any characters converted to UTF-16 from a single-byte or double-byte EBCDIC or ASCII code page, for example, are each represented in one encoding unit. However, a subset of the characters in UTF-16 are represented in two or more encoding units. Some graphic characters are represented by a surrogate pair, consisting of two encoding units (4 bytes). Others are represented by a composite sequence, consisting of a base character and one or more combining marks (4 bytes or more, in 2-byte increments). In national data items, Enterprise COBOL treats each 2-byte encoding unit as a character. The terms character and character position refer to a single encoding unit. In most cases, this is the same as a graphic character. When national data contains surrogate pairs or composite sequences, programmers are responsible for ensuring that operations on national characters do not unintentionally separate the multiple
encoding units that form a graphic character. Care should be taken with reference modification, and truncation during moves should be avoided. The COBOL run-time system does not check for a split between the encoding units that form a graphic character.
Language Reference
Chapter 3. Character-strings
A character-string is a character or a sequence of contiguous characters that forms a COBOL word, a literal, a PICTURE character-string, or a comment-entry. A character-string is delimited by separators. A separator is a string of contiguous characters used to delimit character strings. Separators are described in detail under Chapter 4, Separators, on page 35. Character strings and certain separators form text words. A text word is a character or a sequence of contiguous characters (possibly continued across lines) between character positions 8 and 72 inclusive in source text, library text, or pseudo-text. For more information about pseudo-text, see Pseudo-text on page 47. Source text, library text, and pseudo-text can be written in single-byte EBCDIC and, for some character-strings, DBCS. (The compiler cannot process source code written in ASCII or Unicode.) You can use single-byte EBCDIC and double-byte character-strings to form the following: v COBOL words v Literals v PICTURE character-strings (single-byte EBCDIC character-strings only) v Comment text
COBOL words with single-byte characters

A COBOL word is a character-string of not more than 30 characters that forms a user-defined word, a system-name, or a reserved word. Except for arithmetic operators and relation characters, each character of a COBOL word is selected from the following set: v A through Z v a through z v 0 through 9 v - (hyphen) The hyphen cannot appear as the first or last character in such words. All user-defined words (except for section-names, paragraph-names, segment-numbers, and level-numbers) must contain at least one alphabetic character. Segment numbers and level numbers need not be unique; a given specification of a segment-number or level-number can be identical to any other segment-number or level-number. In COBOL words (but not in the content of alphanumeric, DBCS, and national literals), each lowercase single-byte alphabetic letter is considered to be equivalent to its corresponding single-byte uppercase alphabetic letter. The following rules apply for all COBOL words: v A reserved word cannot be used as a user-defined word or as a system-name.
v The same COBOL word, however, can be used as both a user-defined word and as a system-name. The classification of a specific occurrence of a COBOL word is determined by the context of the clause or phrase in which it occurs.
COBOL words with DBCS characters

The following are the rules for forming user-defined words from DBCScharacters: Use of shift-out and shift-in characters DBCS user-defined words begin with a shift-out character and end with a shift-in character. Value range DBCS user-defined words can contain characters whose values range from X41 to XFE for both bytes. Contained characters DBCS user-defined words can contain only double-byte characters, and must contain at least one DBCS character that is not in the set A through Z, a through z, 0 through 9, and hyphen (DBCS representation of these characters has X42 in the first byte). DBCS user-defined words can contain characters that correspond to single-byte EBCDIC characters and those that do not correspond to single-byte EBCDIC characters. DBCS characters that correspond to single-byte EBCDIC characters follow the normal rules for COBOL user-defined words; that is, the characters A - Z, a - z, 0 - 9, and the hyphen (-) are allowed. The hyphen cannot appear as the first or last character. Any of the DBCS characters that have no corresponding single-byte EBCDIC character can be used in DBCS user-defined words. Continuation Words formed with DBCS characters cannot be continued across lines. Uppercase and lowercase letters Equivalent Maximum length 14 characters
User-defined words
The following sets of user-defined words are supported in Enterprise COBOL. The second column indicates whether DBCS characters are allowed in words of a given set.
User-defined word Alphabet-name Class-name (of data) Condition-name Data-name File-name Index-name Level-numbers: 01-49, 66, 77, 88 Library-name Mnemonic-name Object-oriented class-name Paragraph-name Priority-numbers: 00-99 DBCS characters allowed? Yes Yes Yes Yes Yes Yes No No Yes No Yes No
Language Reference
User-defined word Program-name Record-name Section-name Symbolic-character Text-name
DBCS characters allowed? No Yes Yes Yes No
| |
The maximum length of a user-defined word is 30 bytes, except for level-numbers and priority-numbers. Level-numbers and priority numbers must each be a one-digit or two-digit integer. A given user-defined word can belong to only one of these sets, except that a given number can be both a priority-number and a level-number. Except for priority-numbers and level-numbers, each user-defined word within a set must be unique, except as specified in Chapter 8, Referencing data names, copy libraries, and procedure division names, on page 55. The following types of user-defined words can be referenced by statements and entries in the program in which the user-defined word is declared: v Paragraph-name v Section-name The following types of user-defined words can be referenced by any COBOL program, provided that the compiling system supports the associated library or other system and that the entities referenced are known to that system: v Library-name v Text-name The following types of names, when they are declared within a configuration section, can be referenced by statements and entries in the program that contains the configuration section or in any program contained within that program: v Alphabet-name v Class-name v Condition-name v Mnemonic-name v Symbolic-character The function of each user-defined word is described in the clause or statement in which it appears.
System-names
A system-name is a character string that has a specific meaning to the system. There are three types of system-names: v Computer-name v Language-name v Implementor-name There are three types of implementor-names: v Environment-name v External-class-name
Assignment-name
The meaning of each system-name is described with the format in which it appears. Computer-name can be written in DBCS characters, but the other system-names cannot.
Function-names
A function-name specifies the mechanism provided to determine the value of an intrinsic function. The same word, in a different context, can appear in a program as a user-defined word or a system-name. For a list of function-names and their definitions, see Table of functions (Table 52 on page 466).
Reserved words
A reserved word is a character-string with a predefined meaning in a COBOL source unit. Enterprise COBOL reserved words are listed in Appendix E, Reserved words, on page 559. There are six types of reserved words: v Keywords v Optional words v Figurative constants v Special character words v Special object identifiers v Special registers Keywords Keywords are reserved words that are required within a given clause, entry, or statement. Within each format, such words appear in uppercase on the main path. Optional words Optional words are reserved words that can be included in the format of a clause, entry, or statement in order to improve readability. They have no effect on the execution of the program. Figurative constants See Figurative constants on page 11. Special character words There are two types of special character words, which are recognized as special characters only when represented in single-byte characters: v Arithmetic operators: + - / * ** See Arithmetic expressions on page 241. v Relational operators: < > = <= >= See Conditional expressions on page 246. Special object identifiers COBOL provides two special object identifiers, SELF and SUPER, used in a method procedure division: SELF A special object identifier that you can use in the procedure division of a method. SELF refers to the object instance used to
10
Language Reference
invoke the currently executing method. You can specify SELF only in places that are explicitly listed in the syntax diagrams. SUPER A special object identifier that you can use in the procedure division of a method only as the object identifier in an INVOKE statement. When used in this way, SUPER refers to the object instance used to invoke the currently executing method. The resolution of the method to be invoked ignores any methods declared in the class definition of the currently executing method and methods defined in any class derived from that class. Thus, the method invoked is inherited from an ancestor class.
Special registers See Special registers on page 13.
Figurative constants
Figurative constants are reserved words that name and refer to specific constant values. The reserved words for figurative constants and their meanings are: ZERO, ZEROS, ZEROES Represents the numeric value zero (0) or one or more occurrences of the character zero, depending on context. When the figurative constant ZERO, ZEROS, or ZEROES is used in a context that requires an alphanumeric character, an alphanumeric character zero is used. When the context requires a national character zero, a national character zero is used (value NX0030). When the context cannot be determined, an alphanumeric character zero is used. SPACE, SPACES Represents one or more blanks or spaces. SPACE is treated as an alphanumeric literal when used in a context that requires an alphanumeric character, as a DBCS literal when used in a context that requires a DBCS character, and as a national literal when used in a context that requires a national character. The EBCDIC DBCS space character has the value X4040, and the national space character has the value NX0020. HIGH-VALUE, HIGH-VALUES Represents one or more occurrences of the character that has the highest ordinal position in the collating sequence used. For the EBCDIC collating sequence, the character is XFF; for other collating sequences, the actual character used depends on the collating sequence used. HIGH-VALUE is treated as an alphanumeric literal. HIGH-VALUE and HIGH-VALUES cannot be used in a context that requires a national character value. LOW-VALUE, LOW-VALUES Represents one or more occurrences of the character that has the lowest ordinal position in the collating sequence used. For the EBCDIC collating sequence, the character is X00; for other collating sequences, the actual character used depends on the collating sequence used. LOW-VALUE is treated as an alphanumeric literal. LOW-VALUE/LOW-VALUES cannot be used in a context that requires a national character value.
11
QUOTE, QUOTES Represents one or more occurrences of: v The quotation mark character (), if the QUOTE compiler option is in effect v The apostrophe character (), if the APOST compiler option is in effect QUOTE or QUOTES represents an alphanumeric character when used in a context that requires an alphanumeric character, and represents a national character when used in a context that requires a national character. The national character value of quotation mark is NX0022. The national character value of apostrophe is NX0027. QUOTE and QUOTES cannot be used in place of a quotation mark or an apostrophe to enclose an alphanumeric literal. ALL literal literal can be an alphanumeric literal, a DBCS literal, a national literal, or a figurative constant other than the ALL literal. When literal is not a figurative constant, ALL literal represents one or more occurrences of the string of characters that compose the literal. When literal is a figurative constant, the word ALL has no meaning and is used only for readability. The figurative constant ALL literal must not be used with the CALL, INSPECT, INVOKE, STOP, or STRING statements. symbolic-character Represents one or more of the characters specified as a value of the symbolic-character in the SYMBOLIC CHARACTERS clause of the SPECIAL-NAMES paragraph. symbolic-character always represents an alphanumeric character; it can be used in a context that requires a national character only when implicit conversion of alphanumeric to national characters is defined. (It can be used, for example, in a MOVE statement where the receiving item is a national data item because implicit conversion is defined when the sending item is alphanumeric and the receiving item is national.) NULL, NULLS Represents a value used to indicate that data items defined with USAGE POINTER, USAGE PROCEDURE-POINTER, USAGE FUNCTIONPOINTER, USAGE OBJECT REFERENCE, or the ADDRESS OF special register do not contain a valid address. NULL can be used only where explicitly allowed in the syntax format. NULL has the value of zero. The singular and plural forms of NULL, ZERO, SPACE, HIGH-VALUE, LOW-VALUE, and QUOTE can be used interchangeably. For example, if DATA-NAME-1 is a five-character data item, each of the following statements moves five spaces to DATA-NAME-1:
MOVE SPACE MOVE SPACES MOVE ALL SPACES TO DATA-NAME-1 TO DATA-NAME-1 TO DATA-NAME-1
When the rules of COBOL permit any one spelling of a figurative constant name, any alternative spelling of that figurative constant name can be specified.
12
Language Reference
You can use a figurative constant wherever literal appears in a syntax diagram, except where explicitly prohibited. When a numeric literal appears in a syntax diagram, only the figurative constant ZERO (or ZEROS or ZEROES) can be used. Figurative constants are not allowed as function arguments except in an arithmetic expression, where the expression is an argument to a function. The length of a figurative constant depends on the context of its use. The following rules apply: v When a figurative constant is specified in a VALUE clause or associated with a data item (for example, when it is moved to or compared with another item), the length of the figurative constant character-string is equal to 1 or the number of character positions in the associated data item, whichever is greater. v When a figurative constant, other than the ALL literal, is not associated with another data item (for example, in a CALL, INVOKE, STOP, STRING, or UNSTRING statement), the length of the character-string is one character.
Special registers
Special registers are reserved words that name storage areas generated by the compiler. Their primary use is to store information produced through specific COBOL features. Each such storage area has a fixed name, and must not be defined within the program. For programs with the recursive attribute, for programs compiled with the THREAD option, and for methods, storage for the following special registers is allocated on a per-invocation basis: v ADDRESS-OF v RETURN-CODE v SORT-CONTROL v SORT-CORE-SIZE v SORT-FILE-SIZE v SORT-MESSAGE v SORT-MODE-SIZE v SORT-RETURN v TALLY v XML-CODE v XML-EVENT For the first call to a program, for the first call to a program following a cancel of that program, or for a method invocation, the compiler initializes the special register fields to their initial values. For the following four cases: v Programs that have the INITIAL clause specified v Programs that have the RECURSIVE clause specified v Programs compiled with the THREAD option v Methods the following special registers are reset to their initial value on each program or method entry: v RETURN-CODE
13
v v v v v v v
SORT-CONTROL SORT-CORE-SIZE SORT-FILE-SIZE SORT-MESSAGE SORT-MODE-SIZE SORT-RETURN TALLY
v XML-CODE v XML-EVENT Further, in the above four cases, values set in ADDRESS OF special registers persist only for the span of the particular program or method invocation. In all other cases, the special registers will not be reset; they will be unchanged from the value contained on the previous CALL or INVOKE. Unless otherwise explicitly restricted, a special register can be used wherever a data-name or identifier that has the same definition as the implicit definition of the special register (which is specified later in this section) can be used. You can specify an alphanumeric special register in a function wherever an alphanumeric argument to a function is allowed, unless specifically prohibited. If qualification is allowed, special registers can be qualified as necessary to provide uniqueness. (For more information, see Qualification on page 55.)
ADDRESS OF
The ADDRESS OF special register references the address of a data item in the linkage section, the local-storage section, or the working-storage section. For 01 and 77 level items in the linkage section, the ADDRESS OF special register can be either a sending item or a receiving item. For all other operands, the ADDRESS OF special register can be only a sending item. The ADDRESS OF special register is implicitly defined as USAGE POINTER. A function-identifier is not allowed as the operand of the ADDRESS OF special register.
DEBUG-ITEM
The DEBUG-ITEM special register provides information for a debugging declarative procedure about the conditions that cause debugging section execution. DEBUG-ITEM has the following implicit description:
01 DEBUG-ITEM. 02 DEBUG-LINE 02 FILLER 02 DEBUG-NAME 02 FILLER 02 DEBUG-SUB-1 02 FILLER 02 DEBUG-SUB-2 PICTURE PICTURE PICTURE PICTURE PICTURE PICTURE PICTURE IS IS IS IS IS IS IS X(6). X VALUE SPACE. X(30). X VALUE SPACE. S9999 SIGN IS LEADING SEPARATE CHARACTER. X VALUE SPACE. S9999 SIGN IS LEADING SEPARATE CHARACTER.
14
Language Reference
02 02 02 02
FILLER DEBUG-SUB-3 FILLER DEBUG-CONTENTS
PICTURE PICTURE PICTURE PICTURE
IS IS IS IS
X VALUE SPACE. S9999 SIGN IS LEADING SEPARATE CHARACTER. X VALUE SPACE. X(n).
Before each debugging section is executed, DEBUG-ITEM is filled with spaces. The contents of the DEBUG-ITEM subfields are updated according to the rules for the MOVE statement, with one exception: DEBUG-CONTENTS is updated as if the move were an alphanumeric-to-alphanumeric elementary move without conversion of data from one form of internal representation to another. After updating, the contents of the DEBUG-ITEM subfields are: DEBUG-LINE The source-statement sequence number (or the compiler-generated sequence number, depending on the compiler option chosen) that caused execution of the debugging section. DEBUG-NAME The first 30 characters of the name that caused execution of the debugging section. Any qualifiers are separated by the word OF. DEBUG-SUB-1, DEBUG-SUB-2, DEBUG-SUB-3 If the DEBUG-NAME is subscripted or indexed, the occurrence number of each level is entered in the respective DEBUG-SUB-n. If the item is not subscripted or indexed, these fields remain as spaces. You must not reference the DEBUG-ITEM special register if your program uses more than three levels of subscripting or indexing. DEBUG-CONTENTS Data is moved into DEBUG-CONTENTS, as shown in the following table.
Table 2. DEBUG-ITEM subfield contents Cause of debugging section execution procedure-name-1 ALTER reference GO TO procedure-name-n Statement referred to in DEBUG-LINE ALTER statement GO TO statement Contents of DEBUG-NAME procedure-name-1 procedure-name-n Contents of DEBUG-CONTENTS procedure-name-n in TO PROCEED TO phrase Spaces SORT INPUT SORT OUTPUT MERGE OUTPUT (as applicable) PERFORM LOOP USE PROCEDURE FALL THROUGH
procedure-name-n in SORT or SORT or MERGE statement procedure-name-n MERGE input/output procedure PERFORM statement transfer of control procedure-name-n in a USE procedure Implicit transfer from previous sequential procedure First execution of first nondeclarative procedure This PERFORM statement Statement causing USE procedure execution Previous statement executed in previous sequential procedure1 Line number of first nondeclarative procedure-name procedure-name-n procedure-name-n procedure-name-n
First nondeclarative procedure
START PROGRAM
1. If this procedure is preceded by a section header, and control is passed through the section header, the statement number refers to the section header.
15
JNIENVPTR
The JNIENVPTR special register references the Java Native Interface (JNI) environment pointer. The JNI environment pointer is used in calling Java callable services. JNIENVPTR is implicitly defined as USAGE POINTER. It cannot be specified as a receiving data item. For information about using JNIENVPTR and JNI callable services, see the Enterprise COBOL Programming Guide.
LENGTH OF
The LENGTH OF special register contains the number of bytes used by a data item. LENGTH OF creates an implicit special register whose content is equal to the current byte length of the data item referenced by the identifier. For DBCS data items and national data items, each character occupies 2 bytes of storage. LENGTH OF can be used in the procedure division anywhere a numeric data item that has the same definition as the implied definition of the LENGTH OF special register can be used. The LENGTH OF special register has the implicit definition:
USAGE IS BINARY PICTURE 9(9).
If the data item referenced by the identifier contains the GLOBAL clause, the LENGTH OF special register is a global data item. The LENGTH OF special register can appear within either the starting character position or the length expressions of a reference-modification specification. However, the LENGTH OF special register cannot be applied to any operand that is reference-modified. The LENGTH OF operand cannot be a function, but the LENGTH OF special register is allowed in a function where an integer argument is allowed. If the LENGTH OF special register is used as the argument to the LENGTH function, the result is always 4, independent of the argument specified for LENGTH OF. If the ADDRESS OF special register is used as the argument to the LENGTH special register, the result is always 4, independent of the argument specified for ADDRESS OF. LENGTH OF cannot be either of the following: v A receiving data item v A subscript When the LENGTH OF special register is used as a parameter on a CALL statement, it must be passed BY CONTENT or BY VALUE.
16
Language Reference
When a table element is specified, the LENGTH OF special register contains the length in bytes of one occurrence. When referring to a table element, the element name need not be subscripted. A value is returned for any identifier whose length can be determined, even if the area referenced by the identifier is currently not available to the program. A separate LENGTH OF special register exists for each identifier referenced with the LENGTH OF phrase. For example:
MOVE LENGTH OF A TO B DISPLAY LENGTH OF A, A ADD LENGTH OF A TO B CALL PROGX USING BY REFERENCE A BY CONTENT LENGTH OF A
The intrinsic function LENGTH can also be used to obtain the length of a data item. For national data items, the length returned by the LENGTH function is the number of national character positions, rather than bytes; thus the LENGTH OF special register and the LENGTH intrinsic function have different results for national items. For all other data items, the result is the same.
LINAGE-COUNTER
A separate LINAGE-COUNTER special register is generated for each FD entry that contains a LINAGE clause. When more than one is generated, you must qualify each reference to a LINAGE-COUNTER with its related file-name. The implicit description of the LINAGE-COUNTER special register is one of the following: v If the LINAGE clause specifies a data-name, LINAGE-COUNTER has the same PICTURE and USAGE as that data-name. v If the LINAGE clause specifies an integer, LINAGE-COUNTER is a binary item with the same number of digits as that integer. For more information, see LINAGE clause on page 167. The value in LINAGE-COUNTER at any given time is the line number at which the device is positioned within the current page. LINAGE-COUNTER can be referred to in procedure division statements; it must not be modified by them. LINAGE-COUNTER is initialized to 1 when an OPEN statement for its associated file is executed. LINAGE-COUNTER is automatically modified by any WRITE statement for this file. (See WRITE statement on page 436.) If the file description entry for a sequential file contains the LINAGE clause and the EXTERNAL clause, the LINAGE-COUNTER data item is an external data item. If the file description entry for a sequential file contains the LINAGE clause and the GLOBAL clause, the LINAGE-COUNTER data item is a global data item. You can specify the LINAGE-COUNTER special register wherever an integer argument to a function is allowed.
17
RETURN-CODE
The RETURN-CODE special register can be used to pass a return code to the calling program or operating system when the current COBOL program ends. When a COBOL program ends: v If control returns to the operating system, the value of the RETURN-CODE special register is passed to the operating system as a user return code. The supported user return code values are determined by the operating system, and might not include the full range of RETURN-CODE special register values. v If control returns to a calling program, the value of the RETURN-CODE special register is passed to the calling program. If the calling program is a COBOL program, the RETURN-CODE special register in the calling program is set to the value of the RETURN-CODE special register in the called program. The RETURN-CODE special register has the implicit definition:
01 RETURN-CODE GLOBAL PICTURE S9(4) USAGE BINARY VALUE ZERO.
When used in nested programs, this special register is implicitly defined with the GLOBAL clause in the outermost program. The following are examples of how to set the RETURN-CODE special register: v COMPUTE RETURN-CODE = 8. v MOVE 8 to RETURN-CODE. The RETURN-CODE special register does not return a value from an invoked method or from a program that uses CALL ... RETURNING. For more information, see INVOKE statement on page 345 or CALL statement on page 295. You can specify the RETURN-CODE special register in a function wherever an integer argument is allowed. The RETURN-CODE special register will not contain return code information from a service call for a Language Environment callable service. For more information, see the Enterprise COBOL Programming Guide and the Language Environment Programming Guide.
SHIFT-OUT and SHIFT-IN

The SHIFT-OUT and SHIFT-IN special registers are implicitly defined as alphanumeric data items of the format:
01 01 SHIFT-OUT GLOBAL PICTURE X(1) USAGE DISPLAY VALUE X0E. SHIFT-IN GLOBAL PICTURE X(1) USAGE DISPLAY VALUE X0F.
When used in nested programs, these special registers are implicitly defined with the global attribute in the outermost program. These special registers represent EBCDIC shift-out and shift-in control characters, which are unprintable characters. You can specify the SHIFT-OUT and SHIFT-IN special registers in a function wherever an alphanumeric argument is allowed. These special registers cannot be receiving items. SHIFT-OUT and SHIFT-IN cannot be used in place of the keyboard control characters when you are defining DBCS user-defined words or specifying EBCDIC DBCS literals.
18
Language Reference
Following is an example of how SHIFT-OUT and SHIFT-IN might be used:

DATA DIVISION. WORKING-STORAGE. 01 DBCSGRP. 05 SO PIC X. 05 DBCSITEM PIC G(3) USAGE DISPLAY-1. 05 SI PIC X. ... PROCEDURE DIVISION. MOVE SHIFT-OUT TO SO MOVE G<D1D2D3> TO DBCSITEM MOVE SHIFT-IN TO SI DISPLAY DBCSGRP
SORT-CONTROL
The SORT-CONTROL special register is the name of an alphanumeric data item that is implicitly defined as:
01 SORT-CONTROL GLOBAL PICTURE X(8) USAGE DISPLAY VALUE IGZSRTCD.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. This register contains the ddname of the data set that holds the control statements used to improve the performance of a sorting or merging operation. You can provide a DD statement for the data set identified by the SORT-CONTROL special register. Enterprise COBOL will attempt to open the data set at execution time. Any error will be diagnosed with an informational message. You can specify the SORT-CONTROL special register in a function wherever an alphanumeric argument is allowed. The SORT-CONTROL special register is not necessary for a successful sorting or merging operation. The sort control file takes precedence over the SORT special registers.
SORT-CORE-SIZE
The SORT-CORE-SIZE special register is the name of a binary data item that you can use to specify the number of bytes of storage available to the sort utility. It has the implicit definition:
01 SORT-CORE-SIZE GLOBAL PICTURE S9(8) USAGE BINARY VALUE ZERO.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. SORT-CORE-SIZE can be used in place of the MAINSIZE or RESINV control statements in the sort control file: v The MAINSIZE= option control statement keyword is equivalent to SORT-CORE-SIZE with a positive value. v The RESINV= option control statement keyword is equivalent to SORT-CORE-SIZE with a negative value. v The MAINSIZE=MAX option control statement keyword is equivalent to SORT-CORE-SIZE with a value of +999999 or +99999999.
19
You can specify the SORT-CORE-SIZE special register in a function wherever an integer argument is allowed.
SORT-FILE-SIZE
The SORT-FILE-SIZE special register is the name of a binary data item that you can use to specify the estimated number of records in the sort input file, file-name-1. It has the implicit definition:
01 SORT-FILE-SIZE GLOBAL PICTURE S9(8) USAGE BINARY VALUE ZERO.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. SORT-FILE-SIZE is equivalent to the FILSZ=Ennn control statement in the sort control file. You can specify the SORT-FILE-SIZE special register in a function wherever an integer argument is allowed.
SORT-MESSAGE
The SORT-MESSAGE special register is the name of an alphanumeric data item that is available to both sort and merge programs. The SORT-MESSAGE special register has the implicit definition:
01 SORT-MESSAGE GLOBAL PICTURE X(8) USAGE DISPLAY VALUE SYSOUT.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. You can use the SORT-MESSAGE special register to specify the ddname of a data set that the sort utility should use in place of the SYSOUT data set. The ddname specified in SORT-MESSAGE is equivalent to the name specified on the MSGDDN= control statement in the sort control file. You can specify the SORT-MESSAGE special register in a function wherever an alphanumeric argument is allowed.
SORT-MODE-SIZE
The SORT-MODE-SIZE special register is the name of a binary data item that you can use to specify the length of variable-length records that occur most frequently. It has the implicit definition:
01 SORT-MODE-SIZE GLOBAL PICTURE S9(5) USAGE BINARY VALUE ZERO.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. SORT-MODE-SIZE is equivalent to the SMS= control statement in the sort control file. You can specify the SORT-MODE-SIZE special register in a function wherever an integer argument is allowed.
20
Language Reference
SORT-RETURN
The SORT-RETURN special register is the name of a binary data item and is available to both sort and merge programs. The SORT-RETURN special register has the implicit definition:
01 SORT-RETURN GLOBAL PICTURE S9(4) USAGE BINARY VALUE ZERO.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. It contains a return code of 0 (successful) or 16 (unsuccessful) at the completion of a sort or merge operation. If the sort or merge is unsuccessful and there is no reference to this special register anywhere in the program, a message is displayed on the terminal. You can set the SORT-RETURN special register to 16 in an error declarative or input/output procedure to terminate a sort or merge operation before all records are processed. The operation is terminated on the next input or output function for the sort or merge operation. You can specify the SORT-RETURN special register in a function wherever an integer argument is allowed.
TALLY
The TALLY special register is the name of a binary data item that has the following definition:
01 TALLY GLOBAL PICTURE 9(5) USAGE BINARY VALUE ZERO.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. You can refer to or modify the contents of TALLY. You can specify the TALLY special register in a function wherever an integer argument is allowed.
WHEN-COMPILED
The WHEN-COMPILED special register contains the date at the start of the compilation. WHEN-COMPILED is an alphanumeric data item that has the implicit definition:
01 WHEN-COMPILED GLOBAL PICTURE X(16) USAGE DISPLAY.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. The WHEN-COMPILED special register has the format:
MM/DD/YYhh.mm.ss (MONTH/DAY/YEARhour.minute.second)
For example, if compilation began at 2:04 PM on 27 April 2003, WHEN-COMPILED would contain the value 04/27/0314.04.00. WHEN-COMPILED can be used only as the sending field in a MOVE statement. WHEN-COMPILED special register data cannot be reference-modified.
21
The compilation date and time can also be accessed with the intrinsic function WHEN-COMPILED (see WHEN-COMPILED on page 499). That function supports four-digit year values and provides additional information.
XML-CODE
The XML-CODE special register is used for the following purposes: v To communicate status between the XML parser and the processing procedure that was identified in an XML PARSE statement v To indicate either that an XML GENERATE statement executed successfully or that an exception occurred during XML generation The XML parser sets XML-CODE prior to transferring control to the processing procedure for each event and at parser termination. You can reset XML-CODE prior to returning control from the processing procedure to the XML parser. The XML-CODE special register has the implicit definition:
01 XML-CODE PICTURE S9(9) USAGE BINARY VALUE 0.
| |
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. When the XML parser encounters an XML event, it sets XML-CODE and then passes control to the processing procedure. For all events except an EXCEPTION event, XML-CODE contains zero when the processing procedure receives control. For an EXCEPTION event, the parser sets XML-CODE to an exception code that indicates the nature of the exception. XML PARSE exception codes are detailed in the Enterprise COBOL Programming Guide. You can set XML-CODE before returning to the parser, as follows: v To -1, after a normal event, to indicate that the parser is to terminate without causing an EXCEPTION event. v To 0, after an EXCEPTION event for which continuation is allowed, to indicate that the parser is to continue processing. The parser will attempt to continue processing the XML document, but results are undefined. If you set XML-CODE to any other value before returning to the parser, results are undefined. When the parser returns control to the XML PARSE statement, XML-CODE contains the most recent value set either by the parser or by the processing procedure. | | | | At termination of an XML GENERATE statement, XML-CODE contains either zero, indicating successful completion of XML generation, or a nonzero error code, indicating that an exception occurred during XML generation. XML GENERATE exception codes are detailed in the Enterprise COBOL Programming Guide.
XML-EVENT
The XML-EVENT special register is used to communicate event information from the XML parser to the processing procedure that was identified in the XML PARSE statement. Prior to passing control to the processing procedure, the XML parser
22
Language Reference
sets the XML-EVENT special register to the name of the XML event, as described in Contents of XML-EVENT and XML-TEXT or XML-NTEXT special registers (Table 3). XML-EVENT has the implicit definition:
01 XML-EVENT USAGE DISPLAY PICTURE X(30) VALUE SPACE.
When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. XML-EVENT cannot be used as a receiving data item.
Table 3. Contents of XML-EVENT and XML-TEXT or XML-NTEXT special registers XML event (content of XML-EVENT) ATTRIBUTE-CHARACTER ATTRIBUTE-CHARACTERS ATTRIBUTE-NAME ATTRIBUTE-NATIONAL-CHARACTER Content of XML-TEXT or XML-NTEXT The single character corresponding with the predefined entity reference in the attribute value The value within quotes or apostrophes. This can be a substring of the attribute value if the value includes an entity reference. The attribute name; the string to the left of = Regardless of the type of the XML document specified by identifier-1 in the XML PARSE statement, XML-TEXT is empty and XML-NTEXT contains the single national character corresponding with the (numeric) character reference. The text of the comment between the opening character sequence  The single character corresponding with the predefined entity reference in the element content The element content between start and end tags. This can be a substring of the element content if the content contains an entity reference or another element. Regardless of the type of the XML document specified by identifier-1 in the XML PARSE statement, XML-TEXT is empty and XML-NTEXT contains the single national character corresponding with the (numeric) character reference.1 The entire document type declaration including the opening and closing character sequences, <!DOCTYPE and > The value, between quotes or apostrophes, of the encoding declaration in the XML declaration Always contains the string ]]> Null, zero-length The name of the end element tag or empty element tag The part of the document successfully scanned, up to and including the point at which the exception was detected.2 Special register XML-CODE contains the unique error code identifying the exception. The rest of the processing instruction, not including the closing sequence, ?>, but including trailing, and not leading, white space characters The processing instruction target name, which occurs immediately after the processing instruction opening sequence, <? The value, between quotes or apostrophes, of the stand-alone declaration in the XML declaration
COMMENT CONTENT-CHARACTER CONTENT-CHARACTERS
CONTENT-NATIONAL-CHARACTER
DOCUMENT-TYPE-DECLARATION ENCODING-DECLARATION END-OF-CDATA-SECTION END-OF-DOCUMENT END-OF-ELEMENT EXCEPTION
PROCESSING-INSTRUCTION-DATA
PROCESSING-INSTRUCTION-TARGET STANDALONE-DECLARATION
23
Table 3. Contents of XML-EVENT and XML-TEXT or XML-NTEXT special registers (continued) XML event (content of XML-EVENT) START-OF-CDATA-SECTION START-OF-DOCUMENT START-OF-ELEMENT UNKNOWN-REFERENCE-IN-CONTENT UNKNOWN-REFERENCE-IN-ATTRIBUTE VERSION-INFORMATION Content of XML-TEXT or XML-NTEXT Always contains the string <![CDATA[ The entire document The name of the start element tag or empty element tag, also known as the element type The entity reference name, not including the & and ; delimiters The entity reference name, not including the & and ; delimiters The value, between quotes or apostrophes, of the version declaration in the XML declaration. This is currently always 1.0.
1. National characters with scalar values greater than 65,535 (NXFFFF) are represented using two encoding units (a surrogate pair). Programmers are responsible for ensuring that operations on the content of XML-NTEXT do not split the pair of encoding units that together form a graphic character, thereby forming invalid data. 2. Exceptions for encoding conflicts are signaled before parsing begins. For these exceptions, XML-TEXT is either zero length or contains just the encoding declaration value from the document. See the Enterprise COBOL Programming Guide for information about XML exception codes.
XML-NTEXT
The XML-NTEXT special register is defined during XML parsing to contain document fragments that are USAGE NATIONAL. XML-NTEXT is an elementary national data item of the length of the contained XML document fragment. The length of XML-NTEXT can vary from 0 through 8,388,607 national character positions. The maximum byte length is 16,777,214. There is no equivalent COBOL data description entry. When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. The parser sets XML-NTEXT to the document fragment associated with an event before transferring control to the processing procedure, in these cases: v When the operand of the XML PARSE statement is a national data item v For the ATTRIBUTE-NATIONAL-CHARACTER event v For the CONTENT-NATIONAL-CHARACTER event When XML-NTEXT is set, the XML-TEXT special register has a length of zero. At any given time, only one of the two special registers XML-NTEXT and XML-TEXT has a nonzero length. Use the LENGTH function to determine the number of national characters that XML-NTEXT contains. Use the LENGTH OF special register to determine the number of bytes, rather than the number of national characters, that XML-NTEXT contains. XML-NTEXT cannot be used as a receiving item.
XML-TEXT
The XML-TEXT special register is defined during XML parsing to contain document fragments that are of class alphanumeric.
24
Language Reference
XML-TEXT is an elementary alphanumeric data item of the length of the contained XML document fragment. The length of XML-TEXT can vary from 0 through 16,777,215 bytes. There is no equivalent COBOL data description entry. When used in nested programs, this special register is implicitly defined with the global attribute in the outermost program. The parser sets XML-TEXT to the document fragment associated with an event before transferring control to the processing procedure when the operand of the XML PARSE statement is an alphanumeric data item, except for the ATTRIBUTE-NATIONAL-CHARACTER event and the CONTENT-NATIONALCHARACTER event. When XML-TEXT is set, the XML-NTEXT special register has a length of zero. At any given time, only one of the two special registers XML-NTEXT and XML-TEXT has a nonzero length. Use the LENGTH function or the LENGTH OF special register for XML-TEXT to determine the number of bytes that XML-TEXT contains. XML-TEXT cannot be used as a receiving item.
Literals
A literal is a character-string whose value is specified either by the characters of which it is composed or by the use of a figurative constant. (See Figurative constants on page 11.) For descriptions of the different types of literals, see: v Alphanumeric literals v DBCS literals on page 30 v National literals on page 31 v Numeric literals on page 29
Alphanumeric literals
Enterprise COBOL provides several formats of alphanumeric literals: v Format 1: Basic alphanumeric literals v Format 2: Alphanumeric literals with DBCS characters on page 26 v Format 3: Hexadecimal notation for alphanumeric literals on page 27 v Format 4: Null-terminated alphanumeric literals on page 28
Basic alphanumeric literals

Basic alphanumeric literals can contain any character in a single-byte EBCDIC character set. The following is the format for a basic alphanumeric literal:
Format 1: Basic alphanumeric literals single-byte-characters single-byte-characters
25
The enclosing quotation marks or apostrophes are excluded from the literal when the program is compiled. An embedded quotation mark or apostrophe must be represented by a pair of quotation marks () or a pair of apostrophes (), respectively, when it is the character used as the opening delimiter. For example:
THIS ISNT WRONG THIS ISNT WRONG
The delimiter character used as the opening delimiter for a literal must be used as the closing delimiter for that literal. For example:
THIS IS RIGHT THIS IS RIGHT THIS IS WRONG
You can use apostrophes or quotation marks as the literal delimiters independent of the APOST/QUOTE compiler option. Any punctuation characters included within an alphanumeric literal are part of the value of the literal. The maximum length of an alphanumeric literal is 160 bytes. The minimum length is 1 byte. Alphanumeric literals are in the alphanumeric data class and category. (Data classes and categories are described in Classes and categories of data on page 153.)
Alphanumeric literals with DBCS characters

When the DBCS compiler option is in effect, the characters X0E and X0F in an alphanumeric literal will be recognized as shift codes for DBCS characters. That is, the characters between paired shift codes will be recognized as DBCS characters. Unlike an alphanumeric literal compiled under the NODBCS option, additional syntax rules apply to DBCS characters in an alphanumeric literal. Alphanumeric literals with DBCS characters have the following format:
Format 2: Alphanumeric literals with DBCS characters mixed-SBCS-and-DBCS-characters mixed-SBCS-and-DBCS-characters
or
The opening and closing delimiter. The closing delimiter must match the opening delimiter.
mixed-SBCS-and-DBCS-characters Any mix of single-byte and DBCS characters. Shift-out and shift-in control characters are part of the literal and must be paired. They must contain zero or an even number of intervening bytes. Nested shift codes are not allowed in the DBCS portion of the literal. The syntax rules for single-byte characters in the literal follow the rules for basic alphanumeric literals. The syntax rules for DBCS characters in the literal follow the rules for DBCS literals. The move and comparison rules for alphanumeric literals with DBCS characters are the same as those for any alphanumeric literal.
26
Language Reference
The length of an alphanumeric literal with DBCS characters is its byte length, including the shift control characters. The maximum length is limited by the available space on one line in Area B. An alphanumeric literal with DBCS characters cannot be continued. An alphanumeric literal with DBCS characters is of the alphanumeric category. Alphanumeric literals with DBCS characters cannot be used: v As a literal in the following: ALPHABET clause ASSIGN clause CALL statement program-ID CANCEL statement CLASS clause CURRENCY SIGN clause END PROGRAM marker ENTRY statement PADDING CHARACTER clause PROGRAM-ID paragraph
v v v v
RERUN clause STOP statement As the external class-name for an object-oriented class As the basis-name in a BASIS statement As the text-name in a COPY statement As the library-name in a COPY statement
Enterprise COBOL statements process alphanumeric literals with DBCS characters without sensitivity to the shift codes and character codes. The use of statements that operate on a byte-to-byte basis (for example, STRING and UNSTRING) can result in strings that are not valid mixtures of single-byte EBCDIC and DBCS characters. See the Enterprise COBOL Programming Guide for more information about using alphanumeric literals and data items with DBCS characters in statements that operate on a byte-by-byte basis.
Hexadecimal notation for alphanumeric literals

Hexadecimal notation can be used for alphanumeric literals. Hexadecimal notation has the following format:
Format 3: Hexadecimal notation for alphanumeric literals Xhexadecimal-digits Xhexadecimal-digits
X or X The opening delimiter for the hexadecimal notation of an alphanumeric literal. or The closing delimiter for the hexadecimal notation of an alphanumeric literal. If a quotation mark is used in the opening delimiter, it must be used as the closing delimiter. Similarly, if an apostrophe is used in the opening delimiter, it must be used as the closing delimiter.
27
Hexadecimal digits are characters in the range 0 to 9, a to f, and A to F, inclusive. Two hexadecimal digits represent one character in a single-byte character set (either EBCDIC or ASCII). Four hexadecimal digits represent one character in the DBCS character set. A string of EBCDIC DBCS characters represented in hexadecimal notation must be preceded by the hexadecimal representation of a shift-out control character (X0E) and followed by the hexadecimal representation of a shift-in control character (X0F). An even number of hexadecimal digits must be specified. The maximum length of a hexadecimal literal is 320 hexadecimal digits. The continuation rules are the same as those for any alphanumeric literal. The opening delimiter (X or X) cannot be split across lines. The DBCS compiler option has no effect on the processing of hexadecimal notation of alphanumeric literals. An alphanumeric literal in hexadecimal notation has data class and category alphanumeric. Hexadecimal notation for alphanumeric literals can be used anywhere alphanumeric literals can appear. See also Hexadecimal notation for national literals on page 32.
Null-terminated alphanumeric literals

Alphanumeric literals can be null-terminated, with the following format:
Format 4: Null-terminated alphanumeric literals Zmixed-characters Zmixed-characters
Z or Z The opening delimiter for null-terminated notation of an alphanumeric literal. Both characters of the opening delimiter for null-terminated literals (Z or Z) must be on the same source line. or The closing delimiter for null-terminated notation of an alphanumeric literal. If a quotation mark is used in the opening delimiter, it must be used as the closing delimiter. Similarly, if an apostrophe is used in the opening delimiter, it must be used as the closing delimiter. mixed-characters Can be any of the following: v Solely single-byte characters v Mixed single-byte and double-byte characters v Solely double-byte characters However, you cannot specify the single-byte character with the value X00. X00 is the null character automatically appended to the end of the literal. The content of the literal is otherwise subject to the same rules and restrictions as an alphanumeric literal with DBCS characters (format 2). The length of the string of characters in the literal content can be 0 to 159 bytes. The actual length of the literal includes the terminating null character, and is a maximum of 160 bytes.
28
Language Reference
A null-terminated alphanumeric literal has data class and category alphanumeric. It can be used anywhere an alphanumeric literal can be specified except that null-terminated literals are not supported in ALL literal figurative constants. The LENGTH intrinsic function, when applied to a null-terminated literal, returns the number of bytes in the literal prior to but not including the terminating null. (The LENGTH special register does not support literal operands.)
Numeric literals
A numeric literal is a character-string whose characters are selected from the digits 0 through 9, a sign character (+ or -), and the decimal point. If the literal contains no decimal point, it is an integer. (In this documentation, the word integer appearing in a format represents a numeric literal of nonzero value that contains no sign and no decimal point, except when other rules are included with the description of the format.) The following rules apply: v If the ARITH(COMPAT) compiler option is in effect, then one through 18 digits are allowed. If the ARITH(EXTEND) compiler option is in effect, then one through 31 digits are allowed. v Only one sign character is allowed. If included, it must be the leftmost character of the literal. If the literal is unsigned, it is a positive value. v Only one decimal point is allowed. If a decimal point is included, it is treated as an assumed decimal point (that is, as not taking up a character position in the literal). The decimal point can appear anywhere within the literal except as the rightmost character. The value of a numeric literal is the algebraic quantity expressed by the characters in the literal. The size of a numeric literal is equal to the number of digits specified by the user. Numeric literals can be fixed-point or floating-point numbers.
Rules for floating-point literal values

The format and rules for floating-point literals are listed below.
Format
mantissa E + + exponent
v The sign is optional before the mantissa and the exponent; if you omit the sign, the compiler assumes a positive number. v The mantissa can contain between one and 16 digits. A decimal point must be included in the mantissa. v The exponent is represented by an E followed by an optional sign and one or two digits. v The magnitude of a floating-point literal value must fall between 0.54E-78 and 0.72E+76. For values outside of this range, an E-level diagnostic will be produced and the value will be replaced by either 0 or 0.72E+76, respectively. Numeric literals are in the numeric data class and category. (Data classes and categories are described under Classes and categories of data on page 153.)
29
DBCS literals
The formats and rules for DBCS literals are listed below.
Format for DBCS literals G<DBCS-characters> G<DBCS-characters> N<DBCS-characters> N<DBCS-characters>
G, G, N, or N Opening delimiters. N and N identify a DBCS literal when the NSYMBOL(DBCS) compiler option is in effect. They identify a national literal when the NSYMBOL(NATIONAL) compiler option is in effect, and the rules specified in National literals on page 31 apply. The opening delimiter must be followed immediately by a shift-out control character. For literals with opening delimiter N or N, when embedded quotes or apostrophes are specified as part of DBCS characters in a DBCS literal, a single embedded DBCS quote or apostrophe is represented by two DBCS quotes or apostrophes. If a single embedded DBCS quote or apostrophe is found, an E-level compiler message will be issued and a second embedded DBCS quote or apostrophe will be assumed. < > or Represents the shift-out control character (X0E) Represents the shift-in control character (X0F) The closing delimiter. If a quotation mark is used in the opening delimiter, it must be used as the closing delimiter. Similarly, if an apostrophe is used in the opening delimiter, it must be used as the closing delimiter. The closing delimiter must appear immediately after the shift-in control character. DBCS-characters DBCS-characters can be one or more characters in the range of X00 through XFF for either byte. Any value will be accepted in the content of the literal, although whether it is a valid value at run time depends on the CCSID in effect for the CODEPAGE compiler option. Maximum length 28 characters Continuation rules Cannot be continued across lines
Where DBCS literals are allowed

DBCS literals are allowed in the following places: v Data division In the VALUE clause of DBCS data description entries. If you specify a DBCS literal in a VALUE clause for a data item, the length of the literal must not exceed the size indicated by the data items PICTURE clause. Explicitly or implicitly defining a DBCS data item as USAGE DISPLAY-1 specifies that the data item is to be stored in character form, one character to each 2 bytes. In the VALUE OF clause of file description entries.
30
Language Reference
v Procedure division As an argument passed BY CONTENT in a CALL statement In the DISPLAY and EVALUATE statements As a sending item when a national item is a receiving item in an explicit MOVE statement As a sending item when a DBCS item or group item is a receiving item in the following statements: - INITIALIZE - INSPECT - MOVE - STRING - UNSTRING In a relation condition when the comparand is a DBCS item, national item, or group item As a literal in figurative constant ALL As an argument to the NATIONAL-OF intrinsic function v Compiler-directing statements COPY, REPLACE, and TITLE
National literals
Enterprise COBOL provides the following national literal formats: v Basic national literals v Hexadecimal notation for national literals on page 32
Basic national literals

The following are the format and rules for a basic national literal.
Format 1: Basic national literals Ncharacter-data Ncharacter-data
When the NSYMBOL(NATIONAL) compiler option is in effect, the opening delimiter N or N identifies a national literal. A national literal is of the class and category national. When the NSYMBOL(DBCS) compiler option is in effect, the opening delimiter N or N identifies a DBCS literal, and the rules specified in DBCS literals on page 30 apply. N or N Opening delimiters. The opening delimiter must be coded as single-byte characters. It cannot be split across lines. or The closing delimiter. The closing delimiter must be coded as a single-byte character. If a quotation mark is used in the opening delimiter, it must be used as the closing delimiter. Similarly, if an apostrophe is used in the opening delimiter, it must be used as the closing delimiter. To include the quotation mark or apostrophe used in the opening delimiter in the content of the literal, specify a pair of quotation marks or apostrophes, respectively. Examples:
31
NThis literals content includes an apostrophe NThis literal includes , which is not used in the opening delimiter NThis literal includes , which is used in the opening delimiter
character-data The source text representation of the content of the national literal. character-data can include any combination of EBCDIC single-byte characters and double-byte characters encoded in the Coded Character Set ID (CCSID) specified by the CODEPAGE compiler option. DBCS characters in the content of the literal must be delimited by shift-out and shift-in control characters. Maximum length The maximum length of a national literal is 80 character positions, excluding the opening and closing delimiters. If the source content of the literal contains one or more DBCS characters, the maximum length is limited by the available space in Area B of a single source line. The literal must contain at least one character. Each single-byte character in the literal counts as one character position and each DBCS character in the literal counts as one character position. Shift-in and shift-out delimiters for DBCS characters are not counted. Continuation rules When the content of the literal includes DBCS characters, the literal cannot be continued. When the content of the literal does not include DBCS characters, normal continuation rules apply. The source text representation of character-data is automatically converted to UTF-16 for use at run time (for example, when the literal is moved to or compared with a national data item).
Hexadecimal notation for national literals

The following are the format and rules for the hexadecimal notation format of national literals.
Format 2: Hexadecimal notation for national literals NXhexadecimal-digits NXhexadecimal-digits
The hexadecimal notation format of national literals is not affected by the NSYMBOL compiler option. NX or NX Opening delimiters. The opening delimiter must be represented in single-byte characters. It must not be split across lines. or The closing delimiter. The closing delimiter must be represented as a single-byte character. If a quotation mark is used in the opening delimiter, it must be used as the closing delimiter. Similarly, if an apostrophe is used in the opening delimiter, it must be used as the closing delimiter. hexadecimal-digits Hexadecimal digits in the range 0 to 9, a - f, and A to F, inclusive. Each group of four hexadecimal digits represents a single national character and must represent a valid code point in UTF-16. The number of hexadecimal digits must be a multiple of four.
32
Language Reference
Maximum length The length of a national literal in hexadecimal notation must be from four to 320 hexadecimal digits, excluding the opening and closing delimiters. The length must be a multiple of four. Continuation rules Normal continuation rules apply. The content of a national literal in hexadecimal notation is stored as national characters. The resulting content has the same meaning as a basic national literal that specifies the same national characters. A national literal in hexadecimal notation has data class and category national and can be used anywhere that a basic national literal can be used.
Where national literals are allowed

National literals can be used: v In a VALUE clause associated with a national data item or a VALUE clause associated with a condition-name for a national conditional variable v As a literal in the figurative constant ALL v In a relation condition v In the WHEN phrase of a format-2 SEARCH statement (binary search) v In the ALL, LEADING, or FIRST phrase of an INSPECT statement v In the BEFORE or AFTER phrase of an INSPECT statement v In the DELIMITED BY phrase of a STRING statement v In the DELIMITED BY phrase of an UNSTRING statement v As the method-name in a METHOD-ID paragraph, an END METHOD marker, and an INVOKE statement v As an argument passed BY CONTENT in the CALL statement v As an argument passed BY VALUE in an INVOKE or CALL statement v In the DISPLAY and EVALUATE statements v As a sending item in the following procedural statements: INITIALIZE INSPECT MOVE STRING UNSTRING v In the argument list to the following intrinsic functions: DISPLAY-OF, LENGTH, LOWER-CASE, MAX, MIN, ORD-MAX, ORD-MIN, REVERSE, and UPPER-CASE v In the compiler-directing statements COPY, REPLACE, and TITLE A national literal can be used only as specified in the detailed rules in this document.
PICTURE character-strings
A PICTURE character-string is composed of the currency symbol and certain combinations of characters in the COBOL character set. PICTURE character-strings are delimited only by the separator space, separator comma, separator semicolon, or separator period.
33
A chart of PICTURE clause symbols appears in PICTURE clause symbol meanings (Table 10 on page 188).
Comments
A comment is a character-string that can contain any combination of characters from the character set of the computer. It has no effect on the execution of the program. There are two forms of comments: Comment entry (identification division) This form is described under Optional paragraphs on page 99. Comment line (any division) This form is described under Comment lines on page 46. Character-strings that form comments can contain DBCS characters or a combination of DBCS and single-byte EBCDIC characters. Multiple comment lines that contain DBCS strings are allowed. The embedding of DBCS characters in a comment line must be done on a line-by-line basis. Words containing those characters cannot be continued to a following line. No syntax checking for valid strings is provided in comment lines.
34
Language Reference
Chapter 4. Separators
A separator is a character or a string of two or more contiguous characters that delimits character-strings. The separators are shown in the following table.
Table 4. Separators Separator b
1 1 1 1
Meaning Space Comma Period Semicolon Left parenthesis Right parenthesis Colon
,b .b ;b ( ) :
b b
Quotation mark Apostrophe Opening delimiter for a hexadecimal format alphanumeric literal Opening delimiter for a hexadecimal format alphanumeric literal Opening delimiter for a null-terminated alphanumeric literal Opening delimiter for a null-terminated alphanumeric literal Opening delimiter for a national literal2 Opening delimiter for a national literal2 Opening delimiter for a hexadecimal format national literal Opening delimiter for a hexadecimal format national literal Opening delimiter for a DBCS literal Opening delimiter for a DBCS literal Pseudo-text delimiter
X X Z Z N N NX NX G G ==
1. b represents a blank. 2. N and N are the opening delimiter for a DBCS literal when the NSYMBOL(DBCS) compiler option is in effect.
Rules for separators

In the following description, {} (curly braces) enclose each separator, and b represents a space. Anywhere a space is used as a separator or as part of a separator, more than one space can be used. Space {b} A space can immediately precede or follow any separator except: v The opening pseudo-text delimiter, where the preceding space is required. v Within quotation marks. Spaces between quotation marks are considered part of the alphanumeric literal; they are not considered separators.
35
Period {.b}, Comma {,b}, Semicolon {;b} A separator comma is composed of a comma followed by a space. A separator period is composed of a period followed by a space. A separator semicolon is composed of a semicolon followed by a space. The separator period must be used only to indicate the end of a sentence, or as shown in formats. The separator comma and separator semicolon can be used anywhere the separator space is used. v In the identification division, each paragraph must end with a separator period. v In the environment division, the SOURCE-COMPUTER, OBJECT-COMPUTER, SPECIAL-NAMES, and I-O-CONTROL paragraphs must each end with a separator period. In the FILE-CONTROL paragraph, each file-control entry must end with a separator period. v In the data division, file (FD), sort/merge file (SD), and data description entries must each end with a separator period. v In the procedure division, separator commas or separator semicolons can separate statements within a sentence and operands within a statement. Each sentence and each procedure must end with a separator period. Parentheses { ( } ... { ) } Except in pseudo-text, parentheses can appear only in balanced pairs of left and right parentheses. They delimit subscripts, a list of function arguments, reference-modifiers, arithmetic expressions, or conditions. Colon { : } The colon is a separator and is required when shown in general formats. Quotation marks {} ... {} An opening quotation mark must be immediately preceded by a space or a left parenthesis. A closing quotation mark must be immediately followed by a separator space, comma, semicolon, period, right parenthesis, or pseudo-text delimiter. Quotation marks must appear as balanced pairs. They delimit alphanumeric literals, except when the literal is continued (see Continuation lines on page 44). Apostrophes {} ... {} An opening apostrophe must be immediately preceded by a space or a left parenthesis. A closing apostrophe must be immediately followed by a separator space, comma, semicolon, period, right parenthesis, or pseudo-text delimiter. Apostrophes must appear as balanced pairs. They delimit alphanumeric literals, except when the literal is continued (see Continuation lines on page 44). Null-terminated literal delimiters {Z} ... {}, {Z} ... {} The opening delimiter must be immediately preceded by a space or a left parenthesis. The closing delimiter must be immediately followed by a separator space, comma, semicolon, period, right parenthesis, or pseudo-text delimiter. DBCS literal delimiters {G} ... {}, {G} ... {}, {N} ... {}, {N} ... {} The opening delimiter must be immediately preceded by a space or a left parenthesis. The closing delimiter must be immediately followed by a separator space, comma, semicolon, period, right parenthesis, or pseudo-text delimiter. N and N are DBCS literal delimiters when the NSYMBOL(DBCS) compiler option is in effect.
36
Language Reference
National literal delimiters {N} ... {}, {N} ... {}, {NX} ... {}, {NX} ... {} The opening delimiter must be immediately preceded by a space or a left parenthesis. The closing delimiter must be immediately followed by a separator space, comma, semicolon, period, right parenthesis, or pseudo-text delimiter. N and N are DBCS literal delimiters when the NSYMBOL(DBCS) compiler option is in effect. Pseudo-text delimiters {b==} ... {==b} An opening pseudo-text delimiter must be immediately preceded by a space. A closing pseudo-text delimiter must be immediately followed by a separator space, comma, semicolon, or period. Pseudo-text delimiters must appear as balanced pairs. They delimit pseudo-text. (See COPY statement on page 508.) Any punctuation character included in a PICTURE character-string, a comment character-string, or an alphanumeric literal is not considered as a punctuation character, but as part of the character-string or literal.
Chapter 4. Separators
37
38
Language Reference
Chapter 5. Sections and paragraphs

Sections and paragraphs define a program. Sections and paragraphs are subdivided into sentences, statements, and entries (see Sentences, statements, and entries). Sentences are subdivided into statements (see Statements on page 40), and statements are subdivided into phrases (see Phrases on page 40). Entries are subdivided into clauses (see Clauses on page 40) and phrases. For more information about sections, paragraphs, and statements, see Procedures on page 239.
Sentences, statements, and entries

Unless the associated rules explicitly state otherwise, each required clause or statement must be written in the sequence shown in its format. If optional clauses or statements are used, they must be written in the sequence shown in their formats. These rules are true even for clauses and statements treated as comments. The grammatical hierarchy follows this form: v Identification division Paragraphs - Entries v Clauses v Environment division Sections - Paragraphs v Entries Clauses - Phrases v Data division Sections - Entries v Clauses Phrases v Procedure division Sections - Paragraphs v Sentences Statements - Phrases
Entries
An entry is a series of clauses that ends with a separator period. Entries are constructed in the identification, environment, and data divisions.
39
Clauses
A clause is an ordered set of consecutive COBOL character-strings that specifies an attribute of an entry. Clauses are constructed in the identification, environment, and data divisions.
Sentences
A sentence is a sequence of one or more statements that ends with a separator period. Sentences are constructed in the procedure division.
Statements
A statement is a valid combination of a COBOL verb and its operands. It specifies an action to be taken by the program. Statements are constructed in the procedure division. For descriptions of the different types of statements, see: v Imperative statements on page 268 v Conditional statements on page 270 v Chapter 7, Scope of names, on page 49 v Chapter 23, Compiler-directing statements, on page 505
Phrases
Each clause or statement in a program can be subdivided into smaller units called phrases.
40
Language Reference
Chapter 6. Reference format

COBOL source text must be written in COBOL reference format. Reference format consists of the following areas in a 72-character line: Sequence number area Columns 1 through 6 Indicator area Column 7 Area A Columns 8 through 11 Area B Columns 12 through 72 The figure below illustrates reference format for a COBOL source line.
The sections below provide details about these areas: v Sequence number area v v v v Indicator area Area A on page 42 Area B on page 43 Area A or Area B on page 46
Sequence number area

The sequence number area can be used to label a source statement line. The content of this area can consist of any character in the character set of the computer.
Indicator area
Use the indicator area to specify: v The continuation of words or alphanumeric literals from the previous line onto the current line v The treatment of text as documentation v Debugging lines See Continuation lines on page 44, Comment lines on page 46, and Debugging lines on page 47. The indicator area can be used for source listing formatting. A slash (/) placed in the indicator column will cause the compiler to start a new page for the source listing, and the corresponding source record to be treated as a comment. The effect
41
can be dependent on the LINECOUNT compiler option. For information about the LINECOUNT compiler option, see the Enterprise COBOL Programming Guide.
Area A
The following items must begin in Area A: v Division headers v Section headers v Paragraph headers or paragraph names v Level indicators or level-numbers (01 and 77) v DECLARATIVES and END DECLARATIVES v End program, end class, and end method markers
Division headers
A division header is a combination of words, followed by a separator period, that indicates the beginning of a division: v IDENTIFICATION DIVISION. v ENVIRONMENT DIVISION. v DATA DIVISION. v PROCEDURE DIVISION. A division header (except when a USING phrase is specified with a procedure division header) must be immediately followed by a separator period. Except for the USING phrase, no text can appear on the same line.
Section headers
In the environment and procedure divisions, a section header indicates the beginning of a series of paragraphs. For example:
INPUT-OUTPUT SECTION.
In the data division, a section header indicates the beginning of an entry; for example:
FILE SECTION. LINKAGE SECTION. LOCAL-STORAGE SECTION. WORKING-STORAGE SECTION.
A section header must be immediately followed by a separator period.
Paragraph headers or paragraph names

A paragraph header or paragraph name indicates the beginning of a paragraph. In the environment division, a paragraph consists of a paragraph header followed by one or more entries. For example:
OBJECT-COMPUTER. computer-name.
In the procedure division, a paragraph consists of a paragraph-name followed by one or more sentences.
42
Language Reference
Level indicators (FD and SD) or level-numbers (01 and 77)

A level indicator can be either FD or SD. It must begin in Area A and be followed by a space. (See File section on page 160.) A level-number that must begin in Area A is a one- or two-digit integer with a value of 01 or 77. It must be followed by a space or separator period.
DECLARATIVES and END DECLARATIVES

DECLARATIVES and END DECLARATIVES are keywords that begin and end the declaratives part of the source unit. In the procedure division, each of the keywords DECLARATIVES and END DECLARATIVES must begin in Area A and be followed immediately by a separator period; no other text can appear on the same line. After the keywords END DECLARATIVES, no text can appear before the following section header. (See Declaratives on page 238.)
End program, end class, and end method markers

The end markers are a combination of words followed by a separator period that indicates the end of a COBOL program, method, class, factory, or object definition. For example:
END END END END END PROGRAM program-name. CLASS class-name. METHOD method-name. OBJECT. FACTORY.
For programs program-name must be identical to the program-name of the corresponding PROGRAM-ID paragraph. Every COBOL program, except an outermost program that contains no nested programs and is not followed by another batch program, must end with an END PROGRAM marker. For classes class-name must be identical to the class-name in the corresponding CLASS-ID paragraph. For methods method-name must be identical to the method-name in the corresponding METHOD-ID paragraph. For object paragraphs There is no name in an object paragraph header or in its end marker. The syntax is simply END OBJECT. For factory paragraphs There is no name in a factory paragraph header or in its end marker. The syntax is simply END FACTORY.
Area B
The following items must begin in Area B: v Entries, sentences, statements, and clauses v Continuation lines
43
Entries, sentences, statements, clauses

The first entry, sentence, statement, or clause begins on either the same line as the header or paragraph-name that it follows, or in Area B of the next nonblank line that is not a comment line. Successive sentences or entries either begin in Area B of the same line as the preceding sentence or entry, or in Area B of the next nonblank line that is not a comment line. Within an entry or sentence, successive lines in Area B can have the same format or can be indented to clarify program logic. The output listing is indented only if the input statements are indented. Indentation does not affect the meaning of the program. The programmer can choose the amount of indentation, subject only to the restrictions on the width of Area B. See also Chapter 5, Sections and paragraphs, on page 39.
Continuation lines
Any sentence, entry, clause, or phrase that requires more than one line can be continued in Area B of the next line that is neither a comment line nor a blank line. The line being continued is a continued line; the succeeding lines are continuation lines. Area A of a continuation line must be blank. If there is no hyphen (-) in the indicator area (column 7) of a line, the last character of the preceding line is assumed to be followed by a space. The following cannot be continued: v DBCS user-defined words v DBCS literals v Alphanumeric literals containing DBCS characters v National literals containing DBCS characters However, alphanumeric literals and national literals in hexadecimal notation can be continued regardless of the kind of characters expressed in hexadecimal notation. All characters that make up an opening literal delimiter must be on the same line. For example, Z, G, N, NX, or X. Both characters that make up the pseudo-text delimiter separator == must be on the same line. If there is a hyphen in the indicator area of a line, the first nonblank character of the continuation line immediately follows the last nonblank character of the continued line without an intervening space.
Continuation of alphanumeric and national literals

Alphanumeric and national literals can be continued only when there are no DBCS characters in the content of the literal. The following rules apply to alphanumeric and national literals that do not contain DBCS characters: v If the continued line contains an alphanumeric or national literal without a closing quotation mark, all spaces at the end of the continued line (through column 72) are considered to be part of the literal. The continuation line must contain a hyphen in the indicator area, and the first nonblank character must be a quotation mark. The continuation of the literal begins with the character immediately following the quotation mark.
44
Language Reference
v If an alphanumeric or national literal that is to be continued on the next line has as its last character a quotation mark in column 72, the continuation line must start with two consecutive quotation marks. This will result in a single quotation mark as part of the value of the literal. If the last character on the continued line of an alphanumeric or national literal is a single quotation mark in Area B, the continuation line can start with a single quotation mark. This will result in two consecutive literals instead of one continued literal. The rules are the same when an apostrophe is used instead of a quotation mark in delimiters. If you want to continue a literal such that the continued lines and the continuation lines are part of one literal: v Code a hyphen in the indicator area of each continuation line. v Code the literal value using all columns of each continued line, up to and including column 72. (Do not terminate the continued lines with a single quotation mark followed by a space.) v Code a quotation mark before the first character of the literal on each continuation line. v Terminate the last continuation line with a single quotation mark followed by a space. In the following examples, the number and size of literals created are indicated below the example:
|...+.*..1....+....2....+....3....+....4....+....5....+....6....+....7.. 000001 AAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE GGGGGGGGGGHHHHHHHHHHIIIIIIIIIIJJJJJJJJJJKKKKKKKKKK LLLLLLLLLLMMMMMMMMMM
v Literal 000001 is interpreted as one alphanumeric literal that is 120 bytes long. Each character between the starting quotation mark and up to and including column 72 of continued lines is counted as part of the literal.
|...+.*..1....+....2....+....3....+....4....+....5....+....6....+....7.. 000003 NAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE GGGGGGGGGG
v Literal 000003 is interpreted as one national literal that is 60 national character positions in length (120 bytes). Each character between the starting quotation mark and the ending quotation mark on the continued line is counted as part of the literal. Although single-byte characters are entered, the value of the literals is stored as national characters.
v Literal 000005 is interpreted as one literal that is 140 bytes long. The blanks at the end of each continued line are counted as part of the literal because the continued lines do not end with a quotation mark.
v Literal 000010 is interpreted as three separate literals that have lengths of 50, 50, and 20, respectively. The quotation mark with the following space terminates the
45
continued line. Only the characters within the quotation marks are counted as part of the literals. Literal 000010 is not valid as a VALUE clause literal for non-level-88 data items. To code a continued literal where the length of each continued segment of the literal is less than the length of Area-B, adjust the starting column such that the last character of the continued segment is in column 72.
Area A or Area B
The following items can begin in either Area A or Area B: v Level-numbers v Comment lines v Compiler-directing statements v Debugging lines v Pseudo-text
Level-numbers
A level-number that can begin in Area A or B is a one- or two-digit integer with a value of 02 through 49, 66, or 88. A level-number that must begin in Area A is a one- or two-digit integer with a value of 01 or 77. A level-number must be followed by a space or a separator period. For more information, see Level-numbers on page 172.
Comment lines
A comment line is any line with an asterisk (*) or slash (/) in the indicator area (column 7) of the line. The comment can be written anywhere in Area A and Area B of that line, and can consist of any combination of characters from the character set of the computer. Comment lines can be placed anywhere in a program, method, or class definition. Comment lines placed before the identification division header must follow any control cards (for example, PROCESS or CBL). Important: Comments intermixed with control cards could nullify some of the control cards and cause them to be diagnosed as errors. Multiple comment lines are allowed. Each must begin with either an asterisk (*) or a slash (/) in the indicator area. An asterisk (*) comment line is printed on the next available line in the output listing. The effect can be dependent on the LINECOUNT compiler option. For information about the LINECOUNT compiler option, see the Enterprise COBOL Programming Guide. A slash (/) comment line is printed on the first line of the next page, and the current page of the output listing is ejected. The compiler treats a comment line as documentation, and does not check it syntactically.
Compiler-directing statements
Most compiler-directing statements, including COPY and REPLACE, can start in either Area A or Area B.
46
Language Reference
BASIS, CBL (PROCESS), *CBL (*CONTROL), DELETE, EJECT, INSERT, SKIP1/2/3, and TITLE statements can also start in Area A or Area B.
Debugging lines
A debugging line is any line with a D (or d) in the indicator area of the line. Debugging lines can be written in the environment division (after the OBJECT-COMPUTER paragraph), the data division, and the procedure division. If a debugging line contains only spaces in Area A and Area B, it is considered a blank line. See WITH DEBUGGING MODE in SOURCE-COMPUTER paragraph on page 104.
Pseudo-text
The character-strings and separators that comprise pseudo-text can start in either Area A or Area B. If, however, there is a hyphen in the indicator area (column 7) of a line that follows the opening pseudo-text delimiter, Area A of the line must be blank, and the rules for continuation lines apply to the formation of text words. See Continuation lines on page 44 for details.
Blank lines
A blank line contains nothing but spaces in column 7 through column 72. A blank line can appear anywhere in a program.
47
48
Language Reference
Chapter 7. Scope of names

A user-defined word names a data resource or a COBOL programming element. Examples of named data resources are a file, a data item, or a record. Examples of named programming elements are a program, a paragraph, a method, or a class definition. The sections below define the types of names in COBOL and explain where the names can be referenced: v Types of names v External and internal resources on page 51 v Resolution of names on page 52
Types of names
In addition to identifying a resource, a name can have global or local attributes. Some names are always global, some names are always local, and some names are either local or global depending on specifications in the program in which the names are declared. For programs A global name can be used to refer to the resource with which it is associated both: v From within the program in which the global name is declared v From within any other program that is contained in the program that declares the global name Use the GLOBAL clause in the data description entry to indicate that a name is global. For more information about using the GLOBAL clause, see GLOBAL clause on page 161. A local name can be used only to refer to the resource with which it is associated from within the program in which the local name is declared. By default, if a data-name, a file-name, a record-name, or a condition-name declaration in a data description entry does not include the GLOBAL clause, the name is local. For methods All names declared in methods are implicitly local. For classes Names declared in a class definition are global to all the methods contained in that class definition. For object paragraphs Names declared in the data division of an object paragraph are global to the methods contained in that object paragraph. For factory paragraphs Names declared in the data division of a factory paragraph are global to the methods contained in that factory paragraph. Restriction: Specific rules sometimes prohibit specifying the GLOBAL clause for certain data description, file description, or record description entries.
49
The following list indicates the names that you can use and whether the name can be local or global: data-name data-name assigns a name to a data item. A data-name is global if the GLOBAL clause is specified either in the data description entry that declares the data-name or in another entry to which that data description entry is subordinate. file-name file-name assigns a name to a file connector. A file-name is global if the GLOBAL clause is specified in the file description entry for that file-name. record-name record-name assigns a name to a record. A record-name is global if the GLOBAL clause is specified in the record description that declares the record-name, or in the case of record description entries in the file section, if the GLOBAL clause is specified in the file description entry for the file name associated with the record description entry. condition-name condition-name associates a value with a conditional variable. A condition-name that is declared in a data description entry is global if that entry is subordinate to another entry that specifies the GLOBAL clause. A condition-name that is declared within the configuration section is always global. program-name program-name assigns a name to an external or internal (nested) program. For more information, see Conventions for program-names on page 80. A program-name is neither local nor global. For more information, see Conventions for program-names on page 80. method-name method-name assigns a name to a method. method-name must be specified as the content of an alphanumeric or national literal. section-name section-name assigns a name to a section in the procedure division. A section-name is always local. paragraph-name paragraph-name assigns a name to a paragraph in the procedure division. A paragraph-name is always local. basis-name basis-name specifies the name of source text that is be included by the compiler into the source unit. For details, see BASIS statement on page 505. library-name library-name specifies the COBOL library that the compiler uses for including COPY text. For details, see COPY statement on page 508.
50
Language Reference
text-name text-name specifies the name of COPY text to be included by the compiler into the source unit. For details, see COPY statement on page 508. alphabet-name alphabet-name assigns a name to a specific character set or collating sequence, or both, in the SPECIAL-NAMES paragraph of the environment division. An alphabet-name is always global. class-name (of data) class-name assigns a name to the proposition in the SPECIAL-NAMES paragraph of the environment division for which a truth value can be defined. A class-name is always global. class-name (object-oriented) class-name assigns a name to an object-oriented class or subclass. mnemonic-name mnemonic-name assigns a user-defined word to an implementer-name. A mnemonic-name is always global. symbolic-character symbolic-character specifies a user-defined figurative constant. A symbolic-character is always global. index-name index-name assigns a name to an index associated with a specific table. If a data item that possesses the global attribute includes a table accessed with an index, that index also possesses the global attribute. In addition, the scope of that index-name is identical to the scope of the data-name that includes the table.
External and internal resources

The storage associated with a data item or a file connector can be external or internal to the program or method in which the resource is declared. A data item or file connector is external if the storage associated with that resource is associated with the run unit rather than with any particular program or method within the run unit. An external resource can be referenced by any program or method in the run unit that describes the resource. References to an external resource from different programs or methods using separate descriptions of the resource are always to the same resource. In a run unit, there is only one representation of an external resource. A resource is internal if the storage associated with that resource is associated only with the program or method that describes the resource. External and internal resources can have either global or local names. A data record described in the working-storage section is given the external attribute by the presence of the EXTERNAL clause in its data description entry. Any data item described by a data description entry subordinate to an entry that describes an external record also attains the external attribute. If a record or data
51
item does not have the external attribute, it is part of the internal data of the program or method in which it is described. Two programs or methods in a run unit can reference the same file connector in the following circumstances: v An external file connector can be referenced from any program or method that describes that file connector. v If a program is contained within another program, both programs can refer to a global file connector by referring to an associated global file-name either in the containing program or in any program that directly or indirectly contains the containing program. Two programs or methods in a run unit can reference common data in the following circumstances: v The data content of an external data record can be referenced from any program or method provided that program or method has described that data record. v If a program is contained within another program, both programs can refer to data that possesses the global attribute either in the program or in any program that directly or indirectly contains the containing program. The data records described as subordinate to a file description entry that does not contain the EXTERNAL clause or to a sort-merge file description entry, as well as any data items described subordinate to the data description entries for such records, are always internal to the program or method that describes the file-name. If the EXTERNAL clause is included in the file description entry, the data records and the data items attain the external attribute.
Resolution of names
The rules for resolution of names depend on whether the names are specified in a program or in a class definition.
Names within programs

When a program, program B, is directly contained within another program, program A, both programs can define a condition-name, a data-name, a file-name, or a record-name using the same user-defined word. When such a duplicated name is referenced in program B, the following steps determine the referenced resource (these rules also apply to classes and contained methods): 1. The referenced resource is identified from the set of all names that are defined in program B and all global names defined in program A and in any programs that directly or indirectly contain program A. The normal rules for qualification and any other rules for uniqueness of reference are applied to this set of names until one or more resources is identified. 2. If only one resource is identified, it is the referenced resource. 3. If more than one resource is identified, no more than one resource can have a name local to program B. If zero or one of the resources has a name local to program B, the following rules apply: v If the name is declared in program B, the resource in program B is the referenced resource. v If the name is not declared in program B, the referenced resource is: The resource in program A if the name is declared in program A
52
Language Reference
The resource in the containing program if the name is declared in the program that contains program A This rule is applied to further containing programs until a valid resource is found.
Names within a class definition

Within a class definition, resources can be defined within the following units: v The factory data division v The object data division v A method data division If a resource is defined with a given name in the data division of an object definition, and there is no resource defined with the same name in an instance method of that object definition, a reference to that name from an instance method is a reference to the resource in the object data division. If a resource is defined with a given name in the data division of a factory definition, and there is no resource defined with the same name in a factory method of that factory definition, a reference to that name from a factory method is a reference to the resource in the factory data division. If a resource is defined within a method, any reference within the method to that resource name is always a reference to the resource in the method. The normal rules for qualification and uniqueness of reference apply when the same name is associated with more than one resource within a given method data division, object data division, or factory data division.
53
54
Language Reference
Chapter 8. Referencing data names, copy libraries, and procedure division names
References can be made to external and internal resources. References to data and procedures can be either explicit or implicit. The following sections: v Uniqueness of reference v Data attribute specification on page 66 contain the rules for qualification and for explicit and implicit data references.
Uniqueness of reference
Every user-defined name in a COBOL program is assigned by the user to name a resource for solving a data processing problem. To use a resource, a statement in a COBOL program must contain a reference that uniquely identifies that resource. To ensure uniqueness of reference, a user-defined name can be qualified. A subscript is required for unique reference to a table element, except as specified in Subscripting on page 61. A data-name or function-name, any subscripts, and the specified reference-modifier uniquely reference a data item defined by reference modification. When the same name has been assigned in separate programs to two or more occurrences of a resource of a given type, and when qualification by itself does not allow the references in one of those programs to differentiate between the identically named resources, then certain conventions that limit the scope of names apply. The conventions ensure that the resource identified is that described in the program containing the reference. For more information about resolving program-names, see Resolution of names on page 52. Unless otherwise specified by the rules for a statement, any subscripts and reference modification are evaluated only once as the first step in executing that statement.
Qualification
A name that exists within a hierarchy of names can be made unique by specifying one or more higher-level names in the hierarchy. The higher-level names are called qualifiers, and the process by which such names are made unique is called qualification. Qualification is specified by placing one or more phrases after a user-specified name, with each phrase made up of the word IN or OF followed by a qualifier. (IN and OF are logically equivalent.) In any hierarchy, the data-name associated with the highest level must be unique if it is referenced, and cannot be qualified. You must specify enough qualification to make the name unique; however, it is not always necessary to specify all the levels of the hierarchy. For example, if there is more than one file whose records contain the field EMPLOYEE-NO, but only one of the files has a record named MASTER-RECORD:
55
v EMPLOYEE-NO OF MASTER-RECORD sufficiently qualifies EMPLOYEE-NO. v EMPLOYEE-NO OF MASTER-RECORD OF MASTER-FILE is valid but unnecessary.
Qualification rules
The rules for qualifying a name are: v A name can be qualified even though it does not need qualification except in a REDEFINES clause, in which case it must not be qualified. v Each qualifier must be of a higher level than the name it qualifies and must be within the same hierarchy. v If there is more than one combination of qualifiers that ensures uniqueness, any of those combinations can be used.
Identical names
When programs are directly or indirectly contained within other programs, each program can use identical user-defined words to name resources. A program references the resources that that program describes rather than the same-named resources described in another program, even if the names are different types of user-defined words. These same rules apply to classes and their contained methods.
References to COPY libraries

Format
text-name-1 IN OF library-name-1
If library-name-1 is not specified, SYSLIB is assumed as the library name. For rules on referencing COPY libraries, see COPY statement on page 508.
References to procedure division names

Format 1
paragraph-name-1 IN OF section-name-1
Format 2
section-name-1
56
Language Reference
Procedure division names that are explicitly referenced in a program must be unique within a section. A section-name is the highest and only qualifier available for a paragraph-name and must be unique if referenced. (Section-names are described under Procedures on page 239.) If explicitly referenced, a paragraph-name must not be duplicated within a section. When a paragraph-name is qualified by a section-name, the word SECTION must not appear. A paragraph-name need not be qualified when referred to within the section in which it appears. A paragraph-name or section-name that appears in a program cannot be referenced from any other program.
References to data division names

This section discusses the following types of references: v Simple data reference v Identifier
Simple data reference

The most basic method of referencing data items in a COBOL program is simple data reference, which is data-name-1 without qualification, subscripting, or reference modification. Simple data reference is used to reference a single elementary or group item.
Format
data-name-1
data-name-1 Can be any data description entry. data-name-1 must be unique in a program.
Identifier
When used in a syntax diagram in this information, the term identifier refers to a valid combination of a data-name or function-identifier with its qualifiers, subscripts, and reference-modifiers as required for uniqueness of reference. Rules for identifiers associated with a format can however specifically prohibit qualification, subscripting, or reference modification. The term data-name refers to a name that must not be qualified, subscripted, or reference modified unless specifically permitted by the rules for the format. v For a description of qualification, see Qualification on page 55. v For a description of subscripting, see Subscripting on page 61. v For a description of reference modification, see Reference modification on page 64.
57
Format 1
data-name-1 IN OF data-name-2 IN OF file-name-1
subscript
( leftmost-character-position : length
data-name-1, data-name-2 Can be a record-name. file-name-1 Must be identified by an FD or SD entry in the data division. file-name-1 must be unique within this program.
Format 2
condition-name-1 data-name-1
IN OF
data-name-2
IN OF
file-name-1
Format 3
LINAGE-COUNTER IN OF file-name-2
data-name-1, data-name-2 Can be a record-name.
58
Language Reference
condition-name-1 Can be referenced by statements and entries either in the program that contains the configuration section or in a program contained within that program. file-name-1 Must be identified by an FD or SD entry in the data division. Must be unique within this program. LINAGE-COUNTER Must be qualified each time it is referenced if more than one file description entry that contains a LINAGE clause has been specified in the source unit. file-name-2 Must be identified by the FD or SD entry in the data division. file-name-2 must be unique within this program. Duplication of data-names must not occur in those places where the data-names cannot be made unique by qualification. In the same program, the data-name specified as the subject of the entry whose level-number is 01 that includes the EXTERNAL clause must not be the same data-name specified for any other data description entry that includes the EXTERNAL clause. In the same data division, the data description entries for any two data items for which the same data-name is specified must not include the GLOBAL clause. Data division names that are explicitly referenced must either be uniquely defined or made unique through qualification. Unreferenced data items need not be uniquely defined. The highest level in a data hierarchy (a data item associated with a level indicator (FD or SD in the file section) or with level-number 01) must be uniquely named if referenced. Data items associated with level-numbers 02 through 49 are successively lower levels of the hierarchy.
Condition-name
Format 1 (data division item)
condition-name-1 IN OF data-name-1
IN OF
file-name-1 ( subscript )
59
Format 2 (special-names item)
condition-name-1 IN OF mnemonic-name-1
condition-name-1 Can be referenced by statements and entries either in the program that contains the definition of condition-name-1, or in a program contained within that program. If explicitly referenced, a condition-name must be unique or be made unique through qualification or subscripting (or both) except when the scope of names by itself ensures uniqueness of reference. If qualification is used to make a condition-name unique, the associated conditional variable can be used as the first qualifier. If qualification is used, the hierarchy of names associated with the conditional variable itself must be used to make the condition-name unique. If references to a conditional variable require subscripting, reference to any of its condition-names also requires the same combination of subscripting. In this information, condition-name refers to a condition-name qualified or subscripted, as necessary. data-name-1 Can be a record-name. file-name-1 Must be identified by an FD or SD entry in the data division. file-name-1 must be unique within this program. mnemonic-name-1 For information about acceptable values for mnemonic-name-1, see SPECIAL-NAMES paragraph on page 106.
Index-name
| | | | | | | | | | | An index-name identifies an index. An index can be regarded as a private special register that the compiler generates for working with a table. You name an index by specifying the INDEXED BY phrase in the OCCURS clause that defines a table. You can use an index-name in only the following language elements: v SET statements v PERFORM statements v SEARCH statements v Subscripts v Relation conditions An index-name is not the same as the name of an index data item, and an index-name cannot be used like a data-name.
60
Language Reference
Index data item

| | | | | | An index data item is a data item that can hold the value of an index. You define an index data item by specifying the USAGE IS INDEX clause in a data description entry. The name of an index data item is a data-name. An index data item can be used anywhere a data-name or identifier can be used, unless stated otherwise in the rules of a particular statement. You can use the SET statement to save the value of an index (referenced by index-name) in an index data item.
Subscripting
Subscripting is a method of providing table references through the use of subscripts. A subscript is a positive integer whose value specifies the occurrence number of a table element.
Format
condition-name-1 data-name-1
IN OF
data-name-2
IN OF
file-name-1
integer-1 ALL data-name-3 + index-name-1 + integer-3 integer-2
condition-name-1 The conditional variable for condition-name-1 must contain an OCCURS clause or must be subordinate to a data description entry that contains an OCCURS clause. data-name-1 Must contain an OCCURS clause or must be subordinate to a data description entry that contains an OCCURS clause. data-name-2, file-name-1 Must name data items or records that contain data-name-1. integer-1 Can be signed. If signed, it must be positive. data-name-3 Must be a numeric elementary item representing an integer. data-name-3 can be qualified. data-name-3 cannot be a windowed date field.
61
index-name-1 Corresponds to a data description entry in the hierarchy of the table being referenced that contains an INDEXED BY phrase that specifies that name. integer-2, integer-3 Cannot be signed. The subscripts, enclosed in parentheses, are written immediately following any qualification for the name of the table element. The number of subscripts in such a reference must equal the number of dimensions in the table whose element is being referenced. That is, there must be a subscript for each OCCURS clause in the hierarchy that contains the data-name including the data-name itself. When more than one subscript is required, they are written in the order of successively less inclusive dimensions of the data organization. If a multidimensional table is thought of as a series of nested tables and the most inclusive or outermost table in the nest is considered to be the major table with the innermost or least inclusive table being the minor table, the subscripts are written from left to right in the order major, intermediate, and minor. For example, if TABLE-THREE is defined as:
01 TABLE-THREE. 05 ELEMENT-ONE OCCURS 3 TIMES. 10 ELEMENT-TWO OCCURS 3 TIMES. 15 ELEMENT-THREE OCCURS 2 TIMES
PIC X(8).
a valid subscripted reference to TABLE-THREE is:

ELEMENT-THREE (2 2 1)
Subscripted references can also be reference modified. See the third example under Reference modification examples on page 65. A reference to an item must not be subscripted unless the item is a table element or an item or condition-name associated with a table element. Each table element reference must be subscripted except when such reference appears: v In a USE FOR DEBUGGING statement v As the subject of a SEARCH statement v In a REDEFINES clause v In the KEY is phrase of an OCCURS clause The lowest permissible occurrence number represented by a subscript is 1. The highest permissible occurrence number in any particular case is the maximum number of occurrences of the item as specified in the OCCURS clause.
Subscripting using data-names

When a data-name is used to represent a subscript, it can be used to reference items within different tables. These tables need not have elements of the same size. The same data-name can appear as the only subscript with one item and as one of two or more subscripts with another item. A data-name subscript can be qualified; it cannot be subscripted or indexed. For example, valid subscripted references to TABLE-THREE, assuming that SUB1, SUB2, and SUB3 are all items subordinate to SUBSCRIPT-ITEM, include:
62
Language Reference
ELEMENT-THREE (SUB1 SUB2 SUB3) ELEMENT-THREE IN TABLE-THREE (SUB1 OF SUBSCRIPT-ITEM, SUB2 OF SUBSCRIPT-ITEM, SUB3 OF SUBSCRIPT-ITEM)
Subscripting using index-names (indexing)

Indexing allows such operations as table searching and manipulating specific items. To use indexing, you associate one or more index-names with an item whose data description entry contains an OCCURS clause. An index associated with an index-name acts as a subscript, and its value corresponds to an occurrence number for the item to which the index-name is associated. The INDEXED BY phrase, by which the index-name is identified and associated with its table, is an optional part of the OCCURS clause. There is no separate entry to describe the index associated with index-name. At run time, the contents of the index corresponds to an occurrence number for that specific dimension of the table with which the index is associated. The initial value of an index at run time is undefined, and the index must be initialized before it is used as a subscript. An initial value is assigned to an index with one of the following: v The PERFORM statement with the VARYING phrase v The SEARCH statement with the ALL phrase v The SET statement The use of an integer or data-name as a subscript that references a table element or an item within a table element does not cause the alteration of any index associated with that table. An index-name can be used to reference any table. However, the element length of the table being referenced and of the table that the index-name is associated with should match. Otherwise, the reference will not be to the same table element in each table, and you might get run-time errors. Data that is arranged in the form of a table is often searched. The SEARCH statement provides facilities for producing serial and nonserial searches. It is used to search for a table element that satisfies a specific condition and to adjust the value of the associated index to indicate that table element. To be valid during execution, an index value must correspond to a table element occurrence of neither less than one, nor greater than the highest permissible occurrence number. For more information about index-names, see Index-name on page 60 and INDEXED BY phrase on page 183.
Relative subscripting
In relative subscripting, the name of a table element is followed by a subscript of the form data-name or index-name followed by the operator + or -, and a positive or unsigned integer literal. The operators + and - must be preceded and followed by a space. The value of the subscript used is the same as if the index-name or data-name had been set up or down by the value of the integer. The use of relative indexing does not cause the program to alter the value of the index.
63
Reference modification
Reference modification defines a data item by specifying a leftmost character and optional length for the data item.
Format
data-name-1 FUNCTION function-name-1
( ( leftmost-character-position :
argument-1 ) length
data-name-1 Must reference a data item whose usage is DISPLAY, DISPLAY-1, or NATIONAL. data-name-1 can be qualified or subscripted. data-name-1 cannot be a windowed date field. function-name-1 Must reference an alphanumeric or national function. leftmost-character-position Must be an arithmetic expression. The evaluation of leftmost-characterposition must result in a positive nonzero integer that is less than or equal to the number of characters in the data item referenced by data-name-1. The evaluation of leftmost-character-position must not result in a windowed date field. length Must be an arithmetic expression. The evaluation of length must result in a positive nonzero integer. The evaluation of length must not result in a windowed date field. The sum of leftmost-character-position and length minus the value 1 must be less than or equal to the number of character positions in data-name-1. If length is omitted, the length used will be equal to the number of character positions in data-name-1 plus 1, minus leftmost-character-position. For usages DISPLAY-1 and NATIONAL, each character position occupies 2 bytes. Reference modification operates on whole character positions and not on the individual bytes of the characters in usages DISPLAY-1 and NATIONAL. For usage DISPLAY, reference modification operates as though each character were a single-byte character. Unless otherwise specified, reference modification is allowed anywhere an identifier or function-identifier that references a data item or function with the same usage as the reference-modified data item is permitted. Each character position referenced by data-name-1 or function-name-1 is assigned an ordinal number incrementing by one from the leftmost position to the rightmost position. The leftmost position is assigned the ordinal number one. If the data
64
Language Reference
description entry for data-name-1 contains a SIGN IS SEPARATE clause, the sign position is assigned an ordinal number within that data item. If data-name-1 is described as numeric, numeric-edited, alphabetic, or alphanumeric-edited, it is operated upon for purposes of reference modification as if it were redefined as an alphanumeric data item of the same size as the data item referenced by data-name-1. If data-name-1 is an expanded date field, then the result of reference modification is a nondate. Reference modification creates a unique data item that is a subset of data-name-1 or a subset of the value referenced by function-name-1 and its arguments, if any. This unique data item is considered an elementary data item without the JUSTIFIED clause. When a function is reference-modified, the unique data item has class, category, and usage national if the type of the function is national; otherwise it has class and category alphanumeric and usage display. When data-name-1 is reference-modified, the unique data item has the same class, category, and usage as that defined for the data item referenced by data-name-1. However, if the category of data-name-1 is numeric, numeric-edited, external floating-point, or alphanumeric-edited, the unique data item has the class and category alphanumeric. If length is not specified, the unique data item created extends from and includes the character position identified by leftmost-character-position up to and including the rightmost character position of the data item referenced by data-name-1.
Evaluation of operands
Reference modification for an operand is evaluated as follows: v If subscripting is specified for the operand, the reference modification is evaluated immediately after evaluation of the subscript. v If subscripting is not specified for the operand, the reference modification is evaluated at the time subscripting would be evaluated if subscripts had been specified.
Reference modification examples

The following statement transfers the first 10 characters of the data-item referenced by WHOLE-NAME to the data-item referenced by FIRST-NAME.
77 WHOLE-NAME PIC X(25). 77 FIRST-NAME PIC X(10). ... MOVE WHOLE-NAME(1:10) TO FIRST-NAME.
The following statement transfers the last 15 characters of the data-item referenced by WHOLE-NAME to the data-item referenced by LAST-NAME.
77 WHOLE-NAME PIC X(25). 77 LAST-NAME PIC X(15). ... MOVE WHOLE-NAME(11:) TO LAST-NAME.
The following statement transfers the fourth and fifth characters of the third occurrence of TAB to the variable SUFFIX.
65
01
TABLE-1. 02 TAB OCCURS 10 TIMES PICTURE X(5). 77 SUFFIX PICTURE X(2). ... MOVE TAB OF TABLE-1 (3) (4:2) TO SUFFIX.
Function-identifier
A function-identifier is a syntactically correct sequence of character strings and separators that uniquely references the data item that results from the evaluation of a function.
Format
FUNCTION function-name-1
argument-1
reference-modifier
argument-1 Must be an identifier, literal (other than a figurative constant), or arithmetic expression. For more information, see Chapter 22, Intrinsic functions, on page 459. function-name-1 function-name-1 must be one of the intrinsic function names. reference-modifier Can be specified only for functions of the category alphanumeric or national. A function-identifier that makes reference to an alphanumeric or national function can be specified anywhere that an alphanumeric identifier or national identifier, respectively, is permitted and where references to functions are not specifically prohibited, except as follows: v As a receiving operand of any statement v Where a data item is required to have particular characteristics (such as class and category, size, sign, and permissible values) and the evaluation of the function according to its definition and the particular arguments specified would not have these characteristics A function-identifier that makes reference to an integer or numeric function can be used wherever an arithmetic expression is allowed.
Data attribute specification

Explicit data attributes are data attributes that you specify in COBOL coding. Implicit data attributes are default values. If you do not explicitly code a data attribute, the compiler assumes a default value.
66
Language Reference
For example, you need not specify the USAGE of a data item. If USAGE is omitted and the symbol N is not specified in the PICTURE clause, the default is USAGE DISPLAY, which is the implicit data attribute. When PICTURE symbol N is used, USAGE DISPLAY-1 is the default when the NSYMBOL(DBCS) compiler option is in effect; USAGE NATIONAL is the default when NSYMBOL(NATIONAL) is in effect. These are implicit data attributes.
67
68
Language Reference
Chapter 9. Transfer of control

In the procedure division, unless there is an explicit control transfer or there is no next executable statement, program flow transfers control from statement to statement in the order in which the statements are written. This normal program flow is an implicit transfer of control. In addition to the implicit transfers of control between consecutive statements, implicit transfer of control also occurs when the normal flow is altered without the execution of a procedure branching statement. The following examples show implicit transfers of control, overriding statement-to-statement transfer of control: v After execution of the last statement of a procedure that is executed under control of another COBOL statement, control implicitly transfers. (COBOL statements that control procedure execution are, for example, MERGE, PERFORM, SORT, and USE.) Further, if a paragraph is being executed under the control of a PERFORM statement that causes iterative execution, and that paragraph is the first paragraph in the range of that PERFORM statement, an implicit transfer of control occurs between the control mechanism associated with that PERFORM statement and the first statement in that paragraph for each iterative execution of the paragraph. v During SORT or MERGE statement execution, control is implicitly transferred to an input or output procedure. v During XML PARSE statement execution, control is implicitly transferred to a processing procedure. v During execution of any COBOL statement that causes execution of a declarative procedure, control is implicitly transferred to that procedure. v At the end of execution of any declarative procedure, control is implicitly transferred back to the control mechanism associated with the statement that caused its execution. COBOL also provides explicit control transfers through the execution of any procedure branching, program call, or conditional statement. (Lists of procedure branching and conditional statements are contained in Statement categories on page 268.) Definition: The term next executable statement refers to the next COBOL statement to which control is transferred, according to the rules given above. There is no next executable statement under these circumstances: v When the program contains no procedure division v Following the last statement in a declarative section when the paragraph in which it appears is not being executed under the control of some other COBOL statement v Following the last statement in a program or method when the paragraph in which it appears is not being executed under the control of some other COBOL statement in that program v Following the last statement in a declarative section when the statement is in the range of an active PERFORM statement executed in a different section and this last statement of the declarative section is not also the last statement of the procedure that is the exit of the active PERFORM statement
69
v Following a STOP RUN statement or EXIT PROGRAM statement that transfers control outside the COBOL program v Following a GOBACK statement that transfers control outside the COBOL program v Following an EXIT METHOD statement that transfers control outside the COBOL method v The end program or end method marker When there is no next executable statement and control is not transferred outside the COBOL program, the program flow of control is undefined unless the program execution is in the nondeclarative procedures portion of a program under control of a CALL statement, in which case an implicit EXIT PROGRAM statement is executed. Similarly, if control reaches the end of the procedure division of a method and there is no next executable statement, an implicit EXIT METHOD statement is executed.
70
Language Reference
Chapter 10. Millennium Language Extensions and date fields

Many applications use two digits rather than four digits to represent the year in date fields, and assume that these values represent years from 1900 to 1999. This compact date format works well for the 1900s, but it does not work for the year 2000 and beyond because these applications interpret 00 as 1900 rather than 2000, producing incorrect results. The millennium language extensions are designed to allow applications that use two-digit years to continue performing correctly in the year 2000 and beyond, with minimal modification to existing code. This is achieved using a technique known as windowing, which removes the assumption that all two-digit year fields represent years from 1900 to 1999. Instead, windowing enables two-digit year fields to represent years within a 100-year range known as a century window. For example, if a two-digit year field contains the value 15, many applications would interpret the year as 1915. However, with a century window of 1960-2059, the year would be interpreted as 2015. The millennium language extensions provide support for the most common operations on date fields: comparisons, moving and storing, and incrementing and decrementing. This support is limited to date fields of certain formats; for details, see DATE FORMAT clause on page 174. For information about supported operations and restrictions when using date fields, see Restrictions on using date fields on page 176.
Millennium Language Extensions syntax

The millennium language extensions introduce the following language elements: v The DATE FORMAT clause in data description entries, which defines data items as date fields. v The following intrinsic functions: DATEVAL Converts a nondate to a date field UNDATE Converts a date field to a nondate. YEARWINDOW Returns the first year of the century window specified by the YEARWINDOW compiler option. For details on using the millennium language extensions in applications, see the Enterprise COBOL Programming Guide. The millennium language extensions have no effect unless your program is compiled using the DATEPROC compiler option and the century window is specified by the YEARWINDOW compiler option.
71
Terms and concepts

This document uses the terms discussed in the following sections when referring to the millennium language extensions: v Date field v Nondate on page 73 v Century window on page 73
Date field
A date field can be any of the following: v A data item whose data description entry includes a DATE FORMAT clause v A value returned by one of the following intrinsic functions: DATE-OF-INTEGER DATE-TO-YYYYMMDD DATEVAL DAY-OF-INTEGER DAY-TO-YYYYDDD YEAR-TO-YYYY YEARWINDOW v The conceptual data items DATE, DATE YYYYMMDD, DAY, or DAY YYYYDDD of the ACCEPT statement v The result of certain arithmetic operations (for details, see Arithmetic with date fields on page 243) The term date field refers to both expanded date fields and windowed date fields.
Windowed date field

A windowed date field is a date field that contains a windowed year. A windowed year consists of two digits, representing a year within the century window.
Expanded date field

An expanded date field is a date field that contains an expanded year. An expanded year consists of four digits. The main use of expanded date fields is to provide correct results when these are used in combination with windowed date fields; for example, where migration to four-digit year dates is not complete. If all the dates in an application use four-digit years, there is no need to use the millennium language extensions.
Year-last date field

A year-last date field is a date field whose DATE FORMAT clause specifies one or more Xs preceding the YY or YYYY. Year-last date fields are supported in a limited number of operations, typically involving another date with the same (year-last) date format, or a nondate.
Date format
Date format refers to the date pattern of a date field, specified either: v Explicitly, by the DATE FORMAT clause or DATEVAL intrinsic function argument-2 v Implicitly, by statements and intrinsic functions that return date fields (for details, see Date field above)
72
Language Reference
Compatible date field

The meaning of the term compatible, when applied to date fields, depends on the COBOL division in which the usage occurs: Data division Two date fields are compatible if they have identical USAGE and meet at least one of the following conditions: v They have the same date format. v Both are windowed date fields, where one consists only of a windowed year, DATE FORMAT YY. v Both are expanded date fields, where one consists only of an expanded year, DATE FORMAT YYYY. v One has DATE FORMAT YYXXXX, the other, YYXX. v One has DATE FORMAT YYYYXXXX, the other, YYYYXX. A windowed date field can be subordinate to an expanded date group data item. The two date fields are compatible if the subordinate date field has USAGE DISPLAY, starts 2 bytes after the start of the group expanded date field, and the two fields meet at least one of the following conditions: v The subordinate date field has a DATE FORMAT pattern with the same number of Xs as the DATE FORMAT pattern of the group date field. v The subordinate date field has DATE FORMAT YY. v The group date field has DATE FORMAT YYYYXXXX and the subordinate date field has DATE FORMAT YYXX. Procedure division Two date fields are compatible if they have the same date format except for the year part, which can be windowed or expanded. For example, a windowed date field with DATE FORMAT YYXXX is compatible with: v Another windowed date field with DATE FORMAT YYXXX v An expanded date field with DATE FORMAT YYYYXXX
Nondate
A nondate can be any of the following: v A data item whose date description entry does not include the DATE FORMAT clause v A date field that has been converted using the UNDATE function v A literal v A reference-modified date field v The result of certain arithmetic operations that can include date field operands; for example, the difference between two compatible date fields
Century window
A century window is a 100-year interval within which any two-digit year is unique. There are several ways to specify a century window in a COBOL program: v For windowed date fields, it is specified by the YEARWINDOW compiler option. v For windowing intrinsic functions DATE-TO-YYYYMMDD, DAY-TO-YYYYDDD, and YEAR-TO-YYYY, it is specified by argument-2.
Chapter 10. Millennium Language Extensions and date fields
73
74
Language Reference
Part 2. COBOL source unit structure

Chapter 11. COBOL program structure . . . . 77 Nested programs . . . . . . . . . . . . 79 Conventions for program-names . . . . . . 80 Rules for program-names . . . . . . . . 80 Chapter 12. COBOL class definition structure . Chapter 13. COBOL method definition structure . 83 87
75
76
Language Reference

A COBOL source program is a syntactically correct set of COBOL statements. Nested programs A nested program is a program that is contained in another program. Contained programs can reference some of the resources of the programs that contain them. If program B is contained in program A, it is directly contained if there is no program contained in program A that also contains program B. Program B is indirectly contained in program A if there exists a program contained in program A that also contains program B. For more information about nested programs, see Nested programs on page 79 and the Enterprise COBOL Programming Guide. Object program An object program is a set or group of executable machine language instructions and other material designed to interact with data to provide problem solutions. An object program is generally the machine language result of the operation of a COBOL compiler on a source program. The term object program also refers to the methods that result from compiling a class definition. Run unit A run unit is one or more object programs that interact with one another and that function at run time as an entity to provide problem solutions. Sibling program Sibling programs are programs that are directly contained in the same program. With the exception of the COPY and REPLACE statements and the end program marker, the statements, entries, paragraphs, and sections of a COBOL source program are grouped into the following four divisions: v Identification division v Environment division v Data division v Procedure division The end of a COBOL source program is indicated by the END PROGRAM marker. If there are no nested programs, the absence of additional source program lines also indicates the end of a COBOL program. Following is the format for the entries and statements that constitute a separately compiled COBOL source program.
77
Format: COBOL source program

IDENTIFICATION ID DIVISION. PROGRAM-ID . program-name-1
IS
RECURSIVE INITIAL
. PROGRAM
identification-division-content
ENVIRONMENT DIVISION. environment-division-content
DATA DIVISION. data-division-content
PROCEDURE DIVISION. procedure-division-content
END PROGRAM program-name-1.
Nested source program
nested source program:

IDENTIFICATION ID DIVISION. PROGRAM-ID . program-name-2
COMMON IS INITIAL COMMON INITIAL PROGRAM
identification-division-content
ENVIRONMENT DIVISION. environment-division-content
DATA DIVISION. data-division-content
PROCEDURE DIVISION. procedure-division-content | nested source program | END PROGRAM program-name-2.
A sequence of separate COBOL programs can also be input to the compiler. The following is the format for the entries and statements that constitute a sequence of source programs (batch compile).
78
Language Reference
Format: sequence of COBOL source programs
COBOL-source-program
END PROGRAM program-name An end program marker separates each program in the sequence of programs. program-name must be identical to a program-name declared in a preceding program-ID paragraph. program-name can be specified either as a user-defined word or in an alphanumeric literal. Either way, program-name must follow the rules for forming program-names. program-name cannot be a figurative constant. Any lowercase letters in the literal are folded to uppercase. An end program marker is optional for the last program in the sequence only if that program does not contain any nested source programs.
Nested programs
A COBOL program can contain other COBOL programs, which in turn can contain still other COBOL programs. These contained programs are called nested programs. Nested programs can be directly or indirectly contained in the containing program. Nested programs are not supported for programs compiled with the THREAD option. In the following code fragment, program Outer-program directly contains program Inner-1. Program Inner-1 directly contains program Inner-1a, and Outer-program indirectly contains Inner-1a:
Id division. Program-id. Outer-program. Procedure division. Call Inner-1. Stop run. Id division. Program-id. Inner-1 ... Call Inner-1a. Stop run. Id division. Program-id. Inner-1a. ... End Inner-1a. End Inner-1. End Outer-program.
The following figure describes a more complex nested program structure with directly and indirectly contained programs.
79
Conventions for program-names

The program-name of a program is specified in the PROGRAM-ID paragraph of the programs identification division. A program-name can be referenced only by the CALL statement, the CANCEL statement, the SET statement, or the END PROGRAM marker. Names of programs that constitute a run unit are not necessarily unique, but when two programs in a run unit are identically named, at least one of the programs must be directly or indirectly contained within another separately compiled program that does not contain the other of those two programs. A separately compiled program and all of its directly and indirectly contained programs must have unique program-names within that separately compiled program.
Rules for program-names

The following rules define the scope of a program-name: v If the program-name is that of a program that does not possess the COMMON attribute and that program is directly contained within another program, that program-name can be referenced only by statements included in that containing program. v If the program-name is that of a program that does possess the COMMON attribute and that program is directly contained within another program, that program-name can be referenced only by statements included in the containing
80
Language Reference
program and any programs directly or indirectly contained within that containing program, except that program possessing the COMMON attribute and any programs contained within it. v If the program-name is that of a program that is separately compiled, that program-name can be referenced by statements included in any other program in the run unit, except programs it directly or indirectly contains. The mechanism used to determine which program to call is as follows: v If one of two programs that have the same name as that specified in the CALL statement is directly contained within the program that includes the CALL statement, that program is called. v If one of two programs that have the same name as that specified in the CALL statement possesses the COMMON attribute and is directly contained within another program that directly or indirectly contains the program that includes the CALL statement, that common program is called unless the calling program is contained within that common program. v Otherwise, the separately compiled program is called. The following rules apply to referencing a program-name of a program that is contained within another program. For this discussion, Program-A contains Program-B and Program-C; Program-C contains Program-D and Program-F; and Program-D contains Program-E.
If Program-D does not possess the COMMON attribute, then Program-D can be referenced only by the program that directly contains Program-D, that is, Program-C.
81
If Program-D does possess the COMMON attribute, then Program-D can be referenced by Program-C (because Program-C contains Program-D) and by any programs contained in Program-C except for programs contained in Program-D. In other words, if Program-D possesses the COMMON attribute, Program-D can be referenced in Program-C and Program-F but not by statements in Program-E, Program-A, or Program-B.
82
Language Reference
Chapter 12. COBOL class definition structure

Enterprise COBOL provides object-oriented syntax to facilitate interoperation of COBOL and Java programs. You can use Enterprise COBOL object-oriented syntax to: v Define classes, with methods and data implemented in COBOL v Create instances of Java or COBOL classes v Invoke methods on Java or COBOL objects v Write classes that inherit from Java classes or from other COBOL classes v Define and invoke overloaded methods Basic Java-oriented object capabilities are accessed directly through COBOL language. Additional capabilities are available to the COBOL programmer by calling services through the Java Native Interface (JNI), as described in the Enterprise COBOL Programming Guide. Java programs can be multithreaded, and Java interoperation requires toleration of asynchronous signals. Therefore, to mix COBOL with these Java programs, you must use the thread enablement provided by the THREAD compiler option, as described in the Enterprise COBOL Programming Guide. Java String data is represented at run time in Unicode. The Unicode support provided in Enterprise COBOL with the national data type enables COBOL programs to exchange String data with Java. The following are the entities and concepts used in object-oriented COBOL for Java interoperability: Class The entity that defines operations and state for zero, one, or more object instances and defines operations and state for a common object (a factory object) that is shared by multiple object instances. You create object instances using the NEW operand of the COBOL INVOKE statement or using a Java class instance creation expression. Object instances are automatically freed by the Java run-time systems garbage collection when they are no longer in use. You cannot explicitly free individual objects. Instance method Procedural code that defines one of the operations supported for the object instances of a class. Instance methods introduced by a COBOL class are defined within the object paragraph of the class definition. COBOL instance methods are equivalent to public nonstatic methods in Java. You execute instance methods on a particular object instance by using a COBOL INVOKE statement or a Java method invocation expression. Instance data Data that defines the state of an individual object instance. Instance data in a COBOL class is defined in the working-storage section of the data division within the object paragraph of a class definition.
83
COBOL instance data is equivalent to private nonstatic member data in a Java class. The state of an object also includes the state of the instance data introduced by inherited classes. Each instance object has its own copy of the instance data defined within its class definition and its own copy of the instance data defined in inherited classes. You can access COBOL object instance data only from within COBOL instance methods defined in the class definition that defines the data. You can initialize object instance data with VALUE clauses or you can write an instance method to perform custom initialization. Factory method, static method Procedural code that defines one of the operations supported for the common factory object of the class. COBOL factory methods are defined within the factory paragraph of a class definition. Factory methods are associated with a class, not with any individual instance object of the class. COBOL factory methods are equivalent to public static methods in Java. You execute COBOL factory methods from COBOL using an INVOKE statement that specifies the class-name as the first operand. You execute them from a Java program using a static method invocation expression. A factory method cannot operate directly on instance data of its class, even though the data is described in the same class definition; a factory method must invoke instance methods to act on instance data. COBOL factory methods are typically used to define customized methods that create object instances. For example, you can code a customized factory method that accepts initial values as parameters, creates an instance object using the NEW operand of the INVOKE statement, and then invokes a customized instance method passing those initial values as arguments for use in initializing the instance object. Factory data, static data Data associated with a class, rather than with an individual object instance. COBOL factory data is defined in the working-storage section of the data division within the factory paragraph of a class definition. COBOL factory data is equivalent to private static data in Java. There is a single copy of factory data for a class. Factory data is associated only with the class and is shared by all object instances of the class. It is not associated with any particular instance object. A factory data item might be used, for example, to keep a count of the number of instance objects that have been created. You can access COBOL factory data only within COBOL factory methods defined in the same class definition. Inheritance Inheritance is a mechanism whereby a class definition (the inheriting class) acquires the methods, data descriptions, and file descriptions written in another class definition (the inherited class). When two classes in an inheritance relationship are considered together, the inheriting class is the subclass (or derived class or child class); the inherited class is the superclass (or parent class). The inheriting class also indirectly acquires the methods, data descriptions, and file descriptions that the parent class inherited from its parent class.
84
Language Reference
A COBOL class must inherit from exactly one parent class, which can be implemented in COBOL or Java. Every COBOL class must inherit directly or indirectly from the java.lang.Object class. Instance variable An individual data item defined in the data division of an object paragraph. Java Native Interface (JNI) A facility of Java designed for interoperation with non-Java programs. Java Native Interface (JNI) environment pointer A pointer used to obtain the address of the JNI environment structure used for calling JNI services. The COBOL special register JNIENVPTR is provided for referencing the JNI environment pointer. Object reference A data item that contains information used to identify and reference an individual object. An object reference can refer to an object that is an instance of a Java or COBOL class. Subclass A class that inherits from another class; also called a derived class or child class of the inherited class. Superclass A class that is inherited by another class; also called a parent class of the inheriting class. With the exception of the COPY and REPLACE statements and the END CLASS marker, the statements, entries, paragraphs, and sections of a COBOL class definition are grouped into the following structure: v Identification division v Environment division (configuration section only) v Factory definition Identification division Data division Procedure division - One or more method definitions v Object definition Identification division Data division Procedure division - One or more method definitions The end of a COBOL class definition is indicated by the END CLASS marker. The following is the format for a COBOL class definition.
Chapter 12. COBOL class definition structure
85
Format: COBOL class definition

IDENTIFICATION ID DIVISION. CLASS-ID . class-name-1 INHERITS class-name-2 .
other-identification-division-content ENVIRONMENT DIVISION. class-environment-division-content Factory-definition
Object-definition
END CLASS class-name-1.
Factory-definition:
IDENTIFICATION ID DIVISION. FACTORY. DATA DIVISION. factory-data-division-content END FACTORY. PROCEDURE DIVISION.
method-definition
Object-definition:
IDENTIFICATION ID DIVISION. OBJECT. DATA DIVISION. object-data-division-content END OBJECT. PROCEDURE DIVISION.
method-definition
END CLASS Specifies the end of a class definition. END FACTORY Specifies the end of a factory definition. END OBJECT Specifies the end of an object definition.
86
Language Reference
Chapter 13. COBOL method definition structure

A COBOL method definition describes a method. You can specify method definitions only within the factory paragraph and the object paragraph of a class definition. With the exception of COPY and REPLACE statements and the END METHOD marker, the statements, entries, paragraphs, and sections of a COBOL method definition are grouped into the following four divisions: v Identification division v Environment division (input-output section only) v Data division v Procedure division The end of a COBOL method definition is indicated by the END METHOD marker. The following is the format for a COBOL method definition.
Format: COBOL method definition

IDENTIFICATION ID DIVISION. METHOD-ID . method-name-1 .
other-identification-division-content
ENVIRONMENT DIVISION. method-environment-division-content
DATA DIVISION. method-data-division-content
method-procedure-division-header. method-procedure-division-content END METHOD method-name-1.
METHOD-ID Identifies a method definition. See METHOD-ID paragraph on page 98 for details. method-procedure-division-header Indicates the start of the procedure division and identifies method parameters and the returning item, if any. See The procedure division header on page 235 for details. END METHOD Specifies the end of a method definition. Methods defined in an object definition are instance methods. An instance method in a given class can access:
87
v Data defined in the data division of the object paragraph of that class (instance data) v Data defined in the data division of that instance method (method data) An instance method cannot directly access instance data defined in a parent class, factory data defined in its own class, or method data defined in another method of its class. It must invoke a method to access such data. Methods defined in a factory definition are factory methods. A factory method in a given class can access: v Data defined in the data division of the factory paragraph of that class (factory data) v Data defined in the data division of that factory method (method data) A factory method cannot directly access factory data defined in a parent class, instance data defined in its own class, or method data defined in another method of its class. It must invoke a method to access such data. Methods can be invoked from COBOL programs and methods, and they can be invoked from Java programs. A method can execute an INVOKE statement that directly or indirectly invokes itself. Therefore, COBOL methods are implicitly recursive (unlike COBOL programs, which support recursion only if the RECURSIVE attribute is specified in the program-ID paragraph.)
88
Language Reference
Part 3. Identification division

Chapter 14. Identification division . . . . PROGRAM-ID paragraph . . . . . . . CLASS-ID paragraph . . . . . . . . . General rules . . . . . . . . . . . Inheritance . . . . . . . . . . . FACTORY paragraph . . . . . . . . . OBJECT paragraph . . . . . . . . . . METHOD-ID paragraph . . . . . . . . Method signature . . . . . . . . . Method overloading, overriding, and hiding Method overloading . . . . . . . Method overriding (for instance methods) Method hiding (for factory methods) . . Optional paragraphs . . . . . . . . . . . 91 . . 94 . . 96 . . 97 . . 97 . . 97 . . 98 . . 98 . . 98 . . 98 . . 98 . . 98 . . 99 . . 99
89
90
Language Reference
Chapter 14. Identification division

The identification division must be the first division in every COBOL source program, factory definition, object definition, and method definition. It names the program, class, or method and identifies the factory definition and object definition; it can include the date a program, class, or method was written, the date of compilation, and other such documentary information. Program IDENTIFICATION DIVISION For a program, the first paragraph of the identification division must be the PROGRAM-ID paragraph. The other paragraphs are optional and can appear in any order. Class IDENTIFICATION DIVISION For a class, the first paragraph of the identification division must be the CLASS-ID paragraph. The other paragraphs are optional and can appear in any order. Factory IDENTIFICATION DIVISION A factory IDENTIFICATION DIVISION contains only a factory paragraph header. Object IDENTIFICATION DIVISION An object IDENTIFICATION DIVISION contains only an object paragraph header. Method IDENTIFICATION DIVISION For a method, the first paragraph of the identification division must be the METHOD-ID paragraph. The other paragraphs are optional and can appear in any order. The following is the format for a program IDENTIFICATION DIVISION.
91
Format: program identification division

IDENTIFICATION ID DIVISION. PROGRAM-ID . program-name
IS
RECURSIVE COMMON INITIAL INITIAL COMMON
. PROGRAM
AUTHOR . comment-entry
INSTALLATION . comment-entry
DATE-WRITTEN . comment-entry
DATE-COMPILED.
comment-entry
SECURITY . comment-entry
The following is the format for a class IDENTIFICATION DIVISION.
92
Language Reference
Format: class identification division

IDENTIFICATION DIVISION. ID DIVISION. INHERITS class-name-2. AUTHOR . comment-entry CLASS-ID. class-name-1
DATE-COMPILED.
comment-entry
The following is the format for a factory IDENTIFICATION DIVISION.
Format: factory identification division

IDENTIFICATION ID DIVISION. FACTORY.
The following is the format for an object IDENTIFICATION DIVISION.
Format: object identification division

IDENTIFICATION ID DIVISION. OBJECT.
93
The following is the format for a method IDENTIFICATION DIVISION.
Format: method identification division

IDENTIFICATION ID METHOD-ID . DIVISION.
method-name-1 .
AUTHOR . comment-entry
DATE-COMPILED.
comment-entry
PROGRAM-ID paragraph
The PROGRAM-ID paragraph specifies the name by which the program is known and assigns selected program attributes to that program. It is required and must be the first paragraph in the identification division. program-name A user-defined word or alphanumeric literal, but not a figurative constant, that identifies your program. It must follow the following rules of formation, depending on the setting of the PGMNAME compiler option: PGMNAME(COMPAT) The name can be up to 30 characters in length. Only the hyphen, digits 0-9, and alphabetic characters are allowed in the name when it is specified as a user-defined word. At least one character must be alphabetic.
94
Language Reference
The hyphen cannot be used as the first or last character. If program-name is an alphanumeric literal, the rules for the name are the same except that the extension characters $, #, and @ can be included in the name of the outermost program. PGMNAME (LONGUPPER) If program-name is a user-defined word, it can be up to 30 characters in length. If program-name is an alphanumeric literal, the literal can be up to 160 characters in length. The literal cannot be a figurative constant. Only the hyphen, digit, and alphabetic characters are allowed in the name. At least one character must be alphabetic. The hyphen cannot be used as the first or last character. PGMNAME (LONGMIXED) program-name must be specified as a literal. It cannot be a figurative constant. The name can be up to 160 characters in length. The literal cannot be a figurative constant. program-name can consist of any character in the range X41 to XFE.
For information about the PGMNAME compiler option and how the compiler processes the names, see the Enterprise COBOL Programming Guide. RECURSIVE An optional clause that allows COBOL programs to be recursively reentered. You can specify the RECURSIVE clause only on the outermost program of a compilation unit. Recursive programs cannot contain nested subprograms. If the RECURSIVE clause is specified, program-name can be recursively reentered while a previous invocation is still active. If the RECURSIVE clause is not specified, an active program cannot be recursively reentered. The working-storage section of a recursive program defines storage that is statically allocated and initialized on the first entry to a program and is available in a last-used state to any of the recursive invocations. The local-storage section of a recursive program (as well as a nonrecursive program) defines storage that is automatically allocated, initialized, and deallocated on a per-invocation basis. Internal file connectors that correspond to an FD in the file section of a recursive program are statically allocated. The status of internal file connectors is part of the last-used state of a program that persists across invocations. The following language elements are not supported in a recursive program: v ALTER v GO TO without a specified procedure-name
95
v RERUN v SEGMENT-LIMIT v USE FOR DEBUGGING The RECURSIVE clause is required for programs compiled with the THREAD option. COMMON Specifies that the program named by program-name is contained within another program, and can be called from siblings of the common program and programs contained within them. The COMMON clause can be used only in nested programs. For more information about conventions for program names, see the Enterprise COBOL Programming Guide. INITIAL Specifies that when program-name is called, program-name and any programs contained within it are placed in their initial state. The initial attribute is not supported for programs compiled with the THREAD option. A program is in the initial state: v The first time the program is called in a run unit v Every time the program is called, if it possesses the initial attribute v The first time the program is called after the execution of a CANCEL statement that references the program or a CANCEL statement that references a program that directly or indirectly contains the program v The first time the program is called after the execution of a CALL statement that references a program that possesses the initial attribute and that directly or indirectly contains the program When a program is in the initial state, the following occur: v The programs internal data contained in the working-storage section is initialized. If a VALUE clause is used in the description of the data item, the data item is initialized to the defined value. If a VALUE clause is not associated with a data item, the initial value of the data item is undefined. v Files with internal file connectors associated with the program are not in the open mode. v The control mechanisms for all PERFORM statements contained in the program are set to their initial states. v An altered GO TO statement contained in the program is set to its initial state. For the rules governing nonunique program names, see Rules for program-names on page 80.
CLASS-ID paragraph
The CLASS-ID paragraph specifies the name by which the class is known and assigns selected attributes to that class. It is required and must be the first paragraph in a class identification division. class-name-1 A user-defined word that identifies the class. class-name-1 can optionally have an entry in the REPOSITORY paragraph of the configuration section of the class definition.
96
Language Reference
INHERITS A clause that defines class-name-1 to be a subclass (or derived class) of class-name-2 (the parent class). class-name-1 cannot directly or indirectly inherit from class-name-1. class-name-2 The name of a class inherited by class-name-1. You must specify class-name-2 in the REPOSITORY paragraph of the configuration section of the class definition.
General rules
class-name-1 and class-name-2 must conform to the normal rules of formation for a COBOL user-defined word, using single-byte characters. See REPOSITORY paragraph on page 114 for details on specifying a class-name that is part of a Java package or for using non-COBOL naming conventions for class-names. You cannot include a class definition in a sequence of programs or other class definitions in a single compilation group. Each class must be specified as a separate source file; that is, a class definition cannot be included in a batch compile.
Inheritance
Every method available on instances of a class is also available on instances of any subclass directly or indirectly derived from that class. A subclass can introduce new methods that do not exist in the parent or ancestor class and can override a method from the parent or ancestor class. When a subclass overrides an existing method, it defines a new implementation for that method, which replaces the inherited implementation. The instance data of class-name-1 is the instance data declared in class-name-2 together with the data declared in the working-storage section of class-name-1. Note, however, that instance data is always private to the class that introduces it. The semantics of inheritance are as defined by Java. All classes must be derived directly or directly from the java.lang.Object class. Java supports single inheritance; that is, no class can inherit directly from more than one parent. Only one class-name can be specified in the INHERITS phrase of a class definition.
FACTORY paragraph
The factory IDENTIFICATION DIVISION introduces the factory definition, which is the portion of a class definition that defines the factory object of the class. A factory object is the single common object that is shared by all object instances of the class. The factory definition contains factory data and factory methods.
97
OBJECT paragraph
The object IDENTIFICATION DIVISION introduces the object definition, which is the portion of a class definition that defines the instance objects of the class. The object definition contains object data and object methods.
METHOD-ID paragraph
The METHOD-ID paragraph specifies the name by which a method is known and assigns selected attributes to that method. The METHOD-ID paragraph is required and must be the first paragraph in a method identification division. method-name-1 An alphanumeric literal or national literal that contains the name of the method. The name must conform to the rules of formation for a Java method name. Method names are used directly, without translation. The method name is processed in a case-sensitive manner.
Method signature
The signature of a method consists of the name of the method and the number and types of the formal parameters to the method as specified in the procedure division USING phrase.
Method overloading, overriding, and hiding

COBOL methods can be overloaded, overridden, or hidden, based on the rules of the Java language.
Method overloading
Method names that are defined for a class are not required to be unique. (The set of methods defined for a class includes the methods introduced by the class definition and the methods inherited from parent classes.) Method names defined for a class must have unique signatures. Two methods defined for a class and that have the same name but different signatures are said to be overloaded. The type of the method return value, if any, is not included in the method signature. A class must not define two methods with the same signature but different return value types, or with the same signature but where one method specifies a return value and the other does not. The rules for overloaded method definitions and resolution of overloaded method invocations are based on the corresponding rules for Java.
Method overriding (for instance methods)

An instance method in a subclass overrides an instance method with the same name that is inherited from a parent class if the two methods have the same signature. When a method overrides an instance method defined in a parent class, the presence or absence of a method return value (the procedure division RETURNING data-name) must be consistent in the two methods. Further, when
98
Language Reference
method return values are specified, the return values in the overridden method and the overriding method must have identical data types. An instance method must not override a factory method in a COBOL parent class, or a static method in a Java parent class.
Method hiding (for factory methods)

A factory method is said to hide any and all methods with the same signature in the superclasses of the method definition that would otherwise be accessible. A factory method must not hide an instance method.
Optional paragraphs
These optional paragraphs in the identification division can be omitted: AUTHOR Name of the author of the program. INSTALLATION Name of the company or location. DATE-WRITTEN Date the program was written. DATE-COMPILED Date the program was compiled. SECURITY Level of confidentiality of the program. The comment-entry in any of the optional paragraphs can be any combination of characters from the character set of the computer. The comment-entry is written in Area B on one or more lines. The paragraph name DATE-COMPILED and any comment-entry associated with it appear in the source code listing with the current date inserted. For example:
DATE-COMPILED. 04/27/03.
Comment-entries serve only as documentation; they do not affect the meaning of the program. A hyphen in the indicator area (column 7) is not permitted in comment-entries. You can include DBCS character strings as comment-entries in the identification division of your program. Multiple lines are allowed in a comment-entry that contains DBCS strings. A DBCS string must be preceded by a shift-out control character and followed by a shift-in control character. For example:
AUTHOR. <.A.U.T.H.O.R.-.N.A.M.E>, XYZ CORPORATION DATE-WRITTEN. <.D.A.T.E>
When a comment-entry that is contained on multiple lines uses DBCS characters, shift-out and shift-in characters must be paired on a line.
99
100
Language Reference
Part 4. Environment division

Chapter 15. Configuration section. . SOURCE-COMPUTER paragraph . . OBJECT-COMPUTER paragraph . . . SPECIAL-NAMES paragraph . . . . ALPHABET clause . . . . . . . SYMBOLIC CHARACTERS clause . . CLASS clause . . . . . . . . . CURRENCY SIGN clause . . . . . DECIMAL-POINT IS COMMA clause . REPOSITORY paragraph . . . . . General rules . . . . . . . . Identifying and referencing the class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 . 104 . 104 . 106 . 109 . 111 . 112 . 112 . 114 . 114 . 115 . 115 117 118 121 122 123 124 125 125 126 126 127 127 127 128 128 129 130 130 131 131 131 132 133 134 135 135 136 138 139 140 141 141 141 142
Chapter 16. Input-Output section . . . . . . FILE-CONTROL paragraph . . . . . . . . . SELECT clause . . . . . . . . . . . . . ASSIGN clause . . . . . . . . . . . . . Assignment name for environment variable . . Environment variable contents for a QSAM file Environment variable contents for a line-sequential file . . . . . . . . . . . Environment variable contents for a VSAM file RESERVE clause . . . . . . . . . . . . ORGANIZATION clause . . . . . . . . . File organization . . . . . . . . . . . Sequential organization . . . . . . . . Indexed organization . . . . . . . . . Relative organization . . . . . . . . . Line-sequential organization . . . . . . PADDING CHARACTER clause . . . . . . . RECORD DELIMITER clause . . . . . . . . ACCESS MODE clause . . . . . . . . . . File organization and access modes . . . . . Access modes . . . . . . . . . . . . Relationship between data organizations and access modes . . . . . . . . . . . . RECORD KEY clause . . . . . . . . . . . ALTERNATE RECORD KEY clause . . . . . . RELATIVE KEY clause . . . . . . . . . . PASSWORD clause . . . . . . . . . . . FILE STATUS clause . . . . . . . . . . . I-O-CONTROL paragraph . . . . . . . . . RERUN clause . . . . . . . . . . . . . SAME AREA clause . . . . . . . . . . . SAME RECORD AREA clause . . . . . . . . SAME SORT AREA clause . . . . . . . . . SAME SORT-MERGE AREA clause . . . . . . MULTIPLE FILE TAPE clause . . . . . . . . APPLY WRITE-ONLY clause . . . . . . . .
101
102
Language Reference
Chapter 15. Configuration section

The configuration section is an optional section for programs and classes, and can describe the computer environment on which the program or class is compiled and executed. Program configuration section The configuration section can be specified only in the environment division of the outermost program of a COBOL source program. You should not specify the configuration section in a program that is contained within another program. The entries specified in the configuration section of a program apply to any program contained within that program. Class configuration section Specify the configuration section in the environment division of a class definition. The repository paragraph can be specified in the environment division of a class definition. Entries in a class configuration section apply to the entire class definition, including all methods introduced by that class. Method configuration section The input-output section can be specified in a method configuration section. The entries apply only to the method in which the configuration section is specified.
Format: programs and classes

CONFIGURATION SECTION. source-computer-paragraph
object-computer-paragraph
special-names-paragraph
repository-paragraph
The configuration section can: v Relate IBM-defined environment-names to user-defined mnemonic names v Specify the collating sequence v Specify a currency sign value, and the currency symbol used in the PICTURE clause to represent the currency sign value v Exchange the functions of the comma and the period in PICTURE clauses and numeric literals v Relate alphabet-names to character sets or collating sequences v Specify symbolic characters v Relate class-names to sets of characters v Relate object-oriented class names to external class-names and identify class-names that can be used in a class definition or program
103
SOURCE-COMPUTER paragraph
The SOURCE-COMPUTER paragraph describes the computer on which the source text is to be compiled.
Format
SOURCE-COMPUTER. computer-name DEBUGGING MODE WITH .
computer-name A system-name. For example:

IBM-zSeries
WITH DEBUGGING MODE Activates a compile-time switch for debugging lines written in the source text. A debugging line is a statement that is compiled only when the compile-time switch is activated. Debugging lines allow you, for example, to check the value of a data-name at certain points in a procedure. To specify a debugging line in your program, code a D in column 7 (indicator area). You can include successive debugging lines, but each must have a D in column 7, and you cannot break character strings across lines. All your debugging lines must be written so that the program is syntactically correct, whether the debugging lines are compiled or treated as comments. The presence or absence of the DEBUGGING MODE clause is logically determined after all COPY and REPLACE statements have been processed. You can code debugging lines in the environment division (after the OBJECT-COMPUTER paragraph), and in the data and procedure divisions. If a debugging line contains only spaces in Area A and in Area B, the debugging line is treated the same as a blank line. All of the SOURCE-COMPUTER paragraph is syntax checked, but only the WITH DEBUGGING MODE clause has an effect on the execution of the program.
OBJECT-COMPUTER paragraph
The OBJECT-COMPUTER paragraph specifies the system for which the object program is designated.
104
Language Reference
Format
OBJECT-COMPUTER.
computer-name MEMORY SIZE integer WORDS CHARACTERS MODULES
entry 1
entry 1:
SEQUENCE PROGRAM COLLATING IS
alphabet-name
SEGMENT-LIMIT IS
priority-number
computer-name A system-name. For example:

IBM-zSeries
MEMORY SIZE The amount of main storage needed to run the object program. The MEMORY SIZE clause is syntax checked but has no effect on the execution of the program. integer Expressed in words, characters, or modules.
PROGRAM COLLATING SEQUENCE IS The collating sequence used in this program is the collating sequence associated with the specified alphabet-name. The collating sequence pertains to this program and any programs it might contain. alphabet-name The collating sequence. PROGRAM COLLATING SEQUENCE determines the truth value of the following alphanumeric comparisons: v Those explicitly specified in relation conditions v Those explicitly specified in condition-name conditions The PROGRAM COLLATING SEQUENCE clause also applies to any alphanumeric merge or sort keys, unless the COLLATING SEQUENCE phrase is specified in the MERGE or SORT statement. The PROGRAM COLLATING SEQUENCE clause is not applied to DBCS or national data items.
105
If the PROGRAM COLLATING SEQUENCE clause is omitted, the EBCDIC collating sequence is used. (See Appendix C, EBCDIC and ASCII collating sequences, on page 549.) SEGMENT-LIMIT IS Certain permanent segments can be overlaid by independent segments while still retaining the logical properties of fixed portion segments. (Fixed portion segments are made up of fixed permanent and fixed overlayable segments.) priority-number An integer ranging from 1 through 49. When SEGMENT-LIMIT is specified: v A fixed permanent segment is one with a priority-number less than the priority-number specified. v A fixed overlayable segment is one with a priority-number ranging from that specified through 49, inclusive. For example, if SEGMENT-LIMIT IS 25 is specified: v Sections with priority-numbers 0 through 24 are fixed permanent segments. v Sections with priority-numbers 25 through 49 are fixed overlayable segments. When SEGMENT-LIMIT is omitted, all sections with priority-numbers 0 through 49 are fixed permanent segments. Segmentation is not supported for programs compiled with the THREAD option.
All of the OBJECT-COMPUTER paragraph is syntax checked, but only the PROGRAM COLLATING SEQUENCE clause has an effect on the execution of the program.
SPECIAL-NAMES paragraph
The SPECIAL-NAMES paragraph: v Relates IBM-specified environment-names to user-defined mnemonic-names v Relates alphabetic-names to character sets or collating sequences v Specifies symbolic characters v Relates class names to sets of characters v Specifies one or more currency sign values and defines a picture symbol to represent each currency sign value in PICTURE clauses v Specifies that the functions of the comma and decimal point are to be interchanged in PICTURE clauses and numeric literals The clauses in the SPECIAL-NAMES paragraph can appear in any order.
106
Language Reference
Format
SPECIAL-NAMES. environment-name-1 IS environment-name-2 mnemonic-name-2 IS entry 1 entry 1 mnemonic-name-1
ALPHABET
alphabet-name-1 IS
STANDARD-1 STANDARD-2 NATIVE EBCDIC
literal-1
phrase 1
SYMBOLIC CHARACTERS
symbolic IN alphabet-name-2
CLASS
class-name-1 IS
literal-4 THROUGH THRU literal-5
CURRENCY SIGN IS
literal-6 PICTURE SYMBOL literal-7 WITH
DECIMAL-POINT IS
COMMA .
(1)
Notes: 1 This separator period is optional when no clauses are selected. If you use any clauses, you must code the period after the last clause.
107
Fragments entry 1:
ON STATUS OFF STATUS IS IS condition-2 ON STATUS IS condition-1 condition-1 OFF STATUS IS condition-2
phrase 1:
THROUGH THRU
literal-2
ALSO literal-3
symbolic:
symbolic-character-1 ARE IS
integer-1
environment-name-1 System devices or standard system actions taken by the compiler. Valid specifications for environment-name-1 are shown in the following table.
Table 5. Meanings of environment names environment name-1 SYSIN SYSIPT SYSOUT SYSLIST SYSLST SYSPUNCH SYSPCH CONSOLE C01-C12 CSP S01-S05 AFP-5A Meaning System logical input unit System logical output unit Allowed in ACCEPT DISPLAY
System punch device Console Skip to channel 1 through 12, respectively Suppress spacing
DISPLAY ACCEPT and DISPLAY WRITE ADVANCING WRITE ADVANCING
Pocket select 1-5 on punch devices WRITE ADVANCING Advanced Function Printing WRITE ADVANCING
environment-name-2 A 1-byte user programmable status indicator (UPSI) switch. Valid specifications for environment-name-2 are UPSI-0 through UPSI-7.
108
Language Reference
mnemonic-name-1, mnemonic-name-2 mnemonic-name-1 and mnemonic-name-2 follow the rules of formation for user-defined names. mnemonic-name-1 can be used in ACCEPT, DISPLAY, and WRITE statements. mnemonic-name-2 can be referenced only in the SET statement. mnemonic-name-2 can qualify condition-1 or condition-2 names. Mnemonic-names and environment-names need not be unique. If you choose a mnemonic-name that is also an environment-name, its definition as a mnemonic-name will take precedence over its definition as an environment-name. ON STATUS IS, OFF STATUS IS UPSI switches process special conditions within a program, such as year-beginning or year-ending processing. For example, at the beginning of the procedure division, an UPSI switch can be tested; if it is ON, the special branch is taken. (See Switch-status condition on page 262.) condition-1, condition-2 Condition-names follow the rules for user-defined names. At least one character must be alphabetic. The value associated with the condition-name is considered to be alphanumeric. A condition-name can be associated with the on status or off status of each UPSI switch specified. In the procedure division, the UPSI switch status is tested through the associated condition-name. Each condition-name is the equivalent of a level-88 item; the associated mnemonic-name, if specified, is considered the conditional variable and can be used for qualification. Condition-names specified in the SPECIAL-NAMES paragraph of a containing program can be referenced in any contained program.
ALPHABET clause
The ALPHABET clause provides a means of relating an alphabet-name to a specified character code set or collating sequence. The related character code set or collating sequence can be used for alphanumeric data, but not for DBCS or national data. ALPHABET alphabet-name-1 IS alphabet-name-1 specifies a collating sequence when used in: v The PROGRAM COLLATING SEQUENCE clause of the object-computer paragraph v The COLLATING SEQUENCE phrase of the SORT or MERGE statement alphabet-name-1 specifies a character code set when specified in: v The FD entry CODE-SET clause v The SYMBOLIC CHARACTERS clause STANDARD-1 Specifies the ASCII character set. STANDARD-2 Specifies the International Reference Version of ISO/IEC 646, 7-bit coded character set for information interchange. NATIVE Specifies the native character code set. If the ALPHABET clause is omitted, EBCDIC is assumed.
109
EBCDIC Specifies the EBCDIC character set. literal-1, literal-2, literal-3 Specifies that the collating sequence for alphanumeric data is determined by the program, according to the following rules: v The order in which literals appear specifies the ordinal number, in ascending sequence, of the characters in this collating sequence. v Each numeric literal specified must be an unsigned integer. v Each numeric literal must have a value that corresponds to a valid ordinal position within the collating sequence in effect. Appendix C, EBCDIC and ASCII collating sequences, on page 549 lists the ordinal number for characters in the single-byte EBCDIC and ASCII collating sequences. v Each character in an alphanumeric literal represents that actual character in the character set. (If the alphanumeric literal contains more than one character, each character, starting with the leftmost, is assigned a successively ascending position within this collating sequence.) v Any characters that are not explicitly specified assume positions in this collating sequence higher than any of the explicitly specified characters. The relative order within the set of these unspecified characters within the character set remains unchanged. v Within one alphabet-name clause, a given character must not be specified more than once. v Each alphanumeric literal associated with a THROUGH or ALSO phrase must be one character in length. v When the THROUGH phrase is specified, the contiguous characters in the native character set beginning with the character specified by literal-1 and ending with the character specified by literal-2 are assigned successively ascending positions in this collating sequence. This sequence can be either ascending or descending within the original native character set. That is, if Z THROUGH A is specified, the ascending values, left-to-right, for the uppercase letters are:
ZYXWVUTSRQPONMLKJIHGFEDCBA
When the ALSO phrase is specified, the characters specified as literal-1, literal-3, ... are assigned to the same position in this collating sequence. For example, if you specify:
D ALSO N ALSO %
the characters D, N, and % are all considered to be in the same position in the collating sequence. v When the ALSO phrase is specified and alphabet-name-1 is referenced in a SYMBOLIC CHARACTERS clause, only literal-1 is used to represent the character in the character set. v The character that has the highest ordinal position in this collating sequence is associated with the figurative constant HIGH-VALUE. If more than one character has the highest position because of specification of the ALSO phrase, the last character specified (or defaulted to when any characters are not
110
Language Reference
explicitly specified) is considered to be the HIGH-VALUE character for procedural statements such as DISPLAY and as the sending field in a MOVE statement. (If the ALSO phrase example given above were specified as the high-order characters of this collating sequence, the HIGH-VALUE character would be %.) v The character that has the lowest ordinal position in this collating sequence is associated with the figurative constant LOW-VALUE. If more than one character has the lowest position because of specification of the ALSO phrase, the first character specified is the LOW-VALUE character. (If the ALSO phrase example given above were specified as the low-order characters of the collating sequence, the LOW-VALUE character would be D.) When literal-1, literal-2, or literal-3 is specified, the alphabet-name must not be referred to in a CODE-SET clause (see CODE-SET clause on page 170). literal-1, literal-2, and literal-3 must be alphanumeric or numeric literals. A floating-point literal or a symbolic-character figurative constant must not be specified. All must have the same category.
SYMBOLIC CHARACTERS clause

SYMBOLIC CHARACTERS symbolic-character-1 Provides a means of specifying one or more symbolic characters. symbolic-character-1 is a user-defined word and must contain at least one alphabetic character. The same symbolic-character can appear only once in a SYMBOLIC CHARACTERS clause. The symbolic character can be a DBCS user-defined word. The SYMBOLIC CHARACTERS clause is applicable only to single-byte character sets. Each character represented is an alphanumeric character. The internal representation of symbolic-character-1 is the internal representation of the character that is represented in the specified character set. The following rules apply: v The relationship between each symbolic-character-1 and the corresponding integer-1 is by their position in the SYMBOLIC CHARACTERS clause. The first symbolic-character-1 is paired with the first integer-1; the second symbolic-character-1 is paired with the second integer-1; and so forth. v There must be a one-to-one correspondence between occurrences of symbolic-character-1 and occurrences of integer-1 in a SYMBOLIC CHARACTERS clause. v If the IN phrase is specified, integer-1 specifies the ordinal position of the character that is represented in the character set named by alphabet-name-2. This ordinal position must exist. v If the IN phrase is not specified, symbolic-character-1 represents the character whose ordinal position in the native character set is specified by integer-1. Ordinal positions are numbered starting from 1.
111
CLASS clause
CLASS class-name-1 IS Provides a means for relating a name to the specified set of characters listed in that clause. class-name-1 can be referenced only in a class condition. The characters specified by the values of the literals in this clause define the exclusive set of characters of which this class consists. The class-name in the CLASS clause can be a DBCS user-defined word. literal-4, literal-5 Must be category numeric or alphanumeric, and both must be of the same category. If numeric, they must be unsigned integers and must have a value that is greater than or equal to 1 and less than or equal to the number of characters in the alphabet specified. Each number corresponds to the ordinal position of each character in the single-byte EBCDIC or ASCII collating sequence. Floating-point literals cannot be used in the CLASS clause. If alphanumeric, the literal is the actual single-byte EBCDIC or single-byte ASCII character. literal-4 and literal-5 must not specify a symbolic-character figurative constant. If the value of the alphanumeric literal contains multiple characters, each character in the literal is included in the set of characters identified by class-name. If the alphanumeric literal is associated with a THROUGH phrase, the literal must be one character in length. THROUGH, THRU THROUGH and THRU are equivalent. If THROUGH is specified, class-name includes those characters that begin with the value of literal-4 and that end with the value of literal-5. In addition, the characters specified by a THROUGH phrase can be in either ascending or descending order.
CURRENCY SIGN clause

The CURRENCY SIGN clause affects numeric-edited data items whose PICTURE clause character-strings contain a currency symbol. A currency symbol represents a currency sign value that is: v Inserted in such data items when they are used as receiving items v Removed from such data items when they are used as sending items for a numeric or numeric-edited receiver Typically, currency sign values identify the monetary units stored in a data item. For example: $, EUR, CHF, JPY, HK$, HKD, or X9F (hexadecimal code point in some EBCDIC code pages for , the Euro currency sign). For more details on programming techniques for handling the Euro, see the Enterprise COBOL Programming Guide. The CURRENCY SIGN clause specifies a currency sign value and the currency symbol used to represent that currency sign value in a PICTURE clause.
112
Language Reference
The SPECIAL-NAMES paragraph can contain multiple CURRENCY SIGN clauses. Each CURRENCY SIGN clause must specify a different currency symbol. Unlike all other PICTURE clause symbols, currency symbols are case sensitive. For example, D and d specify different currency symbols. CURRENCY SIGN IS literal-6 literal-6 must be an alphanumeric literal. literal-6 must not be a figurative constant or a null-terminated literal. literal-6 must not contain a DBCS character. If the PICTURE SYMBOL phrase is not specified, literal-6: v Specifies both a currency sign value and the currency symbol for this currency sign value v Must be a single character v Must not be any of the following: Digits 0 through 9 Alphabetic characters A, B, C, D, E, G, N, P, R, S, V, X, Z, their lowercase equivalents, or the space Special characters + - , . * / ; ( ) = v Can be one of the following lowercase alphabetic characters: f, h, i, j, k, l, m, o, q, t, u, w, y If the PICTURE SYMBOL phrase is specified, literal-6: v Specifies a currency sign value. literal-7 in the PICTURE SYMBOL phrase specifies the currency symbol for this currency sign value. v Can consist of one or more characters. v Must not contain any of the following: Digits 0 through 9 Special characters + - . , PICTURE SYMBOL literal-7 Specifies a currency symbol that can be used in a PICTURE clause to represent the currency sign value specified by literal-6. literal-7 must be an alphanumeric literal consisting of one single-byte character. literal-7 must not be any of the following: v A figurative constant v Digits 0 through 9 v Alphabetic characters A, B, C, D, E, G, N, P, R, S, V, X, Z, their lowercase equivalents, or the space v Special characters + - , . * / ; ( ) = If the CURRENCY SIGN clause is specified, the CURRENCY and NOCURRENCY compiler options are ignored. If the CURRENCY SIGN clause is not specified and the NOCURRENCY compiler option is in effect, the dollar sign ($) is used as the default currency sign value and currency symbol. For more information about the CURRENCY and NOCURRENCY compiler options, see the Enterprise COBOL Programming Guide. Some uses of the CURRENCY SIGN clause prevent use of the NUMVAL-C intrinsic function. For details, see NUMVAL-C on page 489.
113
DECIMAL-POINT IS COMMA clause

DECIMAL-POINT IS COMMA Exchanges the functions of the period and the comma in PICTURE character-strings and in numeric literals.
REPOSITORY paragraph
The REPOSITORY paragraph is used in a program or class definition to identify all the object-oriented classes that are intended to be referenced in that program or class definition. Optionally, the REPOSITORY paragraph defines associations between class-names and external class-names.
Format
REPOSITORY.
CLASS class-name-1 IS external-class-name-1 java-array-class-reference
class-name-1 A user-defined word that identifies the class. external-class-name-1 A name that enables a COBOL program to define or access classes with class-names that are defined using Java rules of formation. You must specify external-class-name-1 as an alphanumeric literal with content that conforms to the rules of formation for a fully qualified Java class-name. If the class is part of a Java package, external-class-name-1 must specify the fully qualified name of the package, followed by ., followed by the simple name of the Java class. See Java Language Specification, Second Edition, by Gosling et al., for Java class-name formation rules. java-array-class-reference A reference that enables a COBOL program to access a class that represents an array object, where the elements of the array are themselves objects. java-array-class-reference must be an alphanumeric literal with content in the following format:
jobjectArray : external-class-name-2
jobjectArray Specifies a Java object array class. : A required separator when external-class-name-2 is specified. The colon must not be preceded or followed by space characters.
114
Language Reference
external-class-name-2 The external class-name of the type of the elements of the array. external-class-name-2 must follow the same rules of formation as external-class-name-1. When the repository entry specifies jobjectArray without the colon separator and external-class-name-2, the elements of the object array are of type java.lang.Object.
General rules
1. All referenced class-names must have an entry in the repository paragraph of the COBOL program or class definition that contains the reference. You can specify a given class-name only once in a given repository paragraph. 2. In program definitions, the repository paragraph can be specified only in the outermost program. 3. The repository paragraph of a COBOL class definition can optionally contain an entry for the name of the class itself, but this entry is not required. Such an entry can be used to specify an external class-name that uses non-COBOL characters or that specifies a fully package-qualified class-name when a COBOL class is to be part of a Java package. 4. Entries in a class repository paragraph apply to the entire class definition, including all methods introduced by that class. Entries in a program repository paragraph apply to the entire program, including its contained programs.
Identifying and referencing the class

An external-class-name is used to identify and reference a given class from outside the class definition that defines the class. The external class-name is determined by using the contents of external-class-name-1, external-class-name-2, or class-name-1 (as specified in the repository paragraph of a class), as described below: 1. external-class-name-1 and external-class-name-2 are used directly, without translation. They are processed in a case-sensitive manner. 2. class-name-1 is used if external-class-name-1 or java-array-class-reference is not specified. To create an external name that identifies the class and conforms to Java rules of formation, class-name-1 is processed as follows: v The name is converted to uppercase. v Hyphens are translated to zero. v If the first character of the name is a digit, it is converted as follows: Digits 1 though 9 are changed to A through I. 0 is changed to J. The class can be implemented in Java or COBOL. When referencing a class that is part of a Java package, external-class-name-1 must be specified and must give the fully qualified Java class-name. For example, the repository entry
Repository. Class JavaException is java.lang.Exception
defines local class-name JavaException for referring to the fully qualified external-class-name java.lang.Exception.
115
When defining a COBOL class that is to be part of a Java package, specify an entry in the repository paragraph of that class itself, giving the full Java package-qualified name as the external class-name.
116
Language Reference
Chapter 16. Input-Output section

The input-output section of the environment division contains two paragraphs: v FILE-CONTROL paragraph v I-O-CONTROL paragraph The exact contents of the input-output section depend on the file organization and access methods used. See ORGANIZATION clause on page 126 and ACCESS MODE clause on page 130. Program input-output section The same rules apply to program and method I-O sections. Class input-output section The input-output section is not valid for class definitions. Method input-output section The same rules apply to program and method I-O sections.
Format: Programs and methods
INPUT-OUTPUT SECTION. FILE-CONTROL.
file-control-paragraph
I-O-CONTROL.
i-o-control-paragraph
FILE-CONTROL The keyword FILE-CONTROL identifies the file-control paragraph. This keyword can appear only once, at the beginning of the FILE-CONTROL paragraph. It must begin in Area A and be followed by a separator period. The keyword FILE-CONTROL and the period can be omitted if no file-control-paragraph is specified and there are no files defined in the program. file-control-paragraph Names the files and associates them with the external data sets. Must begin in Area B with a SELECT clause. It must end with a separator period. See FILE-CONTROL paragraph on page 118. file-control-paragraph can be omitted if there are no files defined in the program, even if the FILE-CONTROL keyword is specified. I-O-CONTROL The keyword I-O-CONTROL identifies the I-O-CONTROL paragraph.
117
i-o-control-paragraph Specifies information needed for efficient transmission of data between the external data set and the COBOL program. The series of entries must end with a separator period. See I-O-CONTROL paragraph on page 136.
FILE-CONTROL paragraph
The FILE-CONTROL paragraph associates each file in the COBOL program with an external data set, and specifies file organization, access mode, and other information. The following are the formats for the FILE-CONTROL paragraph: v Sequential file entries v Indexed file entries v Relative file entries v Line-sequential file entries Types of files (Table 6) lists the different type of files available to Enterprise COBOL programs.
Table 6. Types of files File organization Sequential Relative Indexed Line sequential2 Access method QSAM, VSAM1 VSAM1 VSAM1 Text stream I-O
1. VSAM does not support HFS files. 2. Line-sequential support is limited to HFS files.
The FILE-CONTROL paragraph begins with the word FILE-CONTROL followed by a separator period. It must contain one and only one entry for each file described in an FD or SD entry in the data division. Within each entry, the SELECT clause must appear first. The other clauses can appear in any order, except that the PASSWORD clause for indexed files, if specified, must immediately follow the RECORD KEY or ALTERNATE RECORD KEY data-name with which it is associated.
118
Language Reference
Format 1: sequential-file-control-entries
SELECT OPTIONAL
file-name-1 ASSIGN TO
assignment-name-1
RESERVE
integer AREA AREAS ORGANIZATION IS
SEQUENTIAL
PADDING CHARACTER IS
data-name-5 literal-2
RECORD DELIMITER IS
STANDARD-1 assignment-name-2
ACCESS MODE IS
SEQUENTIAL
PASSWORD IS
data-name-6 FILE
STATUS IS
data-name-1 data-name-8
119
Format 2: indexed-file-control-entries
SELECT OPTIONAL
file-name-1 ASSIGN TO
assignment-name-1
INDEXED RESERVE integer AREA AREAS ORGANIZATION IS
RECORD ACCESS MODE IS SEQUENTIAL RANDOM DYNAMIC KEY IS
data-name-2
PASSWORD IS
data-name-6
entry 1
. STATUS FILE IS data-name-1 data-name-8
entry 1:
ALTERNATE RECORD KEY IS WITH data-name-3 DUPLICATES
PASSWORD IS
data-name-7
120
Language Reference
Format 3: relative-file-control-entries
SELECT OPTIONAL RESERVE integer
file-name-1
ASSIGN TO
assignment-name-1 RELATIVE
ORGANIZATION AREA AREAS IS
ACCESS MODE IS
SEQUENTIAL RELATIVE KEY RANDOM DYNAMIC RELATIVE KEY IS IS data-name-4 data-name-4
PASSWORD IS
data-name-6 FILE
STATUS IS
data-name-1 data-name-8
Format 4: line-sequential-file-control-entries
SELECT OPTIONAL
file-name-1 ASSIGN TO LINE SEQUENTIAL
assignment-name-1
ORGANIZATION IS
ACCESS MODE IS
SEQUENTIAL
. STATUS FILE IS data-name-1
SELECT clause
The SELECT clause identifies a file in the COBOL program to be associated with an external data set.
121
SELECT OPTIONAL Can be specified only for files opened in the input, I-O, or extend mode. You must specify SELECT OPTIONAL for those input files that are not necessarily present each time the object program is executed. For more information, see the Enterprise COBOL Programming Guide. file-name-1 Must be identified by an FD or SD entry in the data division. A file-name must conform to the rules for a COBOL user-defined name, must contain at least one alphabetic character, and must be unique within this program. When file-name-1 specifies a sort or a merge file, only the ASSIGN clause can follow the SELECT clause. If the file connector referenced by file-name-1 is an external file connector, all file-control entries in the run unit that reference this file connector must have the same specification for the OPTIONAL phrase.
ASSIGN clause
The ASSIGN clause associates the name of a file in a program with the actual external name of the data file. assignment-name-1 Identifies the external data file. It can be specified as a name or as an alphanumeric literal. assignment-name-1 is not the name of a data item, and assignment-name-1 cannot be contained in a data item. It is just a character string. Any assignment-name after the first is syntax checked, but has no effect on the execution of the program. assignment-name-1 has the following formats:
Format: QSAM file

name labelS-
Format: VSAM sequential file

ASlabelname
Format: line-sequential, VSAM indexed, or VSAM relative file

name label-
label-
Documents (for the programmer) the device and device class to which a
122
Language Reference
file is assigned. It must end in a hyphen; the specified value is not otherwise checked. It has no effect on the execution of the program. If specified, it must end with a hyphen. SASFor QSAM files, the S- (organization) field can be omitted. For VSAM sequential files, the AS- (organization) field must be specified. For VSAM indexed and relative files, the organization field must be omitted. name A required field that specifies the external name for this file. It must be either the name specified in the DD statement for this file or the name of an environment variable that contains file allocation information. For details on specifying an environment variable, see Assignment name for environment variable. name must conform to the following rules of formation: v If assignment-name-1 is a user-defined word: The name can contain from one to eight characters. The name can contain the characters A-Z, a-z, and 0-9. The leading character must be alphabetic. v If assignment-name-1 is a literal: The name can contain from one to eight characters. The name can contain the characters A-Z, a-z, 0-9, @, #, and $. The leading character must be alphabetic. For both user-defined words and literals, the compiler folds name to uppercase to form the ddname for the file. In a sort or merge file, name is treated as a comment. If the file connector referenced by file-name-1 in the SELECT clause is an external file connector, all file-control entries in the run unit that reference this file connector must have a consistent specification for assignment-name-1 in the ASSIGN clause. For QSAM files and VSAM indexed and relative files, the name specified on the first assignment-name-1 must be identical. For VSAM sequential files, it must be specified as AS-name.
Assignment name for environment variable

The name component of assignment-name-1 is initially treated as a ddname. If no file has been allocated using this ddname, then name is treated as an environment variable. The environment variable name must be defined using only uppercase because the COBOL compiler automatically folds the external file-name to uppercase. If this environment variable exists and contains a valid PATH or DSN option (described below), then the file is dynamically allocated using the information supplied by that option. If the environment variable does not contain a valid PATH or DSN option or if the dynamic allocation fails, then attempting to open the file results in file status 98.
123
The contents of the environment variable are checked at each OPEN statement. If a file was dynamically allocated by a previous OPEN statement and the contents of the environment variable have changed since the previous OPEN, then the previous allocation is dynamically deallocated prior to dynamically reallocating the file using the options currently set in the environment variable. When the run unit terminates, the COBOL run-time system automatically deallocates all automatically generated dynamic allocations.
Environment variable contents for a QSAM file

For a QSAM file, the environment variable must contain either a DSN or a PATH option in the format shown below.
Format: Environment variable (QSAM files, DSN option)

DSN(data-set-name (member-name) ) NEW OLD SHR MOD TRACKS CYL
SPACE(nnn,mmmm)
VOL(volume-serial)
UNIT(type)
KEEP DELETE CATALOG UNCATALOG
STORCLAS(storage-class)
MGMTCLAS(management-class)
DATACLAS(data-class)
data-set-name must be fully qualified. The data set must not be a temporary data set; that is, it must not start with an ampersand. After data-set-name or member-name, the data set attributes can follow in any order. The options that follow DSN (such as NEW or TRACKS) must be separated by a comma or by one or more blanks. Blanks at the beginning and end of the environment variable contents are ignored. You must not code blanks within the parentheses or between a keyword and the left parenthesis that immediately follows the keyword. COBOL does not provide a default for data set disposition (NEW, OLD, SHR, or MOD); however, your operating system might provide one. To avoid unexpected results when opening the file, you should always specify NEW, OLD, SHR, or MOD with the DSN option when you use environment variables for dynamic allocation of QSAM files. For information about specifying the values of the data set attributes, see the description of the DD statement in the z/OS MVS JCL Reference.
| | | | | | |
124
Language Reference
Format: Environment variable (QSAM files, PATH option)

PATH(path-name)
path-name must be an absolute path name; that is, it must begin with a slash. For more information about specifying path-name, see the description of the PATH parameter in z/OS MVS JCL Reference. Blanks at the beginning and end of the environment variable contents are ignored. You must not code blanks within the parentheses or between a keyword and the left parenthesis that immediately follows the keyword.
| |
Environment variable contents for a line-sequential file

For a line-sequential file, the environment variable must contain a PATH option in the following format:
Format: Environment variable (Line-sequential files, PATH option)

PATH(path-name)
path-name must be an absolute path name; that is, it must begin with a slash. For more information about specifying path-name, see the description of the PATH parameter in z/OS MVS JCL Reference. Blanks at the beginning and end of the environment variable contents are ignored. You must not code blanks within the parentheses or between a keyword and the left parenthesis that immediately follows the keyword.
| |
Environment variable contents for a VSAM file

For an indexed, relative, or sequential VSAM file, the environment variable must contain a DSN option in the following format:
Format: Environment variable (VSAM files, DSN option)

DSN(data-set-name) OLD SHR
data-set-name specifies the data set name for the base cluster. data-set-name must be fully qualified and must reference an existing predefined and cataloged VSAM data set. If an indexed file has alternate indexes, then additional environment variables must be defined that contain DSN options (as above) for each of the alternate index paths. The names of these environment variables must follow the same naming convention as used for alternate index ddnames. That is:
125
v The environment variable name for each alternate index path is formed by concatenating the base cluster environment variable name with an integer, beginning with 1 for the path associated with the first alternate index and incrementing by 1 for the path associated with each successive alternate index. (For example, if the environment variable name for the base cluster is CUST, then the environment variable names for the alternate indexes would be CUST1, CUST2, ..., .) v If the length of the base cluster environment variable name is already eight characters, then the environment variable names for the alternate indexes are formed by truncating the base cluster portion of the environment variable name on the right to reduce the concatenated result to eight characters. (For example, if the environment variable name for the base cluster is DATAFILE, then the environment variable names for the alternate clusters would be DATAFIL1, DATAFIL2, ..., .) The options that follow DSN (such as SHR) must be separated by a comma or by one or more blanks. Blanks at the beginning and end of the environment variable contents are ignored. You must not code blanks within the parentheses or between a keyword and the left parenthesis that immediately follows the keyword. COBOL does not provide a default for data set disposition (OLD or SHR); however, your operating system might provide one. To avoid unexpected results when opening the file, you should always specify OLD or SHR with the DSN option when you use environment variables for dynamic allocation of VSAM files.
| | | | | |
RESERVE clause
The RESERVE clause allows the user to specify the number of input/output buffers to be allocated at run time for the files. The RESERVE clause is not supported for line-sequential files. If the RESERVE clause is omitted, the number of buffers at run time is taken from the DD statement. If none is specified, the system default is taken. If the file connector referenced by file-name-1 in the SELECT clause is an external file connector, all file-control entries in the run unit that reference this file connector must have the same value for the integer specified in the RESERVE clause.
ORGANIZATION clause
The ORGANIZATION clause identifies the logical structure of the file. The logical structure is established at the time the file is created and cannot subsequently be changed. You can find a discussion of the different ways in which data can be organized and of the different access methods that you can use to retrieve the data under File organization and access modes on page 131.
126
Language Reference
ORGANIZATION IS SEQUENTIAL (format 1) A predecessor-successor relationship among the records in the file is established by the order in which records are placed in the file when it is created or extended. ORGANIZATION IS INDEXED (format 2) The position of each logical record in the file is determined by indexes created with the file and maintained by the system. The indexes are based on embedded keys within the files records. ORGANIZATION IS RELATIVE (format 3) The position of each logical record in the file is determined by its relative record number. ORGANIZATION IS LINE SEQUENTIAL (format 4) A predecessor-successor relationship among the records in the file is established by the order in which records are placed in the file when it is created or extended. A record in a LINE SEQUENTIAL file can consist only of printable characters. If you omit the ORGANIZATION clause, the compiler assumes ORGANIZATION IS SEQUENTIAL. If the file connector referenced by file-name-1 in the SELECT clause is an external file connector, the same organization must be specified for all file-control entries in the run unit that reference this file connector.
File organization
You establish the organization of the data when you create a file. Once the file has been created, you can expand the file, but you cannot change the organization.
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. Records can be fixed length or variable length; there are no keys. Each record in the file except the first has a unique predecessor record; and each record except the last has a unique successor record.
Indexed organization
Each record in the file has one or more embedded keys (referred to as key data items); each key 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. Indexed files must be direct-access storage files. Records can be fixed length or variable length. Each record in an indexed file must have an embedded prime key data item. When records are inserted, updated, or deleted, they are identified solely by the values of their prime keys. Thus, the value in each prime key data item must be unique and must not be changed when the record is updated. You tell COBOL the name of the prime key data item in the RECORD KEY clause of the file-control paragraph. In addition, each record in an indexed file can contain one or more embedded alternate key data items. Each alternate key provides another means of identifying which record to retrieve. You tell COBOL the name of any alternate key data items on the ALTERNATE RECORD KEY clause of the file-control paragraph.
127
The key used for any specific input-output request is known as the key of reference.
Relative organization
Think of the file as a string of record areas, each of which contains a single record. Each record area is identified by a relative record number; the access method stores and retrieves a record based on its relative record number. For example, the first record area is addressed by relative record number 1 and the 10th is addressed by relative record number 10. The physical sequence in which the records were placed in the file has no bearing on the record area in which they are stored, and thus no effect on each records relative record number. Relative files must be direct-access files. Records can be fixed length or variable length.
Line-sequential organization
In a line-sequential file, each record contains a sequence of characters that ends with a record delimiter. The delimiter is not counted in the length of the record. When a record is written, any trailing blanks are removed prior to adding the record delimiter. The characters in the record area from the first character up to and including the added record delimiter constitute one record and are written to the file. When a record is read, characters are read one at a time into the record area until: v The first record delimiter is encountered. The record delimiter is discarded and the remainder of the record is filled with spaces. v The entire record area is filled with characters. If the first unread character is the record delimiter, it is discarded. Otherwise, the first unread character becomes the first character read by the next READ statement. Records written to line-sequential files must consist of data items described as USAGE DISPLAY or DISPLAY-1 or a combination of DISPLAY and DISPLAY-1 items. An external decimal data item either must be unsigned or, if signed, must be declared with the SEPARATE CHARACTER phrase. A line-sequential file must contain only printable characters and the following control characters: v Alarm (X2F) v Backspace (X16) v Form feed (X0C) v New-line (X15) v Carriage-return (X0D) v Horizontal tab (X05) v Vertical tab (X0B) v DBCS shift-out (X0E) v DBCS shift-in (X0F)
Control character Bell Backspace Form feed Line feed Carriage-return ASCII hex value 07 08 0C 0A 0D EBCDIC hex value 2F 16 0C 15 0D
128
Language Reference
Control character Horizontal tab Vertical tab Dummy DBCS shift-out Dummy DBCS shift-in DBCS shift-out DBCS shift-in
ASCII hex value 09 0B 1E 1F
EBCDIC hex value 05 0B
0E 0F
New-line characters are processed as record delimiters. Other control characters are treated by COBOL as part of the data for the records in the file. The following are not supported for line-sequential files: v APPLY WRITE-ONLY clause v CODE-SET clause v DATA RECORDS clause v LABEL RECORDS clause v LINAGE clause v I-O phrase of the OPEN statement v PADDING CHARACTER clause v RECORD CONTAINS 0 clause v RECORD CONTAINS clause format 2 (for example: RECORD CONTAINS 100 to 200 CHARACTERS) v RECORD DELIMITER clause v RECORDING MODE clause v v v v v v v v RERUN clause RESERVE clause REVERSED phrase of the OPEN statement REWRITE statement VALUE OF clause of file description entry WRITE ... AFTER ADVANCING mnemonic-name WRITE ... AT END-OF-PAGE WRITE ... BEFORE ADVANCING
PADDING CHARACTER clause

The PADDING CHARACTER clause specifies a character to be used for block padding on sequential files. data-name-5 Must be defined in the data division as an alphanumeric one-character data item, and must not be defined in the file section. data-name-5 can be qualified. literal-2 Must be a one-character alphanumeric literal. For external files, if data-name-5 is specified, it must reference an external data item.
129
The PADDING CHARACTER clause is syntax checked, but has no effect on the execution of the program.
RECORD DELIMITER clause

The RECORD DELIMITER clause indicates the method of determining the length of a variable-length record on an external medium. It can be specified only for variable-length records. STANDARD-1 If STANDARD-1 is specified, the external medium must be a magnetic tape file. assignment-name-2 Can be any COBOL word. The RECORD DELIMITER clause is syntax checked, but has no effect on the execution of the program.
ACCESS MODE clause

The ACCESS MODE clause 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. For sequentially accessed relative files, the ACCESS MODE clause does not have to precede the RELATIVE KEY clause. ACCESS MODE IS SEQUENTIAL Can be specified in all four formats. Format 1: sequential Records in the file are accessed in the sequence established when the file is created or extended. Format 1 supports only sequential access. Format 2: indexed Records in the file are accessed in the sequence of ascending record key values according to the collating sequence of the file. Format 3: relative Records in the file are accessed in the ascending sequence of relative record numbers of existing records in the file. Format 4: line-sequential Records in the file are accessed in the sequence established when the file is created or extended. Format 4 supports only sequential access.
ACCESS MODE IS RANDOM Can be specified in formats 2 and 3 only. Format 2: indexed The value placed in a record key data item specifies the record to be accessed. Format 3: relative The value placed in a relative key data item specifies the record to be accessed.
130
Language Reference
ACCESS MODE IS DYNAMIC Can be specified in formats 2 and 3 only. Format 2: indexed Records in the file can be accessed sequentially or randomly, depending on the form of the specific input-output statement used. Format 3: relative Records in the file can be accessed sequentially or randomly, depending on the form of the specific input-output request.
File organization and access modes

File organization is the permanent logical structure of the file. You tell the computer how to retrieve records from the file by specifying the access mode (sequential, random, or dynamic). For details on the access methods and data organization, see Types of files (Table 6 on page 118). Sequentially organized data can be accessed only sequentially; however, data that has indexed or relative organization can be accessed in any of the three access modes.
Access modes
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 the specific input-output statement to determine the access mode. Therefore, records can be processed sequentially or randomly or both. For external files, every file-control entry in the run unit that is associated with that external file must specify the same access mode. In addition, for relative file entries, data-name-4 must reference an external data item, and the RELATIVE KEY phrase in each associated file-control entry must reference that same external data item in each case.
Relationship between data organizations and access modes

This section discusses which access modes are valid for each type of data organization. Sequential files Files with sequential organization can be accessed only sequentially. The sequence in which records are accessed is the order in which the records were originally written. Line-sequential files Same as for sequential files (described above). Indexed files All three access modes are allowed.
131
In the sequential access mode, the sequence in which records are accessed is the ascending order of the record key value. The order of retrieval within a set of records that have duplicate alternate record key values is the order in which records were written into the set. In the random access mode, you control the sequence in which records are accessed. The desired record is accessed by placing the value of its key or keys in the RECORD KEY data item (and the ALTERNATE RECORD KEY data item). If a set of records has duplicate alternate record key values, only the first record written is available. In the dynamic access mode, you can change as needed from sequential access to random access by using appropriate forms of input-output statements. Relative files All three access modes are allowed. In the sequential access mode, the sequence in which records are accessed is the ascending order of the relative record numbers of all records that exist within the file. In the random access mode, you control the sequence in which records are accessed. The desired record is accessed by placing its relative record number in the RELATIVE KEY data item; the RELATIVE KEY must not be defined within the record description entry for the file. In the dynamic access mode, you can change as needed from sequential access to random access by using appropriate forms of input-output statements.
RECORD KEY clause

The RECORD KEY clause (format 2) specifies the data item within the record that is the prime RECORD KEY for an indexed file. The values contained in the prime RECORD KEY data item must be unique among records in the file. data-name-2 The prime RECORD KEY data item. It must be described within a record description entry associated with the file. It can be any of the following types of data item: v Alphanumeric v v v v v v v v Numeric Numeric-edited Alphanumeric-edited Alphabetic External floating-point Internal floating-point DBCS National
Regardless of the category of the key data item, the key is treated as an alphanumeric item. The collation order of the key is determined by the items binary value order when the key is used for locating a record or for setting the file position indicator associated with the file. data-name-2 cannot be a windowed date field.
132
Language Reference
data-name-2 must not reference a group item that contains a variable-occurrence data item. data-name-2 can be qualified. If the indexed file contains variable-length records, data-name-2 need not be contained within the minimum record size specified for the file. That is, data-name-2 can exceed the minimum record size, but this is not recommended. The data description of data-name-2 and its relative location within the record must be the same as those used when the file was defined. If the file has more than one record description entry, data-name-2 need be described in only one of those record description entries. The identical character positions referenced by data-name-2 in any one record description entry are implicitly referenced as keys for all other record description entries for that file. For files defined with the EXTERNAL clause, all file description entries in the run unit that are associated with the file must have data description entries for data-name-2 that specify the same relative location in the record and the same length.
ALTERNATE RECORD KEY clause

The ALTERNATE RECORD KEY clause (format 2) specifies a data item within the record that provides an alternative path to the data in an indexed file. data-name-3 An ALTERNATE RECORD KEY data item. It must be described within a record description entry associated with the file. It can be any of the following types of data item: v Alphanumeric v Numeric v Numeric-edited v Alphanumeric-edited v Alphabetic v External floating-point v Internal floating-point v DBCS v National Regardless of the category of the key data item, the key is treated as an alphanumeric item. The collation order of the key is determined by the items binary value order when the key is used for locating a record or for setting the file position indicator associated with the file. data-name-3 cannot be a windowed date field. data-name-3 must not reference a group item that contains a variable-occurrence data item. data-name-3 can be qualified. If the indexed file contains variable-length records, data-name-3 need not be contained within the minimum record size specified for the file. That is, data-name-3 can exceed the minimum record size, but this is not recommended.
133
If the file has more than one record description entry, data-name-3 need be described in only one of these record description entries. The identical character positions referenced by data-name-3 in any one record description entry are implicitly referenced as keys for all other record description entries of that file. The data description of data-name-3 and its relative location within the record must be the same as those used when the file was defined. The number of alternate record keys for the file must also be the same as that used when the file was created. The leftmost character position of data-name-3 must not be the same as the leftmost character position of the prime RECORD KEY or of any other ALTERNATE RECORD KEY. If the DUPLICATES phrase is not specified, the values contained in the ALTERNATE RECORD KEY data item must be unique among records in the file. If the DUPLICATES phrase is specified, the values contained in the ALTERNATE RECORD KEY data item can be duplicated within any records in the file. In sequential access, the records with duplicate keys are retrieved in the order in which they were placed in the file. In random access, only the first record written in a series of records with duplicate keys can be retrieved. For files defined with the EXTERNAL clause, all file description entries in the run unit that are associated with the file must have data description entries for data-name-3 that specify the same relative location in the record and the same length. The file description entries must specify the same number of alternate record keys and the same DUPLICATES phrase.
RELATIVE KEY clause

The RELATIVE KEY clause (format 3) identifies a data-name that specifies the relative record number for a specific logical record within a relative file. data-name-4 Must be defined as an unsigned integer data item whose description does not contain the PICTURE symbol P. data-name-4 must not be defined in a record description entry associated with this relative file. That is, the RELATIVE KEY is not part of the record. data-name-4 can be qualified. data-name-4 cannot be a windowed date field. data-name-4 is required for ACCESS IS SEQUENTIAL only when the START statement is to be used. It is always required for ACCESS IS RANDOM and ACCESS IS DYNAMIC. When the START statement is issued, the system uses the contents of the RELATIVE KEY data item to determine the record at which sequential processing is to begin. If a value is placed in data-name-4, and a START statement is not issued, the value is ignored and processing begins with the first record in the file. If a relative file is to be referenced by a START statement, you must specify the RELATIVE KEY clause for that file. For external files, data-name-4 must reference an external data item, and the RELATIVE KEY phrase in each associated file-control entry must reference that same external data item in each case.
134
Language Reference
The ACCESS MODE IS RANDOM clause must not be specified for file-names specified in the USING or GIVING phrase of a SORT or MERGE statement.
PASSWORD clause
The PASSWORD clause controls access to files. data-name-6, data-name-7 Password data items. Each must be defined in the working-storage section of the data division as an alphanumeric item. The first eight characters are used as the password; a shorter field is padded with blanks to eight characters. Each password data item must be equivalent to one that is externally defined. When the PASSWORD clause is specified, at object time the PASSWORD data item must contain the valid password for this file before the file can be successfully opened. Format 1 considerations: The PASSWORD clause is not valid for QSAM sequential files. Format 2 and 3 considerations: When the PASSWORD clause is specified, it must immediately follow the RECORD KEY or ALTERNATE RECORD KEY data-name with which it is associated. For indexed files, if the file has been completely predefined to VSAM, only the PASSWORD data item for the RECORD KEY need contain the valid password before the file can be successfully opened at file creation time. For any other type of file processing (including the processing of dynamic calls at file creation time through a COBOL object-time subroutine), every PASSWORD data item for this file must contain a valid password before the file can be successfully opened, regardless of whether all paths to the data are used in this object program. For external files, data-name-6 and data-name-7 must reference external data items. The PASSWORD clauses in each associated file-control entry must reference the same external data items.
FILE STATUS clause

The FILE STATUS clause monitors the execution of each input-output operation for the file. When the FILE STATUS clause is specified, the system moves a value into the file status key data item after each input-output operation that explicitly or implicitly refers to this file. The value indicates the status of execution of the statement. (See the file status key description under Common processing facilities on page 278.) data-name-1 The file status key data item can be defined in the working-storage, local-storage, or linkage sections as either of the following:
135
v A two-character alphanumeric item v A two-character numeric data item, with explicit or implicit USAGE IS DISPLAY. It is treated as an alphanumeric item. data-name-1 must not contain the PICTURE symbol P. data-name-1 can be qualified. The file status key data item must not be variably located; that is, the data item cannot follow a data item that contains an OCCURS DEPENDING ON clause. data-name-8 Must be defined as a group item of 6 bytes in the working-storage section or linkage section of the data division. Specify data-name-8 only if the file is a VSAM file (that is, ESDS, KSDS, RRDS). data-name-8 holds the 6-byte VSAM return code, which is composed of the following: v The first 2 bytes of data-name-8 contain the VSAM return code in binary format. The value for this code is defined (by VSAM) as 0, 8, or 12. v The next 2 bytes of data-name-8 contain the VSAM function code in binary format. The value for this code is defined (by VSAM) as 0, 1, 2, 3, 4, or 5. v The last 2 bytes of data-name-8 contain the VSAM feedback code in binary format. The code value is 0 through 255. If VSAM returns a nonzero return code, data-name-8 is set. If FILE STATUS is returned without having called VSAM, data-name-8 is zero. If data-name-1 is set to zero, the content of data-name-8 is undefined. VSAM status return code information is available without transformation in the currently defined COBOL FILE STATUS code. User identification and handling of exception conditions are allowed at the same level as that defined by VSAM. Function code and feedback code are set if and only if the return code is set to a nonzero value. If they are referenced when the return code is set to zero, the contents of the fields are not dependable. Values in the return code, function code, and feedback code fields are defined by VSAM. There are no COBOL additions, deletions, or modifications to the VSAM definitions. For more information, see DFSMS Macro Instructions for Data Sets.
I-O-CONTROL paragraph
The I-O-CONTROL paragraph of the input-output section specifies when checkpoints are to be taken and the storage areas to be shared by different files. This paragraph is optional in a COBOL program.
136
Language Reference
The keyword I-O-CONTROL can appear only once, at the beginning of the paragraph. The word I-O-CONTROL must begin in Area A and must be followed by a separator period. The order in which I-O-CONTROL paragraph clauses are written is not significant. The I-O-CONTROL paragraph ends with a separator period.
Format: QSAM I-O-control entries

RERUN ON SAME RECORD AREA FOR file-name-4 (1) MULTIPLE FILE TAPE (1) APPLY WRITE-ONLY ON file-name-2 CONTAINS file-name-5 POSITION integer-2 assignment-name-1 file-name-1 phrase 1 EVERY file-name-3
phrase 1:
integer-1 RECORDS END REEL OF UNIT file-name-1 OF
Notes: 1 The MULTIPLE FILE clause and APPLY WRITE-ONLY clause are not supported for VSAM files.
Format: VSAM I-O-control entries

RERUN ON SAME RECORD AREA FOR file-name-4 assignment-name-1 file-name-1 phrase 1 EVERY file-name-3
phrase 1:
integer-1 RECORDS OF file-name-1
137
Format: Line-sequential I-O-control entries
SAME RECORD AREA FOR
file-name-3
file-name-4
Format: Sort/merge I-O-control entries
RERUN ON
assignment-name-1
SAME
RECORD SORT SORT-MERGE
phrase 1 AREA FOR
phrase 1:
file-name-3
file-name-4
RERUN clause
The RERUN clause specifies that checkpoint records are to be taken. Subject to the restrictions given with each phrase, more than one RERUN clause can be specified. For information regarding the checkpoint data set definition and the checkpoint method required for complete compliance to Standard COBOL 85, see the Enterprise COBOL Programming Guide. Do not use the RERUN clause: v For files described with the EXTERNAL clause v In programs with the RECURSIVE clause specified v In programs compiled with the THREAD option v In methods file-name-1 Must be a sequentially organized file. VSAM and QSAM considerations:
138
Language Reference
The file named in the RERUN clause must be a file defined in the same program as the I-O-CONTROL paragraph, even if the file is defined as GLOBAL. assignment-name-1 The external data set for the checkpoint file. It must not be the same assignment-name as that specified in any ASSIGN clause throughout the entire program, including contained and containing programs. For QSAM files, it has the format:
Format: QSAM file

name labelS-
That is, it must be a QSAM file. It must reside on a tape or direct access device. See also Appendix F, ASCII considerations, on page 573. SORT/MERGE considerations: When the RERUN clause is specified in the I-O-CONTROL paragraph, checkpoint records are written at logical intervals determined by the sort/merge program during execution of each SORT or MERGE statement in the program. When the RERUN clause is omitted, checkpoint records are not written. There can be only one SORT/MERGE I-O-CONTROL paragraph in a program, and it cannot be specified in contained programs. It will have a global effect on all SORT and MERGE statements in the program unit. EVERY integer-1 RECORDS A checkpoint record is to be written for every integer-1 records in file-name-1 that are processed. When multiple integer-1 RECORDS phrases are specified, no two of them can specify the same value for file-name-1. If you specify the integer-1 RECORDS phrase, you must specify assignment-name-1. EVERY END OF REEL/UNIT A checkpoint record is to be written whenever end-of-volume for file-name-1 occurs. The terms REEL and UNIT are interchangeable. When multiple END OF REEL/UNIT phrases are specified, no two of them can specify the same value for file-name-1. The END OF REEL/UNIT phrase can be specified only if file-name-1 is a sequentially organized file.
SAME AREA clause

The SAME AREA clause specifies that two or more files that do not represent sort or merge files are to use the same main storage area during processing.
139
The files named in a SAME AREA clause need not have the same organization or access. file-name-3, file-name-4 Must be specified in the file-control paragraph of the same program. file-name-3 and file-name-4 must not reference a file that is defined with the EXTERNAL clause. v For QSAM files, the SAME clause is treated as documentation. v For VSAM files, the SAME clause is treated as if equivalent to the SAME RECORD AREA. More than one SAME AREA clause can be included in a program. However: v A specific file-name must not appear in more than one SAME AREA clause. v If one or more file-names of a SAME AREA clause appear in a SAME RECORD AREA clause, all the file-names in that SAME AREA clause must appear in that SAME RECORD AREA clause. However, the SAME RECORD AREA clause can contain additional file-names that do not appear in the SAME AREA clause. v The rule that in the SAME AREA clause only one file can be open at one time takes precedence over the SAME RECORD AREA rule that all the files can be open at the same time.
| |
SAME RECORD AREA clause

The SAME RECORD AREA clause specifies that two or more files are to use the same main storage area for processing the current logical record. The files named in a SAME RECORD AREA clause need not have the same organization or access. file-name-3, file-name-4 Must be specified in the file-control paragraph of the same program. file-name-3 and file-name-4 must not reference a file that is defined with the EXTERNAL clause. All of the files can be open at the same time. A logical record in the shared storage area is considered to be both of the following: v A logical record of each opened output file in the SAME RECORD AREA clause v A logical record of the most recently read input file in the SAME RECORD AREA clause More than one SAME RECORD AREA clause can be included in a program. However: v A specific file-name must not appear in more than one SAME RECORD AREA clause. v If one or more file-names of a SAME AREA clause appear in a SAME RECORD AREA clause, all the file-names in that SAME AREA clause must appear in that SAME RECORD AREA clause. However, the SAME RECORD AREA clause can contain additional file-names that do not appear in the SAME AREA clause. v The rule that in the SAME AREA clause only one file can be open at one time takes precedence over the SAME RECORD AREA rule that all the files can be open at the same time. v If the SAME RECORD AREA clause is specified for several files, the record description entries or the file description entries for these files must not include the GLOBAL clause.
| |
140
Language Reference
v The SAME RECORD AREA clause must not be specified when the RECORD CONTAINS 0 CHARACTERS clause is specified. The files named in the SAME RECORD AREA clause need not have the same organization or access.
SAME SORT AREA clause

The SAME SORT AREA clause is syntax checked but has no effect on the execution of the program. file-name-3, file-name-4 Must be specified in the file-control paragraph of the same program. file-name-3 and file-name-4 must not reference a file that is defined with the EXTERNAL clause. 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 can also be specified. The following rules apply: v More than one SAME SORT AREA clause can be specified. However, a given sort file must not be named in more than one such clause. v 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. v Files named in a SAME SORT AREA clause need not have the same organization or access. v Files named in a SAME SORT AREA clause that are not sort files do not share storage with each other unless they are named in a SAME AREA or SAME RECORD AREA clause. v During the execution of a SORT or MERGE statement that refers to a sort or merge file named in this clause, any nonsort or nonmerge files associated with file-names named in this clause must not be in the open mode.
| |
SAME SORT-MERGE AREA clause

The SAME SORT-MERGE AREA clause is equivalent to the SAME SORT AREA clause (see SAME SORT AREA clause).
MULTIPLE FILE TAPE clause

The MULTIPLE FILE TAPE clause (format 1) specifies that two or more files share the same physical reel of tape. This clause is syntax checked, but has no effect on the execution of the program. The function is performed by the system through the LABEL parameter of the DD statement.
141
APPLY WRITE-ONLY clause

The APPLY WRITE-ONLY clause optimizes buffer and device space allocation for files that have standard sequential organization, have variable-length records, and are blocked. If you specify this phrase, the buffer is truncated only when the space available in the buffer is smaller than the size of the next record. Otherwise, the buffer is truncated when the space remaining in the buffer is smaller than the maximum record size for the file. APPLY WRITE-ONLY is effective only for QSAM files. file-name-2 Each file must have standard sequential organization. APPLY WRITE-ONLY clauses must agree among corresponding external file description entries. For an alternate method of achieving the APPLY WRITE-ONLY results, see the description of the AWO compiler option in the Enterprise COBOL Programming Guide.
142
Language Reference
Part 5. Data division

Chapter 17. Data division overview . File section . . . . . . . . . . Working-storage section . . . . . . Local-storage section . . . . . . . Linkage section . . . . . . . . . Data units . . . . . . . . . . File data . . . . . . . . . . Program data . . . . . . . . Method data . . . . . . . . Factory data . . . . . . . . . Instance data . . . . . . . . Data relationships . . . . . . . . Levels of data . . . . . . . . Levels of data in a record description Special level-numbers . . . . . Indentation . . . . . . . . . Classes and categories of data . . . Alignment rules . . . . . . . Character-string and item size . . . Signed data . . . . . . . . . Operational signs . . . . . . . Editing signs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . entry . . . . . . . . . . . . . . . . . . 145 . . 146 . . 147 . . 148 . . 149 . . 149 . . 149 . . 150 . . 150 . . 150 . . 150 . . 150 . . 151 . . 151 . . 153 . . 153 . . 153 . . 154 . . 155 . . 156 . . 156 . . 156 Language elements that treat date fields as nondates . . . . . . . . . . . . Language elements that do not accept windowed date fields as arguments . . . Language elements that do not accept date fields as arguments . . . . . . . . EXTERNAL clause . . . . . . . . . . GLOBAL clause . . . . . . . . . . . JUSTIFIED clause . . . . . . . . . . . OCCURS clause . . . . . . . . . . . Fixed-length tables . . . . . . . . . ASCENDING KEY and DESCENDING KEY phrases . . . . . . . . . . . . . INDEXED BY phrase . . . . . . . . . Variable-length tables . . . . . . . . . OCCURS DEPENDING ON clause . . . . PICTURE clause . . . . . . . . . . . Symbols used in the PICTURE clause . . . P symbol . . . . . . . . . . . . Currency symbol . . . . . . . . . Character-string representation . . . . . Data categories and PICTURE rules . . . . Alphabetic items . . . . . . . . . Numeric items . . . . . . . . . . Examples of valid ranges . . . . . . Numeric-edited items . . . . . . . Alphanumeric items . . . . . . . . Alphanumeric-edited items . . . . . . DBCS items . . . . . . . . . . . National items . . . . . . . . . . External floating-point items . . . . . PICTURE clause editing . . . . . . . . Simple insertion editing . . . . . . . . Special insertion editing . . . . . . . . Fixed insertion editing . . . . . . . . Floating insertion editing . . . . . . . Representing floating insertion editing . . Zero suppression and replacement editing . . Representing zero suppression . . . . REDEFINES clause . . . . . . . . . . REDEFINES clause considerations . . . . REDEFINES clause examples . . . . . . Undefined results . . . . . . . . . . RENAMES clause . . . . . . . . . . . SIGN clause . . . . . . . . . . . . . SYNCHRONIZED clause . . . . . . . . Slack bytes . . . . . . . . . . . . Slack bytes within records . . . . . . . Slack bytes between records . . . . . . USAGE clause . . . . . . . . . . . . Computational items . . . . . . . . . DISPLAY phrase . . . . . . . . . . DISPLAY-1 phrase . . . . . . . . . . FUNCTION-POINTER phrase . . . . . . INDEX phrase . . . . . . . . . . . NATIONAL phrase . . . . . . . . . . 178 . 178 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 179 180 180 181 181 182 183 184 185 187 187 191 192 192 193 193 193 194 194 195 195 195 195 196 197 198 198 199 200 200 201 201 202 204 205 205 205 207 208 211 211 213 214 216 218 218 218 219 219
Chapter 18. Data divisionfile description entries . . . . . . . . . . . . . . . 157 File section . . . . . . . . . . . . . . 160 EXTERNAL clause . . . . . . . . . . . 161 GLOBAL clause . . . . . . . . . . . . 161 BLOCK CONTAINS clause . . . . . . . . . 162 RECORD clause . . . . . . . . . . . . 163 Format 1 . . . . . . . . . . . . . . 164 Format 2 . . . . . . . . . . . . . . 164 Format 3 . . . . . . . . . . . . . . 165 LABEL RECORDS clause . . . . . . . . . 166 VALUE OF clause . . . . . . . . . . . . 166 DATA RECORDS clause . . . . . . . . . . 167 LINAGE clause . . . . . . . . . . . . . 167 LINAGE-COUNTER special register . . . . . 169 RECORDING MODE clause . . . . . . . . 169 CODE-SET clause . . . . . . . . . . . . 170 Chapter 19. Data divisiondata description entry . . . . . . . . . . . . . . . Format 1 . . . . . . . . . . . . . . Format 2 . . . . . . . . . . . . . . Format 3 . . . . . . . . . . . . . . Level-numbers . . . . . . . . . . . . BLANK WHEN ZERO clause . . . . . . . DATE FORMAT clause . . . . . . . . . Semantics of windowed date fields . . . . Date trigger values . . . . . . . . Restrictions on using date fields . . . . . Combining the DATE FORMAT clause with other clauses . . . . . . . . . . Group items that are date fields . . . .
. . . . . . . . . .
171 171 172 172 172 173 174 175 176 176
. 176 . 177
143
OBJECT REFERENCE phrase . . POINTER phrase . . . . . . PROCEDURE-POINTER phrase . NATIVE phrase . . . . . . VALUE clause . . . . . . . . Format 1 . . . . . . . . . Rules for literal values . . . Format 2 . . . . . . . . . Rules for condition-name entries Format 3 . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
220 221 222 223 223 223 224 225 226 228
144
Language Reference

This overview describes the structure of the data division for programs, object definitions, factory definitions, and methods. Each section in the data division has a specific logical function within a COBOL program, object definition, factory definition, or method and can be omitted when that logical function is not needed. If included, the sections must be written in the order shown. The data division is optional. Program data division The data division of a COBOL source program describes, in a structured manner, all the data to be processed by the program. Object data division The object data division contains data description entries for instance object data (instance data). Instance data is defined in the working-storage section of the object paragraph of a class definition. Factory data division The factory data division contains data description entries for factory object data (factory data). Factory data is defined in the working-storage section of the factory paragraph of a class definition. Method data division A method data division contains data description entries for data accessible within the method. A method data division can contain a local-storage section or a working-storage section, or both. The term method data applies to both. Method data in local-storage is dynamically allocated and initialized on each invocation of the method; method data in working-storage is static and persists across invocations of the method.
145
Format: program and method data division

DATA DIVISION.
FILE SECTION.
file-description-entry
record-description-entry
WORKING-STORAGE SECTION. record-description-entry data-item-description-entry
LOCAL-STORAGE SECTION. record-description-entry data-item-description-entry
LINKAGE SECTION. record-description-entry data-item-description-entry
Format: object and factory data division

DATA DIVISION.
WORKING-STORAGE SECTION. record-description-entry data-item-description-entry
File section
The file section defines the structure of data files. The file section must begin with the header FILE SECTION, followed by a separator period. file-description-entry Represents the highest level of organization in the file section. It provides information about the physical structure and identification of a file, and gives the record-names associated with that file. For the format and the
146
Language Reference
clauses required in a file description entry, see Data divisionfile description entries (Chapter 18, Data divisionfile description entries, on page 157). record-description-entry A set of data description entries (described in Data divisiondata description entry (Chapter 19, Data divisiondata description entry, on page 171)) that describe the particular records contained within a particular file. A record in the file section must be described as a group item or as an elementary item of class alphabetic, alphanumeric, DBCS, national, or numeric. More than one record description entry can 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 that contains the data area is open. A method file section can define external files only. A single run-unit-level file connector is shared by all programs and methods that contain a declaration of a given external file.
Working-storage section
The working-storage section describes data records that are not part of data files but are developed and processed by a program or method. It also describes data items whose values are assigned in the source program or method and do not change during execution of the object program. The working-storage section must begin with the section header WORKING-STORAGE SECTION, followed by a separator period. Program working-storage The working-storage section for programs (and methods) can also describe external data records, which are shared by programs and methods throughout the run unit. All clauses that are used in record descriptions in the file section and also the VALUE and EXTERNAL clauses (which might not be specified in record description entries in the file section) can be used in record descriptions in the working-storage section. Method working-storage A single copy of the working-storage for a method is statically allocated on the first invocation of the method and persists in a last-used state for the duration of the run unit. The same copy is used whenever the method is invoked regardless of which object instance the method is invoked upon. If a VALUE clause is specified on a method working-storage data item, the data item is initialized to the VALUE clause value on the first invocation. If the EXTERNAL clause is specified on a data description entry in a method working-storage section, a single copy of the storage for that data item is allocated once for the duration of the run unit. That storage is shared by all programs and methods in the run unit that contain a definition for the external data item. Object working-storage The data described in the working-storage section of an object paragraph is
147
object instance data, usually called instance data. A separate copy of instance data is statically allocated for each object instance when the object is instantiated. Instance data persists in a last-used state until the object instance is freed by the Java run-time system. Instance data can be initialized by VALUE clauses specified in data declarations or by logic specified in an instance method. Factory working-storage The data described in the working-storage section of a factory paragraph is factory data. A single copy of factory data is statically allocated when the factory object for the class is created. Factory data persists in a last-used state for the duration of the run unit. Factory data can be initialized by VALUE clauses specified in data declarations or by logic specified in a factory method. The working-storage section contains record description entries and data description entries for independent data items, called data item description entries. 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. See Data divisiondata description entry (Chapter 19, Data divisiondata description entry, on page 171) for more information. 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. See Data divisiondata description entry (Chapter 19, Data divisiondata description entry, on page 171) for more information.
Local-storage section
The local-storage section defines storage that is allocated and freed on a per-invocation basis. On each invocation, data items defined in the local-storage section are reallocated. Each data item that has a VALUE clause is initialized to the value specified in that clause. For nested programs, data items defined in the local-storage section are allocated upon each invocation of the containing outermost program. However, each data item is reinitialized to the value specified in its VALUE clause each time the nested program is invoked. For methods, a separate copy of the data defined in local-storage is allocated and initialized on each invocation of the method. The storage allocated for the data is freed when the method returns. Data items defined in the local-storage section cannot specify the EXTERNAL clause. The local-storage section must begin with the header LOCAL-STORAGE SECTION, followed by a separator period.
148
Language Reference
You can specify the local-storage section in recursive programs, in nonrecursive programs, and in methods. Method local-storage content is the same as program local-storage content except that the GLOBAL clause has no effect (because methods cannot be nested).
Linkage section
The linkage section describes data made available from another program or method. record-description-entry See Working-storage section on page 147 for a description. data-item-description-entry See Working-storage section on page 147 for a description. Record description entries and data item description entries in the linkage section provide names and descriptions, but storage within the program or method is not reserved because the data area exists elsewhere. Any data description clause can be used to describe items in the linkage section with the following exceptions: v You cannot specify the VALUE clause for items other than level-88 items. v You cannot specify the EXTERNAL clause. You can specify the GLOBAL clause in the linkage section. The GLOBAL clause has no effect for methods, however.
Data units
Data is grouped into the following conceptual units: v File data v Program data v Method data v Factory data v Instance data
File data
File data is contained in files. (See File section on page 160.) A file is a collection of data records that exist on some input-output device. A file can be considered as a group of physical records; it can also be considered as a group of logical records. The data division describes the relationship between physical and logical records. A physical record is a unit of data that is treated as an entity when moved into or out of storage. The size of a physical record is determined by the particular input-output device on which it is stored. The size does not necessarily have a direct relationship to the size or content of the logical information contained in the file. A logical record is a unit of data whose subdivisions have a logical relationship. A logical record can itself be a physical record (that is, be contained completely within one physical unit of data); several logical records can be contained within one physical record, or one logical record can extend across several physical records.
149
File description entries specify the physical aspects of the data (such as the size relationship between physical and logical records, the size and names of the logical records, labeling information, and so forth). Record description entries describe the logical records in the file (including the category and format of data within each field of the logical record), different values the data might be assigned, and so forth. After the relationship between physical and logical records has been established, only logical records are made available to you. For this reason, a reference in this information to records means logical records, unless the term physical records is used.
Program data
Program data is created by a program instead of being read from a file. The concept of logical records applies to program data as well as to file data. Program data can thus be grouped into logical records, and be defined by a series of record description entries. Items that need not be so grouped can be defined in independent data description entries (called data item description entries).
Method data
Method data is defined in the data division of a method and is processed by the procedural code in that method. Method data is organized into logical records and independent data description entries in the same manner as program data.
Factory data
Factory data is defined in the data division in the factory paragraph of a class definition and is processed by procedural code in the factory methods of that class. Factory data is organized into logical records and independent data description entries in the same manner as program data. There is one factory object for a given class in a run unit, and therefore only one instance of factory data in a run unit for that class.
Instance data
Instance data is defined in the data division in the object paragraph of a class definition and is processed by procedural code in the instance methods of that class. Instance data is organized into logical records and independent data description entries in the same manner as program data. There is one copy of instance data in each object instance of a given class. There can be many object instances for a given class. Each has its own separate copy of instance data.
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.
150
Language Reference
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. Level-numbers can be used to describe a data hierarchy; they can indicate that this data has a special purpose. Although they can be associated with (and subordinate to) level indicators, they can also be used independently to describe internal data or data common to two or more programs. (See Level-numbers on page 172 for level-number rules.)
Levels of data
After a record has been defined, it can be subdivided to provide more detailed data references. For example, in a customer file for a department store, one complete record could contain all data that pertains to one customer. Subdivisions within that record could be, for example, customer name, customer address, account number, department number of sale, unit amount of sale, dollar amount of sale, previous balance, and other pertinent information. The basic subdivisions of a record (that is, those fields not further subdivided) are called elementary items. Thus a record can be made up of a series of elementary items or can itself be an elementary item. It might be necessary to refer to a set of elementary items; thus, elementary items can be combined into group items. Groups can also be combined into a more inclusive group that contains one or more subgroups. Thus within one hierarchy of data items, an elementary item can belong to more than one group item. A system of level-numbers specifies the organization of elementary and group items into records. Special level-numbers are also used to identify data items used for special purposes.
Levels of data in a record description entry

Each group and elementary item in a record requires a separate entry, and each must be assigned a level-number. A level-number is a one-digit or two-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 This level-number specifies the record itself, and is the most inclusive level-number possible. A level-01 entry can be either a group item or an elementary item. It must begin in Area A. These level-numbers specify group and elementary items within a record. They can begin in Area A or Area B. Less inclusive data items are assigned higher (not necessarily consecutive) level-numbers in this series.
02-49
The relationship between level-numbers within a group item defines the hierarchy of data within that group. A group item includes all group and elementary items that follow it until a level-number less than or equal to the level-number of that group is encountered.
151
The following figure illustrates a group wherein all groups immediately subordinate to the level-01 entry have the same level-number.
You can also define groups with subordinate items that have different level-numbers for the same level in the hierarchy. For example, 05 EMPLOYEE-NAME and 04 EMPLOYEE-ADDRESS in the following record description entry define the same level in the hierarchy:
01 EMPLOYEE-RECORD. 05 EMPLOYEE-NAME. 10 FIRST-NAME PICTURE X(10). 10 LAST-NAME PICTURE X(10). 04 EMPLOYEE-ADDRESS. 08 STREET PICTURE X(10). 08 CITY PICTURE X(10).
The following record description entry defines the same data hierarchy as the preceding record description entry:
01 EMPLOYEE-RECORD. 05 EMPLOYEE-NAME. 10 FIRST-NAME PICTURE X(10). 10 LAST-NAME PICTURE X(10). 05 EMPLOYEE-ADDRESS. 10 STREET PICTURE X(10). 10 CITY PICTURE X(10).
152
Language Reference
Elementary items can be specified at any level within the hierarchy.
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; such items regroup previously defined data items. (For details, see RENAMES clause on page 205.) Identifies data item description entries that are independent working-storage, local-storage, or linkage section items; they are not subdivisions of other items and are not subdivided themselves. Level-77 items must begin in Area A. Identifies any condition-name entry that is associated with a particular value of a conditional variable. (For details, see VALUE clause on page 223.)
77
88
Level-77 and level-01 entries in the working-storage, local-storage, and linkage sections that are referenced in a program or method must be given unique data-names because level-77 and level-01 entries cannot be qualified. Subordinate data-names that are referenced in the program or method must be either uniquely defined, or made unique through qualification. Unreferenced data-names need not be uniquely defined.
Indentation
Successive data description entries can begin in the same column as preceding entries, or can be indented. Indentation is useful for documentation but does not affect the action of the compiler.
Classes and categories of data

Most data and all literals used in a COBOL program are divided into classes and categories. The following elementary data items do not have a class and category: v Index data items v Items described with USAGE POINTER, USAGE FUNCTION-POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE A function references an elementary data item and belongs to the data class and category associated with the type of the function, as shown in Classes and categories of functions (Table 7 on page 154). All other elementary data items have a class and category as shown in Classes and categories of data (Table 8 on page 154). Literals have a class and category as shown in Classes and categories of literals (Table 9 on page 154). All group items have class and category alphanumeric, even if the subordinate elementary items belong to another class and category.
153
Table 7. Classes and categories of functions Function type Alphanumeric National Integer Numeric Table 8. Classes and categories of data Level of item Elementary Class Alphabetic Numeric Category Alphabetic Numeric Internal floating-point External floating-point Alphanumeric Numeric-edited Alphanumeric-edited Alphanumeric DBCS National Group Alphanumeric National Alphanumeric (although the elementary items in the group can have any category) Class and category Alphanumeric National Numeric Numeric
Table 9. Classes and categories of literals Literal Alphanumeric (including hexadecimal formats) DBCS National (including hexadecimal formats) Numeric (fixed-point and floating-point) Class and category Alphanumeric DBCS National Numeric
Alignment rules
The standard alignment rules for positioning data in an elementary item depend on the category of a receiving item (that is, an item into which the data is moved; see Elementary moves on page 360). Numeric For such receiving items, the following rules apply: 1. The data is aligned on the assumed decimal point and, if necessary, truncated or padded with zeros. (An assumed decimal point is one that has logical meaning but that does not exist as an actual character in the data.) 2. If an assumed decimal point is not explicitly specified, the receiving item is treated as though an assumed decimal point is specified immediately to the right of the field. The data is then treated according to the preceding rule.
154
Language Reference
Numeric-edited The data is aligned on the decimal point, and (if necessary) truncated or padded with zeros at either end except when editing causes replacement of leading zeros. Internal floating-point A decimal point is assumed immediately to the left of the field. The data is then aligned on the leftmost digit position that follows the decimal point, with the exponent adjusted accordingly. External floating-point The data is aligned on the leftmost digit position; the exponent is adjusted accordingly. Alphanumeric, alphanumeric-edited, alphabetic, DBCS For these receiving items, the following rules apply: 1. The data is aligned at the leftmost character position, and (if necessary) truncated or padded with spaces at the right. 2. If the JUSTIFIED clause is specified for this receiving item, the above rule is modified as described in JUSTIFIED clause on page 180. National For these receiving items, the following rules apply: 1. The data is aligned at the leftmost character position, and (if necessary) truncated or padded with default Unicode spaces (NX0020) at the right. Truncation occurs at the boundary of a national character. 2. If the JUSTIFIED clause is specified for this receiving item, the above rule is modified as described in JUSTIFIED clause on page 180.
Character-string and item size

For items described with a PICTURE clause, the size of an elementary item is expressed in source code by the number of character positions described in the PICTURE character-string. In storage, however, the size is determined by the actual number of bytes the item occupies as determined by the combination of its PICTURE character-string and its USAGE clause. For USAGE DISPLAY items, 1 byte of storage is reserved for each character position described by the items PICTURE character-string. For DBCS items and national items, 2 bytes of storage are reserved for each character position described by the items PICTURE character-string. For internal floating-point items, the size of the item in storage is determined by its USAGE clause. USAGE COMPUTATIONAL-1 reserves 4 bytes of storage for the item; USAGE COMPUTATIONAL-2 reserves 8 bytes of storage. Normally, when an arithmetic item is moved from a longer field into a shorter one, the compiler truncates the data to the number of characters represented in the shorter items PICTURE character-string. For example, if a sending field with PICTURE S99999 that contains the value +12345 is moved to a BINARY receiving field with PICTURE S99, the data is truncated to +45. For additional information, see USAGE clause on page 214. The TRUNC compiler option can affect the value of a binary numeric item. For information about TRUNC, see the Enterprise COBOL Programming Guide.
155
Signed data
There are two categories of algebraic signs used in COBOL: operational signs and editing signs.
Operational signs
Operational signs are associated with signed numeric items, and indicate their algebraic properties. The internal representation of an algebraic sign depends on the items USAGE clause, its SIGN clause (if present), and the operating environment. (For further details about the internal representation, see the Enterprise COBOL Programming Guide.) Zero is considered a unique value regardless of the operational sign. An unsigned field is always assumed to be either positive or zero.
Editing signs
Editing signs are associated with numeric-edited items. Editing signs are PICTURE symbols that identify the sign of the item in edited output.
156
Language Reference
Chapter 18. Data divisionfile description entries

In a COBOL program, the File Description (FD) Entry (or Sort File Description (SD) Entry for sort/merge files) represents the highest level of organization in the file section. The order in which the optional clauses follow the FD or SD entry is not important.
Format 1: sequential files

FD file-name-1 EXTERNAL IS IS GLOBAL BLOCK CONTAINS integer-1 TO integer-2 CHARACTERS RECORDS
RECORD CONTAINS CONTAINS clause 1
integer-3 CHARACTERS integer-4 TO integer-5 CHARACTERS DEPENDING ON data-name-1
LABEL
RECORD IS RECORDS ARE
STANDARD OMITTED
data-name-2
VALUE OF
system-name-1 IS
data-name-3 literal-1
DATA
data-name-4
LINAGE IS
data-name-5 integer-8
clause 2 LINES .
RECORDING MODE IS
mode
CODE-SET IS
alphabet-name
clause 1:
VARYING IS IN SIZE FROM integer-6 TO integer-7 CHARACTERS
clause 2:
FOOTING WITH AT
TOP LINES AT
BOTTOM LINES AT
157
Format 2: relative and indexed files

FD file-name-1 EXTERNAL IS IS GLOBAL
BLOCK CONTAINS integer-1 TO
integer-2
CHARACTERS RECORDS
RECORD CONTAINS CONTAINS clause 1
integer-3 CHARACTERS integer-4 TO integer-5 CHARACTERS DEPENDING ON data-name-1
LABEL
STANDARD OMITTED
VALUE OF
system-name-1 IS
data-name-3 literal-1 .
DATA
data-name-4
clause 1:
VARYING IS IN SIZE FROM integer-6 TO integer-7
CHARACTERS
158
Language Reference
Format 3: line-sequential files

FD file-name-1 EXTERNAL IS IS . RECORD CONTAINS clause 1 DEPENDING ON integer-3 CHARACTERS data-name-1 GLOBAL
clause 1:
VARYING IS IN SIZE FROM integer-6 TO integer-7
CHARACTERS
159
Format 4: sort/merge files

SD file-name-1 RECORD CONTAINS CONTAINS clause 1 DEPENDING ON integer-3 CHARACTERS integer-4 TO integer-5 CHARACTERS data-name-1
BLOCK CONTAINS DATA RECORD IS RECORDS ARE data-name-4 integer-1 TO
integer-2
CHARACTERS RECORDS
LABEL
STANDARD OMITTED VALUE OF data-name-2 . system-name-1 IS data-name-3 literal-1
LINAGE IS
clause 2 LINES
CODE-SET IS
alphabet-name
clause 1:
VARYING IS IN SIZE FROM integer-6 TO integer-7 CHARACTERS
clause 2:
FOOTING WITH AT
TOP LINES AT
BOTTOM LINES AT
File section
The file section must contain a level-indicator for each input and output file: v For all files except sort/merge files, the file section must contain an FD entry. v For each sort or merge file, the file section must contain an SD entry. file-name Must follow the level indicator (FD or SD), and must be the same as that specified in the associated SELECT clause. file-name must adhere to the rules of formation for a user-defined word; at least one character must be alphabetic. file-name must be unique within this program.
160
Language Reference
One or more record description entries must follow 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, and they can appear in any order. FD (formats 1, 2, and 3) The last clause in the FD entry must be immediately followed by a separator period. SD (format 4) An SD entry must be written for each sort or merge file in the program. The last clause in the SD entry must be immediately followed by a separator period. The following example illustrates the file section entries needed for a sort or merge file:
SD 01 SORT-FILE. SORT-RECORD PICTURE X(80).
A record in the file section must be described as a group item or as an elementary item of class alphabetic, alphanumeric, DBCS, national, or numeric.
EXTERNAL clause
The EXTERNAL clause specifies that a file connector is external, and permits communication between two programs by the sharing of files. A file connector is external if the storage associated with that file is associated with the run unit rather than with any particular program within the run unit. An external file can be referenced by any program in the run unit that describes the file. References to an external file from different programs that use separate descriptions of the file are always to the same file. In a run unit, there is only one representative of an external file. In the file section, the EXTERNAL clause can be specified only in file description entries. The records appearing in the file description entry need not have the same name in corresponding external file description entries. In addition, the number of such records need not be the same in corresponding file description entries. Use of the EXTERNAL clause does not imply that the associated file-name is a global name. See the Enterprise COBOL Programming Guide for specific information about the use of the EXTERNAL clause.
GLOBAL clause
The GLOBAL clause specifies that the file connector named by a file-name is a global name. A global file-name is available to the program that declares it and to every program that is contained directly or indirectly in that program. A file-name is global if the GLOBAL clause is specified in the file description entry for that file-name. A record-name is global if the GLOBAL clause is specified in the record description entry by which the record-name is declared or, in the case of record description entries in the file section, if the GLOBAL clause is specified in
161
the file description entry for the file-name associated with the record description entry. For details on using the GLOBAL clause, see the Enterprise COBOL Programming Guide. Two programs in a run unit can reference global file connectors in the following circumstances: v An external file connector can be referenced from any program that describes that file connector. v If a program is contained within another program, both programs can refer to a global file connector by referring to an associated global file-name either in the containing program or in any program that directly or indirectly contains the containing program.
BLOCK CONTAINS clause

The BLOCK CONTAINS clause specifies the size of the physical records. The CHARACTERS phrase indicates that the integer specified in the BLOCK CONTAINS clause reflects the number of bytes in the record. For example, if you have a block with 10 DBCS characters or 10 national characters, the BLOCK CONTAINS clause should say BLOCK CONTAINS 20 CHARACTERS. If the records in the file are not blocked, the BLOCK CONTAINS clause can be omitted. When it is omitted, the compiler assumes that records are not blocked. Even if each physical record contains only one complete logical record, coding BLOCK CONTAINS 1 RECORD would result in fixed blocked records. The BLOCK CONTAINS clause can be omitted when the associated file-control entry specifies a VSAM file. The concept of blocking has no meaning for VSAM files. The BLOCK CONTAINS clause is syntax checked but has no effect on the execution of the program. For external files, the value of all BLOCK CONTAINS clauses of corresponding external files must match within the run unit. This conformance is in terms of bytes and does not depend upon whether the value was specified as CHARACTERS or as RECORDS. integer-1, integer-2 Must be nonzero unsigned integers. They specify: CHARACTERS Specifies the number of bytes required to store the physical record, no matter what USAGE the data items have within the data record. If only integer-2 is specified, it specifies the exact number of bytes in the physical record. When integer-1 and integer-2 are both specified, they represent the minimum and maximum number of bytes in the physical record, respectively. integer-1 and integer-2 must include any control bytes and padding contained in the physical record. (Logical records do not include padding.) The CHARACTERS phrase is the default. CHARACTERS must be specified when: v The physical record contains padding.
162
Language Reference
v Logical records are grouped so that an inaccurate physical record size could be implied. For example, suppose you describe a variable-length record of 100 bytes, yet each time you write a block of 4, one 50-byte record is written followed by three 100-byte records. If the RECORDS phrase were specified, the compiler would calculate the block size as 420 bytes instead of the actual size, 370 bytes. (This calculation includes block and record descriptors.) RECORDS Specifies the number of logical records contained in each physical record. The compiler assumes that the block size must provide for integer-2 records of maximum size, and provides any additional space needed for control bytes.
BLOCK CONTAINS 0 can be specified for QSAM files. If BLOCK CONTAINS 0 is specified for a QSAM file, then: v The block size is determined at run time from the DD parameters or the data set label. If the RECORD CONTAINS 0 CHARACTERS clause is specified and the BLOCK CONTAINS 0 CHARACTERS clause is specified (or omitted), the block size is determined at run time from the DD parameters or the data set label of the file. For output data sets, with either of the above conditions, the DCB used by Language Environment will have a zero block size value. If you do not specify a block size value, the operating system might select a system-determined block size (SDB). See the operating system specifications for further information about SDB. BLOCK CONTAINS can be omitted for SYSIN files and for SYSOUT files. The blocking is determined by the operating system. The BLOCK CONTAINS clause is syntax checked but has no effect on the execution of the program when specified under an SD. The BLOCK CONTAINS clause cannot be used with the RECORDING MODE U clause.
RECORD clause
When the RECORD clause is used, the record size must be specified as the number of bytes needed to store the record internally, regardless of the USAGE of the data items contained within the record. For example, if you have a record with 10 DBCS characters, the RECORD clause should say RECORD CONTAINS 20 CHARACTERS. For a record with 10 national characters, the RECORD clause should say the same, RECORD CONTAINS 20 CHARACTERS. The size of a record is determined according to the rules for obtaining the size of a group item. (See USAGE clause on page 214 and SYNCHRONIZED clause on page 208.) When the RECORD clause is omitted, the compiler determines the record lengths from the record descriptions. When one of the entries within a record description
163
contains an OCCURS DEPENDING ON clause, the compiler uses the maximum value of the variable-length item to calculate the number of bytes needed to store the record internally. If the associated file connector is an external file connector, all file description entries in the run unit that are associated with that file connector must specify the same maximum number of bytes. The following sections describe the formats of the RECORD clause: v Format 1, fixed-length records v Format 2, fixed-length or variable-length records v Format 3 on page 165, variable-length records
Format 1
Format 1 specifies the number of bytes for fixed-length records.
Format 1
RECORD CONTAINS integer-3 CHARACTERS
integer-3 Must be an unsigned integer that specifies the number of bytes contained in each record in the file. The RECORD CONTAINS 0 CHARACTERS clause can be specified for input QSAM files containing fixed-length records; the record size is determined at run time from the DD statement parameters or the data set label. If, at run time, the actual record is larger than the 01 record description, then only the 01 record length is available. If the actual record is shorter, then only the actual record length can be referred to. Otherwise, uninitialized data or an addressing exception can be produced. Usage note: If the RECORD CONTAINS 0 clause is specified, then the SAME AREA, SAME RECORD AREA, or APPLY WRITE-ONLY clauses cannot be specified. Do not specify the RECORD CONTAINS 0 clause for an SD entry.
Format 2
Format 2 specifies the number of bytes for either fixed-length or variable-length records. Fixed-length records are obtained when all 01 record description entry lengths are the same. The format-2 RECORD CONTAINS clause is never required, because the minimum and maximum record lengths are determined from the record description entries.
Format 2
RECORD CONTAINS integer-4 TO integer-5 CHARACTERS
164
Language Reference
integer-4, integer-5 Must be unsigned integers. integer-4 specifies the size of the smallest data record, and integer-5 specifies the size of the largest data record.
Format 3
Format 3 is used to specify variable-length records.
Format 3
RECORD IS VARYING IN SIZE FROM integer-6
TO integer-7
CHARACTERS
DEPENDING ON
data-name-1
integer-6 Specifies the minimum number of bytes to be contained in any record of the file. If integer-6 is not specified, the minimum number of bytes to be contained in any record of the file is equal to the least number of bytes described for a record in that file. integer-7 Specifies the maximum number of bytes in any record of the file. If integer-7 is not specified, the maximum number of bytes to be contained in any record of the file is equal to the greatest number of bytes described for a record in that file. The number of bytes associated with a record description is determined by the sum of the number of bytes in all elementary data items (excluding redefinitions and renamings), plus any implicit FILLER due to synchronization. If a table is specified: v The minimum number of table elements described in the record is used in the summation above to determine the minimum number of bytes associated with the record description. v The maximum number of table elements described in the record is used in the summation above to determine the maximum number of bytes associated with the record description. If v v v data-name-1 is specified: data-name-1 must be an elementary unsigned integer. data-name-1 cannot be a windowed date field. The number of bytes in the record must be placed into the data item referenced by data-name-1 before any RELEASE, REWRITE, or WRITE statement is executed for the file. v The execution of a DELETE, RELEASE, REWRITE, START, or WRITE statement or the unsuccessful execution of a READ or RETURN statement does not alter the content of the data item referenced by data-name-1. v After the successful execution of a READ or RETURN statement for the file, the contents of the data item referenced by data-name-1 indicate the number of bytes in the record just read.
165
During the execution of a RELEASE, REWRITE, or WRITE statement, the number of bytes in the record is determined by the following conditions: v If data-name-1 is specified, by the content of the data item referenced by data-name-1 v If data-name-1 is not specified and the record does not contain a variable occurrence data item, by the number of bytes positions in the record v If data-name-1 is not specified and the record contains a variable occurrence data item, by the sum of the fixed position and that portion of the table described by the number of occurrences at the time of execution of the output statement During the execution of a READ ... INTO or RETURN ... INTO statement, the number of bytes in the current record that participate as the sending data items in the implicit MOVE statement is determined by the following conditions: v If data-name-1 is specified, by the content of the data item referenced by data-name-1 v If data-name-1 is not specified, by the value that would have been moved into the data item referenced by data-name-1 had data-name-1 been specified
LABEL RECORDS clause

The LABEL RECORDS clause indicates 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. For VSAM files, the LABEL RECORDS clause is syntax checked, but has no effect on the execution of the program. COBOL label processing, therefore, is not performed. STANDARD Labels conforming to system specifications exist for this file. STANDARD is permitted for mass storage devices and tape devices. OMITTED No labels exist for this file. OMITTED is permitted for tape devices. data-name-2 User labels are present in addition to standard labels. data-name-2 specifies the name of a user label record. data-name-2 must appear as the subject of a record description entry associated with the file. The LABEL RECORDS clause is treated as a comment under an SD.
VALUE OF clause
The VALUE OF clause describes an item in the label records associated with the file. data-name-3 Should be qualified when necessary, but cannot be subscripted. It must be described in the working-storage section. It cannot be described with the USAGE IS INDEX clause.
166
Language Reference
literal-1 Can be numeric or alphanumeric, or a figurative constant of category numeric or alphanumeric. Cannot be a floating-point literal. The VALUE OF clause is syntax checked, but has no effect on the execution of the program.
DATA RECORDS clause

The DATA RECORDS clause is syntax checked but serves only as documentation for the names of data records associated with the file. data-name-4 The names of record description entries associated with the file. The data-name need not have an associated 01 level number record description with the same name.
LINAGE clause
The LINAGE clause specifies the depth of a logical page in number of lines. Optionally, it also specifies the line number at which the footing area begins and the top and bottom margins of the logical page. (The logical page and the physical page cannot be the same size.) The LINAGE clause is effective for sequential files opened as OUTPUT or EXTEND. All integers must be unsigned. All data-names must be described as unsigned integer data items. data-name-5, integer-8 The number of lines that can be written or spaced on this logical page. The area of the page that these lines represent is called the page body. The value must be greater than zero. WITH FOOTING AT integer-9 or the value of the data item in data-name-6 specifies the first line number of the footing area within the page body. The footing line number must be greater than zero, and not greater than the last line of the page body. The footing area extends between those two lines. LINES AT TOP integer-10 or the value of the data item in data-name-7 specifies the number of lines in the top margin of the logical page. The value can be zero. LINES AT BOTTOM integer-11 or the value of the data item in data-name-8 specifies the number of lines in the bottom margin of the logical page. The value can be zero.
167
The following figure illustrates the use of each phrase of the LINAGE clause.
The logical page size specified in the LINAGE clause is the sum of all values specified in each phrase except the FOOTING phrase. If the LINES AT TOP phrase is omitted, the assumed value for the top margin is zero. Similarly, if the LINES AT BOTTOM phrase is omitted, the assumed value for the bottom margin is zero. Each logical page immediately follows the preceding logical page, with no additional spacing provided. If the FOOTING phrase is omitted, its assumed value is equal to that of the page body (integer-8 or data-name-5). At the time an OPEN OUTPUT statement is executed, the values of integer-8, integer-9, integer-10, and integer-11, if specified, are used to determine the page body, first footing line, top margin, and bottom margin of the logical page for this file. (See the figure above.) These values are then used for all logical pages printed for this file during a given execution of the program. At the time an OPEN statement with the OUTPUT phrase is executed for the file, data-name-5, data-name-6, data-name-7, and data-name-8 determine the page body, first footing line, top margin, and bottom margin for the first logical page only. At the time a WRITE statement with the ADVANCING PAGE phrase is executed or a page overflow condition occurs, the values of data-name-5, data-name-6, data-name-7, and data-name-8 if specified, are used to determine the page body, first footing line, top margin, and bottom margin for the next logical page. If an external file connector is associated with this file description entry, all file description entries in the run unit that are associated with this file connector must have: v A LINAGE clause, if any file description entry has a LINAGE clause v The same corresponding values for integer-8, integer-9, integer-10, and integer-11, if specified v The same corresponding external data items referenced by data-name-5, data-name-6, data-name-7, and data-name-8
168
Language Reference
See ADVANCING phrase on page 438 for the behavior of carriage control characters in external files. The LINAGE clause is treated as a comment under an SD.
LINAGE-COUNTER special register

For information about the LINAGE-COUNTER special register, see LINAGE-COUNTER on page 17.
RECORDING MODE clause

The RECORDING MODE clause specifies the format of the physical records in a QSAM file. The clause is ignored for a VSAM file. Permitted values for RECORDING MODE are: Recording mode F (fixed) All the records in a file are the same length and each is wholly contained within one block. Blocks can contain more than one record, and there is usually a fixed number of records for each block. In this mode, there are no record-length or block-descriptor fields. Recording mode V (variable) The records can be either fixed-length or variable-length, and each must be wholly contained within one block. Blocks can contain more than one record. Each data record includes a record-length field and each block includes a block-descriptor field. These fields are not described in the data division. They are each 4 bytes long and provision is automatically made for them. These fields are not available to you. Recording mode U (fixed or variable) The records can be either fixed-length or variable-length. However, there is only one record for each block. There are no record-length or block-descriptor fields. You cannot use RECORDING MODE U if you are using the BLOCK CONTAINS clause. Recording mode S (spanned) The records can be either fixed-length or variable-length, and can be larger than a block. If a record is larger than the remaining space in a block, a segment of the record is written to fill the block. The remainder of the record is stored in the next block (or blocks, if required). Only complete records are made available to you. Each segment of a record in a block, even if it is the entire record, includes a segment-descriptor field, and each block includes a block-descriptor field. These fields are not described in the data division; provision is automatically made for them. These fields are not available to you. When recording mode S is used, the BLOCK CONTAINS CHARACTERS clause must be used. Recording mode S is not allowed for ASCII files. If the RECORDING MODE clause is not specified for a QSAM file, the Enterprise COBOL compiler determines the recording mode as follows: F The compiler determines the recording mode to be F if the largest level-01 record associated with the file is not greater than the block size specified in the BLOCK CONTAINS clause, and you do one of the following:
169
v Use the RECORD CONTAINS integer clause. (For more information, see the Enterprise COBOL Compiler and Run-Time Migration Guide.) v Omit the RECORD clause and make sure that all level-01 records associated with the file are the same size and none contains an OCCURS DEPENDING ON clause. V The compiler determines the recording mode to be V if the largest level-01 record associated with the file is not greater than the block size specified in the BLOCK CONTAINS clause, and you do one of the following: v Use the RECORD IS VARYING clause. v Omit the RECORD clause and make sure that all level-01 records associated with the file are not the same size or some contain an OCCURS DEPENDING ON clause. v Use the RECORD CONTAINS integer-1 TO integer-2 clause, with integer-1 the minimum length and integer-2 the maximum length of the level-01 records associated with the file. The two integers must be different, with values matching minimum and maximum length of either different length records or records with an OCCURS DEPENDING ON clause. The compiler determines the recording mode to be S if the maximum block size is smaller than the largest record size. Recording mode U is never obtained by default. The RECORDING MODE U clause must be explicitly specified to get recording mode U.
S U
CODE-SET clause
The CODE-SET clause specifies the character code used to represent data on a magnetic tape file. When the CODE-SET clause is specified, an alphabet-name identifies the character code convention used to represent data on the input-output device. alphabet-name must be defined in the SPECIAL-NAMES paragraph as STANDARD-1 (for ASCII-encoded files), STANDARD-2 (for ISO 7-bit encoded files), EBCDIC (for EBCDIC-encoded files), or NATIVE. When NATIVE is specified, the CODE-SET clause is syntax checked but has no effect on the execution of the program. The CODE-SET clause also specifies the algorithm for converting the character codes on the input-output medium from and to the internal EBCDIC character set. When the CODE-SET clause is specified for a file, all data in the file must have USAGE DISPLAY; and if signed numeric data is present, it must be described with the SIGN IS SEPARATE clause. When the CODE-SET clause is omitted, the EBCDIC character set is assumed for the file. If the associated file connector is an external file connector, all CODE-SET clauses in the run unit that are associated with the file connector must have the same character set. The CODE-SET clause is valid only for magnetic tape files. The CODE-SET clause is syntax checked but has no effect on the execution of the program when specified under an SD.
170
Language Reference
Chapter 19. Data divisiondata description entry

A data description entry specifies the characteristics of a data item. In the sections that follow, sets of data description entries are called record description entries. The term data description entry refers to data and record description entries. Data description entries that define independent data items do not make up a record. These entries are known as data item description entries. Data description entries have three general formats, which are described in the following sections: v Format 1 v Format 2 on page 172 v Format 3 on page 172 All data description entries must end with a separator period.
Format 1
Format 1 is used for data description entries in all data division sections.
Format 1
level-number data-name-1 FILLER redefines-clause
blank-when-zero-clause
external-clause
global-clause
justified-clause
occurs-clause
picture-clause
sign-clause
synchronized-clause
usage-clause
value-clause
date-format-clause
The clauses can be written in any order, with two exceptions: v data-name-1 or FILLER, if specified, must immediately follow the level-number. v When the REDEFINES clause is specified, it must immediately follow data-name-1 or FILLER, if either is specified. If data-name-1 or FILLER is not specified, the REDEFINES clause must immediately follow the level-number. The level-number in format 1 can be any number in the range 01-49, or 77. A space, a comma, or a semicolon must separate clauses.
171
Format 2
Format 2 regroups previously defined items.
Format 2
66 data-name-1 renames-clause.
A level-66 entry cannot rename another level-66 entry, nor can it rename a level-01, level-77, or level-88 entry. All level-66 entries associated with one record must immediately follow the last data description entry in that record. See RENAMES clause on page 205 for further details.
Format 3
Format 3 describes condition-names.
Format 3
88 condition-name-1 value-clause.
condition-name-1 A user-specified name that associates a value, a set of values, or a range of values with a conditional variable. Level-88 entries must immediately follow the data description entry for the conditional variable with which the condition-names are associated. Format 3 can be used to describe both elementary and group items. Additional information about condition-name entries can be found under VALUE clause on page 223 and Condition-name condition on page 249.
Level-numbers
The level-number specifies the hierarchy of data within a record, and identifies special-purpose data entries. A level-number begins a data description entry, a renamed or redefined item, or a condition-name entry. A level-number has an integer value between 1 and 49, inclusive, or one of the special level-number values 66, 77, or 88.
Format
level-number data-name-1 FILLER
172
Language Reference
level-number 01 and 77 must begin in Area A and be followed either by a separator period or by a space followed by its associated data-name, FILLER, or appropriate data description clause. Level numbers 02 through 49 can begin in Areas A or B and must be followed by a space or a separator period. Level numbers 66 and 88 can begin in Areas A or B and must be followed by a space. Single-digit level-numbers 1 through 9 can be substituted for level-numbers 01 through 09. Successive data description entries can start in the same column as the first entry or can be indented according to the level-number. Indentation does not affect the magnitude of a level-number. When level-numbers are indented, each new level-number can begin any number of spaces to the right of Area A. The extent of indentation to the right is limited only by the width of Area B. For more information, see Levels of data on page 151. data-name-1 Explicitly identifies the data being described. data-name-1, if specified, identifies a data item used in the program. data-name-1 must be the first word following the level-number. The data item can be changed during program execution. data-name-1 must be specified for level-66 and level-88 items. It must also be specified for any entry containing the GLOBAL or EXTERNAL clause, and for record description entries associated with file description entries that have the GLOBAL or EXTERNAL clauses. FILLER A data item that is not explicitly referred to in a program. The keyword FILLER is optional. If specified, FILLER must be the first word following the level-number. The keyword FILLER can be used with a conditional variable if explicit reference is never made to the conditional variable but only to values that it can assume. FILLER cannot be used with a condition-name. In a MOVE CORRESPONDING statement or in an ADD CORRESPONDING or SUBTRACT CORRESPONDING statement, FILLER items are ignored. In an INITIALIZE statement, elementary FILLER items are ignored. If data-name-1 or the FILLER clause is omitted, the data item being described is treated as though FILLER had been specified.
BLANK WHEN ZERO clause

The BLANK WHEN ZERO clause specifies that an item contains nothing but spaces when its value is zero.
173
Format
BLANK WHEN ZERO ZEROS ZEROES
The BLANK WHEN ZERO clause can be specified only for elementary numeric or numeric-edited items. These items must be described, either implicitly or explicitly, as USAGE IS DISPLAY. When the BLANK WHEN ZERO clause is specified for a numeric item, the item is considered a numeric-edited item. The BLANK WHEN ZERO clause must not be specified for level-66 or level-88 items. The BLANK WHEN ZERO clause must not be specified for the same entry as the PICTURE symbols S or *. The BLANK WHEN ZERO clause is not allowed for: v v v v v v Index data items Date fields DBCS items National items External or internal floating-point items Items described with USAGE POINTER, USAGE FUNCTION-POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE
DATE FORMAT clause

The DATE FORMAT clause specifies that a data item is a windowed or expanded date field: Windowed date fields Contain a windowed (two-digit) year, specified by a DATE FORMAT clause that contains YY. Expanded date fields Contain an expanded (four-digit) year, specified by a DATE FORMAT clause that contains YYYY. If the NODATEPROC compiler option is in effect, the DATE FORMAT clause is syntax checked but has no effect on the execution of the program. NODATEPROC disables date processing. The rules and restrictions described in this reference for the DATE FORMAT clause and date fields apply only if the DATEPROC compiler option is in effect.
Format
DATE FORMAT IS date-pattern
174
Language Reference
date-pattern is a character string, such as YYXXXX, that represents a windowed or expanded year optionally followed or preceded by one to four characters representing other parts of a date such as the month and day:
Date-pattern string YY YYYY X XX XXX XXXX Specifies that the data item contains A windowed (two-digit) year An expanded (four-digit) year A single character; for example, a digit representing a semester or quarter (1-4) Two characters; for example, digits representing a month (01-12) Three characters; for example, digits representing a day of the year (001-366) Four characters; for example, two digits representing a month (01-12) and two digits representing a day of the month (01-31)
For an introduction to date fields and related terms, see Chapter 10, Millennium Language Extensions and date fields, on page 71. For details on using date fields in applications, see Enterprise COBOL Programming Guide.
Semantics of windowed date fields

Windowed date fields undergo automatic expansion relative to the century window when they are used as operands in arithmetic expressions or arithmetic statements. However, the result of incrementing or decrementing a windowed date is still treated as a windowed date for further computation, comparison, and storing. When used in the following situations, windowed date fields are treated as if they were converted to expanded date format: v Operands in subtractions in which the other operand is an expanded date v Operands in relation conditions v Sending fields in arithmetic or MOVE statements The details of the conversion to expanded date format depend on whether the windowed date field is numeric or alphanumeric. Given a century window starting year of 19nn, the year part (yy) of a numeric windowed date field is treated as if it were expanded as follows: v If yy is less than nn, then add 2000 to yy. v If yy is equal to or greater than nn, then add 1900 to yy. For signed numeric windowed date fields, this means that there can be two representations of some years. For instance, windowed year values 99 and -01 are both treated as 1999, since 1900 + 99 = 2000 + -01. Alphanumeric windowed date fields are treated in a similar manner, but use a prefix of 19 or 20 instead of adding 1900 or 2000. For example, when used as an operand of a relation condition, a windowed date field defined by:
01 DATE-FIELD DATE FORMAT YYXXXX PICTURE 9(6) VALUE IS 450101.
is treated as if it were an expanded date field with a value of:

175
v 19450101, if the century window starting year is 1945 or earlier v 20450101, if the century window starting year is later than 1945
Date trigger values

When the DATEPROC(TRIG) compiler option is in effect, expansion of windowed date fields is sensitive to certain trigger or limit values in the windowed date field. For alphanumeric windowed date fields, these special values are LOW-VALUE, HIGH-VALUE, and SPACE. For alphanumeric and numeric windowed date fields with at least one X in the DATE FORMAT clause (that is, windowed date fields other than just a windowed year), values of all zeros or all nines are also treated as triggers. The all-zero value is intended to act as a date earlier than any valid date. The purpose of the all-nines value is to behave like a date later than any valid date. When a windowed date field contains a trigger in this way, it is expanded as if the trigger value were copied to the century part of the expanded date result, rather than inferring 19 or 20 as the century value. This special trigger expansion is done when a windowed date field is used either as an operand in a relation condition or as the sending field in an arithmetic or MOVE statement. Trigger expansion is not done when windowed date fields are used as operands in arithmetic expressions, but can be applied to the final windowed date result of an arithmetic expression.
Restrictions on using date fields

The following sections describe restrictions on using date fields in these contexts: v v v v DATE FORMAT clauses combined with other clauses Group items consisting only of a date field Language elements that treat date fields as nondates Language elements that do not accept date fields as arguments
For restrictions on using date fields in other contexts, see: v Arithmetic with date fields on page 243 v Date fields on page 251 (in conditional expressions) v ADD statement on page 290 v SUBTRACT statement on page 425 v MOVE statement on page 359
Combining the DATE FORMAT clause with other clauses

The following phrases are the only phrases of the USAGE clause that can be combined with the DATE FORMAT clause: v BINARY v COMPUTATIONAL1 v COMPUTATIONAL-3 v COMPUTATIONAL-4 v DISPLAY v PACKED-DECIMAL
1
USAGE COMPUTATIONAL cannot be combined with the DATE FORMAT clause if the TRUNC(BIN) compiler option is in effect.
176
Language Reference
The PICTURE character-string must specify the same number of characters or digits as the DATE FORMAT clause. For alphanumeric date fields, the only PICTURE character-string symbols allowed are A, 9, and X, with at least one X. For numeric date fields, the only PICTURE character-string symbols allowed are 9 and S. The following clauses are not allowed for a data item defined with DATE FORMAT: v BLANK WHEN ZERO v JUSTIFIED v SEPARATE CHARACTER phrase of the SIGN clause The EXTERNAL clause is not allowed for a windowed date field or a group item that contains a windowed date field subordinate item. Some restrictions apply when combining the following clauses with DATE FORMAT: v REDEFINES clause on page 202 v VALUE clause on page 223
Group items that are date fields

If a group item is defined with a DATE FORMAT clause, then the following restrictions apply: v The elementary items in the group must all be USAGE DISPLAY. v The length of the group item must be the same number of characters as the date-pattern in the DATE FORMAT clause. v If the group consists solely of a date field with USAGE DISPLAY, and both the group and the single subordinate item have DATE FORMAT clauses, then the DATE FORMAT clauses must be identical. v If the group item contains subordinate items that subdivide the group, then the following restrictions apply: If a named (not FILLER) subordinate item consists of exactly the year part of the group item date field and has a DATE FORMAT clause, then the DATE FORMAT clause must be YY or YYYY with the same number of year characters as the group item. If the group item is a Gregorian date with a DATE FORMAT clause of YYXXXX, YYYYXXXX, XXXXYY, or XXXXYYYY, and a named subordinate date data item consists of the year and month part of the Gregorian date, then its DATE FORMAT clause must be YYXX, YYYYXX, XXYY, or XXYYYY, respectively (or, for a group date format of YYYYXXXX, a subordinate date format of YYXX as described below). A windowed date field can be subordinate to an expanded date field group item if the subordinate item starts two characters after the group item, neither date is in year-last format, and the date format of the subordinate item either has no Xs or has the same number of Xs following the Ys as the group item, or is YYXX under a group date format of YYYYXXXX. The only subordinate items that can have a DATE FORMAT clause are those that define the year part of the group item, the windowed part of an expanded date field group item, or the year and month part of a Gregorian date group item, as discussed in the above restrictions. For example, the following defines a valid group item:
177
01
YYMMDD DATE FORMAT YYXXXX. 02 YYMM DATE FORMAT YYXX. 03 YY DATE FORMAT YY PICTURE 99. 03 PICTURE 99. 02 DD PICTURE 99.
Language elements that treat date fields as nondates

If date fields are used in the following language elements, they are treated as nondates. That is, the DATE FORMAT is ignored, and the content of the date data item is used without undergoing automatic expansion. v In the environment division file-control paragraph: SELECT ... ASSIGN USING data-name SELECT ... PASSWORD IS data-name SELECT ... FILE STATUS IS data-name v In data division entries: LABEL RECORD IS data-name LABEL RECORDS ARE data-name LINAGE IS data-name FOOTING data-name TOP data-name BOTTOM data-name v In class conditions v In sign conditions v In DISPLAY statements
Language elements that do not accept windowed date fields as arguments

Windowed date fields cannot be used as: v A data-name in the following formats of the environment division file-control paragraph: SELECT ... RECORD KEY IS SELECT ... ALTERNATE RECORD KEY IS SELECT ... RELATIVE KEY IS v A data-name in the RECORD IS VARYING DEPENDING ON clause of a data division file description (FD) or sort description (SD) entry v The object of an OCCURS DEPENDING ON clause of a data division data definition entry v The key in an ASCENDING KEY or DESCENDING KEY phrase of an OCCURS clause of a data division data definition entry v Any data-name or identifier in the following statements: CANCEL GO TO ... DEPENDING ON INSPECT SET SORT STRING UNSTRING v In the CALL statement, as the identifier containing the program-name v In the INVOKE statement, as the identifier specifying the object on which the method is invoked, or the identifier containing the method name v Identifiers in the TIMES and VARYING phrases of the PERFORM statement (windowed date fields are allowed in the PERFORM conditions)
178
Language Reference
v An identifier in the VARYING phrase of a serial (format-1) SEARCH statement, or any identifier in a binary (format-2) SEARCH statement (windowed date fields are allowed in the SEARCH conditions) v An identifier in the ADVANCING phrase of the WRITE statement v Arguments to intrinsic functions, except the UNDATE intrinsic function Windowed date fields can be used as ascending or descending keys in MERGE and SORT statements, with some restrictions. For details, see MERGE statement on page 353 and SORT statement on page 409.
Language elements that do not accept date fields as arguments

Neither windowed date fields nor expanded date fields can be used: v In the DIVIDE statement, except as an identifier in the GIVING or REMAINDER clause v In the MULTIPLY statement, except as an identifier in the GIVING clause (Date fields cannot be used as operands in division or multiplication.)
EXTERNAL clause
The EXTERNAL clause specifies that the storage associated with a data item is associated with the run unit rather than with any particular program or method within the run unit. An external data item can be referenced by any program or method in the run unit that describes the data item. References to an external data item from different programs or methods using separate descriptions of the data item are always to the same data item. In a run unit, there is only one representative of an external data item. The EXTERNAL clause can be specified only on data description entries whose level-number is 01. It can be specified only on data description entries that are in the working-storage section of a program or method. It cannot be specified in linkage section or file section data description entries. Any data item described by a data description entry subordinate to an entry that describes an external record also attains the external attribute. Indexes in an external data record do not possess the external attribute. The data contained in the record named by the data-name clause is external and can be accessed and processed by any program or method in the run unit that describes and, optionally, redefines it. This data is subject to the following rules: v If two or more programs or methods within a run unit describe the same external data record, each record-name of the associated record description entries must be the same, and the records must define the same number of standard data format characters. However, a program or method that describes an external record can contain a data description entry including the REDEFINES clause that redefines the complete external record, and this complete redefinition need not occur identically in other programs or methods in the run unit. v Use of the EXTERNAL clause does not imply that the associated data-name is a global name.
179
GLOBAL clause
The GLOBAL clause specifies that a data-name is available to every program contained within the program that declares it, as long as the contained program does not itself have a declaration for that name. All data-names subordinate to or condition-names or indexes associated with a global name are global names. A data-name is global if the GLOBAL clause is specified either in the data description entry by which the data-name is declared or in another entry to which that data description entry is subordinate. The GLOBAL clause can be specified in the working-storage section, the file section, the linkage section, and the local-storage section, but only in data description entries whose level-number is 01. In the same data division, the data description entries for any two data items for which the same data-name is specified must not include the GLOBAL clause. A statement in a program contained directly or indirectly within a program that describes a global name can reference that name without describing it again. Two programs in a run unit can reference common data in the following circumstances: v The data content of an external data record can be referenced from any program provided that that program has described that data record. v If a program is contained within another program, both programs can refer to data that possesses the global attribute either in the containing program or in any program that directly or indirectly contains the containing program.
JUSTIFIED clause
The JUSTIFIED clause overrides standard positioning rules for receiving items of category alphabetic, alphanumeric, DBCS, or national.
Format
JUSTIFIED JUST
RIGHT
You can specify the JUSTIFIED clause only at the elementary level. JUST is an abbreviation for JUSTIFIED, and has the same meaning. You cannot specify the JUSTIFIED clause: v For numeric, numeric-edited, or alphanumeric-edited items v For edited DBCS items v In descriptions of index data items v For items described as USAGE FUNCTION-POINTER, USAGE POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE v For external or internal floating-point items v For date fields v With level-66 (RENAMES) and level-88 (condition-name) entries
180
Language Reference
When the JUSTIFIED clause is specified for a receiving item, the data is aligned at the rightmost character position in the receiving item. Also: v If the sending item is larger than the receiving item, the leftmost character positions are truncated. v If the sending item is smaller than the receiving item, the unused character positions at the left are filled with spaces. For a DBCS item, each unused position is filled with a DBCS space (X4040); for a national item, each unused position is filled with the default Unicode space (X0020); otherwise, each unused position is filled with an alphanumeric space. If you omit the JUSTIFIED clause, the rules for standard alignment are followed (see Alignment rules on page 154). The JUSTIFIED clause does not affect initial settings as determined by the VALUE clause.
OCCURS clause
The data division clauses used for table handling are the OCCURS clause and the USAGE IS INDEX clause. For the USAGE IS INDEX description, see USAGE clause on page 214. The OCCURS clause specifies tables whose elements can be referred to by indexing or subscripting. It also eliminates the need for separate entries for repeated data items. Formats for the OCCURS clause include fixed-length tables and variable-length tables. The subject of an OCCURS clause is the data-name of the data item that contains the OCCURS clause. Except for the OCCURS clause itself, data description clauses used with the subject apply to each occurrence of the item described. Whenever the subject of an OCCURS clause or any data-item subordinate to it is referenced, it must be subscripted or indexed, with the following exceptions: v When the subject of the OCCURS clause is used as the subject of a SEARCH statement v When the subject or a subordinate data item is the object of the ASCENDING/DESCENDING KEY phrase v When the subordinate data item is the object of the REDEFINES clause When subscripted or indexed, the subject refers to one occurrence within the table. When not subscripted or indexed, the subject references the entire table. The OCCURS clause cannot be specified in a data description entry that: v Has a level number of 01, 66, 77, or 88. v Describes a redefined data item. (However, a redefined item can be subordinate to an item that contains an OCCURS clause.) See REDEFINES clause on page 202.
Fixed-length tables
Fixed-length tables are specified using the OCCURS clause. Because seven subscripts or indexes are allowed, six nested levels and one outermost level of the format-1 OCCURS clause are allowed. The format-1 OCCURS clause can be
181
specified as subordinate to the OCCURS DEPENDING ON clause. In this way, a table of up to seven dimensions can be specified.
Format 1: fixed-length tables

OCCURS integer-2 TIMES
ASCENDING DESCENDING
data-name-2 KEY IS
INDEXED BY
index-name-1
integer-2 The exact number of occurrences. integer-2 must be greater than zero.
ASCENDING KEY and DESCENDING KEY phrases

Data is arranged in ascending or descending order, depending on the keyword specified, according to the values contained in data-name-2. The data-names are listed in their descending order of significance. The order is determined by the rules for comparison of operands (see Relation condition on page 250). The ASCENDING KEY and DESCENDING KEY data items are used in OCCURS clauses and the SEARCH ALL statement for a binary search of the table element. data-name-2 Must be the name of the subject entry or the name of an entry subordinate to the subject entry. data-name-2 cannot be a windowed date field. data-name-2 can be qualified. If data-name-2 names the subject entry, that entire entry becomes the ASCENDING KEY or DESCENDING KEY and is the only key that can be specified for this table element. If data-name-2 does not name the subject entry, then data-name-2: v Must be subordinate to the subject of the table entry itself v Must not be subordinate to, or follow, any other entry that contains an OCCURS clause v Must not contain an OCCURS clause
182
Language Reference
data-name-2 must not have subordinate items that contain OCCURS DEPENDING ON clauses. When the ASCENDING KEY or DESCENDING KEY phrase is specified, the following rules apply: v Keys must be listed in decreasing order of significance. v The total number of keys for a given table element must not exceed 12. v The data in the table must be arranged in ascending or descending sequence according to the collating sequence in use. v A key can have usage BINARY, DISPLAY, DISPLAY-1, NATIONAL, PACKED-DECIMAL, COMPUTATIONAL, COMPUTATIONAL-1, COMPUTATIONAL-2, COMPUTATIONAL-3, COMPUTATIONAL-4, or COMPUTATIONAL-5. v The sum of the lengths of all the keys associated with one table element must not exceed 256. v If a key is specified without qualifiers and it is not a unique name, the key will be implicitly qualified with the subject of the OCCURS clause and all qualifiers of the OCCURS clause subject. The following example illustrates the specification of ASCENDING KEY data items:
WORKING-STORAGE SECTION. 01 TABLE-RECORD. 05 EMPLOYEE-TABLE OCCURS 100 TIMES ASCENDING KEY IS WAGE-RATE EMPLOYEE-NO INDEXED BY A, B. 10 EMPLOYEE-NAME PIC X(20). 10 EMPLOYEE-NO PIC 9(6). 10 WAGE-RATE PIC 9999V99. 10 WEEK-RECORD OCCURS 52 TIMES ASCENDING KEY IS WEEK-NO INDEXED BY C. 15 WEEK-NO PIC 99. 15 AUTHORIZED-ABSENCES PIC 9. 15 UNAUTHORIZED-ABSENCES PIC 9. 15 LATE-ARRIVALS PIC 9.
The keys for EMPLOYEE-TABLE are subordinate to that entry, and the key for WEEK-RECORD is subordinate to that subordinate entry. In the preceding example, records in EMPLOYEE-TABLE must be arranged in ascending order of WAGE-RATE, and in ascending order of EMPLOYEE-NO within WAGE-RATE. Records in WEEK-RECORD must be arranged in ascending order of WEEK-NO. If they are not, results of any SEARCH ALL statement are unpredictable.
INDEXED BY phrase
The INDEXED BY phrase specifies the indexes that can be used with a table. A table without an INDEXED BY phrase can be referred to through indexing by using an index-name associated with another table. See Subscripting using index-names (indexing) on page 63. Indexes normally are allocated in static memory associated with the program that contains the table. Thus indexes are in the last-used state when a program is reentered. However, in the following cases, indexes are allocated on a per-invocation basis. Thus you must set the value of the index on every entry for indexes on tables in the following sections:
183
v The local-storage section v The working-storage section of a class definition (object instance variables) v The linkage section of: Methods Programs compiled with the RECURSIVE clause Programs compiled with the THREAD option Indexes specified in an external data record do not possess the external attribute. index-name-1 Each index-name specifies an index to be created by the compiler for use by the program. These index-names are not data-names and are not identified elsewhere in the COBOL program; instead, they can be regarded as private special registers for the use of this object program only. They are not data and are not part of any data hierarchy. Unreferenced index names need not be uniquely defined. In one table entry, up to 12 index-names can be specified. If a data item that possesses the global attribute includes a table accessed with an index, that index also possesses the global attribute. Therefore, the scope of an index-name is the same as that of the data-name that names the table in which the index is defined.
Variable-length tables
Variable-length tables are specified using the OCCURS DEPENDING ON clause.
Format 2: variable-length tables

OCCURS integer-1 TO integer-2 TIMES DEPENDING ON
data-name-1
data-name-2 KEY IS
INDEXED BY
index-name-1
integer-1 The minimum number of occurrences. The value of integer-1 must be greater than or equal to zero; it must also be less than the value of integer-2.
184
Language Reference
If integer-1 is omitted, a value of 1 is assumed and the keyword TO must also be omitted. integer-2 The maximum number of occurrences. integer-2 must be greater than integer-1. The length of the subject item is fixed. Only the number of repetitions of the subject item is variable.
OCCURS DEPENDING ON clause

The OCCURS DEPENDING ON clause specifies variable-length tables. data-name-1 Identifies the object of the OCCURS DEPENDING ON clause; that is, the data item whose current value represents the current number of occurrences of the subject item. The contents of items whose occurrence numbers exceed the value of the object are undefined. The object of the OCCURS DEPENDING ON clause (data-name-1) must describe an integer data item. The object cannot be a windowed date field. The object of the OCCURS DEPENDING ON clause must not occupy any storage position within the range of the table (that is, any storage position from the first character position in the table through the last character position in the table). The object of the OCCURS DEPENDING ON clause cannot be variably located; the object cannot follow an item that contains an OCCURS DEPENDING ON clause. If the OCCURS clause is specified in a data description entry included in a record description entry that contains the EXTERNAL clause, data-name-1, if specified, must reference a data item that possesses the external attribute. data-name-1 must be described in the same data division as the subject of the entry. If the OCCURS clause is specified in a data description entry subordinate to one that contains the GLOBAL clause, data-name-1, if specified, must be a global name. data-name-1 must be described in the same data division as the subject of the entry. All data-names used in the OCCURS clause can be qualified; they cannot be subscripted or indexed. At the time that the group item, or any data item that contains a subordinate OCCURS DEPENDING ON item or that follows but is not subordinate to the OCCURS DEPENDING ON item, is referenced, the value of the object of the OCCURS DEPENDING ON clause must fall within the range integer-1 through integer-2. When a group item that contains a subordinate OCCURS DEPENDING ON item is referred to, the part of the table area used in the operation is determined as follows: v If the object is outside the group, only that part of the table area that is specified by the object at the start of the operation is used.
185
v If the object is included in the same group and the group data item is referenced as a sending item, only that part of the table area that is specified by the value of the object at the start of the operation is used in the operation. v If the object is included in the same group and the group data item is referenced as a receiving item, the maximum length of the group item is used in the operation. The following statements are affected by the maximum length rule: v ACCEPT identifier (format 1 and 2) v CALL ... USING BY REFERENCE identifier v INVOKE ... USING BY REFERENCE identifier v MOVE ... TO identifier v READ ... INTO identifier v RELEASE identifier FROM ... v RETURN ... INTO identifier v REWRITE identifier FROM ... v STRING ... INTO identifier v UNSTRING ... INTO identifier DELIMITER IN identifier v WRITE identifier FROM ... If a variable-length group item is not followed by a nonsubordinate item, the maximum length of the group is used when it appears as the identifier in CALL ... USING BY REFERENCE identifier. Therefore, the object of the OCCURS DEPENDING ON clause does not need to be set unless the group is variably located. If the group item is followed by a nonsubordinate item, the actual length, rather than the maximum length, is used. At the time the subject of entry is referenced, or any data item subordinate or superordinate to the subject of entry is referenced, the object of the OCCURS DEPENDING ON clause must fall within the range integer-1 through integer-2. Certain uses of the OCCURS DEPENDING ON clause result in complex OCCURS DEPENDING ON (ODO) items. The following constitute complex ODO items: v A data item described with an OCCURS DEPENDING ON clause that is followed by a nonsubordinate elementary data item, described with or without an OCCURS clause v A data item described with an OCCURS DEPENDING ON clause that is followed by a nonsubordinate group item v A group item that contains one or more subordinate items described with an OCCURS DEPENDING ON clause v A data item described with an OCCURS clause or an OCCURS DEPENDING ON clause that contains a subordinate data item described with an OCCURS DEPENDING ON clause (a table that contains variable-length elements) v An index-name associated with a table that contains variable-length elements The object of an OCCURS DEPENDING ON clause cannot be a nonsubordinate item that follows a complex ODO item. Any nonsubordinate item that follows an item described with an OCCURS DEPENDING ON clause is a variably located item. That is, its location is affected by the value of the OCCURS DEPENDING ON object.
186
Language Reference
When implicit redefinition is used in a File Description (FD) entry, subordinate level items can contain OCCURS DEPENDING ON clauses. The INDEXED BY phrase can be specified for a table that has a subordinate item that contains an OCCURS DEPENDING ON clause. For more information about complex OCCURS DEPENDING ON, see the Enterprise COBOL Programming Guide. The ASCENDING KEY phrase, the DESCENDING KEY phrase, and the INDEXED BY clause are described under Fixed-length tables on page 181.
PICTURE clause
The PICTURE clause specifies the general characteristics and editing requirements of an elementary item.
Format
PICTURE PIC character-string IS
PICTURE or PIC The PICTURE clause must be specified for every elementary item except the following: v Index data items v The subject of the RENAMES clause v Items described with USAGE POINTER, USAGE FUNCTION-POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE v Internal floating-point data items In these cases, use of the PICTURE clause is prohibited. The PICTURE clause can be specified only at the elementary level. PIC is an abbreviation for PICTURE and has the same meaning. character-string character-string is made up of certain COBOL characters used as symbols. The allowable combinations determine the category of the elementary data item. character-string can contain a maximum of 50 characters.
Symbols used in the PICTURE clause

Any punctuation character that appears within the PICTURE character-string is not considered a punctuation character, but rather a PICTURE character-string symbol. When specified in the SPECIAL-NAMES paragraph, DECIMAL-POINT IS COMMA exchanges the functions of the period and the comma in PICTURE character-strings and in numeric literals.
187
The lowercase letters that correspond to the uppercase letters that represent the following PICTURE symbols are equivalent to their uppercase representations in a PICTURE character-string:
A, B, E, G, N, P, S, V, X, Z, CR, DB
All other lowercase letters are not equivalent to their corresponding uppercase representations. PICTURE clause symbol meanings (Table 10) defines the meaning of each PICTURE clause symbol. The heading Size refers to the number of bytes the symbol contributes to the actual size of the data item.
Table 10. PICTURE clause symbol meanings Symbol A Meaning Size Restrictions
A character position that Occupies 1 byte can contain only a letter of the alphabet or a space For non-DBCS data, a Occupies 1 byte character position into which the space character is inserted For DBCS data, a character position into which a DBCS space is inserted. Represents a single DBCS character position containing a DBCS space. Occupies 2 bytes
Marks the start of the exponent in an external floating-point item A DBCS character position A national character position when specified with usage NATIONAL or when usage is unspecified and the NSYMBOL(NATIONAL) compiler option is in effect A DBCS character position when specified with usage DISPLAY-1 or when usage is unspecified and the NSYMBOL(DBCS) compiler option is in effect
Occupies 1 byte
G N
Occupies 2 bytes Occupies 2 bytes
Cannot be specified for a non-DBCS item Cannot be specified when a usage other than DISPLAY-1 or NATIONAL is specified
188
Language Reference
Table 10. PICTURE clause symbol meanings (continued) Symbol P Meaning An assumed decimal scaling position. Used to specify the location of an assumed decimal point when the point is not within the number that appears in the data item. See also P symbol on page 191. Size Not counted in the size of the data item. Scaling position characters are counted in determining the maximum number of digit positions in numeric-edited items or in items that appear as arithmetic operands. The size of the value is the number of digit positions represented by the PICTURE character-string. S An indicator of the presence (but not the representation, nor necessarily the position) of an operational sign. An operational sign indicates whether the value of an item involved in an operation is positive or negative. An indicator of the location of the assumed decimal point. Does not represent a character position. When the assumed decimal point is to the right of the rightmost symbol in the string, the V is redundant. X A character position that Occupies 1 byte can contain any allowable character from the character set of the computer A leading numeric character position. When that position contains a zero, a space character replaces the zero. A character position that contains a numeral Each Z is counted in the size of the data item. Not counted in Must be written as the determining the size of leftmost character in the the elementary item, PICTURE string unless an associated SIGN clause specifies the SEPARATE CHARACTER phrase (which would occupy 1 byte) Restrictions Can appear only as a continuous string of Ps in the leftmost or rightmost digit positions within a PICTURE character-string
Not counted in the size of Can appear only once in the elementary item a character-string
9 0
Each 9 is counted in the size of the data item.
A character position into Each 0 is counted in the which the numeral zero is size of the data item. inserted A character position into which the slash character is inserted Each / is counted in the size of the data item.
189
Table 10. PICTURE clause symbol meanings (continued) Symbol , Meaning A character position into which a comma is inserted An editing symbol that represents the decimal point for alignment purposes. In addition, it represents a character position into which a period is inserted. Editing sign control symbols. Each represents the character position into which the editing sign control symbol is placed. Size Each , is counted in the size of the data item. Each . is counted in the size of the data item. Restrictions
+ CR DB *
Each character used in the symbol is counted in determining the size of the data item.
The symbols are mutually exclusive in one character-string.
A check protect symbol: a Each asterisk (*) is leading numeric character counted in the size of the position into which an item. asterisk is placed when that position contains a zero cs can be any valid currency symbol. A currency symbol represents a character position into which a currency sign value is placed. The default currency symbol is the character assigned the value X5B in the code page in effect at compile time. In this document, the default currency symbol is represented by the dollar sign ($) and cs stands for any valid currency symbol. For details, see Currency symbol on page 192. The first occurrence of a currency symbol adds the number of characters in the currency sign value to the size of the data item. Each subsequent occurrence adds one character to the size of the data item.
cs
The following figure shows the sequences in which picture symbols can be specified to form picture character-strings. More detailed explanations of PICTURE clause symbols follow the figure.
190
Language Reference
P symbol
Because the scaling position character P implies an assumed decimal point (to the left of the Ps if the Ps are leftmost PICTURE characters; to the right of the Ps if the Ps are rightmost PICTURE characters), the assumed decimal point symbol V is redundant as either the leftmost or rightmost character within such a PICTURE description. In certain operations that reference a data item whose PICTURE character-string contains the symbol P, the algebraic value of the data item is used rather than the actual character representation of the data item. This algebraic value assumes the decimal point in the prescribed location and zero in place of the digit position
191
specified by the symbol P. The size of the value is the number of digit positions represented by the PICTURE character-string. These operations are any of the following: v Any operation that requires a numeric sending operand v A MOVE statement where the sending operand is numeric and its PICTURE character-string contains the symbol P v A MOVE statement where the sending operand is numeric-edited and its PICTURE character-string contains the symbol P, and the receiving operand is numeric or numeric-edited v A comparison operation where both operands are numeric In all other operations, the digit positions specified with the symbol P are ignored and are not counted in the size of the operand.
Currency symbol
The currency symbol in a picture character-string is represented by the default currency symbol $ or by a single character specified either in the CURRENCY compiler option or in the CURRENCY SIGN clause in the SPECIAL-NAMES paragraph of the environment division. Although the default currency symbol is represented by $ in this document, the actual default currency symbol is the character with the value X5B in the EBCDIC code page in effect at compile time. If the CURRENCY SIGN clause is specified, the CURRENCY and NOCURRENCY compiler options are ignored. If the CURRENCY SIGN clause is not specified and the NOCURRENCY compiler option is in effect, the dollar sign ($) is used as the default currency sign value and currency symbol. For more information about the CURRENCY SIGN clause, see CURRENCY SIGN clause on page 112. For more information about the CURRENCY and NOCURRENCY compiler options, see the Enterprise COBOL Programming Guide. A currency symbol can be repeated within the PICTURE character-string to specify floating insertion. Different currency symbols must not be used in the same PICTURE character-string. Unlike all other picture symbols, currency symbols are case sensitive. For example, D and d specify different currency symbols. A currency symbol can be used only to define a numeric-edited item with USAGE DISPLAY.
Character-string representation
Symbols that can appear more than once The following symbols can appear more than once in one PICTURE character-string:
A B G N P X Z 9 0 / , + - * cs
At least one of the symbols A, G, N, X, Z, 9, or *, or at least two of the symbols +, -, or cs must be present in a PICTURE string. An unsigned nonzero integer enclosed in parentheses immediately following any of these symbols specifies the number of consecutive occurrences of that symbol.
192
Language Reference
Example: The following two PICTURE clause specifications are equivalent:

PICTURE IS $99999.99CR PICTURE IS $9(5).9(2)CR
Symbols that can appear only once The following symbols can appear only once in one PICTURE character-string:
E S V . CR DB
Except for the PICTURE symbol V, each time any of the above symbols appears in the character-string, it represents an occurrence of that character or set of allowable characters in the data item.
Data categories and PICTURE rules

The allowable combinations of PICTURE symbols determine the data category of the item: v Alphabetic items v Numeric items v Numeric-edited items v Alphanumeric items v Alphanumeric-edited items v DBCS items v External floating-point items v National items
Alphabetic items
The PICTURE character-string can contain only the symbol A. The contents of the item in standard data format must consist of any of the letters of the Latin alphabet and the space character. Other clauses: USAGE DISPLAY must be specified or implied. Any associated VALUE clause must specify an alphanumeric literal containing only alphabetic characters, SPACE, or a symbolic-character as the value of a figurative constant.
Numeric items
Types of numeric items are: v Binary v Packed decimal (internal decimal) v Zoned decimal (external decimal) For numeric date fields, the PICTURE character-string can contain only the symbols 9 and S. For all other numeric fields, the PICTURE character-string can contain only the symbols 9, P, S, and V. For binary items, the number of digit positions must range from 1 through 18 inclusive. For packed decimal and zoned decimal items the number of digit positions must range from 1 through 18, inclusive, when the ARITH(COMPAT) compiler option is in effect, or from 1 through 31, inclusive, when the ARITH(EXTEND) compiler option is in effect.
193
For numeric date fields, the number of digit positions must match the number of characters specified by the DATE FORMAT clause. If unsigned, the contents of the item in standard data format must contain a combination of the Arabic numerals 0-9. If signed, it can also contain a +, -, or other representation of the operational sign.
Examples of valid ranges

PICTURE 9999 S99 S999V9 PPP999 S999PPP Valid range of values 0 through 9999 -99 through +99 -999.9 through +999.9 0 through .000999 -1000 through -999000 and +1000 through +999000 or zero
Other clauses: The USAGE of the item can be DISPLAY, BINARY, COMPUTATIONAL, PACKED-DECIMAL, COMPUTATIONAL-3, COMPUTATIONAL-4, or COMPUTATIONAL-5. A VALUE clause can specify a figurative constant ZERO. A VALUE clause associated with an elementary numeric item must specify a numeric literal or the figurative constant ZERO. A VALUE clause associated with a group item consisting of elementary numeric items must specify an alphanumeric literal or a figurative constant, because the group is considered alphanumeric. In both cases, the literal is treated exactly as specified; no editing is performed. The NUMPROC and TRUNC compiler options can affect the use of numeric data items. For details, see the Enterprise COBOL Programming Guide.
Numeric-edited items
The PICTURE character-string can contain the following symbols:
B P V Z 9 0 / , . + CR DB * cs
The combinations of symbols allowed are determined from the PICTURE clause symbol order allowed (see the figure in Symbols used in the PICTURE clause on page 187), and the editing rules (see PICTURE clause editing on page 197). The following rules also apply: v Either the BLANK WHEN ZERO clause must be specified for the item, or the string must contain at least one of the following symbols:
B / Z 0 , . * + CR DB cs
v If the ARITH(COMPAT) compiler option is in effect, then the number of digit positions represented in the character-string must be in the range 1 through 18, inclusive. If the ARITH(EXTEND) compiler option is in effect, then the number of digit positions represented in the character-string must be in the range 1 through 31, inclusive. v The total number of character positions in the string (including editing-character positions) must not exceed 249. The contents of those character positions representing digits in standard data format must be one of the 10 Arabic numerals. Other clauses: USAGE DISPLAY must be specified or implied.
194
Language Reference
Any associated VALUE clause must specify an alphanumeric literal or a figurative constant. The literal is treated exactly as specified; no editing is done.
Alphanumeric items
The PICTURE character-string must consist of either of the following: v One or more occurrences of the symbol X. v Combinations of the symbols A, X, and 9. (A character-string containing all As or all 9s does not define an alphanumeric item.) The item is treated as if the character-string contained only the symbol X. The contents of the item in standard data format can be any allowable characters from the character set of the computer. Other clauses: USAGE DISPLAY must be specified or implied. Any associated VALUE clause must specify an alphanumeric literal or a figurative constant.
Alphanumeric-edited items
The PICTURE character-string can contain the following symbols:
A X 9 B 0 /
The string must contain at least one A or X, and at least one B or 0 (zero) or /. The contents of the item in standard data format must be two or more characters from the character set of the computer. Other clauses: USAGE DISPLAY must be specified or implied. Any associated VALUE clause must specify an alphanumeric literal or a figurative constant. The literal is treated exactly as specified; no editing is done.
DBCS items
The PICTURE character-string can contain the symbols G, G and B, or N. Each G, B or N represents a single DBCS character position. Any associated VALUE clause must contain a DBCS literal or the figurative constant SPACE. When PICTURE symbol G is used, USAGE DISPLAY-1 must be specified. When PICTURE symbol N is used and the NSYMBOL(DBCS) compiler option is in effect, USAGE DISPLAY-1 is implied if the USAGE clause is omitted.
National items
The PICTURE character-string can contain one or more occurrences of the picture symbol N. These rules apply when the NSYMBOL(NATIONAL) compiler option is in effect or the USAGE NATIONAL clause is specified. In the absence of a USAGE NATIONAL clause, if the NSYMBOL(DBCS) compiler option is in effect, picture symbol N represents a DBCS character and the rules of the PICTURE clause for a DBCS item apply. Each N represents a single national character position.
195
Any associated VALUE clause must specify a national literal, a national literal in hexadecimal notation, or one of the following figurative constants: v ZERO v SPACE v QUOTE v ALL national-literal Other clauses: To define a national data item, only the NATIONAL phrase can be specified in the USAGE clause. When PICTURE symbol N is used and the NSYMBOL(NATIONAL) compiler option is in effect, USAGE NATIONAL is implied if the usage clause is omitted. The following clauses can be used: v JUSTIFIED v EXTERNAL v GLOBAL v OCCURS v REDEFINES v RENAMES v SYNCHRONIZED The following clauses cannot be used: v BLANK WHEN ZERO v SIGN v DATE FORMAT
External floating-point items

Format
+ mantissa E + exponent
+ or -
A sign character must immediately precede both the mantissa and the exponent. A + sign indicates that a positive sign will be used in the output to represent positive values and that a negative sign will represent negative values. A - sign indicates that a blank will be used in the output to represent positive values and that a negative sign will represent negative values. Each sign position occupies one byte of storage.
mantissa The mantissa can contain the symbols:

9 . V
196
Language Reference
An actual decimal point can be represented with a period (.) while an assumed decimal point is represented by a V. Either an actual or an assumed decimal point must be present in the mantissa; the decimal point can be leading, embedded, or trailing. The mantissa can contain from 1 to 16 numeric characters. E Indicates the exponent.
exponent The exponent must consist of the symbol 99. Other clauses: The OCCURS, REDEFINES, RENAMES, and USAGE clauses can be associated with external floating-point items. The SIGN clause is accepted as documentation and has no effect on the representation of the sign. The SYNCHRONIZED clause is treated as documentation. The following clauses are invalid with external floating-point items: v BLANK WHEN ZERO v JUSTIFIED v VALUE
PICTURE clause editing

There are two general methods of editing in a PICTURE clause: v Insertion editing: Simple insertion Special insertion Fixed insertion Floating insertion v Suppression and replacement editing: Zero suppression and replacement with asterisks Zero suppression and replacement with spaces The type of editing allowed for an item depends on its data category. The type of editing that is valid for each category is shown in the following table. cs indicates any valid currency symbol.
Table 11. Data categories Data category Alphabetic Numeric Type of editing None None Insertion symbol None None
197
Table 11. Data categories (continued) Data category Numeric-edited Type of editing Simple insertion Special insertion Fixed insertion Floating insertion Zero suppression Replacement Alphanumeric Alphanumeric-edited DBCS External floating-point National None Simple insertion Simple insertion Special insertion None Insertion symbol B0/, . cs + - CR DB cs + Z* Z * + - cs None B0/ B . None
Simple insertion editing

This type of editing is valid for alphanumeric-edited, numeric-edited, and DBCS items. Each insertion symbol is counted in the size of the item, and represents the position within the item where the equivalent character is to be inserted. For edited DBCS items, each insertion symbol (B) is counted in the size of the item and represents the position within the item where the DBCS space is to be inserted. For example:
PICTURE X(10)/XX X(5)BX(7) 99,B999,B000 99,999 GGBBGG Notes: 1. The symbol b represents a blank space. Value of data ALPHANUMER01 ALPHANUMERIC 1234 12345 D1D2D3D4 Edited result ALPHANUMER/01 ALPHA NUMERIC 01,b234,b0001 12,345 D1D2bbbbD3D41
Special insertion editing

This type of editing is valid for either numeric-edited items or external floating-point items. The period (.) is the special insertion symbol; it also represents the actual decimal point for alignment purposes. The period insertion symbol is counted in the size of the item, and represents the position within the item where the actual decimal point is inserted.
198
Language Reference
Either the actual decimal point or the symbol V as the assumed decimal point, but not both, must be specified in one PICTURE character-string. For example:
PICTURE 999.99 999.99 999.99 999.99 +999.99E+99 Value of data 1.234 12.34 123.45 1234.5 12345 Edited result 001.23 012.34 123.45 234.50 +123.45E+02
Fixed insertion editing

This type of editing is valid only for numeric-edited items. The following insertion symbols are used: v cs v + - CR DB (editing-sign control symbols) In fixed insertion editing, only one currency symbol and one editing-sign control symbol can be specified in a PICTURE character-string. Unless it is preceded by a + or - symbol, the currency symbol must be the first character in the character-string. When either + or - is used as a symbol, it must be the first or last character in the character-string. When CR or DB is used as a symbol, it must occupy the rightmost two character positions in the character-string. If these two character positions contain the symbols CR or DB, the uppercase letters are the insertion characters. Editing sign control symbols produce results that depend on the value of the data item, as shown below:
Editing symbol in PICTURE Result: data item positive or character-string zero Result: data item negative + CR DB + space 2 spaces 2 spaces CR DB
For example:
PICTURE 999.99+ +9999.99 9999.99 Value of data +6555.556 -6555.555 +1234.56 Edited result 555.55+ -6555.55 1234.56
199
PICTURE $999.99 -$999.99 -$999.99 $9999.99CR $9999.99CR
Value of data -123.45 -123.456 +123.456 +123.45 -123.45
Edited result $123.45 -$123.45 $123.45 $0123.45 $0123.45DB
Floating insertion editing

This type of editing is valid only for numeric-edited items. The following symbols are used:
cs + -
Within one PICTURE character-string, these symbols are mutually exclusive as floating insertion characters. Floating insertion editing is specified by using a string of at least two of the allowable floating insertion symbols to represent leftmost character positions into which the actual characters can be inserted. The leftmost floating insertion symbol in the character-string represents the leftmost limit at which the actual character can appear in the data item. The rightmost floating insertion symbol represents the rightmost limit at which the actual character can appear. The second leftmost floating insertion symbol in the character-string represents the leftmost limit at which numeric data can appear within the data item. Nonzero numeric data can replace all characters at or to the right of this limit. Any simple-insertion symbols (B 0 / ,) within or to the immediate right of the string of floating insertion symbols are considered part of the floating character-string. If the period (.) special-insertion symbol is included within the floating string, it is considered to be part of the character-string. To avoid truncation, the minimum size of the PICTURE character-string must be: v The number of character positions in the sending item, plus v The number of nonfloating insertion symbols in the receiving item, plus v One character position for the floating insertion symbol
Representing floating insertion editing

In a PICTURE character-string, there are two ways to represent floating insertion editing and thus two ways in which editing is performed: 1. Any or all leading numeric character positions to the left of the decimal point are represented by the floating insertion symbol. When editing is performed, a single floating insertion character is placed to the immediate left of the first nonzero digit in the data, or of the decimal point, whichever is farther to the left. The character positions to the left of the inserted character are filled with spaces.
200
Language Reference
If all numeric character positions in the PICTURE character-string are represented by the insertion character, then at least one of the insertion characters must be to the left of the decimal point. 2. All the numeric character positions are represented by the floating insertion symbol. When editing is performed, then: v If the value of the data is zero, the entire data item will contain spaces. v If the value of the data is nonzero, the result is the same as in rule 1. For example:
PICTURE $$$$.99 $$$9.99 $,$$$,999.99 +,+++,999.99 $$,$$$,$$$.99CR ++,+++,+++.+++ Value of data .123 .12 -1234.56 -123456.789 -1234567 0000.00 Edited result $.12 $0.12 $1,234.56 -123,456.78 $1,234,567.00CR
Zero suppression and replacement editing

This type of editing is valid only for numeric-edited items. In zero suppression editing, the symbols Z and * are used. These symbols are mutually exclusive in one PICTURE character-string. The following symbols are mutually exclusive as floating replacement symbols in one PICTURE character-string: Z * + - cs Specify zero suppression and replacement editing with a string of one or more of the allowable symbols to represent leftmost character positions in which zero suppression and replacement editing can be performed. Any simple insertion symbols (B 0 / ,) within or to the immediate right of the string of floating editing symbols are considered part of the string. If the period (.) special insertion symbol is included within the floating editing string, it is considered to be part of the character-string.
Representing zero suppression

In a PICTURE character-string, there are two ways to represent zero suppression, and two ways in which editing is performed: 1. Any or all of the leading numeric character positions to the left of the decimal point are represented by suppression symbols. When editing is performed, the replacement character replaces any leading zero in the data that appears in the same character position as a suppression symbol. Suppression stops at the leftmost character: v That does not correspond to a suppression symbol v That contains nonzero data v That is the decimal point
201
2. All the numeric character positions in the PICTURE character-string are represented by the suppression symbols. When editing is performed and the value of the data is nonzero, the result is the same as in the preceding rule. If the value of the data is zero, then: v If Z has been specified, the entire data item will contain spaces. v If * has been specified, the entire data item except the actual decimal point will contain asterisks. For example:
PICTURE ****.** ZZZZ.ZZ ZZZZ.99 ****.99 ZZ99.99 Z,ZZZ.ZZ+ *,***.**+ **,***,***.**+ $Z,ZZZ,ZZZ.ZZCR $B*,***,***.**BBDB Value of data 0000.00 0000.00 0000.00 0000.00 0000.00 +123.456 -123.45 +12345678.9 +12345.67 -12345.67 .00 ****.00 00.00 123.45+ **123.4512,345,678.90+ $ 12,345.67 DB Edited result ****.**
$ ***12,345.67
Do not specify both the asterisk (*) as a suppression symbol and the BLANK WHEN ZERO clause for the same entry.
REDEFINES clause
The REDEFINES clause allows you to use different data description entries to describe the same computer storage area.
Format
level-number data-name-1 FILLER REDEFINES data-name-2
(level-number, data-name-1, and FILLER are not part of the REDEFINES clause, and are included in the format only for clarity.) When specified, the REDEFINES clause must be the first entry following data-name-1 or FILLER. If data-name-1 or FILLER is not specified, the REDEFINES clause must be the first entry following the level-number. The level-numbers of data-name-1 and data-name-2 must be identical, and must not be 66 or 88.
202
Language Reference
The subject or object of a REDEFINES clause can be described with any usage. data-name-1, FILLER Identifies an alternate description for the same area, and is the redefining item or the REDEFINES subject. data-name-2 Is the redefined item or the REDEFINES object. When more than one level-01 entry is written subordinate to an FD entry, a condition known as implicit redefinition occurs. That is, the second level-01 entry implicitly redefines the storage allotted for the first entry. In such level-01 entries, the REDEFINES clause must not be specified. Redefinition begins at data-name-1 and ends when a level-number less than or equal to that of data-name-1 is encountered. No entry that has a level-number numerically lower than those of data-name-1 and data-name-2 can occur between these entries. For example:
05 05 A PICTURE X(6). B REDEFINES A. 10 B-1 PICTURE X(2). 10 B-2 PICTURE 9(4). 05 C PICTURE 99V99.
In this example, A is the redefined item, and B is the redefining item. Redefinition begins with B and includes the two subordinate items B-1 and B-2. Redefinition ends when the level-05 item C is encountered. The data description entry for data-name-2, the redefined item, can contain a REDEFINES clause. The data description entry for the redefined item cannot contain an OCCURS clause. However, the redefined item can be subordinate to an item whose data description entry contains an OCCURS clause. In this case, the reference to the redefined item in the REDEFINES clause must not be subscripted. Neither the redefined item nor the redefining item, nor any items subordinate to them, can contain an OCCURS DEPENDING ON clause. If the GLOBAL clause is used in the data description entry that contains the REDEFINES clause, it is only the subject of the REDEFINES clause that possesses the global attribute. The EXTERNAL clause must not be specified in the same data description entry as a REDEFINES clause. If the data item referenced by data-name-2 is either declared to be an external data record or is specified with a level-number other than 01, the number of character positions it contains must be greater than or equal to the number of character positions in the data item referenced by the subject of this entry. If the data-name referenced by data-name-2 is specified with a level-number of 01 and is not declared to be an external data record, there is no such constraint. When the data item implicitly redefines multiple 01-level records in a file description (FD) entry, items subordinate to the redefining or redefined item can contain an OCCURS DEPENDING ON clause.
203
One or more redefinitions of the same storage area are permitted. The entries that give the new descriptions of the storage area must immediately follow the description of the redefined area without intervening entries that define new character positions. Multiple redefinitions must all use the data-name of the original entry that defined this storage area. For example:
05 05 05 A B REDEFINES A C REDEFINES A PICTURE 9999. PICTURE 9V999. PICTURE 99V99.
The redefining entry (identified by data-name-1) and any subordinate entries must not contain any VALUE clauses.
REDEFINES clause considerations

Data items within an area can be redefined without changing their lengths. For example:
05 NAME-2. 10 SALARY PICTURE 10 SO-SEC-NO PICTURE 10 MONTH PICTURE 05 NAME-1 REDEFINES NAME-2. 10 WAGE PICTURE 10 EMP-NO PICTURE 10 YEAR PICTURE XXX. X(9). XX. XXX. X(9). XX.
Data item lengths and types can also be respecified within an area. For example:
05 NAME-2. 10 SALARY PICTURE 10 SO-SEC-NO PICTURE 10 MONTH PICTURE 05 NAME-1 REDEFINES NAME-2. 10 WAGE PICTURE 10 EMP-NO PICTURE 10 YEAR PICTURE XXX. X(9). XX. 999V999. X(6). XX.
When an area is redefined, all descriptions of the area are always in effect; that is, redefinition does not cause any data to be erased, and never supersedes a previous description. Thus, if B REDEFINES C has been specified, either of the two procedural statements MOVE X TO B and MOVE Y TO C could be executed at any point in the program. In the first case, the area described as B would assume the value and format of X. In the second case, the same physical area (described now as C) would assume the value and format of Y. Note that if the second statement is executed immediately after the first, the value of Y replaces the value of X in the one storage area. The usage of a redefining data item need not be the same as that of a redefined item. This does not, however, cause any change in existing data. For example:
05 05 05 B C REDEFINES B A PICTURE 99 USAGE DISPLAY VALUE 8. PICTURE S99 USAGE COMPUTATIONAL-4. PICTURE S99 USAGE COMPUTATIONAL-4.
Redefining B does not change the bit configuration of the data in the storage area. Therefore, the following two statements produce different results:
ADD B TO A ADD C TO A
204
Language Reference
In the first case, the value 8 is added to A (because B has USAGE DISPLAY). In the second statement, the value -3848 is added to A (because C has USAGE COMPUTATIONAL-4), and the bit configuration of the storage area has the binary value -3848. The above example demonstrates how the improper use of redefinition can give unexpected or incorrect results.
REDEFINES clause examples

The REDEFINES clause can be specified for an item within the scope of an area being redefined (that is, an item subordinate to a redefined item). For example:
05 REGULAR-EMPLOYEE. 10 LOCATION PICTURE A(8). 10 GRADE PICTURE X(4). 10 SEMI-MONTHLY-PAY PICTURE 9999V99. 10 WEEKLY-PAY REDEFINES SEMI-MONTHLY-PAY PICTURE 999V999. 05 TEMPORARY-EMPLOYEE REDEFINES REGULAR-EMPLOYEE. 10 LOCATION PICTURE A(8). 10 FILLER PICTURE X(6). 10 HOURLY-PAY PICTURE 99V99.
The REDEFINES clause can also be specified for an item subordinate to a redefining item. For example:
05 REGULAR-EMPLOYEE. 10 LOCATION PICTURE A(8). 10 GRADE PICTURE X(4). 10 SEMI-MONTHLY-PAY PICTURE 999V999. 05 TEMPORARY-EMPLOYEE REDEFINES REGULAR-EMPLOYEE. 10 LOCATION PICTURE A(8). 10 FILLER PICTURE X(6). 10 HOURLY-PAY PICTURE 99V99. 10 CODE-H REDEFINES HOURLY-PAY PICTURE 9999.
Undefined results
Undefined results can occur when: v A redefining item is moved to a redefined item (that is, if B REDEFINES C and the statement MOVE B TO C is executed). v A redefined item is moved to a redefining item (that is, if B REDEFINES C and the statement MOVE C TO B is executed).
RENAMES clause
The RENAMES clause specifies alternative and possibly overlapping groupings of elementary data items.
Format
66 data-name-1 RENAMES data-name-2 THROUGH THRU data-name-3
205
The special level-number 66 must be specified for data description entries that contain the RENAMES clause. (Level-number 66 and data-name-1 are not part of the RENAMES clause, and are included in the format only for clarity.) One or more RENAMES entries can be written for a logical record. All RENAMES entries associated with one logical record must immediately follow that records last data description entry. data-name-1 Identifies an alternative grouping of data items. A level-66 entry cannot rename a level-01, level-77, level-88, or another level-66 entry. data-name-1 cannot be used as a qualifier; it can be qualified only by the names of level indicator entries or level-01 entries. data-name-2, data-name-3 Identify the original grouping of elementary data items; that is, they must name elementary or group items within the associated level-01 entry and must not be the same data-name. Both data-names can be qualified. The OCCURS clause must not be specified in the data entries for data-name-2 and data-name-3, or for any group entry to which they are subordinate. In addition, the OCCURS DEPENDING ON clause must not be specified for any item defined between data-name-2 and data-name-3. When data-name-3 is specified, data-name-1 is treated as a group item that includes all the elementary items that: v Start with data-name-2 if it is an elementary item, or the first elementary item within data-name-2 if it is a group item v End with data-name-3 if it is an elementary item, or the last elementary item within data-name-3 if it is a group item The keywords THROUGH and THRU are equivalent. The leftmost character position in data-name-3 must not precede the leftmost character position in data-name-2, and the rightmost character position in data-name-3 must not precede the rightmost character position in data-name-2. This means that data-name-3 cannot be totally subordinate to data-name-2. When data-name-3 is not specified, all of the data attributes of data-name-2 become the data attributes for data-name-1. That is: v When data-name-2 is a group item, data-name-1 is treated as a group item. v When data-name-2 is an elementary item, data-name-1 is treated as an elementary item. The following figure illustrates valid and invalid RENAMES clause specifications.
206
Language Reference
SIGN clause
The SIGN clause specifies the position and mode of representation of the operational sign for a numeric entry.
Format
LEADING TRAILING IS
SIGN
SEPARATE CHARACTER
207
The SIGN clause can be specified only for a signed numeric data description entry (that is, one whose PICTURE character-string contains an S) or for a group item that contains at least one such elementary entry. USAGE IS DISPLAY must be specified explicitly or implicitly. If a SIGN clause is specified in either an elementary or group entry subordinate to a group item for which a SIGN clause is specified, the SIGN clause for the subordinate entry takes precedence for the subordinate entry. If you specify the CODE-SET clause in an FD entry, any signed numeric data description entries associated with that file description entry must be described with the SIGN IS SEPARATE clause. The SIGN clause is required only when an explicit description of the properties or position of the operational sign is necessary. When specified, the SIGN clause defines the position and mode of representation of the operational sign for the numeric data description entry to which it applies, or for each signed numeric data description entry subordinate to the group to which it applies. If the SEPARATE CHARACTER phrase is not specified, then: v The operational sign is presumed to be associated with the LEADING or TRAILING digit position, whichever is specified, of the elementary numeric data item. (In this instance, specification of SIGN IS TRAILING is the equivalent of the standard action of the compiler.) v The character S in the PICTURE character string is not counted in determining the size of the item (in terms of standard data format characters). If the SEPARATE CHARACTER phrase is specified, then: v The operational sign is presumed to be the LEADING or TRAILING character position, whichever is specified, of the elementary numeric data item. This character position is not a digit position. v The character S in the PICTURE character string is counted in determining the size of the data item (in terms of standard data format characters). v + is the character used for the positive operational sign. v - is the character used for the negative operational sign. The SEPARATE CHARACTER phrase cannot be specified for a date field. Every numeric data description entry whose PICTURE contains the symbol S is a signed numeric data description entry. If the SIGN clause is also specified for such an entry, and conversion is necessary for computations or comparisons, the conversion takes place automatically. The SIGN clause is treated as documentation for external floating-point items. For internal floating-point items, the SIGN clause must not be specified.
SYNCHRONIZED clause
The SYNCHRONIZED clause specifies the alignment of an elementary item on a natural boundary in storage.
208
Language Reference
Format
SYNCHRONIZED SYNC
LEFT RIGHT
SYNC is an abbreviation for SYNCHRONIZED and has the same meaning. The SYNCHRONIZED clause is never required, but can improve performance on some systems for binary items used in arithmetic. The SYNCHRONIZED clause can be specified for elementary items and for level-01 group items, in which case every elementary item within the group item is synchronized. LEFT Specifies that the elementary item is to be positioned so that it will begin at the left character position of the natural boundary in which the elementary item is placed. Specifies that the elementary item is to be positioned such that it will terminate on the right character position of the natural boundary in which it has been placed. When specified, the LEFT and the RIGHT phrases are syntax checked but have no effect on the execution of the program. The length of an elementary item is not affected by the SYNCHRONIZED clause. The following table lists the effect of the SYNCHRONIZE clause on other language elements.
Table 12. SYNCHRONIZE clause effect on other language elements Language element OCCURS clause DISPLAY or PACKED-DECIMAL NATIONAL Comments When specified for an item within the scope of an OCCURS clause, each occurrence of the item is synchronized. Each item is syntax checked, but the SYNCHRONIZED clause has no effect on execution. Each item is syntax checked, but the SYNCHRONIZED clause has no effect on execution.
RIGHT
209
Table 12. SYNCHRONIZE clause effect on other language elements (continued) Language element BINARY or COMPUTATIONAL Comments When the item is the first elementary item subordinate to an item that contains a REDEFINES clause, the item must not require the addition of unused character positions. When the synchronized clause is not specified for a subordinate data item (one with a level number of 02 through 49): v The item is aligned at a displacement that is a multiple of 2 relative to the beginning of the record if its USAGE is BINARY and its PICTURE is in the range of S9 through S9(4). v The item is aligned at a displacement that is a multiple of 4 relative to the beginning of the record if its USAGE is BINARY and its PICTURE is in the range of S9(5) through S9(18), or its USAGE is INDEX. When SYNCHRONIZED is not specified for binary items, no space is reserved for slack bytes. POINTER, PROCEDUREPOINTER, FUNCTIONPOINTER, OBJECT REFERENCE The data is aligned on a fullword boundary.
COMPUTATIONAL-1 The data is aligned on a fullword boundary. COMPUTATIONAL-2 The data is aligned on a doubleword boundary. COMPUTATIONAL-3 The data is treated the same as the SYNCHRONIZED clause for a PACKED-DECIMAL item. COMPUTATIONAL-4 The data is treated the same as the SYNCHRONIZED clause for a COMPUTATIONAL item. COMPUTATIONAL-5 The data is treated the same as the SYNCHRONIZED clause for a COMPUTATIONAL item. DBCS and external floating-point item REDEFINES clause Each item is syntax checked, but the SYNCHRONIZED clause has no effect on execution. For an item that contains a REDEFINES clause, the data item that is redefined must have the proper boundary alignment for the data item that redefines it. For example, if you write the following, be sure that data item A begins on a fullword boundary: 02 A PICTURE X(4). 02 B REDEFINES A PICTURE S9(9) BINARY SYNC.
In the file section, the compiler assumes that all level-01 records that contain SYNCHRONIZED items are aligned on doubleword boundaries in the buffer. You must provide the necessary slack bytes between records to ensure alignment when there are multiple records in a block. In the working-storage section, the compiler aligns all level-01 entries on a doubleword boundary. For the purposes of aligning binary items in the linkage section, all level-01 items are assumed to begin on doubleword boundaries. Therefore, if you issue a CALL statement, such operands of any USING phrase within it must be aligned correspondingly.
210
Language Reference
Slack bytes
There are two types of slack bytes: v Slack bytes within records: unused character positions that precede each synchronized item in the record v Slack bytes between records: unused character positions added between blocked logical records
Slack bytes within records

For any data description that has binary items that are not on their natural boundaries, the compiler inserts slack bytes within a record to ensure that all SYNCHRONIZED items are on their proper boundaries. Because it is important that you know the length of the records in a file, you need to determine whether slack bytes are required and, if so, how many bytes the compiler will add. The algorithm the compiler uses is as follows: v The total number of bytes occupied by all elementary data items that precede the binary item are added together, including any slack bytes previously added. v This sum is divided by m, where: m = 2 for binary items of four-digit length or less m = 4 for binary items of five-digit length or more and for COMPUTATIONAL-1 data items m = 4 for data items described with USAGE INDEX, USAGE POINTER, , USAGE PROCEDURE-POINTER, USAGE OBJECT REFERENCE, or USAGE FUNCTION-POINTER m = 8 for COMPUTATIONAL-2 data items v If the remainder (r) of this division is equal to zero, no slack bytes are required. If the remainder is not equal to zero, the number of slack bytes that must be added is equal to m - r. These slack bytes are added to each record immediately following the elementary data item that precedes the binary item. They are defined as if they constitute an item with a level-number equal to that of the elementary item that immediately precedes the SYNCHRONIZED binary item, and are included in the size of the group that contains them. For example:
01 FIELD-A. 05 FIELD-B 05 FIELD-C. 10 FIELD-D [10 SLACK-BYTES 10 FIELD-E COMPUTATIONAL 01 FIELD-L. 05 FIELD-M 05 FIELD-N [05 SLACK-BYTES 05 FIELD-O. 10 FIELD-P COMPUTATIONAL PICTURE X(5). PICTURE XX. PICTURE X. INSERTED BY COMPILER] PICTURE S9(6) SYNC. PICTURE X(5). PICTURE XX. PICTURE X. INSERTED BY COMPILER] PICTURE S9(6) SYNC.
Slack bytes can also be added by the compiler when a group item is defined with an OCCURS clause and contains within it a SYNCHRONIZED binary data item. To determine whether slack bytes are to be added, the following action is taken: v The compiler calculates the size of the group, including all the necessary slack bytes within a record.
211
v This sum is divided by the largest m required by any elementary item within the group. v If r is equal to zero, no slack bytes are required. If r is not equal to zero, m - r slack bytes must be added. The slack bytes are inserted at the end of each occurrence of the group item that contains the OCCURS clause. For example, a record defined as follows will appear in storage, as shown, in the figure after the record:
01 WORK-RECORD. 05 WORK-CODE PICTURE 05 COMP-TABLE OCCURS 10 TIMES. 10 COMP-TYPE PICTURE [10 SLACK-BYTES PIC XX. 10 COMP-PAY PICTURE 10 COMP-HOURS PICTURE 10 COMP-NAME PICTURE X. X. INSERTED BY COMPILER] S9(4)V99 COMP SYNC. S9(3) COMP SYNC. X(5).
In order to align COMP-PAY and COMP-HOURS on their proper boundaries, the compiler added 2 slack bytes within the record. In the previous example, without further adjustment, the second occurrence of COMP-TABLE would begin 1 byte before a doubleword boundary, and the alignment of COMP-PAY and COMP-HOURS would not be valid for any occurrence of the table after the first. Therefore, the compiler must add slack bytes at the end of the group, as though the record had been written as follows:
01 WORK-RECORD. 05 WORK-CODE PICTURE 05 COMP-TABLE OCCURS 10 TIMES. 10 COMP-TYPE PICTURE [10 SLACK-BYTES PIC XX. 10 COMP-PAY PICTURE 10 COMP-HOURS PICTURE 10 COMP-NAME PICTURE [10 SLACK-BYTES PIC XX. X. X. INSERTED BY COMPILER ] S9(4)V99 COMP SYNC. S9(3) COMP SYNC. X(5). INSERTED BY COMPILER]
In this example, the second and each succeeding occurrence of COMP-TABLE begins 1 byte beyond a doubleword boundary. The storage layout for the first occurrence of COMP-TABLE will now appear as shown in the following figure:
212
Language Reference
Each succeeding occurrence within the table will now begin at the same relative position as the first.
Slack bytes between records

If the file contains blocked logical records that are to be processed in a buffer, and any of the records contain binary entries for which the SYNCHRONIZED clause is specified, you can improve performance by adding any needed slack bytes between records for proper alignment. The lengths of all the elementary data items in the record, including all slack bytes, are added. (For variable-length records, it is necessary to add an additional 4 bytes for the count field.) The total is then divided by the highest value of m for any one of the elementary items in the record. If r (the remainder) is equal to zero, no slack bytes are required. If r is not equal to zero, m - r slack bytes are required. These slack bytes can be specified by writing a level-02 FILLER at the end of the record. Consider the following record description:
01 COMP-RECORD. 05 A-1 PICTURE 05 A-2 PICTURE 05 A-3 PICTURE 05 B-1 PICTURE 05 B-2 PICTURE 05 B-3 PICTURE X(5). X(3). X(3). S9999 USAGE COMP SYNCHRONIZED. S99999 USAGE COMP SYNCHRONIZED. S9999 USAGE COMP SYNCHRONIZED.
The number of bytes in A-1, A-2, and A-3 totals 11. B-1 is a four-digit COMPUTATIONAL item and 1 slack byte must therefore be added before B-1. With this byte added, the number of bytes that precede B-2 totals 14. Because B-2 is a COMPUTATIONAL item of five digits in length, 2 slack bytes must be added before it. No slack bytes are needed before B-3. The revised record description entry now appears as:
01 COMP-RECORD. 05 A-1 05 A-2 05 A-3 [05 SLACK-BYTE-1 05 B-1 PICTURE PICTURE PICTURE PICTURE PICTURE X(5). X(3). X(3). X. INSERTED BY COMPILER] S9999 USAGE COMP SYNCHRONIZED.
213
[05 05 05
SLACK-BYTE-2 B-2 B-3
PICTURE XX. INSERTED BY COMPILER] PICTURE S99999 USAGE COMP SYNCHRONIZED. PICTURE S9999 USAGE COMP SYNCHRONIZED.
There is a total of 22 bytes in COMP-RECORD, but from the rules above, it appears that m = 4 and r = 2. Therefore, to attain proper alignment for blocked records, you must add 2 slack bytes at the end of the record. The final record description entry appears as:
01 COMP-RECORD. 05 A-1 05 A-2 05 A-3 [05 SLACK-BYTE-1 05 B-1 [05 SLACK-BYTE-2 05 B-2 05 B-3 05 FILLER PICTURE PICTURE PICTURE PICTURE PICTURE PICTURE PICTURE PICTURE PICTURE X(5). X(3). X(3). X. INSERTED BY COMPILER] S9999 USAGE COMP SYNCHRONIZED. XX. INSERTED BY COMPILER] S99999 USAGE COMP SYNCHRONIZED. S9999 USAGE COMP SYNCHRONIZED. XX. [SLACK BYTES YOU ADD]
USAGE clause
The USAGE clause specifies the format of a data item in computer storage.
214
Language Reference
Format 1
BINARY USAGE IS COMP NATIVE COMP-1 NATIVE COMP-2 NATIVE COMP-3 NATIVE COMP-4 NATIVE COMP-5 NATIVE COMPUTATIONAL NATIVE COMPUTATIONAL-1 NATIVE COMPUTATIONAL-2 NATIVE COMPUTATIONAL-3 NATIVE COMPUTATIONAL-4 NATIVE COMPUTATIONAL-5 NATIVE DISPLAY NATIVE DISPLAY-1 NATIVE INDEX NATIONAL NATIVE objref phrase PACKED-DECIMAL NATIVE POINTER PROCEDURE-POINTER FUNCTION-POINTER NATIVE (1)
objref phrase:
OBJECT REFERENCE class-name-1
Notes: 1 NATIVE is treated as a comment in all phrases for which NATIVE is shown in the USAGE clause.
The USAGE clause can be specified for a data description entry with a level-number other than 66 or 88. However, if it is specified at the group level, it applies to each elementary item in the group. The usage of an elementary item must not contradict the usage of a group to which the elementary item belongs. The USAGE clause specifies the format in which data is represented in storage. The format can be restricted if certain procedure division statements are used.
215
When the USAGE clause is not specified at either the group or elementary level, a usage clause is implied with: v Usage DISPLAY when the PICTURE clause contains any symbol other than G or N v Usage NATIONAL when the PICTURE clause contains only one or more of the symbol N and the NSYMBOL(NATIONAL) compiler option is in effect v Usage DISPLAY-1 when the PICTURE clause contains one or more of the symbol N and the NSYMBOL(DBCS) compiler option is in effect For data items defined with the DATE FORMAT clause, only usage DISPLAY and COMP-3 (or its equivalents, COMPUTATIONAL-3 and PACKED-DECIMAL) are allowed. For details, see Combining the DATE FORMAT clause with other clauses on page 176.
Computational items
A computational item is a value used in arithmetic operations. It must be numeric. If the USAGE of a group item is described with any of these items, the elementary items within the group have this usage. The maximum length of a computational item is 18 decimal digits, except for a PACKED-DECIMAL item. If the ARITH(COMPAT) compiler option is in effect, then the maximum length of a PACKED-DECIMAL item is 18 decimal digits. If the ARITH(EXTEND) compiler option is in effect, then the maximum length of a PACKED-DECIMAL item is 31 decimal digits. The PICTURE of a computational item can contain only: 9 S V P One or more numeric character positions One operational sign One implied decimal point One or more decimal scaling positions
COMPUTATIONAL-1 and COMPUTATIONAL-2 items (internal floating-point) cannot have PICTURE strings. BINARY Specified for binary data items. Such items have a decimal equivalent consisting of the decimal digits 0 through 9, plus a sign. Negative numbers are represented as the twos complement of the positive number with the same absolute value. The amount of storage occupied by a binary item depends on the number of decimal digits defined in its PICTURE clause:
Digits in PICTURE clause 1 through 4 5 through 9 10 through 18 Storage occupied 2 bytes (halfword) 4 bytes (fullword) 8 bytes (doubleword)
Binary data is big-endian: the operational sign is contained in the leftmost bit.
216
Language Reference
BINARY, COMPUTATIONAL, and COMPUTATIONAL-4 data items can be affected by the BINARY and TRUNC compiler options. For information about the effect of these compiler options, see the Enterprise COBOL Programming Guide. PACKED-DECIMAL Specified for internal decimal items. Such an item appears in storage in packed decimal format. There are two digits for each character position, except for the trailing character position, which is occupied by the low-order digit and the sign. Such an item can contain any of the digits 0 through 9, plus a sign, representing a value not exceeding 18 decimal digits. The sign representation uses the same bit configuration as the 4-bit sign representation in zoned decimal fields. For details, see the Enterprise COBOL Programming Guide. COMPUTATIONAL or COMP (binary) This is the equivalent of BINARY. The COMPUTATIONAL phrase is synonymous with BINARY. COMPUTATIONAL-1 or COMP-1 (floating-point) Specified for internal floating-point items (single precision). COMP-1 items are 4 bytes long. COMPUTATIONAL-2 or COMP-2 (long floating-point) Specified for internal floating-point items (double precision). COMP-2 items are 8 bytes long. 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. COMPUTATIONAL-5 or COMP-5 (native binary) These data items are represented in storage as binary data. The data items can contain values up to the capacity of the native binary representation (2, 4 or 8 bytes), rather than being limited to the value implied by the number of nines in the picture for the item (as is the case for USAGE BINARY data). When numeric data is moved or stored into a COMP-5 item, truncation occurs at the binary field size rather than at the COBOL picture size limit. When a COMP-5 item is referenced, the full binary field size is used in the operation. The TRUNC(BIN) compiler option causes all binary data items (USAGE BINARY, COMP, COMP-4) to be handled as if they were declared USAGE COMP-5.
Picture S9(1) through S9(4) S9(5) through S9(9) S9(10) through S9(18) Storage representation Binary halfword (2 bytes) Binary fullword (4 bytes) Binary doubleword (8 bytes) Numeric values -32768 through +32767 -2,147,483,648 through +2,147,483,647 -9,223,372,036,854,775,808 through +9.223,372,036,854,775,807 0 through 65535 0 through 4,294,967,295
9(1) through 9(4) 9(5) through 9(9)
Binary halfword (2 bytes) Binary fullword (4 bytes)
217
Picture 9(10) through 9(18)
Storage representation Binary doubleword (8 bytes)
Numeric values 0 through 18,446,744,073,709,551,615
The picture for a COMP-5 data item can specify a scaling factor (that is, decimal positions or implied integer positions). In this case, the maximal capacities listed in the table above must be scaled appropriately. For example, a data item with description PICTURE S99V99 COMP-5 is represented in storage as a binary halfword, and supports a range of values from -327.68 to +327.67.
DISPLAY phrase
The data item is stored in character form, one character for each 8-bit byte. This corresponds to the format used for printed output. DISPLAY can be explicit or implicit. USAGE IS DISPLAY is valid for the following types of items: v Alphabetic v Alphanumeric v Alphanumeric-edited v Numeric-edited v External floating-point v External decimal (numeric) Alphabetic, alphanumeric, alphanumeric-edited, and numeric-edited items are discussed in Data categories and PICTURE rules on page 193. External decimal items are sometimes referred to as zoned decimal items. Each digit of a number is represented by a single byte. The 4 high-order bits of each byte are zone bits; the 4 high-order bits of the low-order byte represent the sign of the item. The 4 low-order bits of each byte contain the value of the digit. If the ARITH(COMPAT) compiler option is in effect, then the maximum length of an external decimal item is 18 digits. If the ARITH(EXTEND) compiler option is in effect, then the maximum length of an external decimal item is 31 digits. The PICTURE character-string of an external decimal item can contain only: 9s; the operational-sign, S; the assumed decimal point, V; and one or more Ps.
DISPLAY-1 phrase
The DISPLAY-1 phrase defines an item as DBCS. The data item is stored in character form, with each character occupying 2 bytes of storage.
FUNCTION-POINTER phrase
The FUNCTION-POINTER phrase defines an item as a function-pointer data item. A function-pointer data item can contain the address of a procedure entry point. A function-pointer is a 4-byte elementary item. Function-pointers have the same capabilities as procedure-pointers, but are 4 bytes in length instead of 8 bytes. Function-pointers are thus more easily interoperable with C function pointers.
218
Language Reference
A function-pointer can contain one of the following addresses or can contain NULL: v The primary entry point of a COBOL program, defined by the PROGRAM-ID paragraph of the outermost program v An alternate entry point of a COBOL program, defined by a COBOL ENTRY statement v An entry point in a non-COBOL program A VALUE clause for a function-pointer data item can contain only NULL or NULLS. A function-pointer can be used in the same contexts as a procedure-pointer, as defined in PROCEDURE-POINTER phrase on page 222.
INDEX phrase
A data item defined with the INDEX phrase is an index data item. An index data item is a 4-byte elementary data item (not necessarily connected with any table) that can be used to save index-name values for future reference. Through a SET statement, an index data item can be assigned an index-name value. Such a value corresponds to the occurrence number in a table. Direct references to an index data item can be made only in a SEARCH statement, a SET statement, a relation condition, the USING phrase of the procedure division header, or the USING phrase of the CALL or ENTRY statement. An index data item can be part of a group item referred to in a MOVE statement or an input/output statement. An index data item saves values that represent table occurrences, yet is not necessarily defined as part of any table. Thus when it is referred to directly in a SEARCH or SET statement or indirectly in a MOVE or input/output statement, there is no conversion of values when the statement is executed. The USAGE IS INDEX clause can be written at any level. If a group item is described with the USAGE IS INDEX clause, the elementary items within the group are index data items. The group itself is not an index data item, and the group name cannot be used in SEARCH or SET statements or in relation conditions. The USAGE clause of an elementary item cannot contradict the USAGE clause of a group to which the item belongs. An index data item cannot be a conditional variable. The DATE FORMAT, JUSTIFIED, PICTURE, BLANK WHEN ZERO, or VALUE clauses cannot be used to describe group or elementary items described with the USAGE IS INDEX clause. SYNCHRONIZED can be used with USAGE IS INDEX to obtain efficient use of the index data item.
NATIONAL phrase
The NATIONAL phrase defines an item as a national data item. The data item has class and category national.
219
A data item of usage NATIONAL is represented in storage in UTF-16 in big-endian format (CCSID 1200). The PICTURE clause associated with a national data item can contain only one or more instances of the picture symbol N. | | | | Cross-platform considerations: Enterprise COBOL does not support UTF-16 with byte order marks or UTF-16 in little-endian format (UTF-16LE) in national data items. If you are porting UTF-16 data or UTF-16LE data from another platform, you must convert that data to UTF-16 big-endian format.
OBJECT REFERENCE phrase

A data item defined with the OBJECT REFERENCE phrase is an object reference. class-name-1 An optional class name. You must declare class-name-1 in the REPOSITORY paragraph in the configuration section of the containing class or outermost program. If specified, class-name-1 indicates that data-name-1 always refers to an object-instance of class class-name-1 or a class derived from class-name-1. Important: The programmer must ensure that the referenced object meets this requirement; violations are not diagnosed. If class-name-1 is not specified, the object reference can refer to an object of any class. In this case, data-name-1 is a universal object reference. You can specify data-name-1 within a group item without affecting the semantics of the group item. There is no conversion of values or other special handling of the object references when statements are executed that operate on the group. The group continues to behave as an alphanumeric data item.
The USAGE OBJECT REFERENCE clause can be used at any level except level 66 or 88. If a group item is described with the USAGE OBJECT REFERENCE clause, the elementary items within the group are object-reference data items. The group itself is not an object reference. The USAGE clause of an elementary item cannot contradict the USAGE clause of a group that contains the item. An object reference can be defined in any section of the data division of a factory definition, object definition, method, or program. An object-reference data item can be used in only: v A SET statement (format 7 only) v A relation condition v An INVOKE statement v The USING or RETURNING phrase of an INVOKE statement v The USING or RETURNING phrase of a CALL statement v A program procedure division or ENTRY statement USING or RETURNING phrase v A method procedure division USING or RETURNING phrase Object-reference data items: v Are ignored in CORRESPONDING operations
220
Language Reference
v v v v
Are unaffected by INITIALIZE statements Can be the subject or object of a REDEFINES clause Cannot be a conditional variable Can be written to a file (but upon subsequent reading of the record the content of the object reference is undefined)
A VALUE clause for an object-reference data item can contain only NULL or NULLS. You can use the SYNCHRONIZED clause with the USAGE OBJECT REFERENCE clause to obtain efficient alignment of the object-reference data item. The DATE FORMAT, JUSTIFIED, PICTURE, and BLANK WHEN ZERO clauses cannot be used to describe group or elementary items defined with the USAGE OBJECT REFERENCE clause.
POINTER phrase
A data item defined with USAGE IS POINTER is a pointer data item. A pointer data item is a 4-byte elementary item. You can use pointer data items to accomplish limited base addressing. Pointer data items can be compared for equality or moved to other pointer items. A pointer data item can be used only: v In a SET statement (format 5 only) v In a relation condition v In the USING phrase of a CALL statement, an ENTRY statement, or the procedure division header The USAGE IS POINTER clause can be written at any level except level 88. If a group item is described with the USAGE IS POINTER clause, the elementary items within the group are pointer data items; the group itself is not a pointer data item and cannot be used in the syntax where a pointer data item is allowed. The USAGE clause of an elementary item cannot contradict the USAGE clause of a group to which the item belongs. Pointer data items can be part of a group that is referred to in a MOVE statement or an input/output statement. However, if a pointer data item is part of a group, there is no conversion of values when the statement is executed. A pointer data item can be the subject or object of a REDEFINES clause. SYNCHRONIZED can be used with USAGE IS POINTER to obtain efficient use of the pointer data item. A VALUE clause for a pointer data item can contain only NULL or NULLS. A pointer data item cannot be a conditional variable. A pointer data item does not belong to any class or category. The DATE FORMAT, JUSTIFIED, PICTURE, and BLANK WHEN ZERO clauses cannot be used to describe group or elementary items defined with the USAGE IS POINTER clause.
221
Pointer data items are ignored in CORRESPONDING operations. A pointer data item can be written to a data set, but upon subsequent reading of the record that contains the pointer, the address contained might no longer represent a valid pointer. USAGE IS POINTER is implicitly specified for the ADDRESS OF special register. For more information, see the Enterprise COBOL Programming Guide.
PROCEDURE-POINTER phrase
The PROCEDURE-POINTER phrase defines an item as a procedure-pointer data item. A procedure-pointer data item is an 8-byte elementary item. A procedure-pointer can contain one of the following addresses or can contain NULL: v The primary entry point of a COBOL program as defined by the program-ID paragraph of the outermost program of a compilation unit v An alternate entry point of a COBOL program as defined by a COBOL ENTRY statement v An entry point in a non-COBOL program A procedure-pointer data item can be used only: v In a SET statement (format 6 only) v In a CALL statement v In a relation condition v In the USING phrase of an ENTRY statement or the procedure division header Procedure-pointer data items can be compared for equality or moved to other procedure-pointer data items. The USAGE IS PROCEDURE-POINTER clause can be written at any level except level 88. If a group item is described with the USAGE IS PROCEDURE-POINTER clause, the elementary items within the group are procedure-pointer data items. The group itself is not a procedure-pointer and cannot be used in the syntax where a procedure-pointer data item is allowed. The USAGE clause of an elementary item cannot contradict the USAGE clause of a group to which the item belongs. Procedure-pointer data items can be part of a group that is referred to in a MOVE statement or an input/output statement. However, there is no conversion of values when the statement is executed. If a procedure-pointer data item is written to a data set, subsequent reading of the record that contains the procedure-pointer can result in an invalid value in the procedure-pointer. A procedure-pointer data item can be the subject or object of a REDEFINES clause. SYNCHRONIZED can be used with USAGE IS PROCEDURE-POINTER to obtain efficient alignment of the procedure-pointer data item. The GLOBAL, EXTERNAL, and OCCURS clause can be used with USAGE IS PROCEDURE-POINTER. A VALUE clause for a procedure-pointer data item can contain only NULL or NULLS.
222
Language Reference
The DATE FORMAT, JUSTIFIED, PICTURE, and BLANK WHEN ZERO clauses cannot be used to describe group or elementary items defined with the USAGE IS PROCEDURE-POINTER clause. A procedure-pointer data item cannot be a conditional variable. A procedure-pointer data item does not belong to any class or category. Procedure-pointer data items are ignored in CORRESPONDING operations.
NATIVE phrase
The NATIVE phrase is treated as a comment.
VALUE clause
The VALUE clause specifies the initial contents of a data item or the values associated with a condition-name. The use of the VALUE clause differs depending on the data division section in which it is specified. In the file section and the linkage section, if the VALUE clause is used in entries other than condition-name entries, the VALUE clause is treated as a comment. In the working-storage section and the local-storage section, the VALUE clause can 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, the value is unpredictable.
Format 1
Format 1: literal value
VALUE IS literal
Format 1 specifies the initial value of a data item. Initialization is independent of any BLANK WHEN ZERO or JUSTIFIED clause that is specified. A format-1 VALUE clause specified in a data description entry that contains or is subordinate to an OCCURS clause causes every occurrence of the associated data item to be assigned the specified value. Each structure that contains the DEPENDING ON phrase of the OCCURS clause is assumed to contain the maximum number of occurrences for the purposes of VALUE initialization. The VALUE clause must not be specified for a data description entry that contains or is subordinate to an entry that contains either an EXTERNAL or a REDEFINES clause. This rule does not apply to condition-name entries. If the VALUE clause is specified at the group level, the literal must be an alphanumeric literal or a figurative constant. The group area is initialized without consideration for the subordinate entries within this group. In addition, the VALUE clause must not be specified for subordinate entries within this group.
223
For group entries, the VALUE clause must not be specified if the entry also contains any of the following clauses: JUSTIFIED, SYNCHRONIZED, or USAGE (other than USAGE DISPLAY). The VALUE clause must not conflict with other clauses in the data description entry or in the data description of that entrys hierarchy. Any VALUE clause associated with COMPUTATIONAL-1 or COMPUTATIONAL-2 (internal floating-point) items must specify a floating-point literal. The condition-name VALUE phrase must also specify a floating-point literal. In addition, the figurative constant ZERO and both integer and decimal forms of the zero literal can be specified in a floating-point VALUE clause or condition-name VALUE phrase. For information about floating-point literal values, see Rules for floating-point literal values on page 29. A VALUE clause cannot be specified for external floating-point items. A VALUE clause associated with a DBCS item must contain a DBCS literal, the figurative constant SPACE, or the figurative constant ALL DBCS literal. A VALUE clause that specifies a national literal can be associated only with a national data item. A VALUE clause associated with a national data item must specify a national literal or one of the figurative constants ZERO, SPACE, QUOTES, or ALL national literal. A data item cannot contain a VALUE clause if the prior data item contains an OCCURS clause with the DEPENDING ON phrase.
Rules for literal values

v Wherever a literal is specified, a figurative constant can be substituted, in accordance with the rules specified in Figurative constants on page 11. v If the item is numeric, all VALUE clause literals must be numeric. If the literal defines the value of a working-storage item, the literal is aligned according to the rules for numeric moves, with one additional restriction: The literal must not have a value that requires truncation of nonzero digits. If the literal is signed, the associated PICTURE character-string must contain a sign symbol. v With some exceptions, numeric literals in a VALUE clause must have a value within the range of values indicated by the PICTURE clause for the item. For example, for PICTURE 99PPP, the literal must be within the range 1000 through 99000, or zero. For PICTURE PPP99, the literal must be within the range 0.00000 through 0.00099. The exceptions are the following: Data items described with usage COMP-5 that do not have a picture symbol P in their PICTURE clause When the TRUNC(BIN) compiler option is in effect, data items described with usage BINARY, COMP, or COMP-4 that do not have a picture symbol P in their PICTURE clause A VALUE clause for these items can have a value up to the capacity of the native binary representation.
224
Language Reference
v If the item is an elementary or group alphabetic, alphanumeric, alphanumeric-edited, or numeric-edited item, all VALUE clause literals must be alphanumeric literals. The literal is aligned according to the alphanumeric alignment rules, with one additional restriction: the number of characters in the literal must not exceed the size of the item. v The functions of the editing characters in a PICTURE clause are ignored in determining the initial appearance of the item described. However, editing characters are included in determining the size of the item. Therefore, any editing characters must be included in the literal. For example, if the item is defined as PICTURE +999.99 and the value is to be +12.34, then the VALUE clause should be specified as VALUE +012.34.
Format 2
Format 2: condition-name value
88 condition-name-1 VALUE IS VALUES ARE
literal-1 THROUGH THRU literal-2
This format associates a value, values, or ranges of values with a condition-name. Each such condition-name requires a separate level-88 entry. Level-number 88 and the condition-name are not part of the format-2 VALUE clause itself. They are included in the format only for clarity. condition-name-1 A user-specified name that associates a value with a conditional variable. If the associated conditional variable requires subscripts or indexes, each procedural reference to the condition-name must be subscripted or indexed as required for the conditional variable. Condition-names are tested procedurally in condition-name conditions (see Conditional expressions on page 246). literal-1 When literal-1 is specified alone, the condition-name is associated with a single value. The class of literal-1 must be a valid class for assignment to the associated conditional variable. literal-1 THROUGH literal-2 The condition-name is associated with at least one range of values. Whenever the THROUGH phrase is used, literal-1 must be less than literal-2, unless the associated data item is a non-year-last windowed date field. For details, see Rules for condition-name entries on page 226.
225
literal-1 and literal-2 must be of the same class. The class of literal-1 and literal-2 must be a valid class for assignment to the associated conditional variable. When literals are DBCS, the range of DBCS values specified by the THROUGH phrase is based on the binary collating sequence of the hexadecimal values of the DBCS characters. When literals are national, the range of national character values specified by the THROUGH phrase is based on the binary collating sequence of the hexadecimal values of the national characters represented by the literals. If the associated conditional variable is a DBCS data item, all literals specified in a format-2 VALUE clause must be DBCS literals. The figurative constant SPACE can be specified. If the associated conditional variable is a national data item, all literals specified in a format-2 VALUE clause must be national literals. The figurative constants ZERO, SPACE, QUOTE, and ALL national literal can be specified.
Rules for condition-name entries

v The VALUE clause is required in a condition-name entry, and must be the only clause in the entry. Each condition-name entry is associated with a preceding conditional variable. Thus every level-88 entry must always be preceded either by the entry for the conditional variable or by another level-88 entry when several condition-names apply to one conditional variable. Each such level-88 entry implicitly has the PICTURE characteristics of the conditional variable. v A space, a separator comma, or a separator semicolon must separate successive operands. Each entry must end with a separator period. v The keywords THROUGH and THRU are equivalent. v The condition-name entries associated with a particular conditional variable must immediately follow the conditional variable entry. The conditional variable can be any elementary data description entry except the following: Another condition-name A RENAMES clause (level-66 item) An item described with USAGE IS INDEX An item described with USAGE POINTER, USAGE PROCEDURE-POINTER, USAGE FUNCTION-POINTER, or USAGE OBJECT REFERENCE v A condition-name can be associated with a group item data description entry. In this case: The condition-name value must be specified as an alphanumeric literal or figurative constant. The size of the condition-name value must not exceed the sum of the sizes of all the elementary items within the group. No element within the group can contain a JUSTIFIED or SYNCHRONIZED clause. The group can contain items of any usage. Condition-names can be specified both at the group level and at subordinate levels within the group. The relation test implied by the definition of a condition-name at the group level is performed in accordance with the rules for comparison of alphanumeric operands, regardless of the nature of elementary items within the group.
226
Language Reference
v Relation tests for DBCS data items are performed according to the rules for comparison of DBCS items. These rules can be found in Comparison of DBCS operands on page 259. v Relation tests for national data items are performed according to the rules for comparison of national operands. These rules can be found in Comparison of national operands on page 259. v A VALUE clause that specifies a national literal can be associated with a condition-name defined only for a national data item. v A VALUE clause that specifies a DBCS literal can be associated with a condition-name defined only for a DBCS data item. v The type of literal in a condition-name entry must be consistent with the data type of its conditional variable. In the following example: CITY-COUNTY-INFO, COUNTY-NO, and CITY are conditional variables. The PICTURE associated with COUNTY-NO limits the condition-name value to a two-digit numeric literal. The PICTURE associated with CITY limits the condition-name value to a three-character alphanumeric literal. The associated condition-names are level-88 entries. Any values for the condition-names associated with CITY-COUNTY-INFO cannot exceed five characters. Because this is a group item, the literal must be alphanumeric.
05 CITY-COUNTY-INFO. 88 BRONX 88 BROOKLYN 88 MANHATTAN 88 QUEENS 88 STATEN-ISLAND 10 COUNTY-NO 88 DUTCHESS 88 KINGS 88 NEW-YORK 88 RICHMOND 10 CITY 88 BUFFALO 88 NEW-YORK-CITY 88 POUGHKEEPSIE 05 POPULATION... VALUE 03NYC. VALUE 24NYC. VALUE 31NYC. VALUE 41NYC. VALUE 43NYC. PICTURE 99. VALUE 14. VALUE 24. VALUE 31. VALUE 43. PICTURE X(3). VALUE BUF. VALUE NYC. VALUE POK.
v If the item is a windowed date field, the following restrictions apply: For alphanumeric conditional variables: - Both literal-1 and literal-2 (if specified) must be alphanumeric literals of the same length as the conditional variable. - The literals must not be specified as figurative constants. - If literal-2 is specified, both literals must contain only decimal digits. If the YEARWINDOW compiler option is specified as a negative integer, literal-2 must not be specified. If literal-2 is specified, literal-1 must be less than literal-2 after applying the century window specified by the YEARWINDOW compiler option. That is, the expanded date value of literal-1 must be less than the expanded date value of literal-2. For more information about using condition-names with windowed date fields, see Condition-name conditions and windowed date field comparisons on page 250.
227
Format 3
Format 3: NULL value
VALUE IS NULL NULLS
This format assigns an invalid address as the initial value of an item defined as USAGE POINTER, USAGE PROCEDURE POINTER, or USAGE FUNCTION-POINTER. It also assigns an invalid object reference as the initial value of an item defined as USAGE OBJECT REFERENCE. VALUE IS NULL can be specified only for elementary items described implicitly or explicitly as USAGE POINTER, USAGE PROCEDURE-POINTER, USAGE FUNCTION-POINTER, or USAGE OBJECT REFERENCE.
228
Language Reference
Part 6. Procedure division

Chapter 20. Procedure division structure . . . Requirements for a method procedure division . . The procedure division header . . . . . . . The USING phrase . . . . . . . . . . RETURNING phrase . . . . . . . . . . References to items in the linkage section . . . Declaratives . . . . . . . . . . . . . . Procedures . . . . . . . . . . . . . . Arithmetic expressions . . . . . . . . . . Arithmetic operators . . . . . . . . . . Arithmetic with date fields . . . . . . . . Addition that involves date fields . . . . Subtraction that involves date fields . . . . Storing arithmetic results that involve date fields . . . . . . . . . . . . . . Conditional expressions . . . . . . . . . . Simple conditions . . . . . . . . . . . Class condition . . . . . . . . . . . . Condition-name condition . . . . . . . . Condition-name conditions and windowed date field comparisons . . . . . . . . Relation condition . . . . . . . . . . . Date fields . . . . . . . . . . . . DBCS items . . . . . . . . . . . . Pointer data items . . . . . . . . . . Procedure-pointer and function-pointer data items . . . . . . . . . . . . . . Object-reference data items . . . . . . . Comparison of numeric and alphanumeric operands . . . . . . . . . . . . . . Comparing numeric operands . . . . . . Comparing alphanumeric operands . . . . Comparing numeric and alphanumeric operands . . . . . . . . . . . . . Comparing index-names and index data items . . . . . . . . . . . . . . Comparison of DBCS operands . . . . . . Comparison of national operands . . . . . Comparing two national operands . . . . Sign condition . . . . . . . . . . . . Date fields in sign conditions . . . . . . Switch-status condition . . . . . . . . . Complex conditions . . . . . . . . . . Negated simple conditions . . . . . . . . Combined conditions . . . . . . . . . . Order of evaluation of conditions. . . . . Order of evaluation: . . . . . . . . . Abbreviated combined relation conditions . . . Using parentheses . . . . . . . . . . Statement categories . . . . . . . . . . . Imperative statements . . . . . . . . . Arithmetic . . . . . . . . . . . . Data movement . . . . . . . . . . Ending . . . . . . . . . . . . . Input-output . . . . . . . . . . . Ordering . . . . . . . . . . . . .
233 234 235 236 238 238 238 239 241 242 243 244 244 245 246 246 247 249 250 250 251 253 253 254 255 255 255 257 258 258 259 259 260 261 261 262 262 263 263 264 265 265 266 268 268 268 268 269 269 269
Procedure-branching . . . Program or method linkage Table-handling . . . . . Conditional statements . . . Arithmetic . . . . . . Data movement . . . . Decision . . . . . . . Input-output . . . . . Ordering . . . . . . . Program or method linkage Table-handling . . . . . Delimited scope statements . . Explicit scope terminators . . Implicit scope terminators . . Compiler-directing statements . Statement operations . . . . . CORRESPONDING phrase . . GIVING phrase. . . . . . ROUNDED phrase . . . . SIZE ERROR phrases . . . . Arithmetic statements . . . Arithmetic statement operands Size of operands . . . . Overlapping operands . . Multiple results. . . . . Data manipulation statements . Overlapping operands . . Input-output statements . . . Common processing facilities . File status key . . . . . Invalid key condition . . . INTO and FROM phrases . File position indicator . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
269 269 269 270 270 270 270 270 271 271 271 271 271 272 272 272 272 273 273 274 276 276 276 277 277 277 277 277 278 278 282 283 284
Chapter 21. Procedure division statements . . 285 ACCEPT statement . . . . . . . . . . . 286 Data transfer . . . . . . . . . . . . 286 System information transfer . . . . . . . 287 DATE, DATE YYYYMMDD, DAY, DAY YYYYDDD, DAY-OF-WEEK, and TIME . . . . 288 ADD statement . . . . . . . . . . . . . 290 ROUNDED phrase . . . . . . . . . . 292 SIZE ERROR phrases . . . . . . . . . . 292 CORRESPONDING phrase (format 3) . . . . 292 END-ADD phrase . . . . . . . . . . . 292 ALTER statement . . . . . . . . . . . . 293 Segmentation considerations . . . . . . . 293 CALL statement . . . . . . . . . . . . 295 USING phrase . . . . . . . . . . . . 296 BY REFERENCE phrase . . . . . . . . . 297 BY CONTENT phrase . . . . . . . . . 297 BY VALUE phrase . . . . . . . . . . . 298 RETURNING phrase . . . . . . . . . . 299 ON EXCEPTION phrase . . . . . . . . . 300 NOT ON EXCEPTION phrase . . . . . . . 300 ON OVERFLOW phrase . . . . . . . . . 300
229
END-CALL phrase . . . . . . . . CANCEL statement . . . . . . . . . CLOSE statement . . . . . . . . . . Effect of CLOSE statement on file types . COMPUTE statement . . . . . . . . . ROUNDED phrase . . . . . . . . SIZE ERROR phrases . . . . . . . . END-COMPUTE phrase . . . . . . . CONTINUE statement . . . . . . . . DELETE statement . . . . . . . . . Sequential access mode . . . . . . . Random or dynamic access mode . . . END-DELETE phrase . . . . . . . . DISPLAY statement . . . . . . . . . DIVIDE statement . . . . . . . . . . ROUNDED phrase . . . . . . . . REMAINDER phrase . . . . . . . . SIZE ERROR phrases . . . . . . . . END-DIVIDE phrase . . . . . . . . ENTRY statement . . . . . . . . . . USING phrase . . . . . . . . . . EVALUATE statement . . . . . . . . END-EVALUATE phrase . . . . . . Determining values . . . . . . . . Comparing selection subjects and objects . Executing the EVALUATE statement . . EXIT statement . . . . . . . . . . . EXIT METHOD statement . . . . . . . EXIT PROGRAM statement . . . . . . GOBACK statement . . . . . . . . . GO TO statement . . . . . . . . . . Unconditional GO TO . . . . . . . Conditional GO TO . . . . . . . . Altered GO TO . . . . . . . . . . MORE-LABELS GO TO . . . . . . . IF statement . . . . . . . . . . . . END-IF phrase . . . . . . . . . . Transferring control . . . . . . . . Nested IF statements . . . . . . . . INITIALIZE statement . . . . . . . . REPLACING phrase . . . . . . . . INITIALIZE statement rules . . . . . INSPECT statement . . . . . . . . . TALLYING phrase (formats 1 and 3) . . REPLACING phrase (formats 2 and 3) . . Replacement rules . . . . . . . . BEFORE and AFTER phrases (all formats) . CONVERTING phrase (format 4) . . . . Data types for identifiers and literals . Data flow . . . . . . . . . . . Comparison cycle . . . . . . . . Example of the INSPECT statement . . . INVOKE statement . . . . . . . . . USING phrase . . . . . . . . . . BY VALUE phrase . . . . . . . . . RETURNING phrase . . . . . . . . Conformance requirements for the RETURNING phrase . . . . . . . ON EXCEPTION phrase . . . . . . . NOT ON EXCEPTION phrase . . . . . END-INVOKE phrase . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301 302 304 305 308 309 309 309 310 311 311 311 312 313 316 318 318 319 319 320 320 321 322 322 323 324 325 326 327 328 329 329 329 330 330 331 331 332 332 333 333 334 335 338 339 340 340 341 342 343 343 344 345 347 347 347 348 349 349 349
Interoperable data types for COBOL and Java Miscellaneous argument types for COBOL and Java . . . . . . . . . . . . . . MERGE statement . . . . . . . . . . . ASCENDING/DESCENDING KEY phrase . COLLATING SEQUENCE phrase. . . . . USING phrase . . . . . . . . . . . GIVING phrase. . . . . . . . . . . OUTPUT PROCEDURE phrase . . . . . MERGE special registers . . . . . . . . Segmentation considerations . . . . . . MOVE statement . . . . . . . . . . . Elementary moves . . . . . . . . . . Moves involving date fields . . . . . Moves involving file record areas. . . . . Group moves . . . . . . . . . . . MULTIPLY statement . . . . . . . . . . ROUNDED phrase . . . . . . . . . SIZE ERROR phrases . . . . . . . . . END-MULTIPLY phrase . . . . . . . . OPEN statement . . . . . . . . . . . General rules . . . . . . . . . . . Label records . . . . . . . . . . . OPEN statement notes . . . . . . . . PERFORM statement . . . . . . . . . . Basic PERFORM statement . . . . . . . END-PERFORM . . . . . . . . . . PERFORM with TIMES phrase . . . . . PERFORM with UNTIL phrase . . . . . PERFORM with VARYING phrase . . . . Varying identifiers . . . . . . . . . . Varying two identifiers . . . . . . . . Varying three identifiers . . . . . . . . Varying more than three identifiers . . . . Varying phrase rules . . . . . . . . . READ statement . . . . . . . . . . . KEY IS phrase . . . . . . . . . . . AT END phrases . . . . . . . . . . INVALID KEY phrases . . . . . . . . END-READ phrase . . . . . . . . . Multiple record processing . . . . . . . Sequential access mode . . . . . . . . Sequential files . . . . . . . . . . Multivolume QSAM files . . . . . . Indexed or relative files . . . . . . . Random access mode . . . . . . . . . Indexed files . . . . . . . . . . Relative files. . . . . . . . . . . Dynamic access mode . . . . . . . . RELEASE statement . . . . . . . . . . RETURN statement . . . . . . . . . . AT END phrases . . . . . . . . . . END-RETURN phrase . . . . . . . . REWRITE statement . . . . . . . . . . INVALID KEY phrases . . . . . . . . END-REWRITE phrase . . . . . . . . Reusing a logical record . . . . . . . . Sequential files . . . . . . . . . . . Indexed files . . . . . . . . . . . Relative files. . . . . . . . . . . . SEARCH statement . . . . . . . . . .
349 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 353 353 355 356 356 357 357 358 359 360 363 364 364 365 366 366 366 367 369 369 370 373 373 375 375 376 377 378 379 381 381 382 383 384 384 384 385 385 385 385 386 387 387 387 388 388 389 391 392 392 393 394 394 394 394 394 395 396
230
Language Reference
AT END phrase and WHEN phrases . . . . NEXT SENTENCE. . . . . . . . . . . END-SEARCH phrase . . . . . . . . . Serial search . . . . . . . . . . . . . VARYING phrase . . . . . . . . . . WHEN phrase (serial search) . . . . . . Binary search . . . . . . . . . . . . WHEN phrase (binary search) . . . . . . Search statement considerations . . . . . . SET statement . . . . . . . . . . . . . Format 1: SET for basic table handling . . . . Format 2: SET for adjusting indexes . . . . . Format 3: SET for external switches . . . . . Format 4: SET for condition-names . . . . . Format 5: SET for USAGE IS POINTER data items . . . . . . . . . . . . . . . Format 6: SET for procedure-pointer and function-pointer data items . . . . . . . . Example of COBOL/C interoperability . . . Format 7: SET for USAGE OBJECT REFERENCE data items . . . . . . . . . . . . . SORT statement . . . . . . . . . . . . ASCENDING/DESCENDING KEY phrase . . DUPLICATES phrase . . . . . . . . . . COLLATING SEQUENCE phrase . . . . . . USING phrase . . . . . . . . . . . . INPUT PROCEDURE phrase . . . . . . . GIVING phrase. . . . . . . . . . . . OUTPUT PROCEDURE phrase . . . . . . SORT special registers . . . . . . . . . Segmentation considerations . . . . . . . START statement . . . . . . . . . . . . KEY phrase . . . . . . . . . . . . . INVALID KEY phrases . . . . . . . . . END-START phrase . . . . . . . . . . Indexed files . . . . . . . . . . . . Relative files. . . . . . . . . . . . . STOP statement . . . . . . . . . . . . STRING statement. . . . . . . . . . . . DELIMITED BY phrase . . . . . . . . . INTO phrase . . . . . . . . . . . . POINTER phrase . . . . . . . . . . . ON OVERFLOW phrases . . . . . . . . END-STRING phrase . . . . . . . . . . Data flow . . . . . . . . . . . . . SUBTRACT statement . . . . . . . . . . ROUNDED phrase . . . . . . . . . . SIZE ERROR phrases . . . . . . . . . . CORRESPONDING phrase (format 3) . . . . END-SUBTRACT phrase . . . . . . . . UNSTRING statement . . . . . . . . . . DELIMITED BY phrase . . . . . . . . . Delimiter with two or more characters . . . Two or more delimiters . . . . . . . . INTO phrase . . . . . . . . . . . . POINTER phrase . . . . . . . . . . . TALLYING IN phrase . . . . . . . . . ON OVERFLOW phrases . . . . . . . . When an overflow condition occurs . . . . When an overflow condition does not occur END-UNSTRING phrase . . . . . . . .
397 397 397 397 398 398 399 400 401 402 402 403 404 404 405 406 407 407 409 410 411 411 412 413 413 414 414 415 416 416 416 417 417 417 419 420 421 421 421 421 422 422 425 427 427 427 427 428 429 429 430 430 431 431 431 432 432 432
Data flow . . . . . . . . . . . Values at the end of execution of the UNSTRING statement . . . . . . Example of the UNSTRING statement . . WRITE statement . . . . . . . . . . ADVANCING phrase. . . . . . . . ADVANCING phrase rules . . . . . LINAGE-COUNTER rules . . . . . END-OF-PAGE phrases . . . . . . . INVALID KEY phrases . . . . . . . END-WRITE phrase . . . . . . . . WRITE for sequential files . . . . . . Multivolume files . . . . . . . . Punch function files with the IBM 3525 . Print function files . . . . . . . . Advanced Function Printing . . . . WRITE for indexed files . . . . . . . WRITE for relative files . . . . . . . XML GENERATE statement . . . . . . Nested XML GENERATE or XML PARSE statements . . . . . . . . . . . Operation of XML GENERATE . . . . Format conversion of elementary data . Trimming of generated XML data . . XML element name formation . . . . . XML PARSE statement . . . . . . . . Nested XML GENERATE or XML PARSE statements . . . . . . . . . . . Control flow . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. 432 . . . . . . . . . . . . . . . . . . . . . . . 434 434 436 438 438 439 439 440 441 441 441 442 442 443 443 443 444 447 447 448 449 449 451
. 454 . 454
Part 6. Procedure division
231
232
Language Reference
Chapter 20. Procedure division structure

The procedure division is an optional division. Program procedure division The procedure division consists of optional declaratives, and procedures that contain sections, paragraphs, sentences, and statements. Factory procedure division The factory procedure division contains only factory method definitions. Object procedure division The object procedure division contains only object method definitions. Method procedure division A method procedure division consists of optional declaratives, and procedures that contain sections, paragraphs, sentences, and statements. A method can INVOKE other methods, be recursively invoked, and issue a CALL to a program. A method procedure division cannot contain nested programs or methods. For additional details on a method procedure division, see Requirements for a method procedure division on page 234.
233
Format: procedure division

procedure-division-header factory-or-object-procedure-division-header method-procedure-division-header
(1) DECLARATIVES. sect . use-statement para END DECLARATIVES.
(2) section-name SECTION (3) priority-number . para
sect:
section-name SECTION (3) priority-number
para:
paragraph-name.
sentence
Notes: 1 2 3 See the USE statement under Compiler-directing statements. Section-name can be omitted. If you omit section-name, paragraph-name can be omitted. Priority-numbers are not valid for methods, recursive programs, or programs compiled with the THREAD option.
Requirements for a method procedure division

When using a method procedure division: v You can use the EXIT METHOD statement or the GOBACK statement to return control to the invoking method or program. An implicit EXIT METHOD statement is generated as the last statement of every method procedure division. For details on the EXIT METHOD statement, see EXIT METHOD statement on page 326.
234
Language Reference
v You can use the STOP RUN statement (which terminates the run unit) in a method. v You can use the RETURN-CODE special register within a method procedure division to access return codes from subprograms that are called with the CALL statement, but the RETURN-CODE value is not returned to the invoker of the current method. Use the procedure division RETURNING data name to return a value to the invoker of the current method. For details, see the discussion of RETURNING data-name-2 under The procedure division header. You cannot specify the following statements or clauses in a method procedure division: v ALTER v ENTRY v EXIT PROGRAM v GO TO without a specified procedure name v SEGMENT-LIMIT v USE FOR DEBUGGING
The procedure division header

The procedure division, if specified, is identified by one of the following headers, depending on whether you are specifying a program, a factory definition, an object definition, or a method definition. The following is the format for a procedure division header in a program.
Format: program procedure division header

PROCEDURE DIVISION
USING REFERENCE BY VALUE BY . RETURNING data-name-2
data-name-1
The following is the format for a procedure division header in a factory paragraph or object paragraph.
Format: factory and object procedure division header

PROCEDURE DIVISION.
235
The following is the format for a procedure division header in a method.
Format: method procedure division header

PROCEDURE DIVISION
USING BY
VALUE
data-name-1
RETURNING data-name-2
The USING phrase

The USING phrase specifies the parameters that a program or method receives when the program is called or the method is invoked. The USING phrase is valid in the procedure division header of a called subprogram or invoked method entered at the beginning of the nondeclaratives portion. Each USING identifier must be defined as a level-01 or level-77 item in the linkage section of the called subprogram or invoked method. In a called subprogram entered at the first executable statement following an ENTRY statement, the USING phrase is valid in the ENTRY statement. Each USING identifier must be defined as a level-01 or level-77 item in the linkage section of the called subprogram. However, a data item specified in the USING phrase of the CALL statement can be a data item of any level in the data division of the calling COBOL program or method. A data item specified in the USING phrase of an INVOKE statement can be a data item of any level in the data division of the invoking COBOL program or method. A data item in the USING phrase of the procedure division header can have a REDEFINES clause in its data description entry. It is possible to call COBOL programs from non-COBOL programs or to pass user parameters from a system command to a COBOL main program. COBOL methods can be invoked only from Java or COBOL. The order of appearance of USING identifiers in both calling and called subprograms, or invoking methods or programs and invoked methods, determines the correspondence of single sets of data available to both. The correspondence is positional and not by name. For calling and called subprograms, corresponding identifiers must contain the same number of bytes although their data descriptions need not be the same. For index-names, no correspondence is established. Index-names in calling and called programs, or invoking method or program and invoked methods, always refer to separate indexes.
236
Language Reference
The identifiers specified in a CALL USING or INVOKE USING statement name the data items available to the calling program or invoking method or program that can be referred to in the called program or invoked method. These items can be defined in any data division section. A given identifier can appear more than once in a procedure division USING phrase. The last value passed to it by a CALL or INVOKE statement is used. The BY REFERENCE or BY VALUE phrase applies to all parameters that follow until overridden by another BY REFERENCE or BY VALUE phrase. BY REFERENCE (for programs only) When an argument is passed BY CONTENT or BY REFERENCE, BY REFERENCE must be specified or implied for the corresponding formal parameter on the PROCEDURE or ENTRY USING phrase. BY REFERENCE is the default if neither BY REFERENCE nor BY VALUE is specified. If the reference to the corresponding data item in the CALL statement declares the parameter to be passed BY REFERENCE (explicit or implicit), the program executes as if each reference to a USING identifier in the called subprogram procedure division is replaced by a reference to the corresponding USING identifier in the calling program. If the reference to the corresponding data item in the CALL statement declares the parameter to be passed BY CONTENT, the value of the item is moved when the CALL statement is executed and placed into a system-defined storage item that possesses the attributes declared in the linkage section for data-name-1. The data description of each parameter in the BY CONTENT phrase of the CALL statement must be the same, meaning no conversion or extension or truncation, as the data description of the corresponding parameter in the USING phrase of the procedure division header. BY VALUE When an argument is passed BY VALUE, the value of the argument is passed, not a reference to the sending data item. The receiving subprogram or method has access only to a temporary copy of the sending data item. Any modifications made to the formal parameters that correspond to an argument passed BY VALUE do not affect the argument. Parameters specified in the USING phrase of a method procedure division header must be passed to the method BY VALUE. See the Enterprise COBOL Programming Guide for examples that illustrate these concepts. data-name-1 data-name-1 must be a level-01 or level-77 item in the linkage section. When data-name-1 is an object reference in a method procedure division header, an explicit class-name must be specified in the data description entry for that object reference; that is, data-name-1 must not be a universal object reference. For methods, the parameter data types are restricted to the data types that are interoperable between COBOL and Java, as listed in Interoperable data types for COBOL and Java on page 349.
237
RETURNING phrase
The RETURNING phrase specifies a data item that is to receive the program or method result. data-name-2 data-name-2 is the RETURNING data item. data-name-2 must be a level-01 or level-77 item in the linkage section. In a method procedure division header, the data type of data-name-2 must be one of the types supported for Java interoperation, as listed in Interoperable data types for COBOL and Java on page 349. The RETURNING data item is an output-only parameter. On entry to the method, the initial state of the RETURNING data item has an undefined and unpredictable value. You must initialize the PROCEDURE DIVISION RETURNING data item before you reference its value. The value that is returned to the invoking routine is the value that the data item has at the point of exit from the method. See RETURNING phrase on page 347 for further details on conformance requirements for the INVOKE RETURNING identifier and the method RETURNING data item. Do not use the procedure division RETURNING phrase in: v Programs that contain the ENTRY statement. v Nested programs. v Main programs: Results of specifying procedure division RETURNING on a main program are undefined. You should specify the procedure division RETURNING phrase only on called subprograms. For main programs, use the RETURN-CODE special register to return a value to the operating environment.
References to items in the linkage section

Data items defined in the linkage section of the called program or invoked method can be referenced within the procedure division of that program if and only if they satisfy one of the following conditions: v They are operands of the USING phrase of the procedure division header or the ENTRY statement. v They are operands of SET ADDRESS OF, CALL ... BY REFERENCE ADDRESS OF, or INVOKE ... BY REFERENCE ADDRESS OF. v They are defined with a REDEFINES or RENAMES clause, the object of which satisfies the above conditions. v They are items subordinate to any item that satisfies the condition in the rules above. v They are condition-names or index-names associated with data items that satisfy any of the above conditions.
Declaratives
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.
238
Language Reference
Each declarative section starts with a USE statement that identifies the sections function. The series of procedures that follow specify the actions that are to be taken when the exceptional condition occurs. Each declarative section ends with another section-name followed by a USE statement, or with the keywords END DECLARATIVES. The entire group of declarative sections is preceded by the keyword DECLARATIVES written on the line after the procedure division header. The group is followed by the keywords END DECLARATIVES. The keywords DECLARATIVES and END DECLARATIVES must each begin in Area A and be followed by a separator period. No other text can appear on the same line. In the declaratives part of the procedure division, each section header must be followed by a separator period, and must be followed by a USE statement followed by a separator period. No other text can appear on the same line. The USE statement has three formats, discussed in these sections: v EXCEPTION/ERROR declarative on page 524 v DEBUGGING declarative on page 528 v LABEL declarative on page 526 The USE statement itself is never executed; instead, the USE statement defines the conditions that execute the succeeding procedural paragraphs, which specify the actions to be taken. After the procedure is executed, control is returned to the routine that activated it. A declarative procedure can be performed from a nondeclarative procedure. A nondeclarative procedure can be performed from a declarative procedure. A declarative procedure can be referenced in a GO TO statement in a declarative procedure. A nondeclarative procedure can be referenced in a GO TO statement in a declarative procedure. You can include a statement that executes a previously called USE procedure that is still in control. However, to avoid an infinite loop, you must be sure there is an eventual exit at the bottom. The declarative procedure is exited when the last statement in the procedure is executed.
Procedures
Within the procedure division, a procedure consists of: v A section or a group of sections v A paragraph or group of paragraphs A procedure-name is a user-defined name that identifies a section or a paragraph. Section A section-header optionally followed by one or more paragraphs.
239
Section-header A section-name followed by the keyword SECTION, optionally followed by a priority-number, followed by a separator period. Section-headers are optional after the keywords END DECLARATIVES or if there are no declaratives. Section-name A user-defined word that identifies a section. A referenced section-name, because it cannot be qualified, must be unique within the program in which it is defined. Priority-number An integer or a positive signed numeric literal ranging in value from 0 through 99. Sections in the declaratives portion must contain priority numbers in the range of 0 through 49. You cannot specify priority-numbers: v In a method definition v In a program that is declared with the RECURSIVE attribute v In a program compiled with the THREAD compiler option A section ends immediately before the next section header, or at the end of the procedure division, or, in the declaratives portion, at the keywords END DECLARATIVES.
Paragraph A paragraph-name followed by a separator period, optionally followed by one or more sentences. Paragraphs must be preceded by a period because paragraphs always follow either the identification division header, a section, or another paragraph, all of which must end with a period. Paragraph-name A user-defined word that identifies a paragraph. A paragraph-name, because it can be qualified, need not be unique. If there are no declaratives (format 2), a paragraph-name is not required in the procedure division. A paragraph ends immediately before the next paragraph-name or section header, or at the end of the procedure division, or, in the declaratives portion, at the keywords END DECLARATIVES. Paragraphs need not all be contained within sections, even if one or more paragraphs are so contained. Sentence One or more statements terminated by a separator period. Statement A syntactically valid combination of identifiers and symbols (literals, relational-operators, and so forth) beginning with a COBOL verb.
240
Language Reference
Identifier The word or words necessary to make unique reference to a data item, optionally including qualification, subscripting, indexing, and reference-modification. In any procedure division reference (except the class test), the contents of an identifier must be compatible with the class specified through its PICTURE clause, otherwise results are unpredictable.
Execution begins with the first statement in the procedure division, excluding declaratives. Statements are executed in the order in which they are presented for compilation, unless the statement rules dictate some other order of execution. The end of the procedure division is indicated by one of the following: v An identification division header that indicates the start of a nested source program v An END PROGRAM, END METHOD, END FACTORY, or END OBJECT marker v The physical end of a program; that is, the physical position in a source program after which no further source program lines occur
Arithmetic expressions
Arithmetic expressions are used as operands of certain conditional and arithmetic statements. An arithmetic expression can consist of any of the following: 1. An identifier described as a numeric elementary item (including numeric functions) 2. A numeric literal 3. The figurative constant ZERO 4. Identifiers and literals, as defined in items 1, 2, and 3, separated by arithmetic operators 5. Two arithmetic expressions, as defined in items 1, 2, 3, or 4, separated by an arithmetic operator 6. An arithmetic expression, as defined in items 1, 2, 3, 4, or 5, enclosed in parentheses Any arithmetic expression can be preceded by a unary operator. Identifiers and literals that appear in arithmetic expressions must represent either numeric elementary items or numeric literals on which arithmetic can be performed. If an exponential expression is evaluated as both a positive and a negative number, the result is always the positive number. For example, the square root of 4:
241
4 ** 0.5
is evaluated as +2 and -2. Enterprise COBOL always returns +2. If the value of an expression to be raised to a power is zero, the exponent must have a value greater than zero. Otherwise, the size error condition exists. In any case where no real number exists as the result of an evaluation, the size error condition exists.
Arithmetic operators
Five binary arithmetic operators and two unary arithmetic operators (as shown in Binary and unary operators (Table 13)) can be used in arithmetic expressions. They are represented by specific characters that must be preceded and followed by a space.
Table 13. Binary and unary operators Binary operator + * / ** Meaning Addition Subtraction Multiplication Division Exponentiation Unary operator + Meaning Multiplication by +1 Multiplication by -1
Limitation: Exponents in fixed-point exponential expressions cannot contain more than nine digits. The compiler will truncate any exponent with more than nine digits. In the case of truncation, the compiler will issue a diagnostic message if the exponent is a literal or constant; if the exponent is a variable or data-name, a diagnostic is issued at run time. Parentheses can be used in arithmetic expressions to specify the order in which elements are to be evaluated. Expressions within parentheses are evaluated first. When expressions are contained within nested parentheses, evaluation proceeds from the least inclusive to the most inclusive set. When parentheses are not used, or parenthesized expressions are at the same level of inclusiveness, the following hierarchic order is implied: 1. Unary operator 2. Exponentiation 3. Multiplication and division 4. Addition and subtraction Parentheses either eliminate ambiguities in logic where consecutive operations appear at the same hierarchic level, or modify the normal hierarchic sequence of execution when this is necessary. When the order of consecutive operations at the same hierarchic level is not completely specified by parentheses, the order is from left to right.
242
Language Reference
An arithmetic expression can begin only with a left parenthesis, a unary operator, or an operand (that is, an identifier or a literal). It can end only with a right parenthesis or an operand. An arithmetic expression must contain at least one reference to an identifier or a literal. There must be a one-to-one correspondence between left and right parentheses in an arithmetic expression, with each left parenthesis placed to the left of its corresponding right parenthesis. If the first operator in an arithmetic expression is a unary operator, it must be immediately preceded by a left parenthesis if that arithmetic expression immediately follows an identifier or another arithmetic expression. The following table shows permissible arithmetic symbol pairs. An arithmetic symbol pair is the combination of two such symbols in sequence. In the table: Yes No Indicates a permissible pairing. Indicates that the pairing is not permitted.
Identifier or literal second symbol Identifier or literal first symbol * / ** + first symbol Unary + or unary - first symbol ( first symbol ) first symbol No Unary + or unary second symbol No
Table 14. Valid arithmetic symbol pairs * / ** + second symbol Yes ( second symbol No ) second symbol Yes
Yes Yes
No No
Yes No
Yes Yes
No No
Yes No
No Yes
Yes No
Yes No
No Yes
Arithmetic with date fields

Arithmetic operations that include a date field are restricted to: v Adding a nondate to a date field v Subtracting a nondate from a date field v Subtracting a date field from a compatible date field Date field operands are compatible if they have the same date format except for the year part, which can be windowed or expanded. The following operations are not allowed: v Any operation between incompatible dates v Adding two date fields v Subtracting a date field from a nondate v Unary minus applied to a date field v Division, exponentiation, or multiplication of or by a date field
243
v Arithmetic expressions that specify a year-last date field v Arithmetic statements that specify a year-last date field, except as a receiving data item when the sending field is a nondate The sections below describe the result of using date fields in the supported addition and subtraction operations. For more information about using date fields in arithmetic operations, see: v ADD statement on page 290 v COMPUTE statement on page 308 v SUBTRACT statement on page 425 Usage notes v Arithmetic operations treat date fields as numeric items; they do not recognize any date-specific internal structure. For example, adding 1 to a windowed date field that contains the value 991231 (which might be used in an application to represent December 31, 1999) results in the value 991232, not 000101. v When used as operands in arithmetic expressions or arithmetic statements, windowed date fields are automatically expanded according to the century window specified by the YEARWINDOW compiler option. When the DATEPROC(TRIG) compiler option is in effect, this expansion is sensitive to trigger values in the windowed date field. For details of both regular and trigger-sensitive windowed expansion, see Semantics of windowed date fields on page 175.
Addition that involves date fields

The following table shows the result of using a date field with a compatible operand in an addition.
Table 15. Results of using date fields in addition Nondate second operand Nondate first operand Date field first operand Nondate Date field Date field second operand Date field Not allowed
For details on how a result is stored in a receiving field, see Storing arithmetic results that involve date fields on page 245.
Subtraction that involves date fields

The following table shows the result of using a date field with a compatible operand in the subtraction: first operand - second operand In a SUBTRACT statement, these operands appear in the reverse order: SUBTRACT second operand FROM first operand
Table 16. Results of using date fields in subtraction Nondate second operand Nondate first operand Date field first operand Nondate Date field Date field second operand Not allowed Nondate
244
Language Reference
Storing arithmetic results that involve date fields

The following statements perform arithmetic, then store the result, or sending field, into one or more receiving fields: v ADD v COMPUTE v DIVIDE v MULTIPLY v SUBTRACT In a MULTIPLY statement, only GIVING identifiers can be date fields. In a DIVIDE statement, only GIVING identifiers or the REMAINDER identifier can be date fields. Any windowed date fields that are operands of the arithmetic expression or statement are treated as if they were expanded before use, as described under Semantics of windowed date fields on page 175. If the sending field is a date field, then the receiving field must be a compatible date field. That is, both fields must have the same date format, except for the year part, which can be windowed or expanded. If the ON SIZE ERROR clause is not specified on the statement, the store operation follows the existing COBOL rules for the statement and proceeds as if the receiving and sending fields (after any automatic expansion of windowed date field operands or result) were both nondates. Storing arithmetic results that involve date fields when ON SIZE ERROR is specified (Table 17 on page 246) shows how these statements store the value of a sending field in a receiving field, where either field can be a date field. The section uses the following terms to describe how the store is performed: Nonwindowed The statement performs the store with no special date-sensitive size error processing, as described under SIZE ERROR phrases on page 274. Windowed with nondate sending field The nondate sending field is treated as a windowed date field compatible with the windowed date receiving field, but with the year part representing the number of years since 1900. (This representation is similar to a windowed date field with a base year of 1900, except that the year part is not limited to a positive number of at most two digits.) The store proceeds as if this assumed year part of the sending field were expanded by adding 1900 to it. Windowed with date sending field The store proceeds as if all windowed date field operands had been expanded as necessary, so that the sending field is a compatible expanded date field. Size error processing: For both kinds of sending field, if the assumed or actual year part of the sending field falls within the century window, the sending field is stored in the receiving field after removing the century component of the year part. That is, the low-order or rightmost two digits of the expanded year part are retained and the high-order or leftmost two digits are discarded.
245
If the year part does not fall within the century window, then the receiving field is unmodified, and the size error imperative statement is executed when any remaining arithmetic operations are complete. For example:
77 77 DUE-DATE PICTURE 9(5) DATE FORMAT YYXXX. IN-DATE PICTURE 9(8) DATE FORMAT YYYYXXX VALUE 1995001. ... COMPUTE DUE-DATE = IN-DATE + 10000 ON SIZE ERROR imperative-statement END-COMPUTE
The sending field is an expanded date field representing January 1, 2005. Assuming that 2005 falls within the century window, the value stored in DUE-DATE is 05001; that is, the sending value of 2005001 without the century component 20. Size error processing and trigger values: If the DATEPROC(TRIG) compiler option is in effect and the sending field contains a trigger value (either zero or all nines), the size error imperative statement is executed and the result is not stored in the receiving field. A nondate is considered to have a trigger value of all nines if it has a nine in every digit position of its assumed date format. Thus for a receiving date format of YYXXX, the nondate value 99,999 is a trigger but the values 9,999 and 999,999 are not, although the larger value of 999,999 will cause a size error anyway.
Table 17. Storing arithmetic results that involve date fields when ON SIZE ERROR is specified Nondate sending field Nondate receiving field Windowed date field receiving field Expanded date field receiving field Nonwindowed Windowed Nonwindowed Date field sending field Not allowed Windowed Nonwindowed
Conditional expressions
A conditional expression causes the object program to select alternative paths of control, depending on the truth value of a test. Conditional expressions are specified in EVALUATE, IF, PERFORM, and SEARCH statements. A conditional expression can be specified in either simple conditions or complex conditions. Both simple and complex conditions can be enclosed within any number of paired parentheses; the parentheses do not change whether the condition is simple or complex.
Simple conditions
There are five simple conditions: v Class condition v Condition-name condition v Relation condition v Sign condition
246
Language Reference
v Switch-status condition A simple condition has a truth value of either true or false.
Class condition
The class condition determines whether the content of a data item is alphabetic, alphabetic-lower, alphabetic-upper, numeric, DBCS, KANJI, or contains only the characters in the set of characters specified by the CLASS clause as defined in the SPECIAL-NAMES paragraph of the environment division.
Format
identifier-1 IS NOT NUMERIC ALPHABETIC ALPHABETIC-LOWER ALPHABETIC-UPPER class-name DBCS KANJI
identifier-1 Must reference a data item described with one of the following usages: v DISPLAY, NATIONAL, COMPUTATIONAL-3, or PACKED-DECIMAL when NUMERIC is specified v DISPLAY-1 when DBCS or KANJI is specified v DISPLAY or NATIONAL when ALPHABETIC, ALPHABETIC-UPPER, or ALPHABETIC-LOWER is specified v DISPLAY when class-name is specified Must not be of class alphabetic when NUMERIC is specified. Must not be of class numeric when ALPHABETIC, ALPHABETIC-UPPER, or ALPHABETIC-LOWER is specified. Valid forms of the class condition for different types of identifiers (Table 18 on page 248) lists the forms of class condition that are valid for each type of identifier. If identifier-1 is a function-identifier, it must reference an alphanumeric or national function. A group item can be used in a class condition where an elementary alphanumeric item can be used, except that the NUMERIC class condition cannot be used if the group contains one or more signed elementary items. When identifier-1 is a national data item, the class-condition tests for the national character representation of the characters associated with the specified character class. For example, specifying a class condition of the form IF national-item IS ALPHABETIC is a test for the lowercase and uppercase letters Latin capital letter A through Latin capital letter Z and the space, as represented in national characters. Specifying IF national-item is NUMERIC is a test for the characters 0 through 9.
247
NOT
When used, NOT and the next keyword define the class test to be executed for truth value. For example, NOT NUMERIC is a truth test for determining that the result of a NUMERIC class test is false (in other words, the item contains data that is nonnumeric).
NUMERIC identifier-1 consists entirely of the characters 0 through 9, with or without an operational sign. If its PICTURE does not contain an operational sign, the identifier being tested is determined to be numeric only if the contents are numeric and an operational sign is not present. If its PICTURE does contain an operational sign, the identifier being tested is determined to be numeric only if the item is an elementary item, the contents are numeric, and a valid operational sign is present. Note: Valid operational signs are determined from the setting of the NUMCLS installation option and the NUMPROC compiler option. For more information, see the Enterprise COBOL Programming Guide . ALPHABETIC identifier-1 consists entirely of any combination of the lowercase or uppercase Latin alphabetic characters A through Z and the space. ALPHABETIC-LOWER identifier-1 consists entirely of any combination of the lowercase Latin alphabetic characters a through z and the space. ALPHABETIC-UPPER identifier-1 consists entirely of any combination of the uppercase Latin alphabetic characters A through Z and the space. class-name identifier-1 consists entirely of the characters listed in the definition of class-name in the SPECIAL-NAMES paragraph. DBCS identifier-1 consists entirely of DBCS characters. A range check is performed on the item for valid character representation. The valid range is X41 through XFE for both bytes of each DBCS character and X4040 for the DBCS blank. KANJI identifier-1 consists entirely of DBCS characters. A range check is performed on the item for valid character representation. The valid range is from X41 through X7F for the first byte, from X41 through XFE for the second byte, and X4040 for the DBCS blank.
Table 18. Valid forms of the class condition for different types of identifiers Type of identifier Alphabetic Valid forms of the class condition ALPHABETIC ALPHABETIC-LOWER ALPHABETIC-UPPER class-name ALPHABETIC ALPHABETIC-LOWER ALPHABETIC-UPPER NUMERIC class-name NOT ALPHABETIC NOT ALPHABETIC-LOWER NOT ALPHABETIC-UPPER NOT class-name NOT ALPHABETIC NOT ALPHABETIC-LOWER NOT ALPHABETIC-UPPER NOT NUMERIC NOT class-name
Alphanumeric, alphanumeric-edited, or numeric-edited
248
Language Reference
Table 18. Valid forms of the class condition for different types of identifiers (continued) Type of identifier External-decimal or internal-decimal DBCS National Valid forms of the class condition NUMERIC DBCS KANJI NUMERIC ALPHABETIC ALPHABETIC-LOWER ALPHABETIC-UPPER NUMERIC class-name NOT NUMERIC NOT DBCS NOT KANJI NOT NUMERIC NOT ALPHABETIC NOT ALPHABETIC-LOWER NOT ALPHABETIC-UPPER NOT NUMERIC NOT class-name
Numeric
Condition-name condition
A condition-name condition tests a conditional variable to determine whether its value is equal to any values that are associated with the condition-name.
Format
condition-name-1
A condition-name is used in conditions as an abbreviation for the relation condition. The rules for comparing a conditional variable with a condition-name value are the same as those specified for relation conditions. If condition-name-1 has been associated with a range of values (or with several ranges of values), the conditional variable is tested to determine whether its value falls within the ranges, including the end values. The result of the test is true if one of the values that corresponds to the condition-name equals the value of its associated conditional variable. Condition-names are allowed for DBCS, national, and floating-point data items, as well as others, as defined for the condition-name format of the VALUE clause. The following example illustrates the use of conditional variables and condition-names:
01 AGE-GROUP 88 INFANT 88 BABY 88 CHILD 88 TEENAGER PIC 99. VALUE 0. VALUE 1, 2. VALUE 3 THRU 12. VALUE 13 THRU 19.
AGE-GROUP is the conditional variable; INFANT, BABY, CHILD, and TEENAGER are condition-names. For individual records in the file, only one of the values specified in the condition-name entries can be present. The following IF statements can be added to the above example to determine the age group of a specific record:
249
IF IF IF IF
INFANT... BABY... CHILD... TEENAGER...
(Tests (Tests (Tests (Tests
for for for for
value 0) values 1, 2) values 3 through 12) values 13 through 19)
Depending on the evaluation of the condition-name condition, alternative paths of execution are taken by the object program.
Condition-name conditions and windowed date field comparisons

If the conditional variable is a windowed date field, then the values associated with its condition-names are treated like values of the windowed date field. That is, they are treated as if they were converted to expanded date format, as described under Semantics of windowed date fields on page 175. For example, given YEARWINDOW(1945), a century window of 1945-2044, and the following definition:
05 DATE-FIELD PIC 9(6) DATE FORMAT YYXXXX. 88 DATE-TARGET VALUE 051220.
then a value of 051220 in DATE-FIELD would cause the following condition to be true:
IF DATE-TARGET...
because the value associated with DATE-TARGET and the value of DATE-FIELD would both be treated as if they were prefixed by 20 before comparison. However, the following condition would be false:
IF DATE-FIELD = 051220...
because in a comparison with a windowed date field, literals are treated as if they were prefixed by 19 regardless of the century window. So the above condition effectively becomes:
IF 20051220 = 19051220...
For more information about using windowed date fields in conditional expressions, see Date fields on page 251.
Relation condition
A relation condition compares two operands, either of which can be an identifier, literal, arithmetic expression, or index-name. An alphanumeric literal can be enclosed in parentheses within a relation condition.
250
Language Reference
Format 1
operand-1 IS NOT > LESS THAN < EQUAL TO = GREATER THAN >= LESS THAN <= operand-2 OR EQUAL TO OR EQUAL TO GREATER THAN
operand-1 The subject of the relation condition. Can be an identifier, literal, function-identifier, arithmetic expression, or index-name. operand-2 The object of the relation condition. Can be an identifier, literal, function-identifier, arithmetic expression, or index-name. The relation condition must contain at least one reference to an identifier. The relational operator specifies the type of comparison to be made, as shown in Relational operators and their meanings (Table 19). Each relational operator must be preceded and followed by a space. The relational operators >= and <= must not have a space between them.
Table 19. Relational operators and their meanings Relational operator IS GREATER THAN IS NOT GREATER THAN IS LESS THAN IS NOT LESS THAN IS EQUAL TO IS NOT EQUAL TO IS GREATER THAN OR EQUAL TO IS LESS THAN OR EQUAL TO Can be written IS > IS NOT > IS < IS NOT < IS = IS NOT = IS >= IS <= Meaning Greater than Not greater than Less than Not less than Equal to Not equal to Is greater than or equal to Is less than or equal to
Date fields
Date fields can be alphanumeric, external decimal, or internal decimal; the existing rules for the validity and mode (numeric or alphanumeric) of comparing such items still apply. For example, an alphanumeric date field cannot be compared
251
with an internal decimal date field. In addition to these rules, two date fields can be compared only if they are compatible; they must have the same date format except for the year part, which can be windowed or expanded. For year-last date fields, the only comparisons that are supported are IS EQUAL TO and IS NOT EQUAL TO between two year-last date fields with identical date formats, or between a year-last date field and a nondate. Comparisons with date fields (Table 20 on page 253) shows supported comparisons for nonyear-last date fields. This table uses the following terms to describe how the comparisons are performed: Nonwindowed The comparison is performed with no windowing, as if the operands were both nondates. Windowed The comparison is performed as if: 1. Any windowed date field in the relation were expanded according to the century window specified by the YEARWINDOW compiler option, as described under Semantics of windowed date fields on page 175. This expansion is sensitive to trigger values in the date field comparand if the DATEPROC(TRIG) compiler option is in effect. 2. Any repetitive alphanumeric figurative constant were expanded to the size of the windowed date field with which it is compared, giving an alphanumeric nondate comparand. Repetitive alphanumeric figurative constants include ZERO (in an alphanumeric context), SPACE, LOW-VALUE, HIGH-VALUE, QUOTE and ALL literal. 3. Any nondate operands were treated as if they had the same date format as the date field, but with a base year of 1900. If the DATEPROC(NOTRIG) compiler option is in effect, the comparison is performed as if the nondate operand were expanded by assuming 19 for the century part of the expanded year. If the DATEPROC(TRIG) compiler option is in effect, the comparison is sensitive to date trigger values in the nondate operand. For alphanumeric operands, these trigger values are LOW-VALUE, HIGH-VALUE, and SPACE. For alphanumeric and numeric operands compared with windowed date fields with at least one X in the DATE FORMAT clause (that is, windowed date fields other than just a windowed year), values of all zeros or all nines are also treated as triggers. If a nondate operand contains a trigger value, the comparison proceeds as if the nondate operand were expanded by copying the trigger value to the assumed century part of the expanded year. If the nondate operand does not contain a trigger value, the century part of the expanded year is assumed to be 19. The comparison is then performed according to normal COBOL rules. Alphanumeric comparisons are not changed to numeric comparisons by the prefixing of the century value.
252
Language Reference
Table 20. Comparisons with date fields Nondate second operand Nondate first operand Windowed date field first operand Expanded date field first operand Nonwindowed Windowed1 Nonwindowed Windowed date field second operand Windowed1 Windowed Windowed Expanded date field second operand Nonwindowed Windowed Nonwindowed
1. When compared with windowed date fields, nondates are assumed to contain a windowed year relative to 1900. For details, see item 3 under the definition of Windowed comparison.
Relation conditions can contain arithmetic expressions. For information about the treatment of date fields in arithmetic expressions, see Arithmetic with date fields on page 243.
DBCS items
DBCS data items and literals can be used with all relational operators. Comparisons are based on the binary collating sequence of the hexadecimal values of the DBCS characters. If the DBCS items are not the same length, the smaller item is padded on the right with DBCS spaces. The PROGRAM COLLATING SEQUENCE clause does not affect comparisons of DBCS data items and literals. DBCS items can be compared only with national items and DBCS items.
Pointer data items

Only EQUAL and NOT EQUAL are allowed as relational operators when specifying pointer data items. Pointer data items are items defined explicitly as USAGE IS POINTER, or are ADDRESS OF special registers, which are implicitly defined as USAGE IS POINTER. The operands are equal if the two addresses used in the comparison would both result in the same storage location. This relation condition is allowed in IF, PERFORM, EVALUATE, and SEARCH format-1 statements. It is not allowed in SEARCH format-2 (SEARCH ALL) statements because there is no meaningful ordering that can be applied to pointer data items.
253
Format 2: data-pointer
ADDRESS OF identifier-1 identifier-2 NULL NULLS ADDRESS OF identifier-3 identifier-4 NULL NULLS EQUAL IS NOT = TO
identifier-1, identifier-3 Can specify any level item defined in the linkage section, except 66 and 88. identifier-2, identifier-4 Must be described as USAGE IS POINTER. NULL, NULLS As in this syntax diagram, can be used only if the other operand is defined as USAGE IS POINTER. That is, NULL=NULL is not allowed. The following table summarizes the permissible comparisons for USAGE IS POINTER, NULL, and ADDRESS OF.
Table 21. Permissible comparisons for USAGE IS POINTER, NULL, and ADDRESS OF USAGE IS POINTER second operand USAGE IS POINTER first operand ADDRESS OF first operand NULL/NULLS first operand Yes No Yes ADDRESS OF second operand Yes NULL or NULLS second operand Yes
Yes Yes
Yes Yes
Yes No
Comparison allowed only for EQUAL, NOT EQUAL No comparison allowed
Procedure-pointer and function-pointer data items

Only EQUAL and NOT EQUAL are allowed as relational operators when specifying procedure-pointer or function-pointer data items in a relation condition. Procedure-pointer data items are defined explicitly as USAGE PROCEDURE-POINTER. Function-pointer data items are defined explicitly as USAGE FUNCTION-POINTER. The operands are equal if the two addresses used in the comparison would both result in the same storage location.
254
Language Reference
This relation condition is allowed in IF, PERFORM, EVALUATE, and SEARCH format-1 statements. It is not allowed in SEARCH format-2 (SEARCH ALL) statements, because there is no meaningful ordering that can be applied to procedure-pointer data items.
Format 3: procedure-pointer or function-pointer

EQUAL identifier-1 NULL NULLS IS NOT = TO
identifier-2 NULL NULLS
identifier-1, identifier-2 Must be described as USAGE PROCEDURE-POINTER or USAGE FUNCTION-POINTER. identifier-1 and identifier-2 need not be described the same. NULL, NULLS As in this syntax diagram, can be used only if the other operand is defined as USAGE FUNCTION-POINTER or USAGE PROCEDURE-POINTER. That is, NULL=NULL is not allowed.
Object-reference data items

A data item of usage OBJECT REFERENCE can be compared for equality or inequality with another data item of usage OBJECT REFERENCE or with NULL, NULLS, or SELF. (A comparison with SELF is allowed only in a method.) Two object-references compare equal only if the data items identify the same object.
Format 4: object-reference
object-reference-identifier-1 SELF NULL NULLS EQUAL TO =
IS
NOT
object-reference-identifier-2 SELF NULL NULLS
Comparison of numeric and alphanumeric operands

Comparing numeric operands
When the algebraic values of numeric operands are compared: v The length (number of digits) of the operands is not significant. v Unsigned numeric operands are considered positive. v Zero is considered to be a unique value regardless of sign.
255
v Comparison of numeric operands is permitted regardless of the type of USAGE specified for each. See Comparison of national operands on page 259 for discussion of comparing numeric operands with national operands. Permissible comparisons with numeric second operands (Table 22) summarizes all other permissible comparisons with numeric operands. The symbols used in Permissible comparisons with numeric second operands (Table 22) and Permissible comparisons with alphanumeric second operands (Table 23 on page 257) are as follows: AN NU Comparison for alphanumeric operands Comparison for numeric operands
Blank Comparison is not allowed.

Table 22. Permissible comparisons with numeric second operands ZR second operand NL second operand AN1 AN AN
1 1
First operand Alphanumeric Group (GR) Alphabetic (AL) Alphanumeric (AN) Alphanumericedited (ANE) Numeric-edited (NE) Figurative constant (FC)2 Alphanumeric literal (ANL) Numeric Figurative constant ZERO (ZR) Numeric literal (NL) External decimal (ED) Binary (BI) Arithmetic expression (AE) Internal decimal (ID) Internal floating-point (IFP)
ED second operand AN1 AN AN

1 1
BI second operand
AE second operand
ID second operand
IFP second operand
EFP second operand
FPL second operand
AN AN AN AN AN
AN AN AN AN AN AN AN
AN1 AN1
AN1 AN1 AN1 AN1
NU NU NU NU NU NU NU NU NU NU NU NU NU NU NU NU NU
NU NU NU NU NU NU NU
NU NU NU NU NU NU NU NU NU NU NU NU
256
Language Reference
Table 22. Permissible comparisons with numeric second operands (continued) ZR second operand NU NL second operand NU ED second operand NU BI second operand NU AE second operand NU ID second operand NU IFP second operand NU EFP second operand NU FPL second operand NU
First operand External floating-point (EFP) Floating-point literal (FPL)
NU
NU
NU
NU
NU
NU
1. Integer items only. 2. Includes all figurative constants except ZERO.
Comparing alphanumeric operands

Comparisons of alphanumeric operands are made with respect to the collating sequence of the character set in use as follows. v For the EBCDIC character set, the EBCDIC collating sequence is used. v For the ASCII character set, the ASCII collating sequence is used. (See Appendix C, EBCDIC and ASCII collating sequences, on page 549.) v When the PROGRAM COLLATING SEQUENCE clause is specified in the object-computer paragraph, the collating sequence associated with the alphabet-name clause in the special-names paragraph is used. The size of each operand is the total number of characters in that operand; the size affects the result of the comparison. There are two cases to consider: Operands of equal size Characters in corresponding positions of the two operands are compared, beginning with the leftmost character and continuing through the rightmost character. If all pairs of characters through the last pair test as equal, the operands are considered as equal. If a pair of unequal characters is encountered, the characters are tested to determine their relative positions in the collating sequence. The operand that contains the character higher in the sequence is considered the greater operand. Operands of unequal size If the operands are of unequal size, the comparison is made as though the shorter operand were extended to the right with enough spaces to make the operands equal in size. See Comparison of national operands on page 259 for discussion of comparing alphanumeric operands with national operands. Permissible comparisons with alphanumeric second operands (Table 23) summarizes all other permissible comparisons with alphanumeric operands.
Table 23. Permissible comparisons with alphanumeric second operands GR second operand AL second operand AN second operand ANE second operand NE second operand ANL FC second second operand2 operand
First operand Alphanumeric
257
Table 23. Permissible comparisons with alphanumeric second operands (continued) GR second operand AN AN AN AN AN
2
First operand Group (GR) Alphabetic (AL) Alphanumeric (AN) Alphanumeric-edited (ANE) Numeric-edited (NE) Figurative constant (FC)
AL second operand AN AN AN AN AN AN AN
AN second operand AN AN AN AN AN AN AN
ANE second operand AN AN AN AN AN AN AN
NE second operand AN AN AN AN AN AN AN
ANL FC second second operand2 operand AN AN AN AN AN AN AN AN AN AN
AN AN
Alphanumeric literal (ANL) Numeric
Figurative constant ZERO (ZR) AN Numeric literal (NL) External decimal (ED) Binary (BI) Arithmetic expression (AE) Internal decimal (ID) Internal floating-point (IFP) External floating-point (EFP) Floating-point literal (FPL) 1. Integer items only. AN AN
1
AN AN
1
AN AN
1
AN AN
1
AN AN1 AN1 AN1 AN1
AN1
AN1
AN1
AN1
AN
AN
AN
AN
AN
AN
2. Includes all figurative constants except ZERO.
Comparing numeric and alphanumeric operands

The alphanumeric comparison rules, discussed above, apply. In addition, when numeric and alphanumeric operands are being compared, their USAGE must be the same. In such comparisons: v The numeric operand must be described as an integer literal or data item. v Noninteger literals and data items must not be compared with alphanumeric operands. v External floating-point items can be compared with alphanumeric operands. If either of the operands is a group item, the alphanumeric comparison rules discussed above apply. In addition to those rules: v If the alphanumeric operand is a literal or an elementary data item, the numeric operand is treated as though it were moved to an alphanumeric elementary data item of the same size, and the contents of this alphanumeric data item were then compared with the alphanumeric operand. v If the alphanumeric operand is a group item, the numeric operand is treated as though it were moved to a group item of the same size, and the contents of this group item were compared then with the alphanumeric operand. See MOVE statement on page 359.
Comparing index-names and index data items

Comparisons involving index-names, index data items, or both conform to the following rules:
258
Language Reference
v The comparison of two index-names is actually the comparison of the corresponding occurrence numbers. v In the comparison of an index-name with a data item (other than an index data item), or in the comparison of an index-name with a literal, the occurrence number that corresponds to the value of the index-name is compared with the data item or literal. v In the comparison of an index-name with an arithmetic expression, the occurrence number that corresponds to the value of the index-name is compared with the arithmetic expression. Because an integer function can be used wherever an arithmetic expression can be used, you can compare an index-name to an integer or numeric function. v In the comparison of an index data item with an index-name or another index data item, the actual values are compared without conversion. Results of any other comparison involving an index data item are undefined. Valid comparisons for index-names and index data items are shown in the following table.
Table 24. Comparisons for index-names and index data items Operands compared Index-name Index data item Compare without conversion Data-name Literal (numeric (numeric integer only) integer only) Compare occurrence number with data-name Invalid Compare occurrence number with literal Invalid Arithmetic Expression Compare occurrence number with arithmetic expression Invalid
Index-name Compare occurrence number
Index data item
Compare without conversion
Compare without conversion
Comparison of DBCS operands

The rules for comparing DBCS operands are the same as those for the comparison of alphanumeric operands. The comparison is based on the binary collating sequence of the hexadecimal values of the DBCS characters. The PROGRAM COLLATING SEQUENCE clause is not applied to comparisons of DBCS operands.
Comparison of national operands

An operand of class national can be compared with the following: v A national operand v A numeric integer data item with usage display v A numeric integer literal v The figurative constants ZERO, SPACE, QUOTE, and ALL literal v An alphabetic operand v An alphanumeric operand v An alphanumeric-edited operand v A numeric-edited operand
259
v A DBCS operand v A group item Operands can be data items, literals, or functions. Except for a group item, an operand that is not class national is converted to a national data item before comparison. In the comparing of a national operand to a group item, the national operand is treated as though it were moved to a group item of the same size as the national operand. The comparison proceeds according to the rules for alphanumeric comparison rules for two group items. The following describes the conversion of operands to class national. DBCS A DBCS operand is treated as though it were moved to a temporary national data item of the same length as the operand. DBCS characters are converted to the corresponding national characters. The source code page used for the conversion is the one in effect for the CODEPAGE compiler option when the source code was compiled. Alphanumeric An alphanumeric operand is treated as though it were moved to a temporary national data item of the size needed to represent the characters of the operand. Alphanumeric characters are converted to the corresponding national characters. The source code page used for the conversion is the one in effect for the CODEPAGE compiler option when the source code was compiled. Alphabetic, alphanumeric-edited, numeric-edited The operand is converted as though it were an alphanumeric item. Numeric A numeric operand is treated as though it were moved to an elementary alphanumeric item of the size of the numeric operand, and then converted as an alphanumeric operand. These implicit moves are carried out in accordance with the rules of the MOVE statement. The resulting national data item is used in the comparison operation as described for two national operands.
Comparing two national operands

If the operands are of unequal length, the comparison proceeds as though the shorter operand were padded on the right with the default national space character (NX0020) to make the operands of equal length. The comparison then proceeds according to the rules for the comparison of operands of equal length. If the operands are of equal length, the comparison proceeds by comparing corresponding national character positions in the two operands, starting from the leftmost position, until either unequal national characters are encountered or the rightmost national character position is reached, whichever comes first. The operands are determined to be equal if all corresponding national characters are equal.
260
Language Reference
The first-encountered unequal national character in the operands is compared to determine the relation of the operands. The operand that contains the national character with the higher collating value is the greater operand. The higher collating value is determined using the hexadecimal value of characters. The PROGRAM COLLATING SEQUENCE clause has no effect on comparisons of national operands.
Sign condition
The sign condition determines whether the algebraic value of a numeric operand is greater than, less than, or equal to zero.
Format
operand-1 IS NOT POSITIVE NEGATIVE ZERO
operand-1 Must be defined as a numeric identifier, or as an arithmetic expression that contains at least one reference to a variable. operand-1 can be defined as a floating-point identifier. The operand is: v POSITIVE if its value is greater than zero v NEGATIVE if its value is less than zero v ZERO if its value is equal to zero An unsigned operand is either POSITIVE or ZERO. NOT One algebraic test is executed for the truth value of the sign condition. For example, NOT ZERO is regarded as true when the operand tested is positive or negative in value. If you are using the NUMPROC compiler option, the results of the sign condition test can be affected. For details, see the Enterprise COBOL Programming Guide.
Date fields in sign conditions

The operand in a sign condition can be a date field, but is treated as a nondate for the sign condition test. Thus if the operand is an identifier of a windowed date field, date windowing is not done, so the sign condition can be used to test a windowed date field for an all-zero value. However, if the operand is an arithmetic expression, then any windowed date fields in the expression will be expanded during the computation of the arithmetic result prior to using the result for the sign condition test. For example, given that: v Identifier WIN-DATE is defined as a windowed date field and contains a value of zero v Compiler option DATEPROC is in effect
261
v Compiler option YEARWINDOW (starting-year) is in effect, with a starting-year other than 1900 then this sign condition would evaluate to true:
WIN-DATE IS ZERO
whereas this sign condition would evaluate to false:

WIN-DATE + 0 IS ZERO
Switch-status condition
The switch-status condition determines the on or off status of an UPSI switch.
Format
condition-name
condition-name Must be defined in the special-names paragraph as associated with the on or off value of an UPSI switch. (See SPECIAL-NAMES paragraph on page 106.) The switch-status condition tests the value associated with condition-name. (The value is considered to be alphanumeric.) The result of the test is true if the UPSI switch is set to the value (0 or 1) corresponding to condition-name.
Complex conditions
A complex condition is formed by combining simple conditions, combined conditions, or complex conditions with logical operators, or negating those conditions with logical negation. Each logical operator must be preceded and followed by a space. The following table shows the logical operators and their meanings.
Table 25. Logical operators and their meanings Logical operator AND OR NOT Name Logical conjunction Meaning The truth value is true when both conditions are true.
Logical The truth value is true when either or both conditions are inclusive OR true. Logical negation Reversal of truth value (the truth value is true if the condition is false).
Unless modified by parentheses, the following is the order of precedence (from highest to lowest): 1. Arithmetic operations 2. Simple conditions 3. NOT 4. AND
262
Language Reference
5. OR The truth value of a complex condition (whether parenthesized or not) is the truth value that results from the interaction of all the stated logical operators on either of the following: v The individual truth values of simple conditions v The intermediate truth values of conditions logically combined or logically negated A complex condition can be either of the following: v A negated simple condition v A combined condition (which can be negated)
Negated simple conditions

A simple condition is negated through the use of the logical operator NOT.
Format
NOT condition-1
The negated simple condition gives the opposite truth value of the simple condition. That is, if the truth value of the simple condition is true, then the truth value of that same negated simple condition is false, and vice versa. Placing a negated simple condition within parentheses does not change its truth value. That is, the following two statements are equivalent:
NOT A IS EQUAL TO B. NOT (A IS EQUAL TO B).
Combined conditions
Two or more conditions can be logically connected to form a combined condition.
Format
condition-1
AND OR
condition-2
The condition to be combined can be any of the following: v A simple-condition v A negated simple-condition v A combined condition v A negated combined condition (that is, the NOT logical operator followed by a combined condition enclosed in parentheses) v A combination of the preceding conditions that is specified according to the rules in the following table
263
Table 26. Combined conditionspermissible element sequences Combined condition element simplecondition Left most Yes When not leftmost, can be immediately preceded by: OR NOT AND ( simple-condition ) OR AND ( OR NOT AND ( simple-condition ) Right most Yes When not rightmost, can be immediately followed by: OR AND ) simple-condition NOT ( simple-condition ( simple-condition NOT ( OR AND )
OR AND NOT
No
No
Yes
No
Yes
No
No
Yes
Parentheses are never needed when either ANDs or ORs (but not both) are used exclusively in one combined condition. However, parentheses might be needed to modify the implicit precedence rules to maintain the correct logical relation of operators and operands. There must be a one-to-one correspondence between left and right parentheses, with each left parenthesis to the left of its corresponding right parenthesis. The following table illustrates the relationships between logical operators and conditions C1 and C2.
Table 27. Logical operators and evaluation results of combined conditions C1 AND C2 True False False False NOT (C1 AND C2) False True True True NOT C1 AND C2 False True False False NOT (C1 OR C2) False False False True
Value for C1 True False True False
Value for C2 True True False False
C1 OR C2 True True True False
NOT C1 OR C2 True True False True
Order of evaluation of conditions

Parentheses, both explicit and implicit, define the level of inclusiveness within a complex condition. Two or more conditions connected by only the logical operators AND or OR at the same level of inclusiveness establish a hierarchical level within a complex condition. Therefore an entire complex condition is a nested structure of hierarchical levels, with the entire complex condition being the most inclusive hierarchical level.
264
Language Reference
Within this context, the evaluation of the conditions within an entire complex condition begins at the left of the condition. The constituent connected conditions within a hierarchical level are evaluated in order from left to right, and evaluation of that hierarchical level terminates as soon as a truth value for it is determined, regardless of whether all the constituent connected conditions within that hierarchical level have been evaluated. Values are established for arithmetic expressions and functions if and when the conditions that contain them are evaluated. Similarly, negated conditions are evaluated if and when it is necessary to evaluate the complex condition that they represent. For example:
NOT A IS GREATER THAN B OR A + B IS EQUAL TO C AND D IS POSITIVE
is evaluated as if parenthesized as follows:

(NOT (A IS GREATER THAN B)) OR (((A + B) IS EQUAL TO C) AND (D IS POSITIVE))
Order of evaluation:
1. (NOT (A IS GREATER THAN B)) is evaluated, giving some intermediate truth value, t1. If t1 is true, the combined condition is true, and no further evaluation takes place. If t1 is false, evaluation continues as follows. 2. (A + B) is evaluated, giving some intermediate result, x. 3. (x IS EQUAL TO C) is evaluated, giving some intermediate truth value, t2. If t2 is false, the combined condition is false, and no further evaluation takes place. If t2 is true, the evaluation continues as follows. 4. (D IS POSITIVE) is evaluated, giving some intermediate truth value, t3. If t3 is false, the combined condition is false. If t3 is true, the combined condition is true.
Abbreviated combined relation conditions

When relation-conditions are written consecutively, any relation-condition after the first can be abbreviated in one of two ways: v Omission of the subject v Omission of the subject and relational operator
Format
relation-condition
AND OR
object NOT relational-operator
In any consecutive sequence of relation-conditions, both forms of abbreviation can be specified. The abbreviated condition is evaluated as if: 1. The last stated subject is the missing subject. 2. The last stated relational operator is the missing relational operator.
265
The resulting combined condition must comply with the rules for element sequence in combined conditions, as shown in Combined conditions: permissible element sequences (Table 26 on page 264). If NOT is immediately followed by GREATER THAN, >, LESS THAN, <, EQUAL TO, or =, then the NOT participates as part of the relational operator. NOT in any other position is considered a logical operator (and thus results in a negated relation condition).
Using parentheses
You can use parentheses in combined relation conditions to specify an intended order of evaluation. Using parentheses can also help improve the readability of conditional expressions. The following rules govern the use of parentheses in abbreviated combined relation conditions: 1. Parentheses can be used to change the order of evaluation of the logical operators AND and OR. 2. The word NOT participates as part of the relational operator when it is immediately followed by GREATER THAN, >, LESS THAN, <, EQUAL TO, or =. 3. NOT in any other position is considered a logical operator and thus results in a negated relation condition. If you use NOT as a logical operator, only the relation condition immediately following the NOT is negated; the negation is not propagated through the abbreviated combined relation condition along with the subject and relational operator. 4. The logical NOT operator can appear within a parenthetical expression that immediately follows a relational operator. 5. When a left parenthesis appears immediately after the relational operator, the relational operator is distributed to all objects enclosed in the parentheses. In the case of a distributed relational operator, the subject and relational operator remain current after the right parenthesis which ends the distribution. The following three restrictions apply to cases where the relational operator is distributed throughout the expression: a. A simple condition cannot appear within the scope of the distribution. b. Another relational operator cannot appear within the scope of the distribution. c. The logical operator NOT cannot appear immediately after the left parenthesis, which defines the scope of the distribution. 6. Evaluation proceeds from the least to the most inclusive condition. 7. There must be a one-to-one correspondence between left and right parentheses, with each left parenthesis to the left of its corresponding right parenthesis. If the parentheses are unbalanced, the compiler inserts a parenthesis and issues an E-level message. However, if the compiler-inserted parenthesis results in the truncation of the expression, you will receive an S-level diagnostic message. 8. The last stated subject is inserted in place of the missing subject. 9. The last stated relational operator is inserted in place of the missing relational operator. 10. Insertion of the omitted subject or relational operator ends when: a. Another simple condition is encountered. b. A condition-name is encountered.
266
Language Reference
c. A right parenthesis is encountered that matches a left parenthesis that appears to the left of the subject. 11. In any consecutive sequence of relation conditions, you can use both abbreviated relation conditions that contain parentheses and those that dont. 12. Consecutive logical NOT operators cancel each other and result in an S-level message. Note, however, that an abbreviated combined relation condition can contain two consecutive NOT operators when the second NOT is part of a relational operator. For example, you can abbreviate the first condition as the second condition listed below.
A = B and not A not = C A = B and not not = C
The following table summarizes the rules for forming an abbreviated combined relation condition.
Table 28. Abbreviated combined conditions: permissible element sequences Combined condition element Subject Object When not leftmost, can be immediately preceded by: NOT ( Relational operator AND OR NOT ( Subject AND OR NOT Object ) When not rightmost, can be immediately followed by: Relational operator AND OR )
Left- most Yes No
Right- most No Yes
Relational operator
No
No
Object (
AND OR
No
No
Object Relational operator NOT ( Subject Object Relational operator ( Subject Object NOT ( AND OR )
NOT
Yes
AND OR ( Relational operator AND OR NOT ( Object )
No
Yes
No
No
Yes
The following examples illustrate abbreviated combined relation conditions, with and without parentheses, and their unabbreviated equivalents.
Table 29. Abbreviated combined conditions: unabbreviated equivalents Abbreviated combined relation condition A = B AND NOT < C OR D Equivalent ((A = B) AND (A NOT < C)) OR (A NOT < D)
267
Table 29. Abbreviated combined conditions: unabbreviated equivalents (continued) Abbreviated combined relation condition A NOT > B OR C NOT A = B OR C NOT (A = B OR < C) NOT (A NOT = B AND C AND NOT D) Equivalent (A NOT > B) OR (A NOT > C) (NOT (A = B)) OR (A = C) NOT ((A = B) OR (A < C)) NOT ((((A NOT = B) AND (A NOT = C)) AND (NOT (A NOT = D))))
Statement categories
There are four categories of COBOL statements: v Imperative statements v Conditional statements on page 270 v Delimited scope statements on page 271 v Compiler-directing statements on page 272
Imperative statements
An imperative statement either specifies an unconditional action to be taken by the program or is a conditional statement terminated by its explicit scope terminator (see Delimited scope statements on page 271). A series of imperative statements can be specified wherever an imperative statement is allowed. A conditional statement that is terminated by its explicit scope terminator is also classified as an imperative statement (see Delimited scope statements on page 271). The following lists contain the COBOL imperative statements.
Arithmetic
v v v v v ADD1 COMPUTE1 DIVIDE1 MULTIPLY1 SUBTRACT1
1. Without the ON SIZE ERROR or the NOT ON SIZE ERROR phrase.
Data movement
v v v v v v v v v ACCEPT (DATE, DAY, DAY-OF-WEEK, TIME) INITIALIZE INSPECT MOVE SET STRING2 UNSTRING2 XML GENERATE8 XML PARSE8
2. Without the ON OVERFLOW or the NOT ON OVERFLOW phrase. 8. Without the ON EXCEPTION or NOT ON EXCEPTION phrase.
268
Language Reference
Ending
v v v v STOP RUN EXIT PROGRAM EXIT METHOD GOBACK
Input-output
v v v v v v v v v v ACCEPT identifier CLOSE DELETE3 DISPLAY OPEN READ4 REWRITE3 START3 STOP literal WRITE5
3. Without the INVALID KEY or the NOT INVALID KEY phrase. 4. Without the AT END or NOT AT END, and INVALID KEY or NOT INVALID KEY phrases. 5. Without the INVALID KEY or NOT INVALID KEY, and END-OF-PAGE or NOT END-OF-PAGE phrases.
Ordering
v MERGE v RELEASE v RETURN6 v SORT 6. Without the AT END or NOT AT END phrase.
Procedure-branching
v v v v ALTER EXIT GO TO PERFORM
Program or method linkage

v CALL7 v CANCEL v INVOKE 7. Without the ON OVERFLOW phrase, and without the ON EXCEPTION or NOT ON EXCEPTION phrase.
Table-handling
v SET
269
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. (See Conditional expressions on page 246.) The following lists contain COBOL statements that become conditional when a condition (for example, ON SIZE ERROR or ON OVERFLOW) is included and when the statement is not terminated by its explicit scope terminator.
Arithmetic
v v v v v v v v v v ADD ... ON SIZE ERROR ADD ... NOT ON SIZE ERROR COMPUTE ... ON SIZE ERROR COMPUTE ... NOT ON SIZE ERROR DIVIDE ... ON SIZE ERROR DIVIDE ... NOT ON SIZE ERROR MULTIPLY ... ON SIZE ERROR MULTIPLY ... NOT ON SIZE ERROR SUBTRACT ... ON SIZE ERROR SUBTRACT ... NOT ON SIZE ERROR
Data movement
v v v v v v v v STRING ... ON OVERFLOW STRING ... NOT ON OVERFLOW UNSTRING ... ON OVERFLOW UNSTRING ... NOT ON OVERFLOW XML GENERATE ... ON EXCEPTION XML GENERATE ... NOT ON EXCEPTION XML PARSE ... ON EXCEPTION XML PARSE ... NOT ON EXCEPTION
| |
Decision
v IF v EVALUATE
Input-output
v v v v v v v v v v v v v DELETE ... INVALID KEY DELETE ... NOT INVALID KEY READ ... AT END READ ... NOT AT END READ ... INVALID KEY READ ... NOT INVALID KEY REWRITE ... INVALID KEY REWRITE ... NOT INVALID KEY START ... INVALID KEY START ... NOT INVALID KEY WRITE ... AT END-OF-PAGE WRITE ... NOT AT END-OF-PAGE WRITE ... INVALID KEY
270
Language Reference
v WRITE ... NOT INVALID KEY
Ordering
v RETURN ... AT END v RETURN ... NOT AT END
Program or method linkage

v v v v v CALL ... ON OVERFLOW CALL ... ON EXCEPTION CALL ... NOT ON EXCEPTION INVOKE ... ON EXCEPTION INVOKE ... NOT ON EXCEPTION
Table-handling
v SEARCH
Delimited scope statements

In general, a DELIMITED SCOPE statement uses an explicit scope terminator to turn a conditional statement into an imperative statement. The resulting imperative statement can then be nested. Explicit scope terminators can also be used to terminate the scope of an imperative statement. Explicit scope terminators are provided for all COBOL statements that can have conditional phrases. Unless explicitly specified otherwise, a delimited scope statement can be specified wherever an imperative statement is allowed by the rules of the language.
Explicit scope terminators

An explicit scope terminator marks the end of certain procedure division statements. A conditional statement that is delimited by its explicit scope terminator is considered an imperative statement and must follow the rules for imperative statements. These are the explicit scope terminators: v END-ADD v END-CALL v END-COMPUTE v END-DELETE v END-DIVIDE v END-EVALUATE v END-IF v END-INVOKE v END-MULTIPLY v END-PERFORM v END-READ v END-RETURN v END-REWRITE v END-SEARCH v END-START v END-STRING
271
v v v v
END-SUBTRACT END-UNSTRING END-WRITE END-XML
Implicit scope terminators

At the end of any sentence, an implicit scope terminator is a separator period that terminates the scope of all previous statements not yet terminated. An unterminated conditional statement cannot be contained by another statement. Except for nesting conditional statements within IF statements, nested statements must be imperative statements and must follow the rules for imperative statements. You should not nest conditional statements.
Compiler-directing statements
Statements that direct the compiler to take a specified action are discussed in Chapter 23, Compiler-directing statements, on page 505.
Statement operations
COBOL statements perform the following types of operations: v Arithmetic v Data manipulation v Input/output v Procedure branching There are several phrases common to arithmetic and data manipulation statements, such as: v CORRESPONDING phrase v GIVING phrase v ROUNDED phrase v SIZE ERROR phrases
CORRESPONDING phrase
The CORRESPONDING (CORR) 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 that follow the keyword CORRESPONDING must name group items. In this discussion, these identifiers are referred to as identifier-1 and identifier-2. Two data items (subordinate items), one from identifier-1 and one from identifier-2, correspond if the following conditions are true: v In an ADD or SUBTRACT statement, both of the data items are elementary numeric data items. Other data items are ignored. v In a MOVE statement, at least one of the data items is an elementary item, and the move is permitted by the move rules. v The two subordinate items have the same name and the same qualifiers up to but not including identifier-1 and identifier-2.
272
Language Reference
v The subordinate items are not identified by the keyword FILLER. v Neither identifier-1 nor identifier-2 is described as a level 66, 77, or 88 item, and neither is described as an index data item. Neither identifier-1 nor identifier-2 can be reference-modified. v The subordinate items do not include a REDEFINES, RENAMES, OCCURS, USAGE INDEX, USAGE POINTER, USAGE PROCEDURE-POINTER, USAGE FUNCTION-POINTER, or USAGE OBJECT REFERENCE clause in their descriptions. However, identifier-1 and identifier-2 themselves can contain or be subordinate to items that contain a REDEFINES or OCCURS clause in their descriptions. v Neither identifier-1 nor identifier-2 is described with USAGE POINTER, USAGE FUNCTION-POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE. v The name of each subordinate data item that satisfies these conditions is unique after application of implicit qualifiers. identifier-1, identifier-2, or both can be subordinate to a FILLER item. For example, consider two data hierarchies defined as follows:
05 ITEM-1 OCCURS 6. 10 ITEM-A PIC S9(3). 10 ITEM-B PIC +99.9. 10 ITEM-C PIC X(4). 10 ITEM-D REDEFINES ITEM-C PIC 9(4). 10 ITEM-E USAGE COMP-1. 10 ITEM-F USAGE INDEX. 05 ITEM-2. 10 ITEM-A PIC 99. 10 ITEM-B PIC +9V9. 10 ITEM-C PIC A(4). 10 ITEM-D PIC 9(4). 10 ITEM-E PIC 9(9) USAGE COMP. 10 ITEM-F USAGE INDEX.
| |
If ADD CORR ITEM-2 TO ITEM-1(x) is specified, ITEM-A and ITEM-A(x), ITEM-B and ITEM-B(x), and ITEM-E and ITEM-E(x) are considered to be corresponding and are added together. ITEM-C and ITEM-C(x) are not included because they are not numeric. ITEM-D and ITEM-D(x) are not included because ITEM-D(x) includes a REDEFINES clause in its data description. ITEM-F and ITEM-F(x) are not included because they are index data items. Note that ITEM-1 is valid as either identifier-1 or identifier-2. If any of the individual operations in the ADD CORRESPONDING statement produces a size error condition, imperative-statement-1 in the ON SIZE ERROR phrase is not executed until all of the individual additions are completed.
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 can be a numeric-edited item.
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.
273
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 whenever the most significant digit of the excess is greater than or equal to 5. When the resultant identifier is described by a PICTURE clause that contains rightmost Ps and when the number of places in the calculated result exceeds the number of integer positions specified, rounding or truncation occurs relative to the rightmost integer position for which storage is allocated. In a floating-point arithmetic operation, the ROUNDED phrase has no effect; the result of a floating-point operation is always rounded. For more information on floating-point arithmetic expressions, see the Enterprise COBOL Programming Guide. When the ARITH(EXTEND) compiler option is in effect, the ROUNDED phrase is not supported for arithmetic receivers with 31 digit positions to the right of the decimal point. For example, neither X nor Y below is valid as a receiver with the ROUNDED phrase:
01 01 X PIC V31. Y PIC P(30)9(1). . . . COMPUTE X ROUNDED = A + B COMPUTE Y ROUNDED = A - B
Otherwise, the ROUNDED phrase is fully supported for extended-precision arithmetic statements.
SIZE ERROR phrases

A size error condition can occur in four different ways: v 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. v When division by zero occurs. v When the result of an arithmetic statement is stored in a windowed date field and the year of the result falls outside the century window. For example, given YEARWINDOW(1940) (which specifies a century window of 1940-2039), the following SUBTRACT statement causes a size error:
01 WINDOWED-YEAR DATE FORMAT YY PICTURE 99 VALUE IS 50.
... SUBTRACT 20 FROM WINDOWED-YEAR ON SIZE ERROR imperative-statement
The size error occurs because the result of the subtraction, a windowed date field, has an effective year value of 1930, which falls outside the century window. For details on how windowed date fields are treated as if they were converted to expanded date format, see Subtraction that involves date fields on page 244. For more information about how size errors can occur when using date fields, see Storing arithmetic results that involve date fields on page 245. v In an exponential expression, as indicated in the following table:
274
Language Reference
Table 30. Exponentiation size error conditions Action taken when a SIZE ERROR clause is present Action taken when a SIZE ERROR clause is not present
Size error Zero raised to zero power Zero raised to a negative number A negative number raised to a fractional power
The SIZE ERROR imperative The value returned is 1, and is executed. a message is issued. The SIZE ERROR imperative The program is terminated is executed. abnormally. The SIZE ERROR imperative The absolute value of the is executed. base is used, and a message is issued.
The size error condition applies only to final results, not to any intermediate results. If the resultant identifier is defined with USAGE IS BINARY, COMPUTATIONAL, COMPUTATIONAL-4, or COMPUTATIONAL-5, the largest value that can be contained in it is the maximum value implied by its associated decimal PICTURE character-string, regardless of the TRUNC compiler option in effect. If the ROUNDED phrase is specified, rounding takes place before size error checking. When a size error occurs, the subsequent action of the program depends on whether the ON SIZE ERROR phrase is specified. If the ON SIZE ERROR phrase is not specified and a size error condition occurs, truncation rules apply and the value of the affected resultant identifier is computed. If the ON SIZE ERROR phrase is specified and a size error condition occurs, the value of the resultant identifier affected by the size error is not altered; that is, the error results are not placed in the receiving identifier. After completion of the execution of the arithmetic operation, the imperative statement in the ON SIZE ERROR phrase is executed, control is transferred to the end of the arithmetic statement, and the NOT ON SIZE ERROR phrase, if specified, is ignored. For ADD CORRESPONDING and SUBTRACT CORRESPONDING statements, if an individual arithmetic operation causes a size error condition, the ON SIZE ERROR imperative statement is not executed until all the individual additions or subtractions have been completed. If the NOT ON SIZE ERROR phrase has been specified and, after execution of an arithmetic operation, a size error condition does not exist, the NOT ON SIZE ERROR phrase is executed. When both the ON SIZE ERROR and NOT ON SIZE ERROR phrases are specified, and the statement in the phrase that is executed does not contain any explicit transfer of control, then if necessary an implicit transfer of control is made after execution of the phrase to the end of the arithmetic statement.
275
Arithmetic statements
The arithmetic statements are used for computations. Individual operations are specified by the ADD, SUBTRACT, MULTIPLY, and DIVIDE statements. These individual operations can be combined symbolically in a formula that uses the COMPUTE statement.
Arithmetic statement operands

The data descriptions of operands in an arithmetic statement need not be the same. Throughout the calculation, the compiler performs any necessary data conversion and decimal point alignment.
Size of operands
If the ARITH(COMPAT) compiler option is in effect, the maximum size of each operand is 18 decimal digits. If the ARITH(EXTEND) compiler option is in effect, the maximum size of each operand is 31 decimal digits. The composite of operands is a hypothetical data item resulting from aligning the operands at the decimal point and then superimposing them on one another. If the ARITH(COMPAT) compiler option is in effect, the composite of operands can be a maximum of 30 digits. If the ARITH(EXTEND) compiler option is in effect, the composite of operands can be a maximum of 31 digits. The following table shows how the composite of operands is determined for arithmetic statements:
Table 31. How the composite of operands is determined Statement SUBTRACT ADD MULTIPLY DIVIDE COMPUTE Determination of the composite of operands Superimposing all operands in a given statement except those following the word GIVING Superimposing all receiving data items Superimposing all receiving data items except the REMAINDER data item Restriction does not apply
For example, assume that each item is defined as follows in the data division:
A B C PICTURE 9(7)V9(5). PICTURE 9(11)V99. PICTURE 9(12)V9(3).
If the following statement is executed, the composite of operands consists of 17 decimal digits:
ADD A B TO C
It has the following implicit description:

COMPOSITE-OF-OPERANDS PICTURE 9(12)V9(5).
In the ADD and SUBTRACT statements, if the composite of operands is 30 digits or less with the ARITH(COMPAT) compiler option, or 31 digits or less with the ARITH(EXTEND) compiler option, the compiler ensures that enough places are carried so that no significant digits are lost during execution.
276
Language Reference
In all arithmetic statements, it is important to define data with enough digits and decimal places to ensure the desired accuracy in the final result. For more information, see the section on intermediate results in the Enterprise COBOL Programming Guide.
Overlapping operands
When operands in an arithmetic statement share part of their storage (that is, when the operands overlap), the result of the execution of such a statement is unpredictable.
Multiple results
When an arithmetic statement has multiple results, execution conceptually proceeds as follows: 1. The statement performs all arithmetic operations to find the result to be placed in the receiving items, and stores that result in a temporary location. 2. A sequence of statements transfers or combines the value of this temporary result with each single receiving field. The statements are considered to be written in the same left-to-right order in which the multiple results are listed. For example, executing the following statement:
ADD A, B, C, TO C, D(C), E.
is equivalent to executing the following series of statements:

ADD ADD ADD ADD A, B, C TEMP TO TEMP TO TEMP TO GIVING TEMP. C. D(C). E.
In the above example, TEMP is a compiler-supplied temporary result field. When the addition operation for D(C) is performed, the subscript C contains the new value of C.
Data manipulation statements

| The following COBOL statements move and inspect data: ACCEPT, INITIALIZE, INSPECT, MOVE, READ, RELEASE, RETURN, REWRITE, SET, STRING, UNSTRING, WRITE, XML PARSE, and XML GENERATE.
Overlapping operands
When the sending and receiving fields of a data manipulation statement share a part of their storage (that is, when the operands overlap), the result of the execution of such a statement is unpredictable.
Input-output statements
COBOL input-output statements transfer data to and from files stored on external media, and also control low-volume data that is obtained from or sent to an input/output device. In COBOL, the unit of file data made available to the program is a record. You need only be concerned with such records. Provision is automatically made for such operations as the movement of data into buffers, internal storage, validity checking, error correction (where feasible), blocking and deblocking, and volume-switching procedures. The description of the file in the environment division and data division governs which input-output statements are allowed in the procedure division. Permissible
277
statements for each type of file organization are shown in Permissible statements for sequential files (Table 45 on page 371) and Permissible statements for indexed and relative files (Table 46 on page 371).
Common processing facilities

There are several common processing facilities that apply to more than one input-output statement. The common processing facilities provided are: v File status key v Invalid key condition on page 282 v INTO and FROM phrases on page 283 v File position indicator on page 284 Discussions in the following sections use the terms volume and reel. The term volume refers to all non-unit-record input-output devices. The term reel applies only to tape devices. Treatment of direct-access devices in the sequential access mode is logically equivalent to the treatment of tape devices.
File status key

If the FILE STATUS clause is specified in the file-control entry, a value is placed in the specified file status key (the two-character data item named in the FILE STATUS clause) during execution of any request on that file; the value indicates the status of that request. The value is placed in the file status key before execution of any EXCEPTION/ERROR declarative or INVALID KEY/AT END phrase associated with the request. There are two file status key data-names. One is described by data-name-1 in the FILE STATUS clause of the file-control entry. This is a two-character data item with the first character known as file status key 1 and the second character known as file status key 2. The combinations of possible values and their meanings are shown in File status key values and meanings (Table 32 on page 279). The other file status key is described by data-name-8 in the FILE STATUS clause of the file-control entry. data-name-8 does not apply to QSAM files. For more information about data-name-8, see FILE STATUS clause on page 135.
278
Language Reference
Table 32. File status key values and meanings Highorder digit 0 Loworder digit 0 2
Meaning Successful completion
Meaning No further information This file status value applies only to indexed files with alternate keys that allow duplicates. The input-output statement was successfully executed, but a duplicate key was detected. For a READ statement, the key value for the current key of reference was equal to the value of the same key in the next record within the current key of reference. For a REWRITE or WRITE statement, the record just written created a duplicate key value for at least one alternate record key for which duplicates are allowed.
A READ statement was successfully executed, but the length of the record being processed did not conform to the fixed file attributes for that file. An OPEN statement is successfully executed but the referenced optional file is not present at the time the OPEN statement is executed. The file has been created if the open mode is I-O or EXTEND. This does not apply to VSAM sequential files. For a CLOSE statement with the NO REWIND, REEL/UNIT, or FOR REMOVAL phrase or for an OPEN statement with the NO REWIND phrase, the referenced file was on a non-reel/unit medium. A sequential READ statement was attempted and no next logical record existed in the file because the end of the file had been reached. Or the first READ was attempted on an optional input file that was not present. A sequential READ statement was attempted for a relative file, and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file.
At-end condition
279
Table 32. File status key values and meanings (continued) Highorder digit 2 Loworder digit 1
Meaning Invalid key condition
Meaning A sequence error exists for a sequentially accessed indexed file. The prime record key value was changed by the program between the successful execution of a READ statement and the execution of the next REWRITE statement for that file. Or the ascending requirements for successive record key values were violated. An attempt was made to write a record that would create a duplicate key in a relative file. Or an attempt was made to write or rewrite a record that would create a duplicate prime record key or a duplicate alternate record key without the DUPLICATES phrase in an indexed file. An attempt was made to randomly access a record that does not exist in the file. Or a START or random READ statement was attempted on an optional input file that was not present. An attempt was made to write beyond the externally defined boundaries of a relative or indexed file. Or a sequential WRITE statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file. No further information A permanent error exists because of a boundary violation; an attempt was made to write beyond the externally defined boundaries of a sequential file. An OPEN statement with the INPUT, I-O, or EXTEND phrase was attempted on a nonoptional file that was not present. An OPEN statement was attempted on a file that would not support the open mode specified in the OPEN statement. Possible violations are: v The EXTEND or OUTPUT phrase was specified but the file would not support write operations. v The I-O phrase was specified but the file would not support the input and output operations permitted. v The INPUT phrase was specified but the file would not support read operations.
Permanent error condition
0 4
8 9
An OPEN statement was attempted on a file previously closed with lock. The OPEN statement was unsuccessful because a conflict was detected between the fixed file attributes and the attributes specified for that file in the program. These attributes include the organization of the file (sequential, relative, or indexed), the prime record key, the alternate record keys, the code set, the maximum record size, the record type (fixed or variable), and the blocking factor.
280
Language Reference
Table 32. File status key values and meanings (continued) Highorder digit 4 Loworder digit 1 2 3
Meaning Logic error condition
Meaning An OPEN statement was attempted for a file in the open mode. A CLOSE statement was attempted for a file not in the open mode. For a mass storage file in the sequential access mode, the last input-output statement executed for the associated file prior to the execution of a REWRITE statement was not a successfully executed READ statement. For relative and indexed files in the sequential access mode, the last input-output statement executed for the file prior to the execution of a DELETE or REWRITE statement was not a successfully executed READ statement.
A boundary violation exists because an attempt was made to rewrite a record to a file and the record was not the same size as the record being replaced. Or an attempt was made to write or rewrite a record that was larger than the largest or smaller than the smallest record allowed by the RECORD IS VARYING clause of the associated file-name. A sequential READ statement was attempted on a file open in the input or I-O mode and no valid next record had been established because: v The preceding READ statement was unsuccessful but did not cause an at-end condition. v The preceding READ statement caused an at-end condition.
7 8 9
The execution of a READ statement was attempted on a file not open in the input or I-O mode. The execution of a WRITE statement was attempted on a file not open in the I-O, output, or extend mode. The execution of a DELETE or REWRITE statement was attempted on a file not open in the I-O mode.
281
Table 32. File status key values and meanings (continued) Highorder digit 9 Loworder digit
Meaning
Meaning v For multithreading only: A CLOSE of a VSAM or QSAM file was attempted on a thread that did not open the file. v Without multithreading: For VSAM only: See the information about VSAM return codes in the Enterprise COBOL Programming Guide.
Implementor- 0 defined condition
1 2 3 5 6
For VSAM only: Password failure Logic error For all files, except QSAM: Resource not available For all files except QSAM: Invalid or incomplete file information For VSAM file: An OPEN statement with the OUTPUT phrase was attempted, or an OPEN statement with the I-O or EXTEND phrase was attempted for an optional file but no DD statement was specified for the file. For QSAM file: An OPEN statement with the OUTPUT phrase was attempted, or an OPEN statement with the I-O or EXTEND phrase was attempted for an optional file but no DD statement was specified for the file and the CBLQDA(OFF) run-time option was specified.
7 8
For VSAM only: OPEN statement execution successful: File integrity verified Open failed due to the invalid contents of an environment variable specified in a SELECT ... ASSIGN clause or due to dynamic allocation failure. For more information about the contents of environment variables, see ASSIGN clause on page 122.
Invalid key condition

The invalid key condition can occur during execution of a START, READ, WRITE, REWRITE, or DELETE statement. (For details of the causes for the condition, see information about the appropriate statement in the environment division.) When an invalid key condition occurs, the input-output statement that caused the condition is unsuccessful. When the invalid key condition is recognized, actions are taken in the following order: 1. If the FILE STATUS clause is specified in the file-control entry, a value is placed into the file status key to indicate an invalid key condition. (See File status key values and meanings (Table 32 on page 279).) 2. If the INVALID KEY phrase is specified in the statement that caused the condition, control is transferred to the INVALID KEY imperative statement. Any EXCEPTION/ERROR declarative procedure specified for this file is not executed. Execution then continues according to the rules for each statement specified in the imperative statement. 3. If the INVALID KEY phrase is not specified in the input-output statement for a file and an applicable EXCEPTION/ERROR procedure exists, that procedure is executed. The NOT INVALID KEY phrase, if specified, is ignored.
282
Language Reference
Both the INVALID KEY phrase and the EXCEPTION/ERROR procedure can be omitted. If the invalid key condition does not exist after execution of the input-output operation, the INVALID KEY phrase is ignored, if specified, and the following actions are taken: v If an exception condition that is not an invalid key condition exists, control is transferred according to the rules of the USE statement following the execution of any USE AFTER EXCEPTION procedure. v If no exception condition exists, control is transferred to the end of the input-output statement or the imperative statement specified in the NOT INVALID KEY phrase, if it is specified.
INTO and FROM phrases

The INTO and FROM phrases are valid for READ, RETURN, RELEASE, REWRITE, and WRITE statements. You must specify an identifier that is the name of an entry in the working-storage section or the linkage section, or of a record description for another previously opened file.
Format
READ RETURN RELEASE REWRITE WRITE file-name-1 RECORD record-name-1 FROM identifier-1 INTO identifier-1
v record-name-1 and identifier-1 must not refer to the same storage area. v The INTO phrase can be specified in a READ or RETURN statement. The result of the execution of a READ or RETURN statement with the INTO phrase is equivalent to the application of the following rules in the order specified: The execution of the same READ or RETURN statement without the INTO phrase. The current record is moved from the record area to the area specified by identifier-1 according to the rules for the MOVE statement without the CORRESPONDING phrase. The size of the current record is determined by rules specified in the RECORD clause. If the file description entry contains a RECORD IS VARYING clause, the implied move is a group move. The implied MOVE statement does not occur if the execution of the READ or RETURN statement was unsuccessful. Any subscripting or reference-modification associated with identifier-1 is evaluated after the record has been read or returned and immediately before it is moved to the data item. The record is available in both the record area and the data item referenced by identifier-1. v The FROM phrase can be specified in a RELEASE, REWRITE, or WRITE statement. The result of the execution of a RELEASE, REWRITE, or WRITE statement with the FROM phrase is equivalent to the execution of the following statements in the order specified:
283
1. MOVE identifier-1 TO record-name-1 2. The same RELEASE, REWRITE, or WRITE statement without the FROM phrase After the execution of the RELEASE, REWRITE or WRITE statement is complete, the information in the area referenced by identifier-1 is available even though the information in the area referenced by record-name-1 is not available, except specified by the SAME RECORD AREA clause.
File position indicator

The file position indicator is a conceptual entity used in this document to facilitate exact specification of the next record to be accessed within a given file during certain sequences of input-output operations. The setting of the file position indicator is affected only by the OPEN, CLOSE, READ and START statements. The concept of a file position indicator has no meaning for a file opened in the output or extend mode.
284
Language Reference
Chapter 21. Procedure division statements

Statements, sentences, and paragraphs in the procedure division are executed sequentially except when a procedure branching statement such as EXIT, GO TO, PERFORM, GOBACK, or STOP is used.
285
ACCEPT statement
The ACCEPT statement transfers data into the specified identifier. There is no editing or error checking of the incoming data.
Data transfer
Format 1: data transfer
ACCEPT identifier-1 FROM mnemonic-name-1 environment-name
Format 1 transfers data from an input/output device into identifier-1. When the FROM phrase is omitted, the system input device is assumed. Format 1 is useful for exceptional situations in a program when operator intervention (to supply a given message, code, or exception indicator) is required. The operator must of course be supplied with the appropriate messages with which to reply. identifier-1 Can be a group item or an elementary alphabetic, alphanumeric, alphanumeric-edited, numeric-edited, external decimal, DBCS, national, or external floating-point data item. mnemonic-name-1 Specifies the input device. mnemonic-name-1 must be associated in the SPECIAL-NAMES paragraph with an environment-name. See SPECIAL-NAMES paragraph on page 106. v System input device The length of a data transfer is the same as the length of the record on the input device, with a maximum of 32,760. The system input device is read until identifier-1 is filled or EOF is encountered. If the length of identifier-1 is not an even multiple of the system input device record length, the final record will be truncated as required. If EOF is encountered after data has been moved and before identifier-1 has been filled, identifier-1 is padded with blanks. If EOF is encountered before any data has been moved to identifier-1, padding will not take place and identifier-1 contents will remain unchanged. Each input record is concatenated with the previous input record. If the input record is of a fixed-length format, the entire input record is used. No editing is performed to remove trailing or leading blanks. If the input record is of the variable-length format, the actual record length is used to determine the amount of data received. With variable-format records, the Record Definition Word (RDW) is removed from the beginning of the input record. Only the actual input data is transferred to identifier-1. If identifier-1 is a national data item, data is transferred to identifier-1 without conversion and without checking for validity. The input data is assumed to be in UTF-16 format. v Console
286
Language Reference
1. A system-generated message code is automatically displayed, followed by the literal AWAITING REPLY. The maximum length of an input message is 114 characters. 2. Execution is suspended. 3. After the message code (the same code as in item 1) is entered from the console and recognized by the system, ACCEPT statement execution is resumed. The message is moved to identifier-1 and left-justified regardless of its PICTURE clause. If identifier-1 is a national data item, the message is converted from EBCDIC to national character representation. The conversion uses the EBCDIC code page specified by the CODEPAGE compiler option when the source code was compiled. The ACCEPT statement is terminated after any of the following occurs: If no data is received from the console; for example, if the operator hits the Enter key. The identifier is filled with data. Fewer than 114 characters of data are entered. If 114 bytes of data are entered and the identifier is still not filled with data, more requests for data are issued to the console. If more than 114 characters of data are entered, only the first 114 characters will be recognized by the system. If the identifier is longer than the incoming message, the rightmost characters are padded with spaces. If the incoming message is longer than the identifier, the character positions beyond the length of the identifier are truncated. For information about obtaining ACCEPT input from an HFS file or stdin, see the Enterprise COBOL Programming Guide. environment-name Identifies the source of input data. An environment-name from the names given in Meanings of environment names (Table 5 on page 108) can be specified. If the device is the same as that used for READ statements for a LINE SEQUENTIAL file, results are unpredictable.
System information transfer

System information contained in the specified conceptual data items DATE, DATE YYYYMMDD, DAY, DAY YYYYDDD, DAY-OF-WEEK, or TIME, can be transferred into the identifier. The transfer must follow the rules for the MOVE statement without the CORRESPONDING phrase. See MOVE statement on page 359.
287
Format 2: system information transfer

ACCEPT identifier-2 FROM DATE YYYYMMDD DAY YYYYDDD DAY-OF-WEEK TIME
identifier-2 Can be a group, elementary alphanumeric, alphanumeric-edited, numeric-edited, external decimal, internal decimal, binary, internal floating-point, or external floating-point item. Format 2 accesses the current date in two formats: the day of the week, or the time of day as carried by the system, which can be useful in identifying when a particular run of an object program was executed. You can also use format 2 to supply the date in headings and footings. The current date and time can also be accessed with the intrinsic function CURRENT-DATE, which also supports four-digit year values and provides additional information (see Chapter 22, Intrinsic functions, on page 459).
DATE, DATE YYYYMMDD, DAY, DAY YYYYDDD, DAY-OF-WEEK, and TIME

The conceptual data items DATE, DATE YYYYMMDD, DAY, DAY YYYYDDD, DAY-OF-WEEK, and TIME implicitly have USAGE DISPLAY. Because these are conceptual data items, they cannot be described in the COBOL program. DATE Has the implicit PICTURE 9(6). If the DATEPROC compiler option is in effect, then the returned value has implicit DATE FORMAT YYXXXX, and identifier-2 must be defined with this date format. The sequence of data elements (from left to right) is:
Two digits for the year Two digits for the month Two digits for the day
Thus 27 April 2003 is expressed as 030427. DATE YYYYMMDD Has the implicit PICTURE 9(8). If the DATEPROC compiler option is in effect, then the returned value has implicit DATE FORMAT YYYYXXXX, and identifier-2 must be defined with this date format. The sequence of data elements (from left to right) is:
Four digits for the year Two digits for the month Two digits for the day
Thus 27 April 2003 is expressed as 20030427. DAY Has the implicit PICTURE 9(5). If the DATEPROC compiler option is in
288
Language Reference
effect, then the returned value has implicit DATE FORMAT YYXXX, and identifier-2 must be defined with this date format. The sequence of data elements (from left to right) is:
Two digits for the year Three digits for the day
Thus 27 April 2003 is expressed as 03117. DAY YYYYDDD Has the implicit PICTURE 9(7). If the DATEPROC compiler option is in effect, then the returned value has implicit DATE FORMAT YYYYXXX, and identifier-2 must be defined with this date format. The sequence of data elements (from left to right) is:
Four digits for the year Three digits for the day
Thus 27 April 2003 is expressed as 2003117. DAY-OF-WEEK Has the implicit PICTURE 9(1). The single data element represents the day of the week according to the following values:
1 2 3 4 represents represents represents represents Monday Tuesday Wednesday Thursday 5 represents Friday 6 represents Saturday 7 represents Sunday
Thus Wednesday is expressed as 3. TIME Has the implicit PICTURE 9(8). The sequence of data elements (from left to right) is:
Two Two Two Two digits digits digits digits for for for for hour of day minute of hour second of minute hundredths of second
Thus 2:41 PM is expressed as 14410000.
289
ADD statement
The ADD statement sums two or more numeric operands and stores the result.
Format 1
ADD
identifier-1 literal-1
TO
identifier-2 ROUNDED
SIZE ERROR imperative-statement-1 ON
NOT ON
SIZE ERROR imperative-statement-2
END-ADD
All identifiers or literals that precede the keyword TO are added together, and this sum is added to and stored in identifier-2. This process is repeated for each successive occurrence of identifier-2 in the left-to-right order in which identifier-2 is specified.
Format 2
ADD
TO
GIVING
NOT ON
END-ADD
290
Language Reference
The values of the operands that precede the word GIVING are added together, and the sum is stored as the new value of each data item referenced by identifier-3.
Format 3
ADD CORRESPONDING CORR identifier-1 TO identifier-2 ROUNDED
NOT ON
END-ADD
Elementary data items within identifier-1 are added to and stored in the corresponding elementary items within identifier-2. For all formats: identifier In format 1, must name an elementary numeric item. In format 2, must name an elementary numeric item except when following the word GIVING. Each identifier that follows the word GIVING must name an elementary numeric or numeric-edited item. In format 3, must name a group item. The following restrictions apply to date fields: v In format 1, identifier-2 can specify one or more date fields. identifier-1 must not specify a date field. v In format 2, either identifier-1 or identifier-2 (but not both) can specify at most one date field. If identifier-1 or identifier-2 specifies a date field, then every instance of identifier-3 must specify a date field that is compatible with the date field specified by identifier-1 or identifier-2. That is, they must have the same date format, except for the year part, which can be windowed or expanded. If neither identifier-1 nor identifier-2 specifies a date field, identifier-3 can specify one or more date fields without any restriction on the date formats. v In format 3, only corresponding elementary items within identifier-2 can be date fields. There is no restriction on the format of these date fields. v A year-last date field is allowed in an ADD statement only as identifier-1 and when the result of the addition is a nondate. There are two steps to determining the result of an ADD statement that involves one or more date fields: 1. Addition: determine the result of the addition operation, as described under Addition that involves date fields on page 244. 2. Storage: determine how the result is stored in the receiving field. (In formats 1 and 3, the receiving field is identifier-2; in Format 3, the
291
receiving field is the GIVING identifier-3.) For details, see Storing arithmetic results that involve date fields on page 245. literal Must be a numeric literal. Floating-point data items and literals can be used anywhere that a numeric data item or literal can be specified. When the ARITH(COMPAT) compiler option is in effect, the composite of operands can contain a maximum of 30 digits. When the ARITH(EXTEND) compiler option is in effect, the composite of operands can contain a maximum of 31 digits. For more information, see Arithmetic statement operands on page 276 and the details on arithmetic intermediate results in the Enterprise COBOL Programming Guide.
ROUNDED phrase
For formats 1, 2, and 3, see ROUNDED phrase on page 273.
SIZE ERROR phrases

For formats 1, 2, and 3, see SIZE ERROR phrases on page 274.
CORRESPONDING phrase (format 3)

See CORRESPONDING phrase on page 272.
END-ADD phrase
This explicit scope terminator serves to delimit the scope of the ADD statement. END-ADD permits a conditional ADD statement to be nested in another conditional statement. END-ADD can also be used with an imperative ADD statement. For more information, see Delimited scope statements on page 271.
292
Language Reference
ALTER statement
The ALTER statement changes the transfer point specified in a GO TO statement. The ALTER statement encourages the use of unstructured programming practices; the EVALUATE statement provides the same function as the ALTER statement but helps to ensure that a program is well-structured.
Format
ALTER
procedure-name-1 TO PROCEED TO
procedure-name-2
The ALTER statement modifies the GO TO statement in the paragraph named by procedure-name-1. Subsequent executions of the modified GO TO statement transfer control to procedure-name-2. procedure-name-1 Must name a procedure division paragraph that contains only one sentence: a GO TO statement without the DEPENDING ON phrase. procedure-name-2 Must name a procedure division section or paragraph. Before the ALTER statement is executed, when control reaches the paragraph specified in procedure-name-1, the GO TO statement transfers control to the paragraph specified in the GO TO statement. After execution of the ALTER statement however, the next time control reaches the paragraph specified in procedure-name-1, the GO TO statement transfers control to the paragraph specified in procedure-name-2. The ALTER statement acts as a program switch, allowing, for example, one sequence of execution during initialization and another sequence during the bulk of file processing. Altered GO TO statements in programs with the INITIAL attribute are returned to their initial states each time the program is entered. Do not use the ALTER statement in programs that have the RECURSIVE attribute, in methods, or in programs compiled with the THREAD option.
Segmentation considerations
A GO TO statement in a section whose priority is greater than or equal to 50 must not be referred to by an ALTER statement in a section with a different priority. All other uses of the ALTER statement are valid and are performed even if the GO TO to which the ALTER refers is in a fixed overlayable segment. Altered GO TO statements in independent segments are returned to their initial states when control is transferred to the independent segment that contains the ALTERED GO TO from another independent segment with a different priority. This transfer of control can take place because of:
293
v The effect of previous statements v An explicit transfer of control with a PERFORM or GO TO statement v A sort or merge statement with the INPUT or OUTPUT phrase specified
294
Language Reference
CALL statement
The CALL statement transfers control from one object program to another within the run unit. The program containing the CALL statement is the calling program; the program identified in the CALL statement is the called subprogram. Called programs can contain CALL statements; however, only programs defined with the RECURSIVE clause can execute a CALL statement that directly or indirectly calls itself. Do not specify the name of a class or method in the CALL statement.
Format
CALL identifier-1 literal-1 procedure-pointer-1 function-pointer-1
USING REFERENCE BY ADDRESS OF file-name-1 OMITTED
identifier-2
CONTENT BY ADDRESS OF LENGTH OF literal-2 OMITTED
identifier-3
VALUE BY ADDRESS OF LENGTH OF literal-3
identifier-4
RETURNING identifier-5
exception-phrases
END-CALL
exception-phrases:
EXCEPTION imperative-statement-1 ON OVERFLOW imperative-statement-3 ON
NOT ON
EXCEPTION imperative-statement-2
identifier-1, literal-1 literal-1 must be an alphanumeric literal. identifier-1 must be an alphanumeric, alphabetic, or numeric data item described with USAGE DISPLAY such that its value can be a program-name.
295
The rules of formation for program-names are dependent on the PGMNAME compiler option. For details, see the discussion of program-names in PROGRAM-ID paragraph on page 94 and also the description of the PGMNAME compiler option in the Enterprise COBOL Programming Guide. identifier-1 cannot be a windowed date field. procedure-pointer-1 Must be defined with USAGE IS PROCEDURE-POINTER and must be set to a valid program entry point; otherwise, the results of the CALL statement are undefined. After a program has been canceled by COBOL, released by PL/I or C, or deleted by assembler, any procedure-pointers that had been set to that programs entry point are no longer valid. function-pointer-1 Must be defined with USAGE IS FUNCTION-POINTER and must be set to a valid function or program entry point; otherwise, the results of the CALL statement are undefined. After a program has been canceled by COBOL, released by PL/I or C, or deleted by the assembler, any function-pointers that had been set to that function or programs entry point are no longer valid. When the called subprogram is to be entered at the beginning of the procedure division, literal-1 or the contents of identifier-1 must specify the program-name of the called subprogram. When the called subprogram is entered through an ENTRY statement, literal-1 or the contents of identifier-1 must be the same as the name specified in the called subprograms ENTRY statement. For information about how the compiler resolves calls to program-names found in multiple programs, see Conventions for program-names on page 80.
USING phrase
The USING phrase specifies arguments that are passed to the target program. Include the USING phrase in the CALL statement only if there is a USING phrase in the procedure division header or the ENTRY statement through which the called program is run. The number of operands in each USING phrase must be identical. For more information about the USING phrase, see The procedure division header on page 235. The sequence of the operands in the USING phrase of the CALL statement and in the corresponding USING phrase in the called subprograms procedure division header or ENTRY statement determines the correspondence between the operands used by the calling and called programs. This correspondence is positional. The values of the parameters referenced in the USING phrase of the CALL statement are made available to the called subprogram at the time the CALL statement is executed. The description of the data items in the called program must describe the same number of character positions as the description of the corresponding data items in the calling program.
296
Language Reference
The BY CONTENT, BY REFERENCE, and BY VALUE phrases apply to parameters that follow them until another BY CONTENT, BY REFERENCE, or BY VALUE phrase is encountered. BY REFERENCE is assumed if you do not specify a BY CONTENT, BY REFERENCE, or BY VALUE phrase prior to the first parameter.
BY REFERENCE phrase
If the BY REFERENCE phrase is either specified or implied for a parameter, the corresponding data item in the calling program occupies the same storage area as the data item in the called program. identifier-2 Can be any data item of any level in the data division. identifier-2 cannot be a function-identifier. If it is defined in the linkage section or file section, you must have already provided addressability for identifier-2 prior to invocation of the CALL statement. You can do this by coding either one of the following: SET ADDRESS OF identifier-2 TO pointer or PROCEDURE/ENTRY USING. file-name-1 A file-name for a QSAM file. See the Enterprise COBOL Programming Guide for details on using file-name with the CALL statement. ADDRESS OF identifier-2 identifier-2 must be a level-01 or level-77 item defined in the linkage section. OMITTED Indicates that no argument is passed.
BY CONTENT phrase
If the BY CONTENT phrase is specified or implied for a parameter, the called program cannot change the value of this parameter as referenced in the CALL statements USING phrase, though the called program can change the value of the data item referenced by the corresponding data-name in the called programs procedure division header. Changes to the parameter in the called program do not affect the corresponding argument in the calling program. identifier-3 Can be any data item of any level in the data division. identifier-3 cannot be a function identifier. If defined in the linkage section or file section, you must have already provided addressability for identifier-3 prior to invocation of the CALL statement. You can do this by coding either one of the following: SET ADDRESS OF identifier-3 TO pointer or PROCEDURE/ENTRY USING. literal-2 Can be: v An alphanumeric literal v A figurative constant (except ALL literal or NULL/NULLS) v A DBCS literal v A national literal LENGTH OF special register For information about the LENGTH OF special register, see LENGTH OF on page 16.
297
ADDRESS OF identifier-3 identifier-3 must be a data item of any level except 66 or 88 defined in the linkage section, the working-storage section, or the local-storage section. OMITTED Indicates that no argument is passed. For alphanumeric literals, the called subprogram should describe the parameter as PIC X(n) USAGE DISPLAY, where n is the number of characters in the literal. For DBCS literals, the called subprogram should describe the parameter as PIC G(n) USAGE DISPLAY-1, or PIC N(n) with implicit or explicit USAGE DISPLAY-1, where n is the length of the literal. For national literals, the called subprogram should describe the parameter as PIC N(n) with implicit or explicit USAGE NATIONAL, where n is the length of the literal.
BY VALUE phrase
The BY VALUE phrase applies to all arguments that follow until overridden by another BY REFERENCE or BY CONTENT phrase. If the BY VALUE phrase is specified or implied for an argument, the value of the argument is passed, not a reference to the sending data item. The called program can modify the formal parameter that corresponds to the BY VALUE argument, but any such changes do not affect the argument because the called program has access to a temporary copy of the sending data item. Although BY VALUE arguments are primarily intended for communication with non-COBOL programs (such as C), they can also be used for COBOL-to-COBOL invocations. In this case, BY VALUE must be specified or implied for both the argument in the CALL USING phrase and the corresponding formal parameter in the procedure division USING phrase. identifier-4 Must be an elementary data item in the data division. It must be one of the following: v Binary (USAGE BINARY, COMP, COMP-4, or COMP-5) v Floating point (USAGE COMP-1 or COMP-2) v Function-pointer (USAGE FUNCTION-POINTER) v Pointer (USAGE POINTER) v Procedure-pointer (USAGE PROCEDURE-POINTER) v Object reference (USAGE OBJECT REFERENCE) v One single-byte alphanumeric character (such as PIC X or PIC A) v One national character (PIC N) The following can also be passed BY VALUE: v Reference-modified item of usage display and length 1 v Reference-modified item of usage national and length 1 v SHIFT-IN and SHIFT-OUT special registers v LINAGE-COUNTER special register when it is usage binary
298
Language Reference
ADDRESS OF identifier-4 identifier-4 must be a data item of any level except 66 or 88 defined in the linkage section, the working-storage section, or the local-storage section. LENGTH OF special register A LENGTH OF special register passed BY VALUE is treated as a PIC 9(9) binary. For information about the LENGTH OF special register, see LENGTH OF on page 16. literal-3 Must be one of the following: v A numeric literal v A figurative constant ZERO v A one-character alphanumeric literal v A one-character national literal v A symbolic character v A single-byte figurative constant SPACE QUOTE HIGH-VALUE LOW-VALUE ZERO is treated as a numeric value; a fullword binary zero is passed. If literal-3 is a fixed-point numeric literal, it must have a precision of nine or fewer digits. In this case, a fullword binary representation of the literal value is passed. If literal-3 is a floating-point numeric literal, an 8-byte internal floating-point (COMP-2) representation of the value is passed. literal-3 must not be a DBCS literal.
RETURNING phrase
identifier-5 The RETURNING data item, which can be any data item defined in the data division. The return value of the called program is implicitly stored into identifier-5. You can specify the RETURNING phrase for calls to functions written in COBOL, C, or in other programming languages that use C linkage conventions. If you specify the RETURNING phrase on a CALL to a COBOL subprogram: v The called subprogram must specify the RETURNING phrase on its procedure division header. v identifier-5 and the corresponding procedure division RETURNING identifier in the target program must have the same PICTURE, USAGE, SIGN, SYNCHRONIZE, JUSTIFIED, and BLANK WHEN ZERO clauses (except that PICTURE clause currency symbols can differ, and periods and commas can be interchanged due to the DECIMAL POINT IS COMMA clause). When the target returns, its return value is assigned to identifier-5 using the rules for the SET statement if identifier-6 is of usage INDEX, POINTER,
299
FUNCTION-POINTER, PROCEDURE-POINTER, or OBJECT REFERENCE. When identifier-5 is of any other usage, the rules for the MOVE statement are used. The CALL ... RETURNING data item is an output-only parameter. On entry to the called program, the initial state of the PROCEDURE DIVISION RETURNING data item has an undefined and unpredictable value. You must initialize the PROCEDURE DIVISION RETURNING data item in the called program before you reference its value. The value that is passed back to the calling program is the final value of the PROCEDURE DIVISION RETURNING data item when the called program returns. If an EXCEPTION or OVERFLOW occurs, identifier-5 is not changed. identifier-5 must not be reference-modified. The RETURN-CODE special register is not set by execution of CALL statements that include the RETURNING phrase.
ON EXCEPTION phrase
An exception condition occurs when the called subprogram cannot be made available. At that time, one of the following two actions will occur: 1. If the ON EXCEPTION phrase is specified, control is transferred to imperative-statement-1. Execution then continues according to the rules for each statement specified in imperative-statement-1. If a procedure branching or conditional statement that causes explicit transfer of control is executed, control is transferred in accordance with the rules for that statement. Otherwise, upon completion of the execution of imperative-statement-1, control is transferred to the end of the CALL statement and the NOT ON EXCEPTION phrase, if specified, is ignored. 2. If the ON EXCEPTION phrase is not specified in the CALL statement, the NOT ON EXCEPTION phrase, if specified, is ignored.
NOT ON EXCEPTION phrase

If an exception condition does not occur (that is, the called subprogram can be made available), control is transferred to the called program. After control is returned from the called program, control is transferred to: v imperative-statement-2, if the NOT ON EXCEPTION phrase is specified. v The end of the CALL statement in any other case. (If the ON EXCEPTION phrase is specified, it is ignored.) If control is transferred to imperative-statement-2, execution continues according to the rules for each statement specified in imperative-statement-2. If a procedure branching or conditional statement that causes explicit transfer of control is executed, control is transferred in accordance with the rules for that statement. Otherwise, upon completion of the execution of imperative-statement-2, control is transferred to the end of the CALL statement.
ON OVERFLOW phrase
The ON OVERFLOW phrase has the same effect as the ON EXCEPTION phrase.
300
Language Reference
END-CALL phrase
This explicit scope terminator serves to delimit the scope of the CALL statement. END-CALL permits a conditional CALL statement to be nested in another conditional statement. END-CALL can also be used with an imperative CALL statement. For more information, see Delimited scope statements on page 271.
301
CANCEL statement
The CANCEL statement ensures that the referenced subprogram is entered in initial state the next time that it is called.
Format
CANCEL
identifier-1, literal-1 literal-1 must be an alphanumeric literal. identifier-1 must be an alphanumeric, alphabetic, or zoned decimal data item such that its value can be a program-name. The rules of formation for program-names are dependent on the PGMNAME compiler option. For details, see the discussion of program-names in PROGRAM-ID paragraph on page 94 and the description of the PGMNAME compiler option in the Enterprise COBOL Programming Guide. identifier-1 cannot be a windowed date field. literal-1 or the contents of identifier-1 must be the same as a literal or the contents of an identifier specified in an associated CALL statement. Do not specify the name of a class or a method in the CANCEL statement. After a CANCEL statement for a called subprogram has been executed, that subprogram no longer has a logical connection to the program. The contents of data items in external data records described by the subprogram are not changed when that subprogram is canceled. If a CALL statement is executed later by any program in the run unit naming the same subprogram, that subprogram is entered in its initial state. When a CANCEL statement is executed, all programs contained within the program referenced in the CANCEL statement are also canceled. The result is the same as if a valid CANCEL were executed for each contained program in the reverse order in which the programs appear in the separately compiled program. A CANCEL statement closes all open files that are associated with an internal file connector in the program named in an explicit CANCEL statement. USE procedures associated with those files are not executed. You can cancel a called subprogram in any of the following ways: v By referencing it as the operand of a CANCEL statement v By terminating the run unit of which the subprogram is a member v By executing an EXIT PROGRAM statement or a GOBACK statement in the called subprogram if that subprogram possesses the initial attribute No action is taken when a CANCEL statement is executed if the specified program: v Has not been dynamically called in this run unit by another COBOL program v Has been called and subsequently canceled
302
Language Reference
In a multithreaded environment, a program cannot execute a CANCEL statement naming a program that is active on any thread. The named program must be completely inactive. Called subprograms can contain CANCEL statements. However, a called subprogram must not execute a CANCEL statement that directly or indirectly cancels the calling program itself or that cancels any program higher than itself in the calling hierarchy. In such a case, the run unit is terminated. A program named in a CANCEL statement must be a program that has been called and has not yet executed an EXIT PROGRAM or a GOBACK statement. A program can cancel a program that it did not call, provided that, in the calling hierarchy, the program that executes the CANCEL statement is higher than or equal to the program it is canceling. For example:
A calls B and B calls C A calls B and A calls C (When A receives control, it can cancel C.) (When C receives control, it can cancel B.)
303
CLOSE statement
The CLOSE statement terminates the processing of volumes and files.
Format 1: sequential
CLOSE
file-name-1 (1) REEL (1) UNIT REMOVAL FOR WITH NO REWIND (1) NO REWIND LOCK
WITH
Notes: 1 The REEL, UNIT, and NO REWIND phrases are not valid for VSAM files.
Format 2: indexed and relative files
CLOSE
file-name-1 LOCK WITH
CLOSE
file-name-1 REEL UNIT REMOVAL FOR WITH NO REWIND NO REWIND LOCK
WITH
file-name-1 Designates the file upon which the CLOSE statement is to operate. If more than one file-name is specified, the files need not have the same organization or access. file-name-1 must not be a sort or merge file. REEL and UNIT You can specify these phrases only for QSAM multivolume or single volume files. The terms REEL and UNIT are interchangeable.
304
Language Reference
| | |
WITH NO REWIND and FOR REMOVAL These phrases apply only to QSAM tape files. If they are specified for storage devices to which they do not apply, the close operation is successful and a status key value is set to indicate the file was on a non-reel medium. A CLOSE statement can be executed only for a file in an open mode. After successful execution of a CLOSE statement (without the REEL/UNIT phrase if using format 1): v The record area associated with the file-name is no longer available. Unsuccessful execution of a CLOSE statement leaves availability of the record data undefined. v An OPEN statement for the file must be executed before any other input/output statement can be executed for the file and before data is moved to a record description entry associated with the file. If the FILE STATUS clause is specified in the file-control entry, the associated file status key is updated when the CLOSE statement is executed. 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.
| |
Effect of CLOSE statement on file types

If the SELECT OPTIONAL clause is specified in the file-control entry for a file, and the file is not present at run time, standard end-of-file processing is not performed. For QSAM files, the file position indicator and current volume pointer are unchanged. Files are divided into the following types: Non-reel/unit A file whose input or output medium is such that rewinding, reels, and units have no meaning. All VSAM files are non-reel/unit file types. QSAM files can be non-reel/unit file types. Sequential single volume A sequential file that is contained entirely on one volume. More than one file can be contained on this volume. All VSAM files are single volume. QSAM files can be single volume. Sequential multivolume A sequential file that is contained on more than one volume. QSAM files are the only files that can be multivolume. The concept of volume has no meaning for VSAM files. The permissible combinations of CLOSE statement phrases are shown in: v Sequential files and CLOSE statement phrases (Table 33 on page 306) v Indexed and relative file types and CLOSE statement phrases (Table 34 on page 306) v Line-sequential file types and CLOSE statement phrases (Table 35 on page 306) The meaning of each key letter is shown in Meanings of key letters for sequential file types (Table 36 on page 306).
305
Table 33. Sequential files and CLOSE statement phrases CLOSE statement phrases CLOSE CLOSE REEL/UNIT CLOSE REEL/UNIT WITH NO REWIND CLOSE REEL/UNIT FOR REMOVAL CLOSE WITH NO REWIND CLOSE WITH LOCK Non-reel/ unit C F F D C, H C, E Sequential single-volume C, G F, G B, F D B, C C, E, G Sequential multivolume A, C, G F, G B, F D A, B, C A, C, E, G
Table 34. Indexed and relative file types and CLOSE statement phrases CLOSE statement phrases CLOSE CLOSE WITH LOCK Action C C,E
Table 35. Line-sequential file types and CLOSE statement phrases CLOSE statement phrases CLOSE CLOSE WITH LOCK Action C C,E
Table 36. Meanings of key letters for sequential file types Key A Actions taken Previous volumes unaffected Input and input-output files: Standard volume-switch processing is performed for all previous volumes (except those controlled by a previous CLOSE REEL/UNIT statement). Any subsequent volumes are not processed. Output files: Standard volume-switch processing is performed for all previous volumes (except those controlled by a previous CLOSE REEL/UNIT statement). B C No rewinding of current reel: The current volume is left in its current position. Close file Input and input-output files: If the file is at its end, and label records are specified, the standard ending label procedure is performed. Standard system closing procedures are then performed. If the file is at its end, and label records are not specified, label processing does not take place, but standard system closing procedures are performed. If the file is not at its end, standard system closing procedures are performed, but there is no ending label processing. Output files: If label records are specified, standard ending label procedures are performed. Standard system closing procedures are then performed. If label records are not specified, ending label procedures are not performed, but standard system closing procedures are performed.
306
Language Reference
Table 36. Meanings of key letters for sequential file types (continued) Key D E Actions taken Volume removal: Treated as a comment. File lock: The compiler ensures that this file cannot be opened again during this execution of the object program. If the file is a tape unit, it will be rewound and unloaded. Close volume Input and input-output files: If the current reel/unit is the last or only reel/unit for the file or if the reel is on a non-reel/unit medium, no volume switching is performed. If another reel/unit exists for the file, the following operations are performed: a volume switch, beginning volume label procedure, and the first record on the new volume is made available for reading. If no data records exist for the current volume, another volume switch occurs. Output (reel/unit media) files: The following operations are performed: the ending volume label procedure, a volume switch, and the beginning volume label procedure. The next executed WRITE statement places the next logical record on the next direct access volume available. A close statement with the REEL phrase does not close the output file; only an end-of-volume condition occurs. Output (non-reel/unit media) files: Execution of the CLOSE statement is considered successful. The file remains in the open mode and no action takes place except that the value of the I-O status associated with the file is updated. G H Rewind: The current volume is positioned at its physical beginning. Optional phrases ignored: The CLOSE statement is executed as if none of the optional phrases were present.
307
COMPUTE statement
The COMPUTE statement assigns 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. When arithmetic operations are combined, the COMPUTE statement can be more efficient than the separate arithmetic statements written in a series.
Format
COMPUTE
= EQUAL
arithmetic-expression SIZE ERROR imperative-statement-1 ON
NOT ON
END-COMPUTE
identifier-1 Must name an elementary numeric item or an elementary numeric-edited item. Can name an elementary floating-point data item. If identifier-1 or the result of arithmetic expression (or both) are date fields, see Storing arithmetic results that involve date fields on page 245 for details on how the result is stored in identifier-1. If a year-last date field is specified as identifier-1, the result of arithmetic expression must be a nondate. arithmetic-expression Can be any arithmetic expression, as defined in Arithmetic expressions on page 241. When the COMPUTE statement is executed, the value of arithmetic expression is calculated and stored as the new value of each data item referenced by identifier-1. An arithmetic expression consisting of a single identifier, numeric function, or literal allows the user to set the value of the data items that are referenced by identifier-1 equal to the value of that identifier, function, or literal. A year-last date field must not be specified in the arithmetic expression.
308
Language Reference
ROUNDED phrase
For a discussion of the ROUNDED phrase, see ROUNDED phrase on page 273.
SIZE ERROR phrases

For a discussion of the SIZE ERROR phrases, see SIZE ERROR phrases on page 274.
END-COMPUTE phrase
This explicit scope terminator serves to delimit the scope of the COMPUTE statement. END-COMPUTE permits a conditional COMPUTE statement to be nested in another conditional statement. END-COMPUTE can also be used with an imperative COMPUTE statement. For more information, see Delimited scope statements on page 271.
309
CONTINUE statement
The CONTINUE statement is a no operation statement. CONTINUE indicates that no executable instruction is present.
Format
CONTINUE
310
Language Reference
DELETE statement
The DELETE statement removes a record from an indexed or relative file. For indexed files, the key can then be reused for record addition. For relative files, the space is then available for a new record with the same RELATIVE KEY value. When the DELETE statement is executed, the associated file must be open in I-O mode.
Format
DELETE file-name-1 RECORD
INVALID KEY
imperative-statement-1
NOT INVALID KEY
END-DELETE
file-name-1 Must be defined in an FD entry in the data division and must be the name of an indexed or relative file. After successful execution of a DELETE statement, the record is removed from the file and can no longer be accessed. Execution of the DELETE statement does not affect the contents of the record area associated with file-name-1 or the content of the data item referenced by the data-name specified in the DEPENDING ON phrase of the RECORD clause associated with file-name-1. If the FILE STATUS clause is specified in the file-control entry, the associated file status key is updated when the DELETE statement is executed. The file position indicator is not affected by execution of the DELETE statement.
Sequential access mode

For a file in sequential access mode, the previous input/output statement must be a successfully executed READ statement. When the DELETE statement is executed, the system removes the record that was retrieved by that READ statement. For a file in sequential access mode, the INVALID KEY and NOT INVALID KEY phrases must not be specified. An EXCEPTION/ERROR procedure can be specified.
Random or dynamic access mode

In random or dynamic access mode, DELETE statement execution results depend on the file organization: indexed or relative.
311
When the DELETE statement is executed, the system removes the record identified by the contents of the prime RECORD KEY data item for indexed files, or the RELATIVE KEY data item for relative files. If the file does not contain such a record, an INVALID KEY condition exists. (See Invalid key condition under Common processing facilities on page 278.) Both the INVALID KEY phrase and an applicable EXCEPTION/ERROR procedure can be omitted. Transfer of control after the successful execution of a DELETE statement, with the NOT INVALID KEY phrase specified, is to the imperative statement associated with the phrase.
END-DELETE phrase
This explicit scope terminator serves to delimit the scope of the DELETE statement. END-DELETE permits a conditional DELETE statement to be nested in another conditional statement. END-DELETE can also be used with an imperative DELETE statement. For more information, see Delimited scope statements on page 271.
312
Language Reference
DISPLAY statement
The DISPLAY statement transfers the contents of each operand to the output device. The contents are displayed on the output device in the order, left to right, in which the operands are listed.
Format
DISPLAY
UPON
mnemonic-name-1 environment-name-1
NO ADVANCING WITH
identifier-1 If numeric and not described as an external decimal data item, identifier-1 is converted automatically to external format as follows: v Binary or internal decimal items are converted to external decimal. Negative signed values cause a low-order sign overpunch. v Internal floating-point numbers are converted to external floating-point numbers for display such that: A COMP-1 item will display as if it had an external floating-point PICTURE clause of -.9(8)E-99. A COMP-2 item will display as if it had an external floating-point PICTURE clause of -.9(17)E-99. v Data items defined with USAGE POINTER are converted to an external decimal number that has an implicit PICTURE clause of PIC 9(10). v If the output is directed to CONSOLE, national data items are converted from national character representation to EBCDIC. The conversion uses the EBCDIC code page that was specified in the CODEPAGE compiler option when the source code was compiled. National characters without EBCDIC counterparts are converted to default substitution characters; no exception condition is indicated or raised. If the output is not directed to CONSOLE, national data items are written without conversion and without data validation. No other categories of data require conversion. Data items defined with USAGE PROCEDURE-POINTER, USAGE FUNCTION-POINTER, or USAGE OBJECT REFERENCE cannot be specified in a DISPLAY statement. Index names or index data items cannot be specified in a DISPLAY statement. Date fields are treated as nondates when specified in a DISPLAY statement. That is, the DATE FORMAT is ignored and the content of the data item is transferred to the output device as is.
313
DBCS data items, explicitly or implicitly defined as USAGE DISPLAY-1, are transferred to the sending field of the output device. For proper results, the output device must have the capability to recognize DBCS shift-out and shift-in control characters. Both DBCS and non-DBCS operands can be specified in a single DISPLAY statement. literal-1 Can be any literal or figurative constant. When a figurative constant is specified, only a single occurrence of that figurative constant is displayed. The ALL figurative constant can be used. UPON environment-name-1 or the environment name associated with mnemonic-name-1 must be associated with an output device. See SPECIAL-NAMES paragraph on page 106. A default logical record size is assumed for each device, as follows: The system logical output device 120 characters The system punch device 80 characters The console 100 characters A maximum logical record size is allowed for each device, as follows: The system logical output device 255 characters The system punch device 255 characters The console 100 characters On the system punch device, the last eight characters are used for PROGRAM-ID name. When the UPON phrase is omitted, the systems logical output device is assumed. The list of valid environment-names in a DISPLAY statement is shown in Meanings of environment names (Table 5 on page 108). For details on routing DISPLAY output to stdout, see the Enterprise COBOL Programming Guide.
WITH NO ADVANCING When specified, the positioning of the output device will not be changed in any way following the display of the last operand. If the WITH NO ADVANCING phrase is not specified, after the last operand has been transferred to the output device, the positioning of the output device will be reset to the leftmost position of the next line of the device.
314
Language Reference
Enterprise COBOL does not support output devices that are capable of positioning to a specific character position. See the Enterprise COBOL Programming Guide for more information about the DISPLAY statement. The DISPLAY statement transfers the data in the sending field to the output device. The size of the sending field is the total byte count of all operands listed. If the output device is capable of receiving data of the same size as the data item being transferred, then the data item is transferred. If the output device is not capable of receiving data of the same size as the data item being transferred, then one of the following applies: v If the total count is less than the device maximum, the remaining rightmost positions are padded with spaces. v If the total count exceeds the maximum, as many records are written as are needed to display all operands. Any operand being printed or displayed when the end of a record is reached is continued in the next record. If a DBCS operand must be split across multiple records, it will be split only on a double-byte boundary. Shift code insertion is required for splitting DBCS items. That is, when a DBCS operand is split across multiple records, the shift-in character is inserted at the end of the current record, and the shift-out character is inserted at the beginning of the next record. A space is padded after the shift-in character, if necessary. These inserted shift codes and spaces are included in the total byte count of the sending data items. After the last operand has been transferred to the output device, the device is reset to the leftmost position of the next line of the device. If a DBCS data item or literal is specified in a DISPLAY statement, the size of the sending field is the total byte count of all operands listed, with each DBCS character counted as two bytes, plus the necessary shift codes and spaces for DBCS.
315
DIVIDE statement
The DIVIDE statement divides one numeric data item into or by others and sets the values of data items equal to the quotient and remainder.
Format 1
DIVIDE
INTO
NOT ON
END-DIVIDE
In format 1, the value of identifier-1 or literal-1 is divided into the value of identifier-2, and the quotient is then stored in identifier-2. For each successive occurrence of identifier-2, the division takes place in the left-to-right order in which identifier-2 is specified.
Format 2
DIVIDE identifier-1 literal-1 INTO identifier-2 literal-2
GIVING
NOT ON
END-DIVIDE
316
Language Reference
In format 2, the value of identifier-1 or literal-1 is divided into the value of identifier-2 or literal-2. The value of the quotient is stored in each data item referenced by identifier-3.
Format 3
DIVIDE identifier-1 literal-1 BY identifier-2 literal-2
GIVING
NOT ON
END-DIVIDE
In format 3, the value of identifier-1 or literal-1 is divided by the value of identifier-2 or literal-2. The value of the quotient is stored in each data item referenced by identifier-3.
Format 4
DIVIDE identifier-1 literal-1 INTO identifier-2 literal-2 REMAINDER identifier-4 ROUNDED
GIVING identifier-3
NOT ON
END-DIVIDE
In format 4, the value of identifier-1 or literal-1 is divided into identifier-2 or literal-2. The value of the quotient is stored in identifier-3, and the value of the remainder is stored in identifier-4.
317
Format 5
DIVIDE identifier-1 literal-1 BY identifier-2 literal-2 REMAINDER identifier-4 ROUNDED
GIVING identifier-3
NOT ON
END-DIVIDE
In format 5, the value of identifier-1 or literal-1 is divided by identifier-2 or literal-2. The value of the quotient is stored in identifier-3, and the value of the remainder is stored in identifier-4. For all formats: identifier-1, identifier-2 Must name an elementary numeric item. identifier-1 and identifier-2 cannot be date fields. identifier-3, identifier-4 Must name an elementary numeric or numeric-edited item. If identifier-3 or identifier-4 is a date field, see Storing arithmetic results that involve date fields on page 245 for details on how the quotient or remainder is stored in identifier-3. literal-1, literal-2 Must be a numeric literal. In formats 1, 2, and 3, floating-point data items and literals can be used anywhere that a numeric data item or literal can be specified. In formats 4 and 5, floating-point data items or literals cannot be used.
ROUNDED phrase
For formats 1, 2, and 3, see ROUNDED phrase on page 273. For formats 4 and 5, the quotient used to calculate the remainder is in an intermediate field. The value of the intermediate field is truncated rather than rounded.
REMAINDER phrase
The result of subtracting the product of the quotient and the divisor from the dividend is stored in identifier-4. If identifier-3, the quotient, is a numeric-edited item, the quotient used to calculate the remainder is an intermediate field that contains the unedited quotient.
318
Language Reference
The REMAINDER phrase is invalid if the receiver or any of the operands is a floating-point item. Any subscripts for identifier-4 in the REMAINDER phrase are evaluated after the result of the divide operation is stored in identifier-3 of the GIVING phrase.
SIZE ERROR phrases

For formats 1, 2, and 3, see SIZE ERROR phrases on page 274. For formats 4 and 5, if a size error occurs in the quotient, no remainder calculation is meaningful. Therefore, the contents of the quotient field (identifier-3) and the remainder field (identifier-4) are unchanged. If size error occurs in the remainder, the contents of the remainder field (identifier-4) are unchanged. In either of these cases, you must analyze the results to determine which situation has actually occurred. For information about the NOT ON SIZE ERROR phrase, see SIZE ERROR phrases on page 274.
END-DIVIDE phrase
This explicit scope terminator serves to delimit the scope of the DIVIDE statement. END-DIVIDE turns a conditional DIVIDE statement into an imperative statement that can be nested in another conditional statement. END-DIVIDE can also be used with an imperative DIVIDE statement. For more information, see Delimited scope statements on page 271.
319
ENTRY statement
The ENTRY statement establishes an alternate entry point into a COBOL called subprogram. The ENTRY statement cannot be used in: v Programs that specify a return value using the procedure division RETURNING phrase. For details, see the discussion of the RETURNING phrase under The procedure division header on page 235. v Nested program. See Nested programs on page 79 for a description of nested programs. When a CALL statement that specifies the alternate entry point is executed in a calling program, control is transferred to the next executable statement following the ENTRY statement.
Format
ENTRY literal-1 .
USING REFERENCE BY VALUE BY
identifier-1
literal-1 Must be an alphanumeric literal that conform to the rules for the formation of a program-name in an outermost program (see PROGRAM-ID paragraph on page 94). Must not match the program-ID or any other ENTRY literal in this program. Must not be a figurative constant. Execution of the called program begins at the first executable statement following the ENTRY statement whose literal corresponds to the literal or identifier specified in the CALL statement. The entry point name on the ENTRY statement can be affected by the PGMNAME compiler option. For details, see the Enterprise COBOL Programming Guide.
USING phrase
For a discussion of the USING phrase, see The procedure division header on page 235.
320
Language Reference
EVALUATE statement
The EVALUATE statement provides a shorthand notation for a series of nested IF statements. It can evaluate multiple conditions. The subsequent action depends on the results of these evaluations.
Format
EVALUATE identifier-1 literal-1 expression-1 TRUE FALSE
ALSO
identifier-2 literal-2 expression-2 TRUE FALSE
WHEN
phrase 1
ALSO
phrase 2
WHEN OTHER imperative-statement-2
END-EVALUATE
phrase 1:
ANY condition-1 TRUE FALSE NOT identifier-3 literal-3 arithmetic-expression-1 THROUGH THRU identifier-4 literal-4 arithmetic-expression-2
phrase 2:
ANY condition-2 TRUE FALSE NOT identifier-5 literal-5 arithmetic-expression-3 THROUGH THRU identifier-6 literal-6 arithmetic-expression-4
321
Operands before the WHEN phrase Are interpreted in one of two ways, depending on how they are specified: v Individually, they are called selection subjects. v Collectively, they are called a set of selection subjects. Operands in the WHEN phrase Are interpreted in one of two ways, depending on how they are specified: v Individually, they are called selection objects v Collectively, they are called a set of selection objects. ALSO Separates selection subjects within a set of selection subjects; separates selection objects within a set of selection objects. THROUGH and THRU Are equivalent. Two operands connected by a THRU phrase must be of the same class. The two operands thus connected constitute a single selection object. The number of selection objects within each set of selection objects must be equal to the number of selection subjects. Each selection object within a set of selection objects must correspond to the selection subject having the same ordinal position within the set of selection subjects, according to the following rules: v Identifiers, literals, or arithmetic expressions appearing within a selection object must be valid operands for comparison to the corresponding operand in the set of selection subjects. For comparisons involving date fields, see Date fields on page 251. v condition-1, condition-2, or the word TRUE or FALSE appearing as a selection object must correspond to a conditional expression or the word TRUE or FALSE in the set of selection subjects. v The word ANY can correspond to a selection subject of any type.
END-EVALUATE phrase
This explicit scope terminator serves to delimit the scope of the EVALUATE statement. END-EVALUATE permits a conditional EVALUATE statement to be nested in another conditional statement. For more information, see Delimited scope statements on page 271.
Determining values
The execution of the EVALUATE statement operates as if each selection subject and selection object were evaluated and assigned a numeric, alphanumeric, DBCS, or national value; a range of numeric, alphanumeric, DBCS, or national values; or a truth value. These values are determined as follows: v Any selection subject specified by identifier-1, identifier-2, ... and any selection object specified by identifier-3 or identifier-5 without the NOT or THRU phrase are assigned the value and class of the data item that they reference. v Any selection subject specified by literal-1, literal-2, ... and any selection object specified by literal-3 or literal-5 without the NOT or THRU phrase are assigned
322
Language Reference
the value and class of the specified literal. If literal-3 or literal-5 is the figurative constant ZERO, QUOTE, or SPACE, the figurative constant is assigned the class of the corresponding selection subject. v Any selection subject in which expression-1, expression-2, ... is specified as an arithmetic expression, and any selection object without the NOT or THRU phrase in which arithmetic-expression-1 or arithmetic-expression-3 is specified, are assigned numeric values according to the rules for evaluating an arithmetic expression. (See Arithmetic expressions on page 241.) v Any selection subject in which expression-1, expression-2, ... is specified as a conditional expression, and any selection object in which condition-1 or condition-2 is specified, are assigned a truth value according to the rules for evaluating conditional expressions. (See Conditional expressions on page 246.) v Any selection subject or any selection object specified by the words TRUE or FALSE is assigned a truth value. The truth value true is assigned to those items specified with the word TRUE, and the truth value false is assigned to those items specified with the word FALSE. v Any selection object specified by the word ANY is not further evaluated. v If the THRU phrase is specified for a selection object without the NOT phrase, the range of values includes all values that, when compared to the selection subject, are greater than or equal to the first operand and less than or equal to the second operand according to the rules for comparison. If the first operand is greater than the second operand, there are no values in the range. v If the NOT phrase is specified for a selection object, the values assigned to that item are all values not equal to the value, or range of values, that would have been assigned to the item had the NOT phrase been omitted.
Comparing selection subjects and objects

The execution of the EVALUATE statement then proceeds as if the values assigned to the selection subjects and selection objects were compared to determine whether any WHEN phrase satisfies the set of selection subjects. This comparison proceeds as follows: 1. Each selection object within the set of selection objects for the first WHEN phrase is compared to the selection subject having the same ordinal position within the set of selection subjects. One of the following conditions must be satisfied if the comparison is to be satisfied: a. If the items being compared are assigned numeric, alphanumeric, DBCS, or national values, or a range of numeric, alphanumeric, DBCS, or national values, the comparison is satisfied if the value, or one value in the range of values, assigned to the selection object is equal to the value assigned to the selection subject according to the rules for comparison. b. If the items being compared are assigned truth values, the comparison is satisfied if the items are assigned identical truth values. c. If the selection object being compared is specified by the word ANY, the comparison is always satisfied, regardless of the value of the selection subject. 2. If the above comparison is satisfied for every selection object within the set of selection objects being compared, the WHEN phrase containing that set of selection objects is selected as the one satisfying the set of selection subjects. 3. If the above comparison is not satisfied for every selection object within the set of selection objects being compared, that set of selection objects does not satisfy the set of selection subjects.
323
4. This procedure is repeated for subsequent sets of selection objects in the order of their appearance in the source text, until either a WHEN phrase satisfying the set of selection subjects is selected or until all sets of selection objects are exhausted.
Executing the EVALUATE statement

After the comparison operation is completed, execution of the EVALUATE statement proceeds as follows: v If a WHEN phrase is selected, execution continues with the first imperative-statement-1 following the selected WHEN phrase. Note that multiple WHEN statements are allowed for a single imperative-statement-1. v If no WHEN phrase is selected and a WHEN OTHER phrase is specified, execution continues with imperative-statement-2. v If no WHEN phrase is selected and no WHEN OTHER phrase is specified, execution continues with the next executable statement following the scope delimiter. v The scope of execution of the EVALUATE statement is terminated when execution reaches the end of the scope of the selected WHEN phrase or WHEN OTHER phrase, or when no WHEN phrase is selected and no WHEN OTHER phrase is specified.
324
Language Reference
EXIT statement
The EXIT statement provides a common end point for a series of procedures.
Format
paragraph-name . EXIT.
The EXIT statement enables you to assign a procedure-name to a given point in a program. The EXIT statement is treated as a CONTINUE statement. Any statements following the EXIT statement are executed.
325
EXIT METHOD statement

The EXIT METHOD statement specifies the end of an invoked method.
Format
EXIT METHOD.
You can specify EXIT METHOD only in the procedure division of a method. EXIT METHOD causes the executing method to terminate, and control returns to the invoking statement. If the containing method specifies the procedure division RETURNING phrase, the value in the data item referred to by the RETURNING phrase becomes the result of the method invocation. If you need method-specific data to be in the last-used state on each invocation, declare it in method working-storage. If you need method-specific data to be in the initial state on each invocation, declare it in method local-storage. If control reaches an EXIT METHOD statement in a method definition, control returns to the point that immediately follows the INVOKE statement in the invoking program or method. The state of the invoking program or method is identical to that which existed at the time it executed the INVOKE statement. The contents of data items and the contents of data files shared between the invoking program or method and the invoked method could have changed. The state of the invoked method is not altered except that the end of the ranges of all PERFORM statements executed by the method are considered to have been reached. The EXIT METHOD statement does not have to be the last statement in a sequence of imperative statements, but the statements following the EXIT METHOD will not be executed. When there is no next executable statement in an invoked method, an implicit EXIT METHOD statement is executed.
326
Language Reference
EXIT PROGRAM statement

The EXIT PROGRAM statement specifies the end of a called program and returns control to the calling program. You can specify EXIT PROGRAM only in the procedure division of a program. EXIT PROGRAM must not be used in a declarative procedure in which the GLOBAL phrase is specified.
Format
EXIT PROGRAM.
If control reaches an EXIT PROGRAM statement in a program that does not possess the INITIAL attribute while operating under the control of a CALL statement (that is, the CALL statement is active), control returns to the point in the calling routine (program or method) immediately following the CALL statement. The state of the calling routine is identical to that which existed at the time it executed the CALL statement. The contents of data items and the contents of data files shared between the calling and called routine could have been changed. The state of the called program or method is not altered except that the ends of the ranges of all executed PERFORM statements are considered to have been reached. The execution of an EXIT PROGRAM statement in a called program that possesses the INITIAL attribute is equivalent also to executing a CANCEL statement referencing that program. If control reaches an EXIT PROGRAM statement, and no CALL statement is active, control passes through the exit point to the next executable statement. If a subprogram specifies the procedure division RETURNING phrase, the value in the data item referred to by the RETURNING phrase becomes the result of the subprogram invocation. The EXIT PROGRAM statement should be the last statement in a sequence of imperative statements. When it is not, statements following the EXIT PROGRAM will not be executed if a CALL statement is active. When there is no next executable statement in a called program, an implicit EXIT PROGRAM statement is executed.
327
GOBACK statement
The GOBACK statement functions like the EXIT PROGRAM statement when it is coded as part of a called program (or the EXIT METHOD statement when it is coded as part of an invoked method) and like the STOP RUN statement when coded in a main program. The GOBACK statement specifies the logical end of a called program or invoked method.
Format
GOBACK
A GOBACK statement should appear as the only statement or as the last of a series of imperative statements in a sentence because any statements following the GOBACK are not executed. GOBACK must not be used in a declarative procedure in which the GLOBAL phrase is specified. If control reaches a GOBACK statement while a CALL statement is active, control returns to the point in the calling program or method immediately following the CALL statement, as in the EXIT PROGRAM statement. If control reaches a GOBACK statement while an INVOKE statement is active, control returns to the point in the invoking program or method immediately following the INVOKE statement, as in the EXIT METHOD statement. In addition, the execution of a GOBACK statement in a called program that possesses the INITIAL attribute is equivalent to executing a CANCEL statement referencing that program. The table below shows the action taken for the GOBACK statement in both a main program and a subprogram.
Termination statement GOBACK Main program Subprogram
Return to calling program. (Can be Return to calling program. the system and thus causes the application to end.)
328
Language Reference
GO TO statement
The GO TO statement transfers control from one part of the procedure division to another. The types of GO TO statements are: v Unconditional v Conditional v Altered
Unconditional GO TO
The unconditional GO TO statement transfers control to the first statement in the paragraph or section identified by procedure-name, unless the GO TO statement has been modified by an ALTER statement. (See ALTER statement on page 293.)
Format 1: unconditional
GO TO procedure-name-1
procedure-name-1 Must name a procedure or a section in the same procedure division as the GO TO statement. When the unconditional GO TO statement is not the last statement in a sequence of imperative statements, the statements following the GO TO are not executed. When a paragraph is referred to by an ALTER statement, the paragraph must consist of a paragraph-name followed by an unconditional or altered GO TO statement.
Conditional GO TO
The conditional GO TO statement transfers control to one of a series of procedures, depending on the value of the data item referenced by identifier-1.
Format 2: conditional
GO TO
procedure-name-1
DEPENDING ON
identifier-1
procedure-name-1 Must be a procedure or a section in the same procedure division as the GO TO statement. The number of procedure-names must not exceed 255. identifier-1 Must be a numeric elementary data item that is an integer. identifier-1 cannot be a windowed date field. If 1, control is transferred to the first statement in the procedure named by the first occurrence of procedure-name-1.
329
If 2, control is transferred to the first statement in the procedure named by the second occurrence of procedure-name-1, and so forth. If the value of identifier is anything other than a value within the range of 1 through n (where n is the number of procedure-names specified in this GO TO statement), no control transfer occurs. Instead, control passes to the next statement in the normal sequence of execution.
Altered GO TO
The altered GO TO statement transfers control to the first statement of the paragraph named in the ALTER statement. You cannot specify the altered GO TO statement in the following: v A program or method that has the RECURSIVE attribute v A program compiled with the THREAD compiler option An ALTER statement referring to the paragraph that contains the altered GO TO statement should be executed before the GO TO statement is executed. Otherwise, the GO TO statement acts like a CONTINUE statement.
Format 3: altered
paragraph-name . GO TO .
When an ALTER statement refers to a paragraph, the paragraph can consist only of the paragraph-name followed by an unconditional or altered GO TO statement.
MORE-LABELS GO TO
The GO TO MORE-LABELS statement can be specified only in a LABEL declarative.
Format 4: MORE-LABELS
GO TO MORE-LABELS
For more details, see the Enterprise COBOL Programming Guide.
330
Language Reference
IF statement
The IF statement evaluates a condition and provides for alternative actions in the object program, depending on the evaluation.
Format
IF condition-1 THEN
statement-1 NEXT SENTENCE
(1) END-IF ELSE statement-2 NEXT SENTENCE
Notes: 1 END-IF can be specified with statement-2 or NEXT SENTENCE.
condition-1 Can be any simple or complex condition, as described in Conditional expressions on page 246. statement-1, statement-2 Can be any one of the following: v An imperative statement v A conditional statement v An imperative statement followed by a conditional statement NEXT SENTENCE The NEXT SENTENCE phrase transfers control to an implicit CONTINUE statement immediately following the next separator period. When NEXT SENTENCE is specified with END-IF, control does not pass to the statement following the END-IF. Instead, control passes to the statement after the closest following period.
END-IF phrase
This explicit scope terminator serves to delimit the scope of the IF statement. END-IF permits a conditional IF statement to be nested in another conditional statement. For more information about explicit scope terminators, see Delimited scope statements on page 271. The scope of an IF statement can be terminated by any of the following: v An END-IF phrase at the same level of nesting v A separator period v If nested, by an ELSE phrase associated with an IF statement at a higher level of nesting
331
Transferring control
If the condition tested is true, one of the following actions takes place: v If statement-1 is specified, statement-1 is executed. If statement-1 contains a procedure branching or conditional statement, control is transferred according to the rules for that statement. If statement-1 does not contain a procedure-branching statement, the ELSE phrase, if specified, is ignored, and control passes to the next executable statement after the corresponding END-IF or separator period. v If NEXT SENTENCE is specified, control passes to an implicit CONTINUE statement immediately preceding the next separator period. If the condition tested is false, one of the following actions takes place: v If ELSE statement-2 is specified, statement-2 is executed. If statement-2 contains a procedure-branching or conditional statement, control is transferred, according to the rules for that statement. If statement-2 does not contain a procedure-branching or conditional statement, control is passed to the next executable statement after the corresponding END-IF or separator period. v If ELSE NEXT SENTENCE is specified, control passes to an implicit CONTINUE STATEMENT immediately preceding the next separator period. v If neither ELSE statement-2 nor ELSE NEXT SENTENCE is specified, control passes to the next executable statement after the corresponding END-IF or separator period. When the ELSE phrase is omitted, all statements following the condition and preceding the corresponding END-IF or the separator period for the sentence are considered to be part of statement-1.
Nested IF statements
When an IF statement appears as statement-1 or statement-2, or as part of statement-1 or statement-2, that IF statement is nested. Nested IF statements are considered to be matched IF, ELSE, and END-IF combinations proceeding from left to right. Thus, any ELSE encountered is matched with the nearest preceding IF that either has not been already matched with an ELSE or has not been implicitly or explicitly terminated. Any END-IF encountered is matched with the nearest preceding IF that has not been implicitly or explicitly terminated.
332
Language Reference
INITIALIZE statement
The INITIALIZE statement sets selected categories of data fields to predetermined values. It is functionally equivalent to one or more MOVE statements. When the REPLACING phrase is not used: v SPACE is the implied sending field for alphabetic, alphanumeric, national, alphanumeric-edited, and DBCS items. v ZERO is the implied sending field for numeric and numeric-edited items.
Format
INITIALIZE
identifier-1
REPLACING
ALPHABETIC ALPHANUMERIC NATIONAL NUMERIC ALPHANUMERIC-EDITED NUMERIC-EDITED DBCS EGCS
BY DATA
identifier-1 Receiving areas. identifier-1 must be a data item of a category that is valid as a receiving item in a MOVE statement. identifier-2, literal-1 Sending areas. If identifier-2 or literal-1 is of class national, the NATIONAL option of the REPLACING phrase must be specified. A subscripted item can be specified for identifier-1. A complete table can be initialized only by specifying identifier-1 as a group that contains the complete table. Usage note: The data description entry for identifier-1 can contain the DEPENDING ON phrase of the OCCURS clause. However, you cannot use the INITIALIZE statement to initialize a variably-located item or group that follows a DEPENDING ON phrase of the OCCURS clause within the same 01-level item. The data description entry for identifier-1 must not contain a RENAMES clause. Special registers can be specified for identifier-1 and identifier-2 only if they are valid receiving fields or sending fields, respectively, for the implied MOVE statements.
REPLACING phrase
When the REPLACING phrase is used:
333
v identifier-2 or literal-1 must be of a category that is valid as a sending field in a MOVE statement to an item of the corresponding category specified in the REPLACING phrase. A floating-point data item or floating-point literal will be treated as if it were in the NUMERIC category. v The same category cannot be repeated in a REPLACING phrase. v The keyword following the word REPLACING corresponds to a category of data shown in Classes and categories of data on page 153.
INITIALIZE statement rules

1. Whether identifier-1 references an elementary or group item, all operations are performed as if a series of MOVE statements had been written, each of which had an elementary item as a receiving field. If the REPLACING phrase is specified: v If identifier-1 references a group item, any elementary item within the data item referenced by identifier-1 is initialized only if it belongs to the category specified in the REPLACING phrase. v If identifier-1 references an elementary item, that item is initialized only if it belongs to the category specified in the REPLACING phrase. Initialization takes place as if the data item referenced by identifier-2 or literal-1 were the sending operand in an implicit MOVE statement to the identified item. All such elementary receiving fields, including all occurrences of table items within the group, are affected, with the following exceptions: v Index data items v Object references v Data items defined with USAGE IS POINTER, USAGE IS FUNCTION-POINTER, or USAGE IS PROCEDURE-POINTER v Elementary FILLER data items v Items that are subordinate to identifier-1 and contain a REDEFINES clause, or any items subordinate to such an item. (However, identifier-1 can contain a REDEFINES clause or be subordinate to a redefining item.) 2. The areas referenced by identifier-1 are initialized in the order (left to right) of the appearance of identifier-1 in the statement. Within a group receiving field, affected elementary items are initialized in the order of their definition within the group. 3. If identifier-1 occupies the same storage area as identifier-2, the result of the execution of this statement is undefined, even if these operands are defined by the same data description entry.
334
Language Reference
INSPECT statement
The INSPECT statement examines characters or groups of characters in a data item and does the following: v Counts the occurrences of a specific character (alphanumeric, DBCS, or national) in a data item (formats 1 and 3). v Counts the occurrences of specific characters and fills all or portions of a data item with specified characters, such as spaces or zeros (formats 2 and 3). v Converts all occurrences of specific characters in a data item to user-supplied replacement characters (format 4).
Format 1
INSPECT identifier-1 TALLYING
identifier-2
FOR
CHARACTERS phrase 1
ALL LEADING
phrase 1
phrase 1:
BEFORE AFTER identifier-4 literal-2
INITIAL
335
Format 2
INSPECT identifier-1 REPLACING
CHARACTERS BY
phrase 1
ALL LEADING FIRST
BY
phrase 1
phrase 1:
INITIAL
336
Language Reference
Format 3
INSPECT identifier-1 TALLYING
identifier-2
FOR
CHARACTERS phrase 1
ALL LEADING REPLACING
phrase 1
CHARACTERS BY
phrase 1
ALL LEADING FIRST
BY
phrase 1
phrase 1:
INITIAL
Format 4
INSPECT identifier-1 CONVERTING identifier-6 literal-4 TO identifier-7 literal-5
BEFORE AFTER
INITIAL
337
identifier-1 Is the inspected item and can be any of the following: v An alphanumeric data item v A numeric data item with USAGE DISPLAY v A DBCS data item v A national data item v An external floating-point item All identifiers and literals (except identifier-2) must be DBCS items, either DBCS literals or DBCS data items, if any are DBCS items. identifier-2 cannot be a DBCS item. DBCS characters, not bytes of data, are tallied in identifier-2. All identifiers and literals (except identifier-2) must be national data items or national literals if any are of class national. National character positions are tallied in identifier-2. None of the identifiers in an INSPECT statement can be windowed date fields.
TALLYING phrase (formats 1 and 3)

This phrase counts the occurrences of a specific character or special character in a data item. When identifier-1 is a DBCS data item, DBCS characters are counted; when identifier-1 is a national data item, national characters (encoding units) are counted; otherwise, alphanumeric characters (bytes) are counted. identifier-2 Is the count field, and must be an elementary integer item defined without the symbol P in its PICTURE character-string. identifier-2 cannot be an external floating-point item. You must initialize identifier-2 before execution of the INSPECT statement begins. identifier-3 or literal-1 Is the tallying field (the item whose occurrences will be tallied). identifier-3 can be any of the following: v An elementary alphanumeric data item v A DBCS data item v A national data item v A numeric data item with USAGE DISPLAY v An external floating-point item literal-1 can be an alphanumeric, DBCS, or national literal or any figurative constant that does not begin with the word ALL. When identifier-1 is national, the figurative constant is considered to be a one-character national literal. When identifier-1 is DBCS, you cannot specify a figurative constant. Otherwise, the figurative constant is considered to be a one-character alphanumeric literal. CHARACTERS When CHARACTERS is specified and neither the BEFORE nor AFTER phrase is specified, the count field (identifier-2) is increased by 1 for each character (including the space character) in the inspected item (identifier-1).
338
Language Reference
Thus, execution of the INSPECT TALLYING statement increases the value in the count field by the number of character positions in the inspected item. ALL When ALL is specified and neither the BEFORE nor AFTER phrase is specified, the count field (identifier-2) is increased by 1 for each nonoverlapping occurrence of the tallying comparand (identifier-3 or literal-1) in the inspected item (identifier-1), beginning at the leftmost character position and continuing to the rightmost.
LEADING When LEADING is specified and neither the BEFORE nor AFTER phrase is specified, the count field (identifier-2) is increased by 1 for each contiguous nonoverlapping occurrence of the tallying comparand in the inspected item (identifier-1), provided that the leftmost such occurrence is at the point where comparison began in the first comparison cycle for which the tallying comparand is eligible to participate. FIRST (format 3 only) When FIRST is specified and neither the BEFORE nor AFTER phrase is specified, the substitution field replaces the leftmost occurrence of the subject field in the inspected item (identifier-1).
REPLACING phrase (formats 2 and 3)

This phrase fills all or portions of a data item with specified characters, such as spaces or zeros. identifier-3 or literal-1 Is the subject field (it identifies the characters to be replaced). identifier-3 can be: v An elementary alphanumeric data item v A DBCS data item v A national data item v A numeric data item with USAGE DISPLAY v An external floating-point item literal-1 can be an alphanumeric, DBCS, or national literal or any figurative constant that does not begin with the word ALL. When identifier-1 is national, the figurative constant is considered to be a one-character national literal. When identifier-1 is DBCS, you cannot specify a figurative constant. In all other cases, the figurative constant is considered to be a one-character alphanumeric literal. identifier-5 or literal-3 Is the substitution field (the item that replaces the subject field). identifier-5 can be: v v v v An elementary alphanumeric data item A DBCS data item A national data item A numeric data item with USAGE DISPLAY
v An external floating-point item literal-3 can be an alphanumeric, DBCS, or national literal or any figurative constant that does not begin with the word ALL. The length of the
339
figurative constant is the same length as the subject field. When identifier-1 is national, the figurative constant is considered to be a national literal. When identifier-1 is DBCS, you cannot specify a figurative constant. Otherwise, the figurative constant is considered to be an alphanumeric literal. The subject field and the substitution field must be the same length. CHARACTERS BY When the CHARACTERS BY phrase is used, the substitution field must be one character position in length. When CHARACTERS BY is specified and neither the BEFORE nor AFTER phrase is specified, the substitution field replaces each character in the inspected item (identifier-1), beginning at the leftmost character position and continuing to the rightmost. ALL When ALL is specified and neither the BEFORE nor AFTER phrase is specified, the substitution field replaces each nonoverlapping occurrence of the subject field in the inspected item (identifier-1), beginning at the leftmost character position and continuing to the rightmost.
LEADING When LEADING is specified and neither the BEFORE nor AFTER phrase is specified, the substitution field replaces each contiguous nonoverlapping occurrence of the subject field in the inspected item (identifier-1), provided that the leftmost such occurrence is at the point where comparison began in the first comparison cycle for which this substitution field is eligible to participate. FIRST When FIRST is specified and neither the BEFORE nor AFTER phrase is specified, the substitution field replaces the leftmost occurrence of the subject field in the inspected item (identifier-1). When both the TALLYING and REPLACING phrases are specified (format 3), the INSPECT statement is executed as if an INSPECT TALLYING statement (format 1) were specified, immediately followed by an INSPECT REPLACING statement (format 2).
Replacement rules
The following replacement rules apply: v When the subject field is a figurative constant, the one-character substitution field replaces each character in the inspected item equivalent to the figurative constant. v When the substitution field is a figurative constant, the substitution field replaces each nonoverlapping occurrence of the subject field in the inspected item. v When the subject and substitution fields are character-strings, the character-string specified in the substitution field replaces each nonoverlapping occurrence of the subject field in the inspected item. v After replacement has occurred in a given character position in the inspected item, no further replacement for that character position is made in this execution of the INSPECT statement.
BEFORE and AFTER phrases (all formats)

This phrase narrows the set of items being tallied or replaced.
340
Language Reference
No more than one BEFORE phrase and one AFTER phrase can be specified for any one ALL, LEADING, CHARACTERS, FIRST or CONVERTING phrase. identifier-4 or literal-2 Is the delimiter. identifier-4 can be: v An elementary alphanumeric data item v A DBCS data item v A national data item v A numeric data item with USAGE DISPLAY v An external floating-point item literal-2 can be an alphanumeric, DBCS, or national literal or any figurative constant that does not begin with the word ALL. When identifier-1 is national, the figurative constant is considered to be a one-character national literal. When identifier-1 is DBCS, you cannot specify a figurative constant. In all other cases, the figurative constant is considered to be a one-character alphanumeric literal. Delimiters are not counted or replaced. However, the counting or replacing of the inspected item is bounded by the presence of the identifiers and literals. INITIAL The first occurrence of a specified item. The BEFORE and AFTER phrases change how counting and replacing are done: v When BEFORE is specified, counting or replacing of the inspected item (identifier-1) begins at the leftmost character position and continues until the first occurrence of the delimiter is encountered. If no delimiter is present in the inspected item, counting or replacing continues toward the rightmost character position. v When AFTER is specified, counting or replacing of the inspected item (identifier-1) begins with the first character position to the right of the delimiter and continues toward the rightmost character position in the inspected item. If no delimiter is present in the inspected item, no counting or replacement takes place.
CONVERTING phrase (format 4)

This phrase converts all occurrences of a specific character or string of characters in a data item (identifier-1) to user-supplied replacement characters. identifier-6 or literal-4 Specifies the character string to be replaced. identifier-6 can be: v An elementary alphanumeric data item v A DBCS data item v A national data item v A numeric data item with USAGE DISPLAY v An external floating-point item literal-4 can be an alphanumeric, DBCS, or national literal or any figurative constant that does not begin with the word ALL. When identifier-1 is
341
national, the figurative constant is considered to be a one-character national literal. When identifier-1 is DBCS, you cannot specify a figurative constant. In all other cases, the figurative constant is considered to be a one-character alphanumeric literal. The same character must not appear more than once in either literal-4 or identifier-6. identifier-7 or literal-5 Specifies the replacing character string. The replacing character string (identifier-7 or literal-5) must be the same size as the replaced character string (identifier-6 or literal-4). identifier-7 can be: v An elementary alphanumeric data item v A DBCS data item v A national data item v A numeric data item with USAGE DISPLAY v An external floating-point item literal-5 can be an alphanumeric, DBCS, or national literal or any figurative constant that does not begin with the word ALL. The length of the figurative constant is the same as the length of identifier-6 or literal-4. When identifier-1 is national, the figurative constant is considered to be a national literal. When identifier-1 is DBCS, you cannot specify a figurative constant. In all other cases, the figurative constant is considered to be an alphanumeric literal. A format-4 INSPECT statement is interpreted and executed as if a format-2 INSPECT statement had been written with a series of ALL phrases (one for each character of literal-4), specifying the same identifier-1. The effect is as if each single character of literal-4 were referenced as literal-1, and the corresponding single character of literal-5 referenced as literal-3. Correspondence between the characters of literal-4 and the characters of literal-5 is by ordinal position within the data item. If identifier-4, identifier-6, or identifier-7 occupies the same storage area as identifier-1, the result of the execution of this statement is undefined, even if they are defined by the same data description entry.
Data types for identifiers and literals

Table 37. Treatment of the content of data items When referenced by any identifier except identifier-2, the content of each ... Alphanumeric or alphabetic item Alphanumeric-edited, numeric-edited, or unsigned numeric (external decimal) item DBCS item National item Is treated ... As an alphanumeric character-string As if redefined as alphanumeric, with the INSPECT statement referring to the alphanumeric item As a DBCS character string As a national character string
342
Language Reference
Table 37. Treatment of the content of data items (continued) When referenced by any identifier except identifier-2, the content of each ... Signed numeric (external decimal) item Is treated ... As if moved to an unsigned external decimal item of the same length and then redefined as alphanumeric, with the INSPECT statement referring to the alphanumeric item. If the sign is a separate character, the byte containing the sign is not examined and, therefore, not replaced. External floating-point item As if redefined as alphanumeric, with the INSPECT statement referring to the alphanumeric item
Data flow
Except when the BEFORE or AFTER phrase is specified, inspection begins at the leftmost character position of the inspected item (identifier-1) and proceeds character-by-character to the rightmost position. The comparands of the following phrases are compared in the left-to-right order in which they are specified in the INSPECT statement: v TALLYING (literal-1 or identifier-3, ... ) v REPLACING (literal-3 or identifier-5, ... ) If any identifier is subscripted or reference modified, or is a function-identifier, the subscript, reference-modifier, or function is evaluated only once as the first operation in the execution of the INSPECT statement. For examples of TALLYING and REPLACING, see the Enterprise COBOL Programming Guide.
Comparison cycle
The comparison cycle consists of the following actions: 1. The first comparand is compared with an equal number of leftmost contiguous character positions in the inspected item. The comparand matches the inspected characters only if both are equal, character-for-character. If the CHARACTERS phrase is specified, an implied one-character comparand is used. The implied character is always considered to match the inspected character in the inspected item. 2. If no match occurs for the first comparand and there are more comparands, the comparison is repeated for each successive comparand until either a match is found or all comparands have been acted upon. 3. Depending on whether a match is found, these actions are taken: v If a match is found, tallying or replacing takes place as described in the TALLYING and REPLACING phrase descriptions. If there are more character positions in the inspected item, the first character position following the rightmost matching character is now considered to be in the leftmost character position. The process described in actions 1 and 2 is then repeated.
343
v If no match is found and there are more character positions in the inspected item, the first character position following the leftmost inspected character is now considered to be in the leftmost character position. The process described in actions 1 and 2 is then repeated. 4. Actions 1 through 3 are repeated until the rightmost character position in the inspected item either has been matched or has been considered as being in the leftmost character position. When the BEFORE or AFTER phrase is specified, the comparison cycle is modified, as described in BEFORE and AFTER phrases (all formats) on page 340.
Example of the INSPECT statement

The following figure shows an example of INSPECT statement results.
344
Language Reference
INVOKE statement
The INVOKE statement can create object instances of a COBOL or Java class and can invoke a method defined in a COBOL or Java class.
Format
INVOKE identifier-1 class-name-1 SELF SUPER literal-1 identifier-2 NEW
USING BY
VALUE LENGTH OF literal-2
identifier-3
RETURNING identifier-4
EXCEPTION imperative-statement-1 ON
NOT ON
END-INVOKE
identifier-1 Must be defined as USAGE OBJECT REFERENCE. The contents of identifier-1 specify the object on which a method is invoked. When identifier-1 is specified, either literal-1 or identifier-2 must be specified, identifying the name of the method to be invoked. The results of the INVOKE statement are undefined if either: v identifier-1 does not contain a valid reference to an object. v identifier-1 contains NULL. class-name-1 When class-name-1 is specified together with literal-1 or identifier-2, the INVOKE statement invokes a static or factory method of class-name-1. literal-1 or identifier-2 specifies the name of the method that is to be invoked. The method must be a static method if class-name-1 is a Java class; the method must be a factory method if class-name-1 is a COBOL class. When class-name-1 is specified together with NEW, the INVOKE statement creates a new object that is an instance of class class-name-1. You must specify class-name-1 in the REPOSITORY paragraph of the configuration section of the class or program that contains the INVOKE statement. SELF An implicit reference to the object used to invoke the currently executing
345
method. When SELF is specified, the INVOKE statement must appear within the procedure division of a method. SUPER An implicit reference to the object that was used to invoke the currently executing method. The resolution of the method to be invoked will ignore any methods declared in the class definition of the currently executing method and methods defined in any class derived from that class; thus the method invoked will be one that is inherited from an ancestor class. literal-1 The value of literal-1 is the name of the method to be invoked. The referenced object must support the method identified by literal-1. literal-1 must be an alphanumeric literal or a national literal. literal-1 is interpreted in a case-sensitive manner. The method name, the number of arguments, and the data types of the arguments in the USING phrase of the INVOKE statement are used to select the method with matching signature that is supported by the object. The method can be overloaded. identifier-2 An alphanumeric data item or a national data item that at run time contains the name of the method to be invoked. The referenced object must support the method identified by identifier-2. If identifier-2 is specified, identifier-1 must be defined as USAGE OBJECT REFERENCE without any optional phrases; that is, identifier-1 must be a universal object reference. The content of identifier-2 is interpreted in a case-sensitive manner. The method name, the number of arguments, and the data types of the arguments in the USING phrase of the INVOKE statement are used to select the method with matching signature that is supported by the object. The method can be overloaded. identifier-2 cannot be a windowed date field. NEW The NEW operand specifies that the INVOKE statement is to create a new object instance of the class class-name-1. class-name-1 must be specified. When class-name-1 is implemented in Java, the USING phrase of the INVOKE statement can be specified. The number of arguments and the data types of the arguments in the USING phrase of the INVOKE statement are used to select the Java constructor with matching signature that is supported by the class. An object instance of class class-name-1 is allocated, the selected constructor (or the default constructor) is executed, and a reference to the created object is returned. When class-name-1 is implemented in COBOL, the USING phrase of the INVOKE statement must not be specified. An object instance of class class-name-1 is allocated, instance data items are initialized to the values specified in associated VALUE clauses, and a reference to the created object is returned. When NEW is specified, you must also specify a RETURNING phrase as described in RETURNING phrase on page 347.
346
Language Reference
USING phrase
The USING phrase specifies arguments that are passed to the target method. The argument data types and argument linkage conventions are restricted to those supported by Java.
BY VALUE phrase
Arguments specified in an INVOKE statement must be passed BY VALUE. The BY VALUE phrase specifies that the value of the argument is passed, not a reference to the sending data item. The invoked method can modify the formal parameter corresponding to the BY VALUE argument, but any changes do not affect the argument since the invoked method has access to a temporary copy of the sending data item. identifier-3 Must be an elementary data item in the data division. The data type of identifier-3 must be one of the types supported for Java interoperation, as listed in Interoperable data types for COBOL and Java on page 349. When identifier-3 is an object reference, an explicit class-name must be specified in the data description entry for that object reference. That is, identifier-3 must not be a universal object reference. Miscellaneous cases that are also supported as identifier-3 are listed in Miscellaneous argument types for COBOL and Java on page 351, with their corresponding Java type. literal-2 Must be of a type suitable for Java interoperation. Supported literal forms are listed in Miscellaneous argument types for COBOL and Java on page 351, with their corresponding Java type. literal-2 must not be a DBCS literal. LENGTH OF identifier-3 Specifies that the length of identifier-3 is passed as an argument in the LENGTH OF special register. A LENGTH OF special register passed BY VALUE is treated as a PIC 9(9) binary value. For information about the LENGTH OF special register, see LENGTH OF on page 16.
RETURNING phrase
The RETURNING phrase specifies a data item that will contain the value returned from the invoked method. You can specify the RETURNING phrase on the INVOKE statement when invoking methods that are written in COBOL or Java. identifier-4 The RETURNING data item. identifier-4: v Must be defined in the data division v Must not be reference-modified v Is not changed if an EXCEPTION occurs The data type of identifier-4 must be one of the types supported for Java interoperation, as listed in Interoperable data types for COBOL and Java on page 349.
347
When identifier-4 is an object reference, in general it must be an object reference that is typed to a specific class. The exception is that for an INVOKE statement specifying the NEW operand, a universal object reference is also supported as the returning item. If identifier-4 is specified and the target method is written in COBOL, the target method must have a RETURNING phrase in its procedure division header. When the target method returns, its return value is assigned to identifier-4 using the rules for the SET statement if identifier-4 is described with USAGE OBJECT REFERENCE; otherwise, the rules for the MOVE statement are used. The RETURNING data item is an output-only parameter. On entry to the called method, the initial state of the PROCEDURE DIVISION RETURNING data item has an undefined and unpredictable value. You must initialize the PROCEDURE DIVISION RETURNING data item in the invoked method before you reference its value. The value that is passed back to the invoker is the final value of the PROCEDURE DIVISION RETURNING data item when the invoked method returns. See the Enterprise COBOL Programming Guide for discussion of local and global object references as defined in Java. These attributes affect the life-time of object references. Note: The RETURN-CODE special register is not set by execution of INVOKE statements.
Conformance requirements for the RETURNING phrase

For INVOKE statements specifying class-name-1 NEW, the RETURNING phrase is required. The returning item must be one of the following: v A universal object reference v An object reference specifying class-name-1 v An object reference specifying a superclass of class-name-1 For INVOKE statements without the NEW phrase, the RETURNING item specified in the method invocation and in the corresponding target method must satisfy the following requirements: v The presence or absence of a return value must be the same on the INVOKE statement and in the target method. v If the RETURNING item is not an object reference, and the target method is implemented in COBOL, the corresponding RETURNING item in the target method must have an identical data description entry. If the target method is implemented in Java, the method result type must be the Java type corresponding to the data type of the item specified in the RETURNING phrase, as described in Interoperable data types for COBOL and Java on page 349. v If the RETURNING item is an object reference, the returning item specified in the target method must be an object reference typed to the same class as the RETURNING item specified in the INVOKE statement. Note: Adherence to conformance requirements is the responsibility of the programmer. Conformance requirements are not verified by the compiler.
348
Language Reference
ON EXCEPTION phrase
An exception condition occurs when the identified object or class does not support a method with a signature that matches the signature of the method specified in the INVOKE statement. When an exception condition occurs, one of the following actions occurs: v If the ON EXCEPTION phrase is specified, control is transferred to imperative-statement-1. v If the ON EXCEPTION phrase is not specified, a severity-3 LE condition is raised at run time.
NOT ON EXCEPTION phrase

If an exception condition does not occur (that is, the identified method is supported by the specified object), control is transferred to the invoked method. After control is returned from the invoked method, control is then transferred: 1. To imperative-statement-2, if the NOT ON EXCEPTION phrase is specified. 2. To the end of the INVOKE statement if the NOT ON EXCEPTION phrase is not specified.
END-INVOKE phrase
This explicit scope terminator serves to delimit the scope of the INVOKE statement. An INVOKE statement that is terminated by END-INVOKE, along with its contained statements, becomes a unit that is treated as though it were an imperative statement. It can be specified as an imperative statement in a conditional statement; for example, in the exception phrase of another statement.
Interoperable data types for COBOL and Java

A subset of COBOL data types can be used for interoperation between COBOL and Java. You can specify the interoperable data types as arguments in COBOL INVOKE statements and as the RETURNING item in COBOL INVOKE statements. Similarly, you can pass these types as arguments from a Java method invocation expression and receive them as parameters in the USING phrase or as the RETURNING item in the procedure division header of a COBOL method. The following table lists the primitive Java types and the COBOL data types that are supported for interoperation and the correspondence between them.
Table 38. Interoperable Java and COBOL data types Java data type boolean
1
COBOL data type Conditional variable and two condition-names of the form: level-number data-name 88 data-name-false 88 data-name-true PIC X. VALUE X00. VALUE X01 THROUGH XFF.
byte short int long
Single-byte alphanumeric, PIC X or PIC A USAGE BINARY, COMP, COMP-4, or COMP-5, with a PICTURE clause of the form S9(n), where 1 <= n <= 4 USAGE BINARY, COMP, COMP-4, or COMP-5, with a PICTURE clause of the form S9(n), where 5 <= n <= 9 USAGE BINARY, COMP, COMP-4, or COMP-5, with a PICTURE clause of the form S9(n), where 10 <= n <= 18
349
Table 38. Interoperable Java and COBOL data types (continued) Java data type float
2 2
COBOL data type USAGE COMP-1 USAGE COMP-2 Single-character national: PIC N USAGE NATIONAL USAGE OBJECT REFERENCE class-name
double char
class types (object references)
1. Enterprise COBOL interprets a PIC X argument or parameter as the Java boolean type only when the PIC X data item is followed by exactly two condition-names of the form shown. In all other cases, a PIC X argument or parameter is interpreted as the Java byte type. 2. Java floating-point data is represented in IEEE floating-point, while Enterprise COBOL uses the IBM hexadecimal floating-point representation. The representations are automatically converted as necessary when Java methods are invoked from COBOL and when COBOL methods are invoked from Java.
In addition to the primitive types, Java Strings and arrays of Java primitive types can interoperate with COBOL. This requires specialized mechanisms provided by the COBOL run-time system and the Java Native Interface (JNI). In a Java program, to pass array data to COBOL or to receive array data from COBOL, you declare the array types using the usual Java syntax. In the COBOL program, you declare the array as an object reference that contains an instance of one of the special classes provided for array support. Conversion between the Java and COBOL types is automatic at the time of method invocation. In a Java program, to pass String data to COBOL or to receive String data from COBOL, you declare the array types using the usual Java syntax. In the COBOL program, you declare the String as an object reference that contains an instance of the special jstring class. Conversion between the Java and COBOL types is automatic at the time of method invocation. The following table lists the Java array and String data types and the corresponding special COBOL data types.
Table 39. Interoperable COBOL and Java array and String data types Java data type boolean[ ] byte[ ] short[ ] int[ ] long[ ] char[ ] Object[ ] String COBOL data type object reference jboooleanArray object reference jbyteArray object reference jshortArray object reference jintArray object reference jlongArray object reference jcharArray object reference jobjectArray object reference jstring
The following java array types are not currently supported:

Java data type float[ ] double[ ] COBOL data type object reference jfloatArray object reference jdoubleArray
350
Language Reference
You must code an entry in the repository paragraph for each special class that you want to use, just as you do for other classes. For example, to use jstring, code the following entry:
Configuration Section. Repository. Class jstring is jstring.
Alternatively, for the String type, the COBOL repository entry can specify an external class name of java.lang.String:
Repository. Class jstring is java.lang.String.
Callable services are provided by the Java Native Interface (JNI) for manipulating the COBOL objects of these types in COBOL. For example, callable services can be used to set COBOL alphanumeric or national data into a jstring object or to extract data from a jstring object. For details on use of JNI callable services for these and other purposes, see the Enterprise COBOL Programming Guide. For details on repository entries for class definitions, see REPOSITORY paragraph on page 114. For examples, see the Enterprise COBOL Programming Guide.
Miscellaneous argument types for COBOL and Java

Miscellaneous cases of COBOL items that can be used as arguments in an INVOKE statement are listed in the following table along with the corresponding Java type.
Table 40. COBOL miscellaneous argument types and corresponding Java types COBOL argument Reference-modified item of usage display with length one Reference-modified item of usage national with length one SHIFT-IN and SHIFT-OUT special registers LINAGE-COUNTER special register when its usage is binary LENGTH OF special register Corresponding Java data type byte char byte int int
The following table lists COBOL literal types that can be used as arguments in an INVOKE statement, with the corresponding Java type.
Table 41. COBOL literal argument types and corresponding Java types COBOL literal argument Fixed-point numeric literal with no decimal positions and with nine digits or less Floating-point numeric literal Figurative constant ZERO One-character alphanumeric literal One-character national literal Symbolic character Corresponding Java data type int double int byte char byte
351
Table 41. COBOL literal argument types and corresponding Java types (continued) COBOL literal argument Figurative constants SPACE, QUOTE, HIGH-VALUE, or LOW-VALUE Corresponding Java data type byte
352
Language Reference
MERGE statement
The MERGE statement combines 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. A MERGE statement can appear anywhere in the procedure division except in a declarative section. The MERGE statement is not supported for programs compiled with the THREAD compiler option.
Format
MERGE file-name-1 ON
data-name-1 KEY
USING file-name-2 SEQUENCE COLLATING IS alphabet-name-1
file-name-3
OUTPUT PROCEDURE IS
procedure-name-1 THROUGH THRU procedure-name-2
GIVING
file-name-4
file-name-1 The name given in the SD entry that describes the records to be merged. No file-name can be repeated in the MERGE statement. No pair of file-names in a MERGE statement can be specified in the same SAME AREA, SAME SORT AREA, or SAME SORT-MERGE AREA clause. However, any file-names in the MERGE statement can be specified in the same SAME RECORD AREA clause. When the MERGE statement is executed, all records contained in file-name-2, file-name-3, ... , are accepted by the merge program and then merged according to the keys specified.
ASCENDING/DESCENDING KEY phrase

This phrase specifies that records are to be processed in an ascending or descending sequence (depending on the phrase specified), based on the specified merge keys.
353
data-name-1 Specifies a KEY data item on which the merge will be based. Each such data-name must identify a data item in a record associated with file-name-1. The data-names following the word KEY are listed from left to right in the MERGE statement in order of decreasing significance without regard to how they are divided into KEY phrases. The leftmost data-name is the major key, the next data-name is the next most significant key, and so forth. The following rules apply: v A specific key data item must be physically located in the same position and have the same data format in each input file. However, it need not have the same data-name. v If file-name-1 has more than one record description, the KEY data items need be described in only one of the record descriptions. v If file-name-1 contains variable-length records, all of the KEY data-items must be contained within the first n character positions of the record, where n equals the minimum records size specified for file-name-1. v KEY data items must not contain an OCCURS clause or be subordinate to an item that contains an OCCURS clause. v KEY data items cannot be variably located. v KEY data items cannot be group items that contain variable-occurrence data items. v KEY data items can be qualified. v KEY data items can be: Alphabetic, alphanumeric, alphanumeric-edited, numeric-edited, or numeric data items Internal or external floating-point data items National data items Windowed date fields, under these conditions: - The input files specified in the USING phrase can be sequential, relative, or indexed, but must not have any record key, alternate record key, or relative key in the same position as a windowed date merge key. The file system does not support windowed date fields as keys, so any ordering imposed by the file system could conflict with the windowed date field support for the merge operation. In fact, if the merge is to succeed, then input files must have already been sorted into the same order as that specified by the MERGE statement, including any windowed date ordering. - The GIVING phrase must not specify an indexed file, because the (binary) ordering assumed or imposed by the file system conflicts with the windowed date ordering provided in the output of the merge. Attempting to write the windowed date merge output to such an indexed file will either fail or reimpose binary ordering, depending on how the file is accessed (as specified in the ACCESS MODE clause in the file-control entry). - If an alphanumeric windowed date field is specified as a KEY for a MERGE statement, the collating sequence in effect for the merge operation must be EBCDIC. The COLLATING SEQUENCE phrase of the MERGE statement or, if this phrase is not specified, a PROGRAM COLLATING SEQUENCE clause in the OBJECT-COMPUTER paragraph, must not specify a collating sequence other than EBCDIC or NATIVE.
354
Language Reference
If the MERGE statement meets these conditions, the merge operation takes advantage of SORT Year 2000 features, provided that the execution environment includes a sort product that supports century windowing. A year-last windowed date field can be specified as a KEY for a MERGE statement and can thereby exploit the corresponding century windowing capability of the sort product. For more information about using windowed date fields as KEY data items, see the Enterprise COBOL Programming Guide. The direction of the merge operation depends on the specification of the ASCENDING or DESCENDING keywords as follows: v When ASCENDING is specified, the sequence is from the lowest key value to the highest key value. v When DESCENDING is specified, the sequence is from the highest key value to the lowest key value. | | If the KEY is a national item, the sequence of the KEY values is based on the binary values of the national characters. When the COLLATING SEQUENCE phrase is not specified, the key comparisons are performed according to the rules for comparison of operands in a relation condition (see Relation condition on page 250). When the COLLATING SEQUENCE phrase is specified, the indicated collating sequence is used for key data items of alphabetic, alphanumeric, alphanumeric-edited, external floating-point, and numeric-edited categories. For all other key data items, the comparisons are performed according to the rules for comparison of operands in a relation condition.
COLLATING SEQUENCE phrase

This phrase specifies the collating sequence to be used in alphanumeric comparisons for the KEY data items in this merge operation. The COLLATING SEQUENCE phrase has no effect for keys that are not alphabetic or alphanumeric. alphabet-name-1 Must be specified in the ALPHABET clause of the SPECIAL-NAMES paragraph. Any one of the alphabet-name clause phrases can be specified, with the following results: STANDARD-1 The ASCII collating sequence is used for all alphanumeric comparisons. (The ASCII collating sequence is shown in Appendix C, EBCDIC and ASCII collating sequences, on page 549.) STANDARD-2 The 7-bit code defined in the International Reference Version of ISO/IEC 646, 7-bit coded character set for information interchange is used for all alphanumeric comparisons. NATIVE The EBCDIC collating sequence is used for all alphanumeric
355
comparisons. (The EBCDIC collating sequence is shown in Appendix C, EBCDIC and ASCII collating sequences, on page 549.) EBCDIC The EBCDIC collating sequence is used for all alphanumeric comparisons. (The EBCDIC collating sequence is shown in Appendix C, EBCDIC and ASCII collating sequences, on page 549.) literal The collating sequence established by the specification of literals in the ALPHABET-NAME clause is used for all alphanumeric comparisons.
When the COLLATING SEQUENCE phrase is omitted, the PROGRAM COLLATING SEQUENCE clause (if specified) in the OBJECT-COMPUTER paragraph identifies the collating sequence to be used. When both the COLLATING SEQUENCE phrase of the MERGE statement and the PROGRAM COLLATING SEQUENCE clause of the OBJECT-COMPUTER paragraph are omitted, the EBCDIC collating sequence is used. (See Appendix C, EBCDIC and ASCII collating sequences, on page 549.)
USING phrase
file-name-2, file-name-3, ... Specifies the input files. During the MERGE operation, all the records on file-name-2, file-name-3, ... (that is, the input files) are transferred to file-name-1. At the time the MERGE statement is executed, these files must not be open. The input files are automatically opened, read, and closed. If DECLARATIVE procedures are specified for these files for input operations, the declaratives will be driven for errors if errors occur. All input files must specify sequential or dynamic access mode and be described in FD entries in the data division. If file-name-1 contains variable-length records, the size of the records contained in the input files (file-name-2, file-name-3, ...) must be neither less than the smallest record nor greater than the largest record described for file-name-1. If file-name-1 contains fixed-length records, the size of the records contained in the input files must not be greater than the largest record described for file-name-1. For more information, see the Enterprise COBOL Programming Guide.
GIVING phrase
file-name-4, ... Specifies the output files. When the GIVING phrase is specified, all the merged records in file-name-1 are automatically transferred to the output files (file-name-4...). All output files must specify sequential or dynamic access mode and be described in FD entries in the data division. If the output files (file-name-4, ...) contain variable-length records, the size of the records contained in file-name-1 must be neither less than the smallest record nor
356
Language Reference
greater than the largest record described for the output files. If the output files contain fixed-length records, the size of the records contained in file-name-1 must not be greater than the largest record described for the output files. For more information, see the Enterprise COBOL Programming Guide. At the time the MERGE statement is executed, the output files (file-name-4, ...) must not be open. The output files are automatically opened, read, and closed. If DECLARATIVE procedures are specified for these files for output operations, the declaratives will be driven for errors if errors occur.
OUTPUT PROCEDURE phrase

This phrase specifies the name of a procedure that is to select or modify output records from the merge operation. procedure-name-1 Specifies the first (or only) section or paragraph in the OUTPUT PROCEDURE. procedure-name-2 Identifies the last section or paragraph of the OUTPUT PROCEDURE. | | | | | | | | | The OUTPUT PROCEDURE can consist of any procedure needed to select, modify, or copy the records that are made available one at time by the RETURN statement in merged order from the file referenced by file-name-1. The range includes all statements that are executed as the result of a transfer of control by CALL, EXIT, GO TO, PERFORM, and XML PARSE statements in the range of the output procedure. The range also includes all statements in declarative procedures that are executed as a result of the execution of statements in the range of the output procedure. The range of the output procedure must not cause the execution of any MERGE, RELEASE, or SORT statement. If an output procedure is specified, control passes to it after the file referenced by file-name-1 has been sequenced by the MERGE statement. The compiler inserts a return mechanism at the end of the last statement in the output procedure and when control passes the last statement in the output procedure, the return mechanism provides the termination of the merge and then passes control to the next executable statement after the MERGE statement. Before entering the output procedure, the merge procedure reaches a point at which it can select the next record in merged order when requested. The RETURN statements in the output procedure are the requests for the next record. The OUTPUT PROCEDURE phrase is similar to a basic PERFORM statement. For example, if you name a procedure in an OUTPUT PROCEDURE, that procedure is executed during the merging operation just as if it were named in a PERFORM statement. As with the PERFORM statement, execution of the procedure is terminated after the last statement completes execution. The last statement in an OUTPUT PROCEDURE can be the EXIT statement (see EXIT statement on page 325).
MERGE special registers

SORT-CONTROL special register You identify the sort control file (through which you can specify additional options to the sort/merge function) with the SORT-CONTROL special register.
357
If you use a sort control file to specify control statements, the values specified in the sort control file take precedence over those in the other SORT special registers. For information, see SORT-CONTROL on page 19. SORT-MESSAGE special register For information, see SORT-MESSAGE on page 20. The special register SORT-MESSAGE is equivalent to an option control statement keyword in the sort control file. SORT-RETURN special register For information, see SORT-RETURN on page 21.
If the MERGE statement appears in a section that is not in an independent segment, then any output procedure referenced by that MERGE statement must appear either: v Totally within nonindependent segments, or v Wholly contained in a single independent segment If a MERGE statement appears in an independent segment, then any output procedure referenced by that MERGE statement must be contained either: v Totally within nonindependent segments, or v Wholly within the same independent segment as that MERGE statement
358
Language Reference
MOVE statement
The MOVE statement transfers data from one area of storage to one or more other areas.
Format 1
MOVE
TO
identifier-2
Format 2
MOVE CORRESPONDING CORR identifier-1 TO identifier-2
identifier-1, literal-1 Sending area identifier-2 Receiving areas When format 1 is specified, all identifiers can be either group or elementary items. The data in the sending area is moved into the data item referenced by each identifier-2 in the order in which the identifier-2 data items are specified in the MOVE statement. See Elementary moves on page 360 and Group moves on page 364. When format 2 is specified, both identifiers must be group items. CORR is an abbreviation for, and is equivalent to, CORRESPONDING. When CORRESPONDING is specified, selected items in identifier-1 are moved to identifier-2 according to the rules for the CORRESPONDING phrase on page 272. The results are the same as if each pair of CORRESPONDING identifiers were referenced in a separate MOVE statement. Data items described with the following types of usage cannot be specified in a MOVE statement: v INDEX v POINTER v FUNCTION-POINTER v PROCEDURE-POINTER v OBJECT REFERENCE A data item defined with a usage of INDEX, POINTER, FUNCTION-POINTER, PROCEDURE-POINTER, or OBJECT REFERENCE can be part of a group item that is referenced in a MOVE CORRESPONDING statement; however, no movement of data from those data items will take place.
359
The evaluation of the length of the sending or receiving area can be affected by the DEPENDING ON phrase of the OCCURS clause (see OCCURS clause on page 181). If the sending field (identifier-1) is reference-modified or subscripted, or is an alphanumeric, alphabetic, or national function-identifier, the reference-modifier, subscript, or function is evaluated only once, immediately before data is moved to the first of the receiving operands. Any length evaluation, subscripting, or reference-modification associated with a receiving field (identifier-2) is evaluated immediately before the data is moved into that receiving field. For example, the result of the statement:
MOVE A(B) TO B, C(B).
is equivalent to:
MOVE A(B) TO TEMP. MOVE TEMP TO B. MOVE TEMP TO C(B).
where TEMP is defined as an intermediate result item. The subscript B has changed in value between the time that the first move took place and the time that the final move to C(B) is executed. For further information about intermediate results, see the Enterprise COBOL Programming Guide. After execution of a MOVE statement, the sending fields contain the same data as before execution. Note: Overlapping operands in a MOVE statement can cause unpredictable results.
Elementary moves
An elementary move is one in which the receiving item is an elementary item and the sending item is an elementary item or a literal. Each elementary item belongs to one of the following categories: v Alphabetic: includes alphabetic data items and the figurative constant SPACE. v Alphanumeric: includes alphanumeric data items, alphanumeric literals, the figurative constant ALL alphanumeric-literal, and all other figurative constants (except NULL) when used in a context requiring an alphanumeric data item. v Alphanumeric-edited: includes alphanumeric-edited data items. v Numeric: includes numeric data items, numeric literals, and the figurative constant ZERO (when ZERO is moved to a numeric or numeric-edited item). v Numeric-edited: includes numeric-edited data items. v Floating-point: includes internal floating-point items (defined as USAGE COMP-1 or USAGE COMP-2), external floating-point items (defined as USAGE DISPLAY), and floating-point literals. v DBCS: includes DBCS data items, DBCS literals, and the figurative constant ALL DBCS-literal.
360
Language Reference
v National: includes national data items, national literals, national functions, and figurative constants ZERO, SPACE, QUOTE, and ALL literal, where literal is a national literal. Any necessary conversion of data from one form of internal representation to another takes place during the move, along with any specified editing in, or de-editing implied by, the receiving item. The following rules outline the execution of valid elementary moves. When the receiving field is: Alphabetic: v Alignment and any necessary space filling or truncation occur as described under Alignment rules on page 154. v If the size of the sending item is greater than the size of the receiving item, excess characters on the right are truncated after the receiving item is filled. Alphanumeric or alphanumeric-edited: v Alignment and any necessary space filling or truncation take place, as described under Alignment rules on page 154. v If the size of the sending item is greater than the size of the receiving item, excess characters on the right are truncated after the receiving item is filled. v If the sending item has an operational sign, the unsigned value is used. If the operational sign occupies a separate character, that character is not moved, and the size of the sending item is considered to be one less character than the actual size. National: v If the sending item is an alphabetic, alphanumeric, alphanumeric-edited, DBCS, numeric integer, or numeric-edited data item or an alphanumeric literal or alphanumeric function, the sending data is converted to national characters and treated as though it were moved to a temporary national data item of a length not to cause truncation or padding. The source code page used for the conversion is the one in effect for the CODEPAGE compiler option when the source code was compiled. The resulting national data item is treated as the sending data item. v If the sending data item is national, it is used as the sending data item without conversion. v Alignment and any necessary space filling or truncation take place as described under Alignment rules on page 154. The programmer is responsible for ensuring that multiple encoding units that together form a graphic character are not split by truncation. v If the sending item has an operational sign, the unsigned value is used. If the operational sign occupies a separate character, that character is not moved, and the size of the sending item is considered to be one less character than the actual size. Numeric or numeric-edited: v Except where zeros are replaced because of editing requirements, alignment by decimal point and any necessary zero filling take place, as described under Alignment rules on page 154.
361
v If the receiving item is signed, the sign of the sending item is placed in the receiving item, with any necessary sign conversion. If the sending item is unsigned, a positive operational sign is generated for the receiving item. v If the receiving item is unsigned, the absolute value of the sending item is moved, and no operational sign is generated for the receiving item. v When the sending item is alphanumeric, the data is moved as if the sending item were described as an unsigned integer. v When the sending item is floating-point, the data is first converted to either a binary or internal decimal representation and is then moved. v De-editing allows moving a numeric-edited data item into a numeric or numeric-edited receiver. The compiler accomplishes this by first establishing the unedited value of the numeric-edited item (this value can be signed), then moving the unedited numeric value to the receiving numeric or numeric-edited data item. Floating-point: v The sending item is converted first to internal floating-point and then moved. v When data is moved to or from an external floating-point item, the data is converted first to or from its equivalent internal floating-point value. DBCS: v No conversion takes place. v If the sending and receiving items are not the same size, the data item will be either truncated or padded with DBCS spaces on the right. Notes: 1. If the receiving field is alphanumeric, numeric-edited, or national and the sending field is numeric, any digit positions described with picture symbol P are considered to have the value zero. Each P is counted in the size of the sending item. 2. If the receiving field is numeric and the sending field is an alphanumeric literal or an ALL literal, all characters of the literal must be numeric characters. The following table shows valid and invalid elementary moves for each category. In the table: v YES = Move is valid. v NO = Move is invalid.
Table 42. Valid and invalid elementary moves Alphabetic receiving item Alphabetic and SPACE sending item Alphanumeric sending item2 Alphanumericedited sending item Yes Alphanumeric receiving item Yes AlphaExternal numeric Numeric- floatingedited Numeric edited point receiving receiving receiving receiving item item item item Yes No No No Internal floatingpoint DBCS National receiving receiving receiving item item1 item No No Yes
Yes Yes
Yes Yes
Yes Yes
Yes3 No
Yes3 No
Yes8 No
Yes8 No
No No
Yes Yes
362
Language Reference
Table 42. Valid and invalid elementary moves (continued) Alphabetic receiving item Numeric integer and ZERO sending item4 Numeric noninteger sending item5 Numeric-edited sending item Floating-point sending item6 DBCS sending item7 National sending item9 No Alphanumeric receiving item Yes AlphaExternal numeric Numeric- floatingedited Numeric edited point receiving receiving receiving receiving item item item item Yes Yes Yes Yes Internal floatingpoint DBCS National receiving receiving receiving item item1 item Yes No Yes
No
No
No
Yes
Yes
Yes
Yes
No
No
No No No No
Yes No No No
Yes No No No
Yes Yes No No
Yes Yes No No
Yes Yes No No
Yes Yes No No
No No Yes No
Yes No Yes Yes
1. Includes DBCS data items. 2. Includes alphanumeric literals. 3. Figurative constants and alphanumeric literals must consist only of numeric characters and will be treated as numeric integer fields. 4. Includes integer numeric literals. 5. Includes noninteger numeric literals. 6. Includes floating-point literals, external floating-point data items (USAGE DISPLAY), and internal floating-point data items (USAGE COMP-1 or USAGE COMP-2). 7. Includes DBCS data-items, DBCS literals, and SPACE. 8. Figurative constants and alphanumeric literals must consist only of numeric characters and will be treated as numeric integer fields. The ALL literal cannot be used as a sending item. 9. Includes national data items, national literals, national functions, and figurative constants ZERO, SPACE, QUOTE, and ALL national literal.
Moves involving date fields

If the sending item is specified as a year-last date field, then all receiving fields must also be year-last date fields with the same date format as the sending item. If a year-last date field is specified as a receiving item, then the sending item must be either a nondate or a year-last date field with the same date format as the receiving item. In both cases, the move is then performed as if all items were nondates. Moves involving date fields (Table 43 on page 364) describes the behavior of moves involving non-year-last date fields. If the sending item is a date field, then the receiving item must be a compatible date field. If the sending and receiving items are both date fields, then they must be compatible; that is, they must have the same date format, except for the year part, which can be windowed or expanded. This table uses the following terms to describe the moves: Normal The move is performed with no date-sensitive behavior, as if the sending and receiving items were both nondates.
363
Expanded The windowed date field sending item is treated as if it were first converted to expanded form, as described under Semantics of windowed date fields on page 175. Invalid The move is not allowed.
Table 43. Moves involving date fields Nondate receiving item Nondate sending item Windowed date field sending item Expanded date field sending item Normal Invalid Invalid Windowed date field receiving item Normal Normal Normal1 Expanded date field receiving item Normal Expanded Normal
1. A move from an expanded date field to a windowed date field is, in effect, a windowed move, because it truncates the century component of the expanded date field. If the move is alphanumeric, it treats the receiving windowed date field as if its data description specified JUSTIFIED RIGHT. This is true even if the receiving windowed date field is a group item, for which the JUSTIFIED clause cannot be specified.
Moves involving file record areas

| | | | | The successful execution of an OPEN statement for a given file makes the record area for that file available. You can move data to or from the record description entries associated with a file only when the file is in the open status. Execution of an implicit or explicit CLOSE statement removes a file from open status and makes the record area unavailable.
Group moves
A group move is one in which one or both of the sending and receiving fields are group items. A group move is treated exactly as though it were an alphanumeric elementary move, except that there is no conversion of data from one form of internal representation to another. In a group move, the receiving area is filled without consideration for the individual elementary items contained within either the sending area or the receiving area, except as noted in the OCCURS clause. (See OCCURS clause on page 181.) All group moves are valid.
364
Language Reference
MULTIPLY statement
The MULTIPLY statement multiplies numeric items and sets the values of data items equal to the results.
Format 1
MULTIPLY
BY
NOT ON
END-MULTIPLY
In format 1, the value of identifier-1 or literal-1 is multiplied by the value of identifier-2; the product is then placed in identifier-2. For each successive occurrence of identifier-2, the multiplication takes place in the left-to-right order in which identifier-2 is specified.
Format 2
MULTIPLY identifier-1 literal-1 BY identifier-2 literal-2
GIVING
NOT ON
END-MULTIPLY
365
In format 2, the value of identifier-1 or literal-1 is multiplied by the value of identifier-2 or literal-2. The product is then stored in the data items referenced by identifier-3. For all formats: identifier-1, identifier-2 Must name an elementary numeric item. identifier-1 and identifier-2 cannot be date fields. literal-1, literal-2 Must be a numeric literal. For format-2: identifier-3 Must name an elementary numeric or numeric-edited item. identifier-3, the GIVING phrase identifier, is the only identifier in the MULTIPLY statement that can be a date field. If identifier-3 names a date field, see Storing arithmetic results that involve date fields on page 245 for details on how the product is stored in identifier-3. Floating-point data items and literals can be used anywhere a numeric data item or literal can be specified. When the ARITH(COMPAT) compiler option is in effect, the composite of operands can contain a maximum of 30 digits. When the ARITH(EXTEND) compiler option is in effect, the composite of operands can contain a maximum of 31 digits. For more information, see Arithmetic statement operands on page 276 and the details on arithmetic intermediate results in the Enterprise COBOL Programming Guide.
ROUNDED phrase
For formats 1 and 2, see ROUNDED phrase on page 273.
SIZE ERROR phrases

For formats 1 and 2, see SIZE ERROR phrases on page 274.
END-MULTIPLY phrase
This explicit scope terminator serves to delimit the scope of the MULTIPLY statement. END-MULTIPLY permits a conditional MULTIPLY statement to be nested in another conditional statement. END-MULTIPLY can also be used with an imperative MULTIPLY statement. For more information, see Delimited scope statements on page 271.
366
Language Reference
OPEN statement
The OPEN statement initiates the processing of files. It also checks or writes labels, or both.
OPEN
INPUT
file-name-1 (1) REVERSED (1) NO REWIND WITH
OUTPUT
file-name-2 NO REWIND WITH
I-O
file-name-3
EXTEND
file-name-4
Notes: 1 The REVERSED and WITH NO REWIND phrases are not valid for VSAM files.
OPEN
INPUT
file-name-1
OUTPUT
file-name-2
I-O
file-name-3
EXTEND
file-name-4
367
OPEN
INPUT
file-name-1
OUTPUT
file-name-2
EXTEND
file-name-4
The phrases INPUT, OUTPUT, I-O, and EXTEND specify the mode to be used for opening the file. 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 can appear in any order. INPUT Permits input operations. OUTPUT Permits output operations. This phrase can be specified when the file is being created. Do not specify OUTPUT for files that: v Contain records. The file will be replaced by new data. If the OUTPUT phrase is specified for a file that already contains records, the data set must be defined as reusable and cannot have an alternate index. The records in the file will be replaced by the new data and any ALTERNATE RECORD KEY clause in the SELECT statement will be ignored. v Are defined with a DD dummy card. Unpredictable results can occur. I-O Permits both input and output operations. The I-O phrase can be specified only for files assigned to direct access devices. The I-O phrase is not valid for line-sequential files. EXTEND Permits output operations that append to or create a file. The EXTEND phrase is allowed for sequential access files only if the new data is written in ascending sequence. The EXTEND phrase is allowed for files that specify the LINAGE clause. For QSAM files, do not specify the EXTEND phrase for a multiple file reel. If you want to append to a file, but are unsure if the file exists, use the SELECT OPTIONAL clause before opening the file in EXTEND mode. The file will be created or appended to, depending on whether the file exists. file-name-1, file-name-2, file-name-3, file-name-4 Designate a file upon which the OPEN statement is to operate. If more than one file is specified, the files need not have the same organization or access mode. Each file-name must be defined in an FD entry in the data
368
Language Reference
division and must not name a sort or merge file. The FD entry must be equivalent to the information supplied when the file was defined. REVERSED Valid only for sequential single-reel files. REVERSED is not valid for VSAM files. If the concept of reels has no meaning for the storage medium (for example, a direct access device), the REVERSED and NO REWIND phrases do not apply. NO REWIND Valid only for sequential single-reel files. It is not valid for VSAM files.
General rules
v If a file opened with the INPUT phrase is an optional file that is not present, the OPEN statement sets the file position indicator to indicate that an optional input file is not present. v Execution of an OPEN INPUT or OPEN I-O statement sets the file position indicator: For indexed files, to the characters with the lowest ordinal position in the collating sequence associated with the file. v For sequential and relative files, to 1. When the EXTEND phrase is specified, the OPEN statement positions the file immediately after the last record written in the file. (The record with the highest prime record key value for indexed files or relative key value for relative files is considered the last record.) Subsequent WRITE statements add records as if the file were opened OUTPUT. The EXTEND phrase can be specified when a file is being created; it can also be specified for a file that contains records, or that has contained records that have been deleted. For VSAM files, if no records exist in the file, the file position indicator is set so that the first format 1 READ statement executed results in an AT END condition. When NO REWIND is specified, the OPEN statement execution does not reposition the file; prior to OPEN statement execution, the file must be positioned at its beginning. When the NO REWIND phrase is specified (or when both the NO REWIND and REVERSE phrases are omitted), file positioning is specified with the LABEL parameter of the DD statement. When REVERSED is specified, OPEN statement execution positions the QSAM file at its end. Subsequent READ statements make the data records available in reversed order, starting with the last record. When OPEN REVERSED is specified, the record format must be fixed. When the REVERSED, NO REWIND, or EXTEND phrases are not specified, OPEN statement execution positions the file at its beginning.
v v
If the PASSWORD clause is specified in the file-control entry, the password data item must contain a valid password before the OPEN statement is executed. If a valid password is not present, OPEN statement execution is unsuccessful.
Label records
If label records are specified for the file when the OPEN statement is executed, the labels are processed according to the standard label conventions, as follows: INPUT files The beginning labels are checked.
369
OUTPUT files The beginning labels are written. I-O files The labels are checked; new labels are then written. EXTEND files The following procedures are executed: v Beginning file labels are processed only if this is a single-volume file. v Beginning volume labels of the last existing volume are processed as though the file was being opened with the INPUT phrase. v Existing ending file labels are processed as though the file was being opened with the INPUT phrase; they are then deleted. v Processing continues as if the file were opened as an OUTPUT file. When label records are specified but not present, or are present but not specified, execution of the OPEN statement is unpredictable.
OPEN statement notes

1. The successful execution of an OPEN statement determines the availability of the file and results in that file being in open mode. A file is available if it is physically present and is recognized by the input-output control system. The following table shows the results of opening available and unavailable files. For more information regarding file availability, see the Enterprise COBOL Programming Guide.
Table 44. Availability of a file Opened as INPUT INPUT (optional file) I-O I-O (optional file) OUTPUT File is available Normal open Normal open Normal open Normal open Normal open; the file contains no records Normal open Normal open File is unavailable Open is unsuccessful. Normal open; the first read causes the at end condition or the invalid key condition. Open is unsuccessful. Open causes the file to be created. Open causes the file to be created.
EXTEND EXTEND (optional file)
Open is unsuccessful. Open causes the file to be created.
| | | |
2. The successful execution of the OPEN statement places the file in open status and makes the associated record area available to the program. 3. The OPEN statement does not obtain or release the first data record. 4. You can move data to or from the record area only when the file is in open status. 5. An OPEN statement must be successfully executed prior to the execution of any of the permissible input-output statements, except a SORT or MERGE statement with the USING or GIVING phrase. In the following table, an X indicates that the specified statement can be used with the open mode given at the top of the column.
370
Language Reference
Table 45. Permissible statements for sequential files Statement READ WRITE REWRITE Input open mode X X X Output open mode I-O open mode X X Extend open mode
In the following table, an X indicates that the specified statement, used in the access mode given for that row, can be used with the open mode given at the top of the column.
Table 46. Permissible statements for indexed and relative files File access mode Sequential Statement READ WRITE REWRITE START DELETE Random READ WRITE REWRITE START DELETE Dynamic READ WRITE REWRITE START DELETE X X X X X X X X X X X X Input open mode X X X X X X X X Output open I-O open mode mode X X Extend open mode
In the following table, an X indicates that the specified statement can be used with the open mode given at the top of the column.
Table 47. Permissible statements for line-sequential files Statement READ WRITE REWRITE Input open mode X X X Output open mode I-O open mode Extend open mode
1. A file can be opened for INPUT, OUTPUT, I-O, or EXTEND (sequential and line-sequential files only) in the same program. After the first OPEN statement execution for a given file, each subsequent OPEN statement execution must be preceded by a successful CLOSE file statement execution without the REEL or UNIT phrase (for QSAM files only), or the LOCK phrase. 2. If the FILE STATUS clause is specified in the file-control entry, the associated file status key is updated when the OPEN statement is executed.
371
3. If an OPEN statement is issued for a file already in the open status, the EXCEPTION/ERROR procedure (if specified) for this file is executed.
372
Language Reference
PERFORM statement
The PERFORM statement transfers control explicitly to one or more procedures and implicitly returns control to the next executable statement after execution of the specified procedures is completed. The PERFORM statement is: An out-of-line PERFORM statement When procedure-name-1 is specified. An in-line PERFORM statement When procedure-name-1 is omitted. An in-line PERFORM must be delimited by the END-PERFORM phrase. The in-line and out-of-line formats cannot be combined. For example, if procedure-name-1 is specified, imperative statements and the END-PERFORM phrase must not be specified. The PERFORM statement formats are: v Basic PERFORM v TIMES phrase PERFORM v UNTIL phrase PERFORM v VARYING phrase PERFORM
Basic PERFORM statement

The procedures referenced in the basic PERFORM statement are executed once, and control then passes to the next executable statement following the PERFORM statement. Note: A PERFORM statement must not cause itself to be executed. A recursive PERFORM statement can cause unpredictable results.
Format 1
PERFORM procedure-name-1 THROUGH procedure-name-2 THRU END-PERFORM imperative-statement-1
procedure-name-1, procedure-name-2 Must name a section or paragraph in the procedure division. When both procedure-name-1 and procedure-name-2 are specified, if either is a procedure-name in a declarative procedure, both must be procedure-names in the same declarative procedure. If procedure-name-1 is specified, imperative-statement-1 and the END-PERFORM phrase must not be specified. If procedure-name-1 is omitted, imperative-statement-1 and the END-PERFORM phrase must be specified.
373
imperative-statement-1 The statements to be executed for an in-line PERFORM An in-line PERFORM statement functions according to the same general rules as an otherwise identical out-of-line PERFORM statement, except that statements contained within the in-line PERFORM are executed in place of the statements contained within the range of procedure-name-1 (through procedure-name-2, if specified). Unless specifically qualified by the word in-line or the word out-of-line, all the rules that apply to the out-of-line PERFORM statement also apply to the in-line PERFORM. Whenever an out-of-line PERFORM statement is executed, control is transferred to the first statement of the procedure named procedure-name-1. Control is always returned to the statement following the PERFORM statement. The point from which this control is returned is determined as follows: v If procedure-name-1 is a paragraph name and procedure-name-2 is not specified, the return is made after the execution of the last statement of the procedure-name-1 paragraph. v If procedure-name-1 is a section name and procedure-name-2 is not specified, the return is made after the execution of the last statement of the last paragraph in the procedure-name-1 section. v If procedure-name-2 is specified and it is a paragraph name, the return is made after the execution of the last statement of the procedure-name-2 paragraph. v If procedure-name-2 is specified and it is a section name, the return is made after the execution of the last statement of the last paragraph in the procedure-name-2 section. The only necessary relationship between procedure-name-1 and procedure-name-2 is that a consecutive sequence of operations is executed, beginning at the procedure named by procedure-name-1 and ending with the execution of the procedure named by procedure-name-2. PERFORM statements can be specified within the performed procedure. If there are two or more logical paths to the return point, then procedure-name-2 can name a paragraph that consists only of an EXIT statement; all the paths to the return point must then lead to this paragraph. When the performed procedures include another PERFORM statement, the sequence of procedures associated with the embedded PERFORM statement must be totally included in or totally excluded from the performed procedures of the first PERFORM statement. That is, an active PERFORM statement whose execution point begins within the range of performed procedures of another active PERFORM statement must not allow control to pass through the exit point of the other active PERFORM statement. However, two or more active PERFORM statements can have a common exit. The following figure illustrates valid sequences of execution for PERFORM statements.
374
Language Reference
When control passes to the sequence of procedures by means other than a PERFORM statement, control passes through the exit point to the next executable statement, as if no PERFORM statement referred to these procedures.
END-PERFORM
Delimits the scope of the in-line PERFORM statement. Execution of an in-line PERFORM is completed after the last statement contained within it has been executed.
PERFORM with TIMES phrase

The procedures referred to in the TIMES phrase PERFORM statement are executed the number of times specified by the value in identifier-1 or integer-1. Control then passes to the next executable statement following the PERFORM statement.
Format 2
PERFORM procedure-name-1 THROUGH procedure-name-2 THRU TIMES imperative-statement-1 identifier-1 integer-1 END-PERFORM TIMES
identifier-1 integer-1
If procedure-name-1 is specified, imperative-statement-1 and the END-PERFORM phrase must not be specified. identifier-1 Must name an integer item. identifier-1 cannot be a windowed date field.
375
If identifier-1 is zero or a negative number at the time the PERFORM statement is initiated, control passes to the statement following the PERFORM statement. After the PERFORM statement has been initiated, any change to identifier-1 has no effect in varying the number of times the procedures are initiated. integer-1 Can be a positive signed integer.
PERFORM with UNTIL phrase

In the UNTIL phrase format, the procedures referred to are performed until the condition specified by the UNTIL phrase is true. Control is then passed to the next executable statement following the PERFORM statement.
Format 3
PERFORM procedure-name-1 THROUGH THRU phrase 1 imperative-statement-1 procedure-name-2 END-PERFORM phrase 1
phrase 1:
UNTIL condition-1 TEST WITH BEFORE AFTER
If procedure-name-1 is specified, imperative-statement-1 and the END-PERFORM phrase must not be specified. condition-1 Can be any condition described under Conditional expressions on page 246. If the condition is true at the time the PERFORM statement is initiated, the specified procedures are not executed. Any subscripting associated with the operands specified in condition-1 is evaluated each time the condition is tested. If the TEST BEFORE phrase is specified or assumed, the condition is tested before any statements are executed (corresponds to DO WHILE). If the TEST AFTER phrase is specified, the statements to be performed are executed at least once before the condition is tested (corresponds to DO UNTIL). In either case, if the condition is true, control is transferred to the next executable statement following the end of the PERFORM statement. If neither the TEST BEFORE nor the TEST AFTER phrase is specified, the TEST BEFORE phrase is assumed.
376
Language Reference
PERFORM with VARYING phrase

The VARYING phrase increases or decreases the value of one or more identifiers or index-names, according to certain rules. (See Varying phrase rules on page 382.) The format-4 VARYING phrase PERFORM statement can serially search an entire seven-dimensional table.
Format 4
PERFORM procedure-name-1 THROUGH procedure-name-2 THRU imperative-statement-1 END-PERFORM phrase 1 phrase 2
phrase 1
phrase 1:
VARYING TEST WITH identifier-4 literal-2 BEFORE AFTER UNTIL condition-1 identifier-2 index-name-1 FROM identifier-3 index-name-2 literal-1 BY
phrase 2:
AFTER
identifier-5 index-name-3
FROM
identifier-6 index-name-4 literal-3
phrase 3
phrase 3:
BY identifier-7 literal-4 UNTIL condition-2
If procedure-name-1 is specified, imperative-statement-1 and the END-PERFORM phrase must not be specified. If procedure-name-1 is omitted, the AFTER phrase must not be specified. identifier-2 through identifier-7 Must name a numeric elementary item. These identifiers cannot be windowed date fields. literal-1 through literal-4 Must represent a numeric literal. condition-1, condition-2 Can be any condition described under Conditional expressions on page 246. If the condition is true at the time the PERFORM statement is initiated, the specified procedures are not executed.
377
After the conditions specified in the UNTIL phrase are satisfied, control is passed to the next executable statement following the PERFORM statement. If any of the operands specified in condition-1 or condition-2 is subscripted, reference modified, or is a function-identifier, the subscript, reference-modifier, or function is evaluated each time the condition is tested. Floating-point data items and literals can be used anywhere a numeric data item or literal can be specified. When TEST BEFORE is indicated, all specified conditions are tested before the first execution, and the statements to be performed are executed, if at all, only when all specified tests fail. When TEST AFTER is indicated, the statements to be performed are executed at least once, before any condition is tested. If neither the TEST BEFORE nor the TEST AFTER phrase is specified, the TEST BEFORE phrase is assumed.
Varying identifiers
The way in which operands are increased or decreased depends on the number of variables specified. In the following discussion, every reference to identifier-n refers equally to index-name-n (except when identifier-n is the object of the BY phrase). If identifier-2 or identifier-5 is subscripted, the subscripts are evaluated each time the content of the data item referenced by the identifier is set or augmented. If identifier-3, identifier-4, identifier-6, or identifier-7 is subscripted, the subscripts are evaluated each time the content of the data item referenced by the identifier is used in a setting or an augmenting operation. The following figure illustrates the logic of the PERFORM statement when an identifier is varied with TEST BEFORE.
The following figure illustrates the logic of the PERFORM statement when an identifier is varied with TEST AFTER.
378
Language Reference
Varying two identifiers

PERFORM PROCEDURE-NAME-1 THROUGH PROCEDURE-NAME-2 VARYING IDENTIFIER-2 FROM IDENTIFIER-3 BY IDENTIFIER-4 UNTIL CONDITION-1 AFTER IDENTIFIER-5 FROM IDENTIFIER-6 BY IDENTIFIER-7 UNTIL CONDITION-2
1. identifier-2 and identifier-5 are set to their initial values, identifier-3 and identifier-6, respectively. 2. condition-1 is evaluated as follows: a. If it is false, steps 3 through 7 are executed. b. If it is true, control passes directly to the statement following the PERFORM statement. 3. condition-2 is evaluated as follows: a. If it is false, steps 4 through 6 are executed. b. If it is true, identifier-2 is augmented by identifier-4, identifier-5 is set to the current value of identifier-6, and step 2 is repeated. 4. procedure-name-1 and procedure-name-2 are executed once (if specified). 5. identifier-5 is augmented by identifier-7. 6. Steps 3 through 5 are repeated until condition-2 is true. 7. Steps 2 through 6 are repeated until condition-1 is true. At the end of PERFORM statement execution: v identifier-5 contains the current value of identifier-6. v identifier-2 has a value that exceeds the last-used setting by the increment or decrement value (unless condition-1 was true at the beginning of PERFORM statement execution, in which case, identifier-2 contains the current value of identifier-3). The following figure illustrates the logic of the PERFORM statement when two identifiers are varied with TEST BEFORE.
379
The following figure illustrates the logic of the PERFORM statement when two identifiers are varied with TEST AFTER.
380
Language Reference
Varying three identifiers

PERFORM PROCEDURE-NAME-1 THROUGH PROCEDURE-NAME-2 VARYING IDENTIFIER-2 FROM IDENTIFIER-3 BY IDENTIFIER-4 UNTIL CONDITION-1 AFTER IDENTIFIER-5 FROM IDENTIFIER-6 BY IDENTIFIER-7 UNTIL CONDITION-2 AFTER IDENTIFIER-8 FROM IDENTIFIER-9 BY IDENTIFIER-10 UNTIL CONDITION-3
The actions are the same as those for two identifiers, except that identifier-8 goes through the complete cycle each time identifier-5 is augmented by identifier-7, which, in turn, goes through a complete cycle each time identifier-2 is varied. At the end of PERFORM statement execution: v identifier-5 and identifier-8 contain the current values of identifier-6 and identifier-9, respectively. v identifier-2 has a value exceeding its last-used setting by one increment/decrement value (unless condition-1 was true at the beginning of PERFORM statement execution, in which case identifier-2 contains the current value of identifier-3).
Varying more than three identifiers

You can produce analogous PERFORM statement actions to the example above with the addition of up to four AFTER phrases.
381
Varying phrase rules

No matter how many variables are specified, the following rules apply: v In the VARYING or AFTER phrases, when an index-name is specified: The index-name is initialized and incremented or decremented according to the rules under INDEX phrase on page 219. (See also SET statement on page 402.) In the associated FROM phrase, an identifier must be described as an integer and have a positive value; a literal must be a positive integer. In the associated BY phrase, an identifier must be described as an integer; a literal must be a nonzero integer. v In the FROM phrase, when an index-name is specified: In the associated VARYING or AFTER phrase, an identifier must be described as an integer. It is initialized as described in the SET statement. In the associated BY phrase, an identifier must be described as an integer and have a nonzero value; a literal must be a nonzero integer. v In the BY phrase, identifiers and literals must have nonzero values. v Changing the values of identifiers or index-names in the VARYING, FROM, and BY phrases during execution changes the number of times the procedures are executed.
382
Language Reference
READ statement
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. When the READ statement is executed, the associated file must be open in INPUT or I-O mode.
Format 1: sequential retrieval

READ file-name-1 NEXT RECORD INTO identifier-1
END imperative-statement-1 AT
NOT AT
END imperative-statement-2
END-READ
Format 2: random retrieval

READ file-name-1 RECORD INTO identifier-1
KEY IS
data-name-1
INVALID KEY
NOT INVALID KEY
END-READ
file-name-1 Must be defined in a data division FD entry. NEXT RECORD Reads the next record in the logical sequence of records. NEXT is optional when ACCESS MODE IS SEQUENTIAL and has no effect on READ statement execution. You must specify the NEXT RECORD phrase for files in dynamic access mode, which are retrieved sequentially. INTO identifier-1 identifier-1 is the receiving field. identifier-1 must be a valid receiving field for the selected sending record description entry in accordance with the rules of the MOVE statement.
383
The record areas associated with file-name-1 and identifier-1 must not be the same storage area. When there is only one record description associated with file-name-1 or all the records and the data item referenced by identifier-1 describe an elementary alphanumeric item or a group item, the result of the execution of a READ statement with the INTO phrase is equivalent to the application of the following rules in the order specified: v The execution of the same READ statement without the INTO phrase. v The current record is moved from the record area to the area specified by identifier-1 according to the rules for the MOVE statement without the CORRESPONDING phrase. The size of the current record is determined by rules specified for the RECORD clause. If the file description entry contains a RECORD IS VARYING clause, the implied move is a group move. The implied MOVE statement does not occur if the execution of the READ statement was unsuccessful. Any subscripting or reference modification associated with identifier-1 is evaluated after the record has been read and immediately before it is moved to the data item. The record is available in both the record area and the data item referenced by identifier-1. If identifier-1 is a date field, then the implied MOVE statement is performed according to the behavior described under Moves involving date fields on page 363. When there are multiple record descriptions associated with file-name-1 and they do not all describe a group item or elementary alphanumeric item, the following rules apply: 1. If the file referenced by file-name-1 is described as containing variable-length records, or as a QSAM file with RECORDING MODE S or U, a group move will take place. 2. If the file referenced by file-name-1 is described as containing fixed-length records, a move will take place according to the rules for a MOVE statement using, as a sending field description, the record that specifies the largest number of character positions. If more than one such record exists, the sending field record selected will be the one among those records that appears first under the description of file-name-1.
KEY IS phrase
The KEY IS phrase can be specified only for indexed files. data-name-1 must identify a record key associated with file-name-1. data-name-1 can be qualified; it cannot be subscripted.
AT END phrases
For sequential access, both the AT END phrase and an applicable EXCEPTION/ERROR procedure can be omitted. For information about at-end condition processing, see AT END condition on page 386.
INVALID KEY phrases

Both the INVALID KEY phrase and an applicable EXCEPTION/ERROR procedure can be omitted.
384
Language Reference
For information about INVALID KEY phrases processing, see Invalid key condition on page 282.
END-READ phrase
This explicit scope terminator serves to delimit the scope of the READ statement. END-READ permits a conditional READ statement to be nested in another conditional statement. END-READ can also be used with an imperative READ statement. For more information, see Delimited scope statements on page 271.
Multiple record processing

If more than one record description entry is associated with file-name-1, those records automatically share the same storage area; that is, they are implicitly redefined. After a READ statement is executed, only those data items within the range of the current record are replaced; data items stored beyond that range are undefined. The following figure illustrates this concept. If the range of the current record exceeds the record description entries for file-name-1, the record is truncated on the right to the maximum size. In either of these cases, the READ statement is successful and the I-O status is set to 04 indicating a record length conflict has occurred.
Sequential access mode

Format 1 must be used for all files in sequential access mode. Execution of a format-1 READ statement retrieves the next logical record from the file. The next record accessed is determined by the file organization.
Sequential files
The NEXT RECORD is the next record in a logical sequence of records. The NEXT phrase need not be specified; it has no effect on READ statement execution. If SELECT OPTIONAL is specified in the file-control entry for this file, and the file is absent during this execution of the object program, execution of the first READ
385
statement causes an at-end condition; however, since no file is present, the system-defined end-of-file processing is not performed. AT END condition: If the file position indicator indicates that no next logical record exists, or that an optional input file is not present, the following occurs in the order specified: 1. A value derived from the setting of the file position indicator is placed into the I-O status associated with file-name-1 to indicate the at-end condition. 2. If the AT END phrase is specified in the statement causing the condition, control is transferred to imperative-statement-1 in the AT END phrase. Any USE AFTER STANDARD EXCEPTION procedure associated with file-name-1 is not executed. 3. If the AT END phrase is not specified and an applicable USE AFTER STANDARD EXCEPTION procedure exists, the procedure is executed. Return from that procedure is to the next executable statement following the end of the READ statement. Both the AT END phrase and an applicable EXCEPTION/ERROR procedure can be omitted. When the at-end condition occurs, execution of the READ statement is unsuccessful. The contents of the associated record area are undefined and the file position indicator is set to indicate that no valid next record has been established. For QSAM files, attempts to access or move data into the record area following an unsuccessful read can result in a protection exception. If an at-end condition does not occur during the execution of a READ statement, the AT END phrase is ignored, if specified, and the following actions occur: 1. The file position indicator is set and the I-O status associated with file-name-1 is updated. 2. If an exception condition that is not an at-end condition exists, control is transferred to the end of the READ statement following the execution of any USE AFTER STANDARD EXCEPTION procedure applicable to file-name-1. If no USE AFTER STANDARD EXCEPTION procedure is specified, control is transferred to the end of the READ statement or to imperative-statement-2, if specified. 3. If no exception condition exists, the record is made available in the record area and any implicit move resulting from the presence of an INTO phrase is executed. Control is transferred to the end of the READ statement or to imperative-statement-2, if specified. In the latter case, execution continues according to the rules for each statement specified in imperative-statement-2. If a procedure branching or conditional statement which causes explicit transfer of control is executed, control is transferred in accordance with the rules for that statement; otherwise, upon completion of the execution of imperative-statement-2, control is transferred to the end of the READ statement. Following the unsuccessful execution of a READ statement, the contents of the associated record area are undefined and the file position indicator is set to indicate that no valid next record has been established. Attempts to access or move data into the record area following an unsuccessful read can result in a protection exception.
| |
Multivolume QSAM files

If end-of-volume is recognized during execution of a READ statement, and logical end-of-file has not been reached, the following actions are taken:
386
Language Reference
v v v v
The standard ending volume label procedure is executed. A volume switch occurs. The standard beginning volume label procedure is executed. The first data record of the next volume is made available.
Indexed or relative files

The NEXT RECORD is the next logical record in the key sequence. For indexed files, the key sequence is the sequence of ascending values of the current key of reference. For relative files, the key sequence is the sequence of ascending values of relative record numbers for records that exist in the file. Before the READ statement is executed, the file position indicator must have been set by a successful OPEN, START, or READ statement. When the READ statement is executed, the record indicated by the file position indicator is made available if it is still accessible through the path indicated by the file position indicator. If the record is no longer accessible (because it has been deleted, for example), the file position indicator is updated to point to the next existing record in the file, and that record is made available. For files in sequential access mode, the NEXT phrase need not be specified. For files in dynamic access mode, the NEXT phrase must be specified for sequential record retrieval. AT END condition: This condition exists when the file position indicator indicates that no next logical record exists or that an optional input file is not present. The same procedure occurs as for sequential files (see AT END condition on page 386). If neither an at-end nor an invalid key condition occurs during the execution of a READ statement, the AT END or the INVALID KEY phrase is ignored, if specified. The same actions occur as when the at-end condition does not occur with sequential files (see AT END condition on page 386). Sequentially accessed indexed files: When an ALTERNATE RECORD KEY with DUPLICATES is the key of reference, file records with duplicate key values are made available in the order in which they were placed in the file. Sequentially accessed relative files: If the RELATIVE KEY clause is specified for this file, READ statement execution updates the RELATIVE KEY data item to indicate the relative record number of the record being made available.
Random access mode

Format 2 must be specified for indexed and relative files in random access mode, and also for files in the dynamic access mode when record retrieval is random. Execution of the READ statement depends on the file organization, as explained in the following sections.
Indexed files
Execution of a format-2 READ statement causes the value of the key of reference to be compared with the value of the corresponding key data item in the file records, until the first record having an equal value is found. The file position indicator is
387
positioned to this record, which is then made available. If no record can be so identified, an INVALID KEY condition exists, and READ statement execution is unsuccessful. (See Invalid key condition under Common processing facilities on page 278.) If the KEY phrase is not specified, the prime RECORD KEY becomes the key of reference for this request. When dynamic access is specified, the prime RECORD KEY is also used as the key of reference for subsequent executions of sequential READ statements, until a different key of reference is established. When the KEY phrase is specified, data-name-1 becomes the key of reference for this request. When dynamic access is specified, this key of reference is used for subsequent executions of sequential READ statements, until a different key of reference is established.
Relative files
Execution of a format-2 READ statement sets the file position indicator pointer to the record whose relative record number is contained in the RELATIVE KEY data item, and makes that record available. If the file does not contain such a record, the INVALID KEY condition exists, and READ statement execution is unsuccessful. (See Invalid key condition under Common processing facilities on page 278.) The KEY phrase must not be specified for relative files.
Dynamic access mode

For files with indexed or relative organization, dynamic access mode can be specified in the file-control entry. In dynamic access mode, either sequential or random record retrieval can be used, depending on the format used. Format 1 with the NEXT phrase must be specified for sequential retrieval. All other rules for sequential access apply. READ statement notes: v If the FILE-STATUS clause is specified in the file-control entry, the associated file status key is updated when the READ statement is executed. v Following unsuccessful READ statement execution, the contents of the associated record area and the value of the file position indicator are undefined. Attempts to access or move data into the record area following an unsuccessful read can result in a protection exception.
388
Language Reference
RELEASE statement
The RELEASE statement transfers records from an input/output area to the initial phase of a sorting operation. The RELEASE statement can be used only within the range of an INPUT PROCEDURE associated with a SORT statement.
Format
RELEASE record-name-1 FROM identifier-1
Within an INPUT PROCEDURE, at least one RELEASE statement must be specified. When the RELEASE statement is executed, the current contents of record-name-1 are placed in the sort file. This makes the record available to the initial phase of the sorting operation. record-name-1 Must specify the name of a logical record in a sort-merge file description entry (SD). record-name-1 can be qualified. FROM phrase The result of the execution of the RELEASE statement with the FROM identifier-1 phrase is equivalent to the execution of the following statements in the order specified.
MOVE identifier-1 to record-name-1. RELEASE record-name-1.
The MOVE is performed according to the rules for the MOVE statement without the CORRESPONDING phrase. identifier-1 identifier-1 must reference one of the following: v An entry in the working-storage section, the local-storage section, or the linkage section v A record description for another previously opened file v An alphanumeric or national function. identifier-1 must be a valid sending item with record-name-1 as the receiving item in accordance with the rules of the MOVE statement. identifier-1 and record-name-1 must not refer to the same storage area. After the RELEASE statement is executed, the information is still available in identifier-1. (See INTO and FROM phrases on page 283 under Common processing facilities.) If the RELEASE statement is executed without specifying the SD entry for file-name-1 in a SAME RECORD AREA clause, the information in record-name-1 is no longer available.
389
If the SD entry is specified in a SAME RECORD AREA clause, record-name-1 is still available as a record of the other files named in that clause. When FROM identifier-1 is specified, the information is still available in identifier-1. When control passes from the INPUT PROCEDURE, the sort file consists of all those records placed in it by execution of RELEASE statements.
390
Language Reference
RETURN statement
The RETURN statement transfers records from the final phase of a sorting or merging operation to an OUTPUT PROCEDURE. The RETURN statement can be used only within the range of an OUTPUT PROCEDURE associated with a SORT or MERGE statement.
Format
RETURN file-name-1 RECORD INTO identifier-1
END imperative-statement-1 AT
NOT AT
END imperative-statement-2
END-RETURN
Within an OUTPUT PROCEDURE, at least one RETURN statement must be specified. When the RETURN statement is executed, the next record from file-name-1 is made available for processing by the OUTPUT PROCEDURE. file-name-1 Must be described in a data division SD entry. If more than one record description is associated with file-name-1, those records automatically share the same storage; that is, the area is implicitly redefined. After RETURN statement execution, only the contents of the current record are available. If any data items lie beyond the length of the current record, their contents are undefined. INTO phrase When there is only one record description associated with file-name-1 or all the records and the data item referenced by identifier-1 describe an elementary alphanumeric item or a group item, the result of the execution of a RETURN statement with the INTO phrase is equivalent to the application of the following rules in the order specified: v The execution of the same RETURN statement without the INTO phrase. v The current record is moved from the record area to the area specified by identifier-1 according to the rules for the MOVE statement without the CORRESPONDING phrase. The size of the current record is determined by rules specified for the RECORD clause. If the file description entry contains a RECORD IS VARYING clause, the implied move is a group move. The implied MOVE statement does not occur if the execution of the RETURN statement was unsuccessful. Any subscripting or reference modification associated with identifier-1 is evaluated after the record has been read and immediately before it is moved to the data item. The record is available in both the record area and the data item referenced by identifier-1.
391
When there are multiple record descriptions associated with file-name-1 and they do not all describe a group item or elementary alphanumeric item, the following rules apply: 1. If the file referenced by file-name-1 contains variable-length records, a group move will take place. 2. If the file referenced by file-name-1 contains fixed-length records, a move will take place according to the rules for a MOVE statement using, as a sending field description, the record that specifies the largest number of character positions. If more than one such record exists, the sending field record selected will be the one among those records that appears first under the description of file-name-1. identifier-1 must be a valid receiving field for the selected sending record description entry in accordance with the rules of the MOVE statement. The record areas associated with file-name-1 and identifier-1 must not be the same storage area.
AT END phrases
The imperative-statement specified on the AT END phrase executes after all records have been returned from file-name-1. No more RETURN statements can be executed as part of the current output procedure. If an at-end condition does not occur during the execution of a RETURN statement, then after the record is made available and after executing any implicit move resulting from the presence of an INTO phrase, control is transferred to the imperative statement specified by the NOT AT END phrase. If an at-end condition does occur, control is transferred to the end of the RETURN statement.
END-RETURN phrase
This explicit scope terminator serves to delimit the scope of the RETURN statement. END-RETURN permits a conditional RETURN statement to be nested in another conditional statement. END-RETURN can also be used with an imperative RETURN statement. For more information, see Delimited scope statements on page 271.
392
Language Reference
REWRITE statement
The REWRITE statement logically replaces an existing record in a direct-access file. When the REWRITE statement is executed, the associated direct-access file must be open in I-O mode. The REWRITE statement is not supported for line-sequential files.
Format
REWRITE record-name-1 FROM identifier-1
INVALID KEY
NOT INVALID KEY
END-REWRITE
record-name-1 Must be the name of a logical record in a data division FD entry. The record-name can be qualified. FROM phrase The result of the execution of the REWRITE statement with the FROM identifier-1 phrase is equivalent to the execution of the following statements in the order specified.
MOVE identifier-1 TO record-name-1. REWRITE record-name-1
The MOVE is performed according to the rules for the MOVE statement without the CORRESPONDING phrase. identifier-1 identifier-1 can reference one of the following: v A record description for another previously opened file v An alphanumeric or national function v A data item defined in the working-storage section, the local-storage section, or the linkage section identifier-1 must be a valid sending item with record-name-1 as the receiving item in accordance with the rules of the MOVE statement. identifier-1 and record-name-1 must not refer to the same storage area. After the REWRITE statement is executed, the information is still available in identifier-1 (INTO and FROM phrases on page 283 under Common processing facilities).
393
INVALID KEY phrases

(See Invalid key condition on page 282 under Common processing facilities.) An INVALID KEY condition exists when: v The access mode is sequential, and the value contained in the prime RECORD KEY of the record to be replaced does not equal the value of the prime RECORD KEY data item of the last-retrieved record from the file v The value contained in the prime RECORD KEY does not equal that of any record in the file v The value of an ALTERNATE RECORD KEY data item for which DUPLICATES is not specified is equal to that of a record already in the file
END-REWRITE phrase
This explicit scope terminator serves to delimit the scope of the REWRITE statement. END-REWRITE permits a conditional REWRITE statement to be nested in another conditional statement. END-REWRITE can also be used with an imperative REWRITE statement. For more information, see Delimited scope statements on page 271.
Reusing a logical record

After successful execution of a REWRITE statement, the logical record is no longer available in record-name-1 unless the associated file is named in a SAME RECORD AREA clause (in which case, the record is also available as a record of the other files named in the SAME RECORD AREA clause). The file position indicator is not affected by execution of the REWRITE statement. If the FILE STATUS clause is specified in the file-control entry, the associated file status key is updated when the REWRITE statement is executed.
Sequential files
For files in the sequential access mode, 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 number of character positions in record-name-1 must equal the number of character positions in the record being replaced. The INVALID KEY phrase must not be specified for a file with sequential organization. An EXCEPTION/ERROR procedure can be specified.
Indexed files
The number of character positions in record-name-1 can be different from the number of character positions in the record being replaced. 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.
394
Language Reference
Both the INVALID KEY phrase and an applicable EXCEPTION/ERROR procedure can be omitted. When the access mode is random or dynamic, the record to be replaced is specified by the value contained in the prime RECORD KEY. Values of ALTERNATE RECORD KEY data items in the rewritten record can differ from those in the record being replaced. The system ensures that later access to the record can be based upon any of the record keys. If an invalid key condition exists, the execution of the REWRITE statement is unsuccessful, the updating operation does not take place, and the data in record-name-1 is unaffected. (See Invalid key condition on page 282 under Common processing facilities.)
Relative files
The number of character positions in record-name-1 can be different from the number of character positions in the record being replaced. For relative files in sequential access mode, the INVALID KEY phrase must not be specified. An EXCEPTION/ERROR procedure can be specified. For relative files in random or dynamic access mode, the INVALID KEY phrase or an applicable EXCEPTION/ERROR procedure can be specified. Both can be omitted. 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. (See Invalid key condition on page 282 under Common processing facilities.) The updating operation does not take place, and the data in record-name is unaffected.
395
SEARCH statement
The SEARCH statement searches a table for an element that satisfies the specified condition and adjusts the associated index to indicate that element.
Format 1: serial search

SEARCH identifier-1 VARYING identifier-2 index-name-1
WHEN condition-1 END imperative-statement-1 AT
imperative-statement-2 NEXT-SENTENCE
END-SEARCH
Format 2: binary search

SEARCH ALL identifier-1 END imperative-statement-1 AT
WHEN
data-name-1 IS
EQUAL TO =
condition-name-1
AND
data-name-2 IS
EQUAL TO =
condition-name-2 imperative-statement-2 NEXT SENTENCE
END-SEARCH
identifier-1 identifier-1 can be a data item subordinate to a data item that contains an
396
Language Reference
OCCURS clause; that is, it can be a part of a multidimensional table. In this case, the data description entry must specify an INDEXED BY phrase for each dimension of the table. The data division description of identifier-1 should contain an OCCURS clause with the INDEXED BY phrase, but a table can be searched using an index defined for an appropriately described different table. For format 2, the description of identifier-1 must contain the KEY IS phrase in the OCCURS clause. identifier-1 must not be subscripted or reference-modified. identifier-1 refers to all occurrences within the table element. SEARCH statement execution modifies only the value in the index associated with identifier-1 (and, if present, in index-name-1 or identifier-2). Therefore, to search an entire two-dimensional to seven-dimensional table, it is necessary to execute a SEARCH statement for each dimension. Before each execution, SET statements must be executed to reinitialize the associated index-names.
AT END phrase and WHEN phrases

After imperative-statement-1 or imperative-statement-2 is executed, control passes to the end of the SEARCH statement, unless imperative-statement-1 or imperative-statement-2 ends with a GO TO statement.
NEXT SENTENCE
NEXT SENTENCE transfers control to the first statement following the closest separator period. When NEXT SENTENCE is specified with END-SEARCH, control does not pass to the statement following the END-SEARCH. Instead, control passes to the statement after the closest following period. For the format-2 SEARCH ALL statement, neither imperative-statement-2 nor NEXT SENTENCE is required. Without them, the SEARCH statement sets the index to the value in the table that matched the condition.
END-SEARCH phrase
This explicit scope terminator serves to delimit the scope of the SEARCH statement. END-SEARCH permits a conditional SEARCH statement to be nested in another conditional statement. For more information, see Delimited scope statements on page 271.
Serial search
A format-1 SEARCH statement executes a serial search beginning at the current index setting. When the search begins, if the value of the index-name associated with identifier-1 is not greater than the highest possible occurrence number, the following actions take place: v The conditions in the WHEN phrase are evaluated in the order in which they are written. v If none of the conditions is satisfied, the index-name for identifier-1 is increased to correspond to the next table element, and step 1 is repeated.
397
v If upon evaluation, one of the WHEN conditions is satisfied, the search is terminated immediately, and the imperative-statement associated with that condition is executed. The index-name points to the table element that satisfied the condition. If NEXT SENTENCE is specified, control passes to the statement following the closest period. v If the end of the table is reached (that is, the incremented index-name value is greater than the highest possible occurrence number) without the WHEN condition being satisfied, the search is terminated, as described in the next paragraph. If, when the search begins, the value of the index-name associated with identifier-1 is greater than the highest possible occurrence number, the search immediately ends, and, if specified, the AT END imperative-statement is executed. If the AT END phrase is omitted, control passes to the next statement after the SEARCH statement.
VARYING phrase
index-name-1 One of the following actions applies: v If index-name-1 is an index for identifier-1, this index is used for the search. Otherwise, the first (or only) index-name is used. v If index-name-1 is an index for another table element, then the first (or only) index-name for identifier-1 is used for the search; the occurrence number represented by index-name-1 is increased by the same amount as the search index-name and at the same time. When the VARYING index-name-1 phrase is omitted, the first (or only) index-name for identifier-1 is used for the search. If indexing is used to search a table without an INDEXED BY phrase, correct results are ensured only if both the table defined with the index and the table defined without the index have table elements of the same length and with the same number of occurrences. identifier-2 Must be either an index data item or an elementary integer item. identifier-2 cannot be a windowed date field. identifier-2 cannot be subscripted by the first (or only) index-name for identifier-1. During the search, one of the following actions applies: v If identifier-2 is an index data item, then, whenever the search index is increased, the specified index data item is simultaneously increased by the same amount. v If identifier-2 is an integer data item, then, whenever the search index is increased, the specified data item is simultaneously increased by 1.
WHEN phrase (serial search)

condition-1 Can be any condition described under Conditional expressions on page 246. The following figure illustrates a format-1 SEARCH operation containing two WHEN phrases.
398
Language Reference
Entrance
Index setting: >AT END highest permissible occurrence number
imperativestatement-1
Condition-1
True
False
Condition-2
True
False Increment index-name for identifier-1
Increment index-name-1 or identifier-2
These operations are included only when called for in the statement. Control transfers to the next sentence, unless the imperative statement ends with a GO TO statement.
Binary search
The format-2 SEARCH ALL statement executes a binary search. The search index need not be initialized by SET statements, because its setting is varied during the search operation so that its value is at no time less than the value of the first table element, nor ever greater than the value of the last table element. The index used is always that associated with the first index-name specified in the OCCURS clause. The results of a SEARCH ALL operation are predictable only when: v The data in the table is ordered in ASCENDING/DESCENDING KEY order v The contents of the ASCENDING/DESCENDING keys specified in the WHEN clause provide a unique table reference. identifier-1 identifier-1 can reference: v A data item subordinate to a data item that contains an OCCURS clause; that is, it can be a part of a two- to seven-dimensional table. In this case, the data description entry must specify an INDEXED BY phrase for each dimension of the table. v A DBCS item if the ASCENDING/DESCENDING KEY is defined as a DBCS item.
399
v A national data item if the ASCENDING/DESCENDING KEY is defined as a national data item. identifier-1 cannot reference: v An indexed data item v A floating-point data item v A data item defined with USAGE POINTER, USAGE FUNCTION-POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE v A windowed date field identifier-1 must refer to all occurrences within the table element; that is, it must not be subscripted or reference-modified. The data division description of identifier-1 must contain an OCCURS clause with the INDEXED BY option. It must also contain the KEY IS phrase in its OCCURS clause. AT END The condition that exists when the search operation terminates without satisfying the condition specified in any of the associated WHEN phrases.
WHEN phrase (binary search)

If the WHEN relation-condition is specified, the compare is based on the length and sign of data-name. For example, if the length of data-name is shorter than the length of the search argument, the search argument is truncated to the length of data-name before the compare is done. If the search argument is signed and data-name is unsigned, the sign is removed from the search argument before the compare is done. If the WHEN phrase cannot be satisfied for any setting of the index within this range, the search is unsuccessful. Control is passed to imperative-statement-1 of the AT END phrase, when specified, or to the next statement after the SEARCH statement. In either case, the final setting of the index is not predictable. If the WHEN option can be satisfied, control passes to imperative-statement-2, if specified, or to the next executable sentence if the NEXT SENTENCE phrase is specified. The index contains the value indicating the occurrence that allowed the WHEN conditions to be satisfied. condition-name-1, condition-name-2 Each condition-name specified must have only a single value, and each must be associated with an ASCENDING/DESCENDING KEY identifier for this table element. data-name-1, data-name-2 Must specify an ASCENDING/DESCENDING KEY data item in the identifier-1 table element and must be subscripted by the first index-name associated with identifier-1. Each data-name can be qualified. data-name-1 must be a valid operand for comparison with identifier-3, literal-1, or arithmetic-expression-1 according to the rules of comparison. data-name-2 must be a valid operand for comparison with identifier-4, literal-2, or arithmetic-expression-2 according to the rules of comparison. data-name-1 and data-name-2 cannot be: v Floating-point data items
400
Language Reference
v Group items containing variable-occurrence data items v Windowed date fields identifier-3, identifier-4 Must not be an ASCENDING/DESCENDING KEY data item for identifier-1 or an item that is subscripted by the first index-name for identifier-1. identifier-3 and identifier-4 cannot be data items defined with any of the usages POINTER, FUNCTION-POINTER, PROCEDURE-POINTER, or OBJECT REFERENCE. identifier-3 and identifier-4 cannot be windowed date fields. If identifier-3 or literal-1 is of class national, then data-name-1 must be of class national. If identifier-4 or literal-2 is of class national, then data-name-2 must be of class national. arithmetic-expression Can be any of the expressions defined under Arithmetic expressions on page 241, with the following restriction: Any identifier in arithmetic-expression must not be an ASCENDING/DESCENDING KEY data item for identifier-1 or an item that is subscripted by the first index-name for identifier-1. When an ASCENDING/DESCENDING KEY data item is specified, explicitly or implicitly, in the WHEN phrase, all preceding ASCENDING/DESCENDING KEY data-names for identifier-1 must also be specified.
Search statement considerations

Index data items cannot be used as subscripts, because of the restrictions on direct reference to them. When the object of the VARYING option is an index-name for another table element, one format-1 SEARCH statement steps through two table elements at once. To ensure correct execution of a SEARCH statement for a variable-length table, make sure the object of the OCCURS DEPENDING ON clause (data-name-1) contains a value that specifies the current length of the table. The scope of a SEARCH statement can be terminated by any of the following: v An END-SEARCH phrase at the same level of nesting v A separator period v An ELSE or END-IF phrase associated with a previous IF statement
401
SET statement
The SET statement is used to perform one of the following operations: v Placing values associated with table elements into indexes associated with index-names v Incrementing or decrementing an occurrence number v Setting the status of an external switch to ON or OFF v Moving data to condition names to make conditions true v v v v Setting Setting Setting Setting USAGE USAGE USAGE USAGE POINTER data items to a data address PROCEDURE-POINTER data items to an entry address FUNCTION-POINTER data items to an entry address OBJECT REFERENCE data items to refer to an object instance
Index-names are related to a given table through the INDEXED BY phrase of the OCCURS clause; they are not further defined in the program. When the sending and receiving fields in a SET statement share part of their storage (that is, the operands overlap), the result of the execution of that SET statement is undefined.
Format 1: SET for basic table handling

When this form of the SET statement is executed, the current value of the receiving field is replaced by the value of the sending field (with conversion).
Format 1: SET (basic table handling)
SET
index-name-1 identifier-1
TO
index-name-2 identifier-2 integer-1
| | | | | | | |
index-name-1 Receiving field. Must name an index that is specified in the INDEXED BY phrase of an OCCURS clause. identifier-1 Receiving field. Must name either an index data item or an elementary numeric integer item. A receiving field cannot be a windowed date field. index-name-2 Sending field. Must name an index that is specified in the INDEXED BY phrase of an OCCURS clause. The value of the index before the SET statement is executed must correspond to an occurrence number of its associated table. identifier-2 Sending field.
402
Language Reference
Must name either an index data item or an elementary numeric integer item. A sending field cannot be a windowed date field. integer-1 Sending field. Must be a positive integer. The following table shows valid combinations of sending and receiving fields in a format-1 SET statement.
Table 48. Sending and receiving fields for format-1 SET statement Index-name receiving field Valid Valid Valid Valid
**
Sending field Index-name* Index data item* Integer data item Integer literal
Index data item receiving field Valid** Valid

**
Integer data item receiving field Valid Invalid Invalid Invalid
Invalid Invalid
| |
*An index-name refers to an index named in the INDEXED BY phrase of an OCCURS clause. An index data item is defined with the USAGE IS INDEX clause.
**
No conversion takes place.
Receiving fields are acted upon in the left-to-right order in which they are specified. Any subscripting or indexing associated with identifier-1 is evaluated immediately before that receiving field is acted upon. The value used for the sending field is the value at the beginning of SET statement execution. The value of an index after execution of a SEARCH or PERFORM statement can be undefined; therefore, use a format-1 SET statement to reinitialize such indexes before you attempt other table-handling operations. If index-name-2 is for a table that has a subordinate item that contains an OCCURS DEPENDING ON clause, then undefined values can be received into identifier-1. For more information about complex OCCURS DEPENDING ON, see the Enterprise COBOL Programming Guide.
Format 2: SET for adjusting indexes

When this form of the SET statement is executed, the value of the receiving index is increased (UP BY) or decreased (DOWN BY) by a value that corresponds to the value in the sending field.
Format 2: SET (adjusting indexes)
SET
index-name-3
UP BY DOWN BY
identifier-3 integer-2
403
The receiving field is an index specified by index-name-3. The index value both before and after the SET statement execution must correspond to an occurrence number in an associated table. The sending field can be specified as identifier-3, which must be an elementary integer data item, or as integer-2, which must be a nonzero integer. identifier-3 cannot be a windowed date field. When the format-2 SET statement is executed, the contents of the receiving field are increased (UP BY) or decreased (DOWN BY) by a value that corresponds to the number of occurrences represented by the value of identifier-3 or integer-2. Receiving fields are acted upon in the left-to-right order in which they are specified. The value of the incrementing or decrementing field at the beginning of SET statement execution is used for all receiving fields. If index-name-3 is for a table that has a subordinate item that contains an OCCURS DEPENDING ON clause, and if the ODO object is changed before executing a format-2 SET Statement, then index-name-3 cannot contain a value that corresponds to an occurrence number of its associated table. For more information about complex OCCURS DEPENDING ON, see the Enterprise COBOL Programming Guide.
Format 3: SET for external switches

When this form of the SET statement is executed, the status of each external switch associated with the specified mnemonic-name is turned ON or OFF.
Format 3: SET (external switches)
SET
mnemonic-name-1
TO
ON OFF
mnemonic-name-1 Must be associated with an external switch, the status of which can be altered.
Format 4: SET for condition-names

When this form of the SET statement is executed, the value associated with a condition-name is placed in its conditional variable according to the rules of the VALUE clause.
Format 4: SET (condition-names)
SET
condition-name-1
TO TRUE
404
Language Reference
condition-name-1 Must be associated with a conditional variable. If more than one literal is specified in the VALUE clause of condition-name-1, its associated conditional variable is set equal to the first literal. If multiple condition-names are specified, the results are the same as if a separate SET statement had been written for each condition-name in the same order in which they are specified in the SET statement.
Format 5: SET for USAGE IS POINTER data items

When this form of the SET statement is executed, the current value of the receiving field is replaced by the address value contained in the sending field.
Format 5: SET (data-pointer data items)
SET
identifier-4 ADDRESS OF identifier-5 identifier-6 ADDRESS OF identifier-7 NULL NULLS
TO
identifier-4 Receiving fields. Must be described as USAGE IS POINTER. ADDRESS OF identifier-5 Receiving fields. identifier-5 must be level-01 or level-77 items defined in the linkage section. The addresses of these items are set to the value of the operand specified in the TO phrase. identifier-5 must not be reference-modified. identifier-6 Sending field. Must be described as USAGE IS POINTER. ADDRESS OF identifier-7 Sending field. identifier-7 must name an item of any level except 66 or 88 in the linkage section, the working-storage section, or the local-storage section. ADDRESS OF identifier-7 contains the address of the identifier, and not the content of the identifier. NULL, NULLS Sending field. Sets the receiving field to contain the value of an invalid address.
405
The following table shows valid combinations of sending and receiving fields in a format-5 SET statement.
Table 49. Sending and receiving fields for format-5 SET statement USAGE IS POINTER receiving field Valid Valid Valid ADDRESS OF receiving field Valid Valid Valid NULL/NULLS receiving field Invalid Invalid Invalid
Sending field USAGE IS POINTER ADDRESS OF NULL/NULLS
Format 6: SET for procedure-pointer and function-pointer data items

When this format of the SET statement is executed, the current value of the receiving field is replaced by the address value specified by the sending field. At run time, function-pointers and procedure-pointers can reference the address of the primary entry point of a COBOL program, an alternate entry point in a COBOL program, or an entry point in a non-COBOL program; or they can be NULL. COBOL function-pointers are more easily used than procedure-pointers for interoperation with C functions.
Format 6: SET (procedure- and function-pointer data items)
SET
procedure-pointer-data-item-1 function-pointer-data-item-1 procedure-pointer-data-item-2 function-pointer-data-item-2 ENTRY identifier-8 literal-1 NULL NULLS pointer-data-item-3
TO
procedure-pointer-data-item-1, procedure-pointer-data-item-2 Must be described as USAGE IS PROCEDURE-POINTER. procedure-pointer-data-item-1 is a receiving field; procedure-pointer-data-item-2 is a sending field. function-pointer-data-item-1, function-pointer-data-item-2 Must be described as USAGE IS FUNCTION-POINTER. function-pointer-data-item-1 is a receiving field; function-pointer-data-item-2 is a sending field.
406
Language Reference
identifier-8 Must be defined as an alphanumeric item such that the value can be a program name. For more information, see PROGRAM-ID paragraph on page 94. For entry points in non-COBOL programs, identifier-8 can contain the characters @, #, and, $. literal-1 Must be alphanumeric and must conform to the rules for formation of program-names. For details on formation rules, see the discussion of program-name under PROGRAM-ID paragraph on page 94. identifier-8 or literal-1 must refer to one of the following types of entry points: v The primary entry point of a COBOL program as defined by the PROGRAM-ID paragraph. The PROGRAM-ID must reference the outermost program of a compilation unit; it must not reference a nested program. v An alternate entry point of a COBOL program as defined by a COBOL ENTRY statement. v An entry point in a non-COBOL program. The program-name referenced by the SET ... TO ENTRY statement can be affected by the PGMNAME compiler option. For details, see the Enterprise COBOL Programming Guide. NULL, NULLS Sets the receiving field to contain the value of an invalid address. pointer-data-item-3 Must be defined with USAGE POINTER. You must set pointer-data-item-3 in a non-COBOL program to point to a valid program entry point.
Example of COBOL/C interoperability

The following example demonstrates a COBOL CALL to a C function that returns a function-pointer to a service, followed by a COBOL CALL to the service:
IDENTIFICATION DIVISION. PROGRAM-ID DEMO. DATA DIVISION. WORKING-STORAGE SECTION. 01 FP USAGE FUNCTION-POINTER. PROCEDURE DIVISION. CALL c-function RETURNING FP. CALL FP.
Format 7: SET for USAGE OBJECT REFERENCE data items

When this format of the SET statement is executed the value in the receiving item is replaced by the value in the sending item.
Format 7: SET (object reference data items)

SET object-reference-id-1 TO object-reference-id-2 NULL SELF
407
object-reference-id-1 and object-reference-id-2 must be defined as USAGE OBJECT REFERENCE. object-reference-id-1 is the receiving item and object-reference-id-2 is the sending item. If object-reference-id-1 is defined as an object reference of a certain class (defined as USAGE OBJECT REFERENCE class-name), object-reference-id-2 must be an object reference of the same class or a class derived from that class. If the figurative constant NULL is specified, the receiving object-reference-id-1 is set to the NULL value. If SELF is specified, the SET statement must appear in the procedure division of a method. object-reference-id-1 is set to reference the object upon which the currently executing method was invoked.
408
Language Reference
SORT statement
The SORT statement accepts records from one or more files, sorts them according to the specified keys, and makes the sorted records available either through an output procedure or in an output file. See also MERGE statement on page 353. The SORT statement can appear anywhere in the procedure division except in the declarative portion. The SORT statement is not supported for programs compiled with the THREAD option.
Format
SORT file-name-1 ON
data-name-1 KEY
DUPLICATES WITH IN ORDER
SEQUENCE COLLATING IS
alphabet-name-1
USING file-name-2 INPUT PROCEDURE IS
GIVING file-name-3 OUTPUT PROCEDURE IS
file-name-1 The name given in the SD entry that describes the records to be sorted. No pair of file-names in a SORT statement can be specified in the same SAME SORT AREA clause or the SAME SORT-MERGE AREA clause. File-names
409
associated with the GIVING clause (file-name-3, ...) cannot be specified in the SAME AREA clause; however, they can be associated with the SAME RECORD AREA clause.
ASCENDING/DESCENDING KEY phrase

This phrase specifies that records are to be processed in ascending or descending sequence (depending on the phrase specified), based on the specified sort keys. data-name-1 Specifies a KEY data item on which the SORT statement will be based. Each such data-name must identify a data item in a record associated with file-name-1. The data-names following the word KEY are listed from left to right in the SORT statement in order of decreasing significance without regard to how they are divided into KEY phrases. The leftmost data-name is the major key, the next data-name is the next most significant key, and so forth. The following rules apply: v A specific KEY data item must be physically located in the same position and have the same data format in each input file. However, it need not have the same data-name. v If file-name-1 has more than one record description, the KEY data items need be described in only one of the record descriptions. v If file-name-1 contains variable-length records, all of the KEY data-items must be contained within the first n character positions of the record, where n equals the minimum records size specified for file-name-1. v KEY data items must not contain an OCCURS clause or be subordinate to an item that contains an OCCURS clause. v KEY data items cannot be variably located. v KEY data items cannot be group items that contain variable-occurrence data items. v KEY data items can be qualified. v KEY data items can be: Alphabetic, alphanumeric, alphanumeric-edited, numeric-edited, or numeric data items Internal or external floating-point data items National data items Windowed date fields, under these conditions: - The GIVING phrase must not specify an indexed file, because the (binary) ordering assumed or imposed by the file system conflicts with the windowed date ordering provided in the sort output. Attempting to write the windowed date merge output to such an indexed file will either fail or re-impose binary ordering, depending on how the file is accessed (the ACCESS MODE in the file-control entry). - If an alphanumeric windowed date field is specified as a KEY for a SORT statement, the collating sequence in effect for the merge operation must be EBCDIC. Thus the COLLATING SEQUENCE phrase of the SORT statement or, if this phrase is not specified, then any PROGRAM COLLATING SEQUENCE clause in the OBJECT-COMPUTER paragraph, must not specify a collating sequence other than EBCDIC or NATIVE.
410
Language Reference
If the SORT statement meets these conditions, the sort operation takes advantage of SORT Year 2000 features, provided that the execution environment includes a sort product that supports century windowing. A year-last windowed date field can be specified as a KEY for a SORT statement and can thereby exploit the corresponding century windowing capability of the sort product. For more information about using windowed date fields as KEY data items, see the Enterprise COBOL Programming Guide. If file-name-3 references an indexed file, the first specification of data-name-1 must be associated with an ASCENDING phrase and the data item referenced by that data-name-1 must occupy the same character positions in this record as the data item associated with the major record key for that file. The direction of the sorting operation depends on the specification of the ASCENDING or DESCENDING keywords as follows: v When ASCENDING is specified, the sequence is from the lowest key value to the highest key value. v When DESCENDING is specified, the sequence is from the highest key value to the lowest. If the KEY is a national item, the sequence of the KEY values is based on the binary values of the national characters. v If the KEY data item is in internal floating point, the sequence of key values will be in numeric order. v When the COLLATING SEQUENCE phrase is not specified, the key comparisons are performed according to the rules for comparison of operands in a relation condition (see Relation Condition under Conditional expressions on page 246). v When the COLLATING SEQUENCE phrase is specified, the indicated collating sequence is used for key data items of alphabetic, alphanumeric, alphanumeric-edited, external floating-point, and numeric-edited categories. For all other key data items, the comparisons are performed according to the rules for comparison of operands in a relation condition.
| |
DUPLICATES phrase
If the DUPLICATES phrase is specified, and the contents of all the key elements associated with one record are equal to the corresponding key elements in one or more other records, the order of return of these records is as follows: v The order of the associated input files as specified in the SORT statement. Within a given file the order is that in which the records are accessed from that file. v The order in which these records are released by an input procedure, when an input procedure is specified. If the DUPLICATES phrase is not specified, the order of these records is undefined. For more information about use of the DUPLICATES phrase, see the related discussion of alternate indexes in the Enterprise COBOL Programming Guide.
COLLATING SEQUENCE phrase

This phrase specifies the collating sequence to be used in alphanumeric comparisons for the KEY data items in this sorting operation.
411
The COLLATING SEQUENCE phrase has no effect for keys that are not alphanumeric. alphabet-name-1 Must be specified in the ALPHABET clause of the SPECIAL-NAMES paragraph. Any one of the alphabet-name clause phrases can be specified with the following results: STANDARD-1 The ASCII collating sequence is used for all alphanumeric comparisons. (The ASCII collating sequence is in Appendix C, EBCDIC and ASCII collating sequences, on page 549.) STANDARD-2 The International Reference Version of ISO/IEC 646, 7-bit coded character set for information processing interchange is used for all alphanumeric comparisons. NATIVE The EBCDIC collating sequence is used for all alphanumeric comparisons. (The EBCDIC collating sequence is in Appendix C, EBCDIC and ASCII collating sequences, on page 549.) EBCDIC The EBCDIC collating sequence is used for all alphanumeric comparisons. (The EBCDIC collating sequence is in Appendix C, EBCDIC and ASCII collating sequences, on page 549.) literal The collating sequence established by the specification of literals in the alphabet-name clause is used for all alphanumeric comparisons. When the COLLATING SEQUENCE phrase is omitted, the PROGRAM COLLATING SEQUENCE clause (if specified) in the OBJECT-COMPUTER paragraph specifies the collating sequence to be used. When both the COLLATING SEQUENCE phrase and the PROGRAM COLLATING SEQUENCE clause are omitted, the EBCDIC collating sequence is used.
USING phrase
file-name-2, ... The input files. When the USING phrase is specified, all the records in file-name-2, ..., (that is, the input files) are transferred automatically to file-name-1. At the time the SORT statement is executed, these files must not be open. The compiler opens, reads, makes records available, and closes these files automatically. If EXCEPTION/ERROR procedures are specified for these files, the compiler makes the necessary linkage to these procedures. All input files must be described in FD entries in the data division. If the USING phrase is specified and if file-name-1 contains variable-length records, the size of the records contained in the input files (file-name-2, ...) must be neither less than the smallest record nor greater than the largest record described for file-name-1. If file-name-1 contains fixed-length records, the size of the records contained in the input files must not be greater than the largest record described for file-name-1. For more information, see the Enterprise COBOL Programming Guide.
412
Language Reference
INPUT PROCEDURE phrase

This phrase specifies the name of a procedure that is to select or modify input records before the sorting operation begins. procedure-name-1 Specifies the first (or only) section or paragraph in the input procedure. procedure-name-2 Identifies the last section or paragraph of the input procedure. | | | | | | | | | The input procedure can consist of any procedure needed to select, modify, or copy the records that are made available one at a time by the RELEASE statement to the file referenced by file-name-1. The range includes all statements that are executed as the result of a transfer of control by CALL, EXIT, GO TO, PERFORM, and XML PARSE statements in the range of the input procedure, as well as all statements in declarative procedures that are executed as a result of the execution of statements in the range of the input procedure. The range of the input procedure must not cause the execution of any MERGE, RETURN, or SORT statement. If an input procedure is specified, control is passed to the input procedure before the file referenced by file-name-1 is sequenced by the SORT statement. The compiler inserts a return mechanism at the end of the last statement in the input procedure. When control passes the last statement in the input procedure, the records that have been released to the file referenced by file-name-1 are sorted.
GIVING phrase
file-name-3, ... The output files. When the GIVING phrase is specified, all the sorted records in file-name-1 are automatically transferred to the output files (file-name-3, ...). All output files must be described in FD entries in the data division. If the output files (file-name-3, ...) contain variable-length records, the size of the records contained in file-name-1 must be neither less than the smallest record nor greater than the largest record described for the output files. If the output files contain fixed-length records, the size of the records contained in file-name-1 must not be greater than the largest record described for the output files. For more information, see the Enterprise COBOL Programming Guide. At the time the SORT statement is executed, the output files (file-name-3, ...) must not be open. For each of the output files, the execution of the SORT statement causes the following actions to be taken: v The processing of the file is initiated. The initiation is performed as if an OPEN statement with the OUTPUT phrase had been executed. v The sorted logical records are returned and written onto the file. Each record is written as if a WRITE statement without any optional phrases had been executed. For a relative file, the relative key data item for the first record returned contains the value 1; for the second record returned, the value 2. After execution of the SORT statement, the content of the relative key data item indicates the last record returned to the file. v The processing of the file is terminated. The termination is performed as if a CLOSE statement without optional phrases had been executed.
413
These implicit functions are performed such that any associated USE AFTER EXCEPTION/ERROR procedures are executed; however, the execution of such a USE procedure must not cause the execution of any statement manipulating the file referenced by, or accessing the record area associated with, file-name-3. On the first attempt to write beyond the externally defined boundaries of the file, any USE AFTER STANDARD EXCEPTION/ERROR procedure specified for the file is executed. If control is returned from that USE procedure or if no such USE procedure is specified, the processing of the file is terminated.
OUTPUT PROCEDURE phrase

This phrase specifies the name of a procedure that is to select or modify output records from the sorting operation. procedure-name-3 Specifies the first (or only) section or paragraph in the output procedure. procedure-name-4 Identifies the last section or paragraph of the output procedure. | | | | | | | | | | The output procedure can consist of any procedure needed to select, modify, or copy the records that are made available one at a time by the RETURN statement in sorted order from the file referenced by file-name-1. The range includes all statements that are executed as the result of a transfer of control by CALL, EXIT, GO TO, PERFORM, and XML PARSE statements in the range of the output procedure. The range also includes all statements in declarative procedures that are executed as a result of the execution of statements in the range of the output procedure. The range of the output procedure must not cause the execution of any MERGE, RELEASE, or SORT statement. If an output procedure is specified, control passes to it after the file referenced by file-name-1 has been sequenced by the SORT statement. The compiler inserts a return mechanism at the end of the last statement in the output procedure and when control passes the last statement in the output procedure, the return mechanism provides the termination of the sort and then passes control to the next executable statement after the SORT statement. Before entering the output procedure, the sort procedure reaches a point at which it can select the next record in sorted order when requested. The RETURN statements in the output procedure are the requests for the next record. The INPUT PROCEDURE and OUTPUT PROCEDURE phrases are similar to those for a basic PERFORM statement. For example, if you name a procedure in an output procedure, that procedure is executed during the sorting operation just as if it were named in a PERFORM statement. As with the PERFORM statement, execution of the procedure is terminated after the last statement completes execution. The last statement in an input or output procedure can be the EXIT statement (see EXIT statement on page 325).
SORT special registers

The special registers, SORT-CORE-SIZE, SORT-MESSAGE, and SORT-MODE-SIZE, are equivalent to option control statement keywords in the sort control file. You define the sort control data set with the SORT-CONTROL special register.
414
Language Reference
Note: If you use a sort control file to specify control statements, the values specified in the sort control file take precedence over those in the special register. SORT-MESSAGE special register See SORT-MESSAGE on page 20. SORT-CORE-SIZE special register See SORT-CORE-SIZE on page 19. SORT-FILE-SIZE special register See SORT-FILE-SIZE on page 20. SORT-MODE-SIZE special register See SORT-MODE-SIZE on page 20. SORT-CONTROL special register See SORT-CONTROL on page 19. SORT-RETURN special register See SORT-RETURN on page 21.
If the SORT statement appears in a section that is not in an independent segment, any input or output procedure referenced by that SORT statement must appear either: v Totally within nonindependent segments v Wholly contained in a single independent segment If a SORT statement appears in an independent segment, then any input or output procedure referenced by that SORT statement must be contained either: v Totally within nonindependent segments v Wholly within the same independent segment as that SORT statement
415
START statement
The START statement provides a means of positioning within an indexed or relative file for subsequent sequential record retrieval. When the START statement is executed, the associated indexed or relative file must be open in either INPUT or I-O mode.
Format
START file-name-1
KEY IS
EQUAL TO = GREATER THAN > NOT LESS THAN NOT < GREATER THAN >= OR EQUAL TO
data-name-1
INVALID KEY
NOT INVALID KEY
END-START
file-name-1 Must name a file with sequential or dynamic access. file-name-1 must be defined in an FD entry in the data division and must not name a sort file.
KEY phrase
When the KEY phrase is specified, the file position indicator is positioned at the logical record in the file whose key field satisfies the comparison. When the KEY phrase is not specified, KEY IS EQUAL (to the prime record key) is implied. data-name-1 Can be qualified; it cannot be subscripted. When the START statement is executed, a comparison is made between the current value in the key data-name and the corresponding key field in the files index. If the FILE STATUS clause is specified in the file-control entry, the associated file status key is updated when the START statement is executed (See File status key on page 278).
INVALID KEY phrases

If the comparison is not satisfied by any record in the file, an invalid key condition exists; the position of the file position indicator is undefined, and (if specified) the
416
Language Reference
INVALID KEY imperative-statement is executed. (See INTO and FROM phrases on page 283 under Common processing facilities.) Both the INVALID KEY phrase and an applicable EXCEPTION/ERROR procedure can be omitted.
END-START phrase
This explicit scope terminator serves to delimit the scope of the START statement. END-START permits a conditional START statement to be nested in another conditional statement. END-START can also be used with an imperative START statement. For more information, see Delimited scope statements on page 271.
Indexed files
When the KEY phrase is specified, the key data item used for the comparison is data-name-1. When the KEY phrase is not specified, the key data item used for the EQUAL TO comparison is the prime RECORD KEY. When START statement execution is successful, the RECORD KEY or ALTERNATE RECORD KEY with which data-name-1 is associated becomes the key of reference for subsequent READ statements. data-name-1 Can be any of the following: v The prime RECORD KEY. v Any ALTERNATE RECORD KEY. v A data item within a record description for a file whose leftmost character position corresponds to the leftmost character position of that record key; it can be qualified. The size of the data item must be less than or equal to the length of the record key for the file. Regardless of its category, data-name-1 is treated as an alphanumeric item for purposes of the comparison operation. The file position indicator points to the first record in the file whose key field satisfies the comparison. If the operands in the comparison are of unequal lengths, the comparison proceeds as if the longer field were truncated on the right to the length of the shorter field. All other numeric and alphanumeric comparison rules apply, except that the PROGRAM COLLATING SEQUENCE clause, if specified, has no effect. When START statement execution is successful, the RECORD KEY with which data-name-1 is associated becomes the key of reference for subsequent READ statements. When START statement execution is unsuccessful, the key of reference is undefined.
Relative files
When the KEY phrase is specified, data-name-1 must specify the RELATIVE KEY.
417
Whether or not the KEY phrase is specified, the key data item used in the comparison is the RELATIVE KEY data item. Numeric comparison rules apply. The file position indicator points to the logical record in the file whose key satisfies the specified comparison.
418
Language Reference
STOP statement
The STOP statement halts execution of the object program either permanently or temporarily.
Format
STOP RUN literal
literal Can be a fixed-point numeric literal (signed or unsigned) or an alphanumeric literal. It can be any figurative constant except ALL literal. When STOP literal is specified, the literal is communicated to the operator, and object program execution is suspended. Program execution is resumed only after operator intervention, and continues at the next executable statement in sequence. The STOP literal statement is useful for special situations when operator intervention is needed during program execution; for example, when a special tape or disk must be mounted or a specific daily code must be entered. However, the ACCEPT and DISPLAY statements are preferred when operator intervention is needed. Do not use the STOP literal statement in programs compiled with the THREAD compiler option. When STOP RUN is specified, execution is terminated and control is returned to the system. When STOP RUN is not the last or only statement in a sequence of imperative statements within a sentence, the statements following STOP RUN are not executed. The STOP RUN statement closes all files defined in any of the programs in the run unit. For use of the STOP RUN statement in calling and called programs, see the following table.
Termination statement Main program STOP RUN Return to calling program. (Can be the system and cause the application to end.) Subprogram Return directly to the program that called the main program. (Can be the system and cause the application to end.)
419
STRING statement
The STRING statement strings 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.
Format
STRING
DELIMITED BY
identifier-2 literal-2 SIZE
INTO
identifier-3 POINTER identifier-4 WITH
OVERFLOW imperative-statement-1 ON
NOT ON
OVERFLOW imperative-statement-2
END-STRING
identifier-1 Represents the sending fields. When a sending field or any of the delimiters is an elementary numeric item, each numeric item must be described as an integer and its PICTURE character-string must not contain the symbol P. literal-1 Represents the sending fields. The following rules apply to all literals in the STRING statement: v When literals or identifiers are alphanumeric, any literal can be specified as any figurative constant except the ALL literal. Each figurative constant is considered a one-character alphanumeric literal.
420
Language Reference
v When literals or identifiers are national, any literal can be specified as a figurative constant SPACE, ZERO, or QUOTE. Each figurative constant is considered a one-character national literal. When any identifier or literal in the STRING statement is class DBCS, all identifiers and literals must be class DBCS, except identifier-4. When any identifier or literal in the STRING statement is class national, all identifiers and literals must be class national, except identifier-4. None of the identifiers in a STRING statement can be a windowed date field.
DELIMITED BY phrase
The DELIMITED BY phrase sets the limits of the string. identifier-2, literal-2 Are delimiters; that is, characters that delimit the data to be transferred. If identifier-1 or identifier-2 occupies the same storage area as identifier-3 or identifier-4, undefined results will occur, even if the identifiers are defined by the same data description entry. SIZE Transfers the complete sending area.
INTO phrase
identifier-3 Represents the receiving field. It must not represent an edited data item or external floating-point item and must not be described with the JUSTIFIED clause. identifier-3 can be reference-modified. If identifier-3 and identifier-4 occupy the same storage area, undefined results will occur, even if the identifiers are defined by the same data description entry.
POINTER phrase
identifier-4 Represents the pointer field, which points to a character position in the receiving field. It must be an elementary integer data item large enough to contain a value equal to the length of the receiving area plus 1. The pointer field must not contain the symbol P in its PICTURE character-string. When identifier-3 (the receiving field) is a DBCS data item, identifier-4 indicates the relative DBCS character position (not the relative byte position) in the receiving field. When identifier-3 is a national data item, identifier-4 indicates the relative national character position in the receiving field.
ON OVERFLOW phrases
imperative-statement-1 Executed when the pointer value (explicit or implicit): v Is less than 1
421
v Exceeds a value equal to the length of the receiving field When either of the above conditions occurs, an overflow condition exists, and no more data is transferred. Then the STRING operation is terminated, the NOT ON OVERFLOW phrase, if specified, is ignored, and control is transferred to the end of the STRING statement or, if the ON OVERFLOW phrase is specified, to imperative-statement-1. If control is transferred to imperative-statement-1, execution continues according to the rules for each statement specified in imperative-statement-1. If a procedure branching or conditional statement that causes explicit transfer of control is executed, control is transferred according to the rules for that statement; otherwise, upon completion of the execution of imperative-statement-1, control is transferred to the end of the STRING statement. If at the time of execution of a STRING statement, conditions that would cause an overflow condition are not encountered, then after completion of the transfer of data, the ON OVERFLOW phrase, if specified, is ignored. Control is then transferred to the end of the STRING statement, or if the NOT ON OVERFLOW phrase is specified, to imperative-statement-2. If control is transferred to imperative-statement-2, execution continues according to the rules for each statement specified in imperative-statement-2. If a procedure branching or conditional statement that causes explicit transfer of control is executed, control is transferred according to the rules for that statement. Otherwise, upon completion of the execution of imperative-statement-2, control is transferred to the end of the STRING statement.
END-STRING phrase
This explicit scope terminator serves to delimit the scope of the STRING statement. END-STRING permits a conditional STRING statement to be nested in another conditional statement. END-STRING can also be used with an imperative STRING statement. For more information, see Delimited scope statements on page 271.
Data flow
When the STRING statement is executed, data is transferred from the sending fields to the receiving field. The order in which sending fields are processed is the order in which they are specified. The following rules apply: v Characters from the sending fields are transferred to the receiving fields in the following manner: For national sending fields, data is transferred using the rules for elementary national-to-national moves, except that no space filling takes place. For DBCS sending fields, data is transferred using the rules for DBCS-to-DBCS elementary moves, except that no space filling takes place. Otherwise, data is transferred to the receiving fields using the rules for alphanumeric-to-alphanumeric elementary moves, except that no space filling takes place (see MOVE statement on page 359). v When DELIMITED BY identifier or literal is specified, the contents of each sending item are transferred, character-by-character, beginning with the leftmost character position and continuing until either:
422
Language Reference
A delimiter for this sending field is reached (the delimiter itself is not transferred). The rightmost character of this sending field has been transferred. v When DELIMITED BY SIZE identifier is specified, each entire sending field is transferred to the receiving field. v When the receiving field is filled, or when all the sending fields have been processed, the operation is ended. v When the POINTER phrase is specified, an explicit pointer field is available to the COBOL user to control placement of data in the receiving field. The user must set the explicit pointers initial value, which must not be less than 1 and not more than the character position count of the receiving field. (Note that the pointer field must be defined as a field large enough to contain a value equal to the length of the receiving field plus 1; this precludes arithmetic overflow when the system updates the pointer at the end of the transfer.) v When the POINTER phrase is not specified, no pointer is available to the user. However, a conceptual implicit pointer with an initial value of 1 is used by the system. v Conceptually, when the STRING statement is executed, the initial pointer value (explicit or implicit) is the first character position within the receiving field into which data is to be transferred. Beginning at that position, data is then positioned, character-by-character, from left to right. After each character is positioned, the explicit or implicit pointer is increased by 1. The value in the pointer field is changed only in this manner. At the end of processing, the pointer value always indicates a value equal to one character position beyond the last character transferred into the receiving field. Note: Subscript, reference modification, variable-length or variable location calculations, and function evaluations are performed only once, at the beginning of the execution of the STRING statement. Therefore, if identifier-3 or identifier-4 is used as a subscript, reference-modifier, or function argument in the STRING statement, or affects the length or location of any of the identifiers in the STRING statement, their values are not affected by any results of the STRING statement. After STRING statement execution is completed, only that part of the receiving field into which data was transferred is changed. The rest of the receiving field contains the data that was present before this execution of the STRING statement. When the following STRING statement is executed, the results obtained will be like those illustrated in the figure after the statement.
STRING ID-1 ID-2 DELIMITED BY ID-3 ID-4 ID-5 DELIMITED BY SIZE INTO ID-7 WITH POINTER ID-8 END-STRING
423
424
Language Reference
SUBTRACT statement
The SUBTRACT statement subtracts one numeric item, or the sum of two or more numeric items, from one or more numeric items, and stores the result.
Format 1
SUBTRACT
FROM
NOT ON
END-SUBTRACT
All identifiers or literals preceding the keyword FROM are added together and their sum is subtracted from and stored immediately in identifier-2. This process is repeated for each successive occurrence of identifier-2, in the left-to-right order in which identifier-2 is specified.
Format 2
SUBTRACT
FROM
GIVING
NOT ON
END-SUBTRACT
425
All identifiers or literals preceding the keyword FROM are added together and their sum is subtracted from identifier-2 or literal-2. The result of the subtraction is stored as the new value of each data item referenced by identifier-3.
Format 3
SUBTRACT CORRESPONDING CORR identifier-1 FROM
NOT ON
END-SUBTRACT
Elementary data items within identifier-1 are subtracted from, and the results are stored in, the corresponding elementary data items within identifier-2. When the ARITH(COMPAT) compiler option is in effect, the composite of operands can contain a maximum of 30 digits. When the ARITH(EXTEND) compiler option is in effect, the composite of operands can contain a maximum of 31 digits. For more information about arithmetic intermediate results, see the Enterprise COBOL Programming Guide. For all formats: identifier In format 1, must name an elementary numeric item. In format 2, must name an elementary numeric item, unless the identifier follows the word GIVING. Each identifier following the word GIVING must name a numeric or numeric-edited elementary item. In format 3, must name a group item. The following restrictions apply to date fields: v In format 1, identifier-1 can specify at most one date field. If identifier-1 specifies a date field, then every instance of identifier-2 must specify a date field that is compatible with the date field specified by identifier-1. If identifier-1 does not specify a date field, then identifier-2 can specify one or more date fields, with no restriction on their DATE FORMAT clauses. v In format 2, identifier-1 and identifier-2 can each specify at most one date field. If identifier-1 specifies a date field, then the FROM identifier-2 must be a date field that is compatible with the date field specified by identifier-1. identifier-3 can specify one or more date fields. If identifier-2 specifies a date field and identifier-1 does not, then every instance of identifier-3 must specify a date field that is compatible with the date field specified by identifier-2. v In format 3, if an item within identifier-1 is a date field, then the corresponding item within identifier-2 must be a compatible date field.
426
Language Reference
v A year-last date field is allowed in a SUBTRACT statement only as identifier-1 and when the result of the subtraction is a nondate. There are two steps to determining the result of a SUBTRACT statement that involves one or more date fields: 1. Subtraction: determine the result of the subtraction operation, as described under Subtraction that involves date fields on page 244. 2. Storage: determine how the result is stored in the receiving field. (In formats 1 and 3, the receiving field is identifier-2; in format 3, the receiving field is the GIVING identifier-3.) For details, see Storing arithmetic results that involve date fields on page 245. literal Must be a numeric literal. Floating-point data items and literals can be used anywhere numeric data items and literals can be specified.
ROUNDED phrase
For information about the ROUNDED phrase, and for operand considerations, see ROUNDED phrase on page 273.
SIZE ERROR phrases

For information about the SIZE ERROR phrases, and for operand considerations, see SIZE ERROR phrases on page 274.
CORRESPONDING phrase (format 3)

See CORRESPONDING phrase on page 272.
END-SUBTRACT phrase
This explicit scope terminator serves to delimit the scope of the SUBTRACT statement. END-SUBTRACT permits a conditional SUBTRACT statement to be nested in another conditional statement. END-SUBTRACT can also be used with an imperative SUBTRACT statement. For more information, see Delimited scope statements on page 271.
427
UNSTRING statement
The UNSTRING statement causes contiguous data in a sending field to be separated and placed into multiple receiving fields.
Format
UNSTRING identifier-1
INTO DELIMITED BY ALL identifier-2 literal-1 OR ALL identifier-3 literal-2
identifier-4 DELIMITER IN POINTER identifier-7 WITH TALLYING IN identifier-5 COUNT IN identifier-8 identifier-6
OVERFLOW imperative-statement-1 ON
NOT ON
OVERFLOW imperative-statement-2
END-UNSTRING
identifier-1 Represents the sending field. Data is transferred from this field to the data receiving fields (identifier-4). identifier-1 must be an alphanumeric, alpahnumeric-edited, alphabetic, national, or DBCS data item. identifier-1 can be reference-modified. If any of identifier-1, identifier-2, literal-1, or any occurrence of identifier-3, identifier-4, identifier-5, or literal-2 is of class DBCS, then all must be of class DBCS. If any of identifier-1, identifier-2, literal-1, or any occurrence of identifier-3, identifier-4, identifier-5, or literal-2 is of class national, then all must be of class national.
428
Language Reference
If identifier-1 is alphanumeric, alphanumeric-edited, or alphabetic, then identifier-4, identifier-5, and any occurrences of identifier-2, identifier-3, literal-1, or literal-2 must have one of these categories. None of the identifiers in an UNSTRING statement can be windowed date fields. One UNSTRING statement can take the place of a series of MOVE statements, except that evaluation or calculation of certain elements is performed only once, at the beginning of the execution of the UNSTRING statement. For more information, see Values at the end of execution of the UNSTRING statement on page 434. The rules for moving are the same as those for a MOVE statement for an elementary sending item of the category of identifier-1, with the appropriate identifier-4 as the receiving item (see MOVE statement on page 359). For example, rules for moving a DBCS item are used when identifier-1 is a DBCS item.
DELIMITED BY phrase
This phrase specifies delimiters within the data that control the data transfer. If the DELIMITED BY phrase is not specified, the DELIMITER IN and COUNT IN phrases must not be specified. identifier-2, identifier-3 Must be one of the following: v An alphanumeric data item v A DBCS data item v A national data item Each represents one delimiter. literal-1, literal-2 Must be one of the following: v An alphanumeric literal, including any figurative constant except the ALL literal v A DBCS literal, including a figurative constant SPACE v A national literal, including a figurative constant SPACE, ZERO, or QUOTE Each represents one delimiter. When a figurative constant is specified, it is considered to be a one-character literal. ALL One or more contiguous occurrences of any delimiters are treated as if they were only one occurrence; this one occurrence is moved to the delimiter receiving field (identifier-5), if specified. The delimiting characters in the sending field are treated as an elementary item of the same usage and category as identifier-1 and are moved into the current delimiter receiving field according to the rules of the MOVE statement. When DELIMITED BY ALL is not specified, and two or more contiguous occurrences of any delimiter are encountered, the current data receiving field (identifier-4) is filled with spaces or zeros, according to the description of the data receiving field.
Delimiter with two or more characters

A delimiter that contains two or more characters is recognized as a delimiter only if the delimiting characters are both of the following:
429
v Contiguous v In the sequence specified in the sending field
Two or more delimiters

When two or more delimiters are specified, an OR condition exists, and each nonoverlapping occurrence of any one of the delimiters is recognized in the sending field in the sequence specified. For example:
DELIMITED BY AB or BC
An occurrence of either AB or BC in the sending field is considered a delimiter. An occurrence of ABC is considered an occurrence of AB.
INTO phrase
This phrase specifies the fields where the data is to be moved. identifier-4 Represents the data receiving fields. Each must have the same usage, either DISPLAY, DISPLAY-1, or NATIONAL. These fields can be defined as one of the following: v An alphabetic data item v An alphanumeric data item v A numeric data item (without the symbol P in its picture character-string) v A DBCS data item v A national data item identifier-4 cannot be defined as a floating-point item, an alphanumeric-edited data item, or a numeric-edited data item. DELIMITER IN If the DELIMITED BY phrase is not specified, the DELIMITER IN phrase must not be specified. identifier-5 Represents the delimiter receiving fields. It can be: v An alphanumeric data item v A DBCS data item v A national data item
COUNT IN If the DELIMITED BY phrase is not specified, the COUNT IN phrase must not be specified. identifier-6 Is the data count field for each data transfer. Each field holds the count of examined character positions in the sending field, terminated by the delimiters or the end of the sending field, for the move to this receiving field; the delimiters are not included in this count. identifier-6 must be an integer data item defined without the symbol P in the PICTURE string.
430
Language Reference
When identifier-1 (the sending field) is a DBCS data item, identifier-6 indicates the number of DBCS characters positions, not the number of bytes, examined in the sending field. When identifier-1 is a national data item, identifier-6 indicates the number of national character positions, not the number of bytes, examined in the sending field.
POINTER phrase
When the POINTER phrase is specified, the value of the pointer field behaves as if it were increased by 1 for each examined character position in the sending field. When execution of the UNSTRING statement is completed, the pointer field contains a value equal to its initial value, plus the number of character positions examined in the sending field. When this phrase is specified, the user must initialize identifier-7 before execution of the UNSTRING statement begins. identifier-7 Is the pointer field. This field contains a value that indicates a relative character position in the sending field. identifier-7 must be an integer data item defined without the symbol P in the PICTURE string. It must be described as a data item of sufficient size to contain a value equal to 1 plus the number of character positions in the data item referenced by identifier-1. When identifier-1 (the sending field) is a DBCS data item, identifier-7 indicates the relative DBCS character position (not the relative byte position) in the sending field. When identifier-1 is a national data item, identifier-7 indicates the relative national character position, not the relative byte position.
TALLYING IN phrase
When the TALLYING phrase is specified, the field-count field contains (at the end of execution of the UNSTRING statement) a value equal to the initial value, plus the number of data receiving areas acted upon. When this phrase is specified, the user must initialize identifier-8 before execution of the UNSTRING statement begins. identifier-8 Is the field-count field. This field is increased by the number of data receiving fields acted upon in this execution of the UNSTRING statement. It must be an integer data item defined without the symbol P in the PICTURE string.
ON OVERFLOW phrases
An overflow condition exists when: v The pointer value (explicit or implicit) is less than 1. v The pointer value (explicit or implicit) exceeds a value equal to the length of the sending field.
431
v All data receiving fields have been acted upon, and the sending field still contains unexamined character positions.
When an overflow condition occurs

An overflow condition results in the following: 1. No more data is transferred. 2. The UNSTRING operation is terminated. 3. The NOT ON OVERFLOW phrase, if specified, is ignored. 4. Control is transferred to the end of the UNSTRING statement or, if the ON OVERFLOW phrase is specified, to imperative-statement-1. imperative-statement-1 Statement or statements for dealing with an overflow condition. If control is transferred to imperative-statement-1, execution continues according to the rules for each statement specified in imperativestatement-1. If a procedure branching or conditional statement that causes explicit transfer of control is executed, control is transferred according to the rules for that statement. Otherwise, upon completion of the execution of imperative-statement-1, control is transferred to the end of the UNSTRING statement.
When an overflow condition does not occur

When, during execution of an UNSTRING statement, conditions that would cause an overflow condition are not encountered, then: 1. The transfer of data is completed. 2. The ON OVERFLOW phrase, if specified, is ignored. 3. Control is transferred to the end of the UNSTRING statement or, if the NOT ON OVERFLOW phrase is specified, to imperative-statement-2. imperative-statement-2 Statement or statements for dealing with an overflow condition that does not occur. If control is transferred to imperative-statement-2, execution continues according to the rules for each statement specified in imperativestatement-2. If a procedure branching or conditional statement that causes explicit transfer of control is executed, control is transferred according to the rules for that statement. Otherwise, upon completion of the execution of imperative-statement-2, control is transferred to the end of the UNSTRING statement.
END-UNSTRING phrase
This explicit scope terminator serves to delimit the scope of the UNSTRING statement. END-UNSTRING permits a conditional UNSTRING statement to be nested in another conditional statement. END-UNSTRING can also be used with an imperative UNSTRING statement. For more information, see Delimited scope statements on page 271.
Data flow
When the UNSTRING statement is initiated, data is transferred from the sending field to the current data receiving field, according to the following rules: Stage 1: Examine
432
Language Reference
1. If the POINTER phrase is specified, the field is examined, beginning at the relative character position specified by the value in the pointer field. If the POINTER phrase is not specified, the sending field character-string is examined, beginning with the leftmost character position. 2. If the DELIMITED BY phrase is specified, the examination proceeds from left to right, examining character positions one-by-one until a delimiter is encountered. If the end of the sending field is reached before a delimiter is found, the examination ends with the last character position in the sending field. If there are more receiving fields, the next one is selected; otherwise, an overflow condition occurs. If the DELIMITED BY phrase is not specified, the number of character positions examined is equal to the size of the current data receiving field, which depends on its data category, as shown in Treatment of the content of data items (Table 37 on page 342).
Table 50. Character positions examined when DELIMITED BY is not specified If the receiving field is ... Alphanumeric or alphabetic DBCS National Numeric The number of character positions examined is ... Equal to the number of character positions in the current receiving field Equal to the number of DBCS character positions in the current receiving field Equal to the number of national character positions in the current receiving field Equal to the number of character positions in the integer portion of the current receiving field 1 less than the size of the current receiving field Determined by the size of the current receiving field at the beginning of the UNSTRING operation
Described with the SIGN IS SEPARATE clause Described as a variable-length data item
Stage 2: Move 3. The examined character positions (excluding any delimiter characters) are treated as an alphanumeric elementary item, and are moved into the current data receiving field, according to the rules for the MOVE statement (see MOVE statement on page 359). 4. If the DELIMITER IN phrase is specified, the delimiting characters in the sending field are treated as an elementary alphanumeric item and are moved to the current delimiter receiving field, according to the rules for the MOVE statement. If the delimiting condition is the end of the sending field, the current delimiter receiving field is filled with spaces. 5. If the COUNT IN phrase is specified, a value equal to the number of examined character positions (excluding any delimiters) is moved into the data count field, according to the rules for an elementary move. Stage 3: Successive iterations 6. If the DELIMITED BY phrase is specified, the sending field is further examined, beginning with the first character position to the right of the delimiter. If the DELIMITED BY phrase is not specified, the sending field is further examined, beginning with the first character position to the right of the last character position examined.
433
7. For each succeeding data receiving field, this process of examining and moving is repeated until either of the following occurs: v All the characters in the sending field have been transferred. v There are no more unfilled data receiving fields.
Values at the end of execution of the UNSTRING statement

The following operations are performed only once, at the beginning of the execution of the UNSTRING statement: v Calculations of subscripts, reference modifications, variable-lengths, variable locations v Evaluations of functions Therefore, if identifier-4, identifier-5, identifier-6, identifier-7, or identifier-8 is used as a subscript, reference-modifier, or function argument in the UNSTRING statement, or affects the length or location of any of the identifiers in the UNSTRING statement, then these values are determined at the beginning of the UNSTRING statement, and are not affected by any results of the UNSTRING statement.
Example of the UNSTRING statement

The following figure shows the execution results for an example of the UNSTRING statement.
434
Language Reference
435
WRITE statement
The WRITE statement releases a logical record to an output or input/output file. When the WRITE statement is executed: v The associated sequential file must be open in OUTPUT or EXTEND mode. v The associated indexed or relative file must be open in OUTPUT, I-O, or EXTEND mode.

WRITE record-name-1 (1) FROM identifier-1 phrase 1 BEFORE AFTER ADVANCING identifier-2 integer-1 LINE LINES
invalid_key
mnemonic-name-1 PAGE not_invalid_key
END-WRITE
phrase 1:
AT
END-OF-PAGE EOP
NOT AT
END-OF-PAGE EOP
invalid_key:
INVALID KEY
not_invalid_key:
NOT INVALID KEY
Notes: 1 The BEFORE, AFTER, INVALID KEY, and AT END OF PAGE phrases are not valid for VSAM files.
436
Language Reference

WRITE record-name-1 FROM identifier-1
INVALID KEY
NOT INVALID KEY
END-WRITE

WRITE record-name-1 FROM identifier-1
AFTER ADVANCING
identifier-2 integer-1 PAGE
LINE LINES
END-WRITE
record-name-1 Must be defined in a data division FD entry. record-name-1 can be qualified. It must not be associated with a sort or merge file. For relative files, the number of character positions in the record being written can be different from the number of character positions in the record being replaced. FROM phrase The result of the execution of the WRITE statement with the FROM identifier-1 phrase is equivalent to the execution of the following statements in the order specified:
MOVE identifier-1 TO record-name-1. WRITE record-name-1.
The MOVE is performed according to the rules for a MOVE statement without the CORRESPONDING phrase. identifier-1 identifier-1 can reference any of the following: v A data item defined in the working-storage section, the local-storage section, or the linkage section v A record description for another previously opened file v An alphanumeric or national function
437
identifier-1 must be a valid sending item for a MOVE statement with record-name-1 as the receiving item. identifier-1 and record-name-1 must not refer to the same storage area. After the WRITE statement is executed, the information is still available in identifier-1. (See INTO and FROM phrases on page 283 under Common processing facilities.) identifier-2 Must be an integer data item.
ADVANCING phrase
The ADVANCING phrase controls positioning of the output record on the page. The BEFORE and AFTER phrases are not supported for VSAM files. QSAM files are sequentially organized. The ADVANCING and END-OF-PAGE phrases control the vertical positioning of each line on a printed page. You can specify the ADVANCING PAGE and END-OF-PAGE phrases in a single WRITE statement. If the printed page is held on an intermediate device (a disk, for example), the format can appear different than the expected output when it is edited or browsed.
ADVANCING phrase rules

When the ADVANCING phrase is specified, the following rules apply: 1. When BEFORE ADVANCING is specified, the line is printed before the page is advanced. 2. When AFTER ADVANCING is specified, the page is advanced before the line is printed. 3. When identifier-2 is specified, the page is advanced the number of lines equal to the current value in identifier-2. identifier-2 must name an elementary integer data item. identifier-2 cannot name a windowed date field. 4. When integer is specified, the page is advanced the number of lines equal to the value of integer. 5. Integer or the value in identifier-2 can be zero. 6. When PAGE is specified, the record is printed on the logical page BEFORE or AFTER (depending on the phrase used) the device is positioned to the next logical page. If PAGE has no meaning for the device used, then BEFORE or AFTER (depending on the phrase specified) ADVANCING 1 LINE is provided. If the FD entry contains a LINAGE clause, the repositioning is to the first printable line of the next page, as specified in that clause. If the LINAGE clause is omitted, the repositioning is to line 1 of the next succeeding page. 7. When mnemonic-name is specified, a skip to channels 1 through 12, or space suppression, takes place. mnemonic-name must be equated with environment-name-1 in the SPECIAL-NAMES paragraph. The mnemonic-name phrase can also be specified for stacker selection with a card punch file. When using stacker selection, WRITE AFTER ADVANCING must be used. The ADVANCING phrase of the WRITE statement, or the presence of a LINAGE clause on the file, causes a carriage control character to be generated in the record that is written. If the corresponding file is described with the EXTERNAL clause,
438
Language Reference
all file connectors within the run unit must be defined such that carriage control characters will be generated for records that are written. That is, if all the files have a LINAGE clause, some of the programs can use the WRITE statement with the ADVANCING phrase and other programs can use the WRITE statement without the ADVANCING phrase. However, if none of the files has a LINAGE clause, then if any of the programs use the WRITE statement with the ADVANCING phrase, all of the programs in the run unit that have a WRITE statement must use the WRITE statement with the ADVANCING phrase. When the ADVANCING phrase is omitted, automatic line advancing is provided, as if AFTER ADVANCING 1 LINE had been specified.
LINAGE-COUNTER rules
If the LINAGE clause is specified for this file, the associated LINAGE-COUNTER special register is modified during the execution of the WRITE statement, according to the following rules: 1. If ADVANCING PAGE is specified, LINAGE-COUNTER is reset to 1. 2. If ADVANCING identifier-2 or integer is specified, LINAGE-COUNTER is increased by the value in identifier-2 or integer. 3. If the ADVANCING phrase is omitted, LINAGE-COUNTER is increased by 1. 4. When the device is repositioned to the first available line of a new page, LINAGE-COUNTER is reset to 1. Note: If you use the ADV compiler option, the compiler adds 1 byte to the record length in order to allow for the control character. If in your record definition you already reserve the first byte for the control character, you should use the NOADV option. For files defined with the LINAGE clause, the NOADV option has no effect. The compiler processes these files as if the ADV option were specified.
END-OF-PAGE phrases
The AT END-OF-PAGE phrase is not supported for VSAM files. When END-OF-PAGE is specified, and the logical end of the printed page is reached during execution of the WRITE statement, the END-OF-PAGE imperative-statement is executed. When the END-OF-PAGE phrase is specified, the FD entry for this file must contain a LINAGE clause. The logical end of the printed page is specified in the associated LINAGE clause. An END-OF-PAGE condition is reached when execution of a WRITE END-OF-PAGE statement causes printing or spacing within the footing area of a page body. This occurs when execution of such a WRITE statement causes the value in the LINAGE-COUNTER special register to equal or exceed the value specified in the WITH FOOTING phrase of the LINAGE clause. The WRITE statement is executed, and then the END-OF-PAGE imperative-statement is executed. An automatic page overflow condition is reached whenever the execution of any given WRITE statement (with or without the END-OF-PAGE phrase) cannot be completely executed within the current page body. This occurs when a WRITE statement, if executed, would cause the value in the LINAGE-COUNTER to exceed the number of lines for the page body specified in the LINAGE clause. In this case, the line is printed BEFORE or AFTER (depending on the option specified) the device is repositioned to the first printable line on the next logical page, as
439
specified in the LINAGE clause. If the END-OF-PAGE phrase is specified, the END-OF-PAGE imperative-statement is then executed. If the WITH FOOTING phrase of the LINAGE clause is not specified, the automatic page overflow condition exists because no end-of-page condition (as distinct from the page overflow condition) can be detected. If the WITH FOOTING phrase is specified, but the execution of a given WRITE statement would cause the LINAGE-COUNTER to exceed both the footing value and the page body value specified in the LINAGE clause, then both the end-of-page condition and the automatic page overflow condition occur simultaneously. The keywords END-OF-PAGE and EOP are equivalent. You can specify both the ADVANCING PAGE phrase and the END-OF-PAGE phrase in a single WRITE statement.
INVALID KEY phrases

The INVALID KEY phrase is not supported for VSAM sequential files. An invalid key condition is caused by the following: v For sequential files, an attempt is made to write beyond the externally defined boundary of the file. v For indexed files: An attempt is made to write beyond the externally defined boundary of the file. ACCESS SEQUENTIAL is specified and the file is opened OUTPUT, and the value of the prime record key is not greater than that of the previous record. The file is opened OUTPUT or I-O and the value of the prime record key equals that of an already existing record. v For relative files: An attempt is made to write beyond the externally defined boundary of the file. When the access mode is random or dynamic and the RELATIVE KEY data item specifies a record that already exists in the file. The number of significant digits in the relative record number is larger than the size of the relative key data item for the file. When an invalid key condition occurs: v If the INVALID KEY phrase is specified, imperative-statement-1 is executed. (See File status key values and meanings (Table 32 on page 279).) v Otherwise, the WRITE statement is unsuccessful and the contents of record-name are unaffected (except for QSAM files) and the following occurs: For sequential files, the file status key, if specified, is updated and an EXCEPTION/ERROR condition exists. If an explicit or implicit EXCEPTION/ERROR procedure is specified for the file, the procedure is executed. If no such procedure is specified, the results are unpredictable. For relative and indexed files, program execution proceeds according to the rules described by Invalid key condition on page 282 under Common processing facilities.
440
Language Reference
The INVALID KEY conditions that apply to a relative file in OPEN OUTPUT mode also apply to one in OPEN EXTEND mode. v If the NOT INVALID KEY phrase is specified and a valid key condition exists at the end of the execution of the WRITE statement, control is passed to imperative-statement-4. Both the INVALID KEY phrase and an applicable EXCEPTION/ERROR procedure can be omitted.
END-WRITE phrase
This explicit scope terminator serves to delimit the scope of the WRITE statement. END-WRITE permits a conditional WRITE statement to be nested in another conditional statement. END-WRITE can also be used with an imperative WRITE statement. For more information, see Delimited scope statements on page 271.
WRITE for sequential files

The maximum record size for the file is established at the time the file is created, and cannot subsequently be changed. After the WRITE statement is executed, the logical record is no longer available in record-name-1 unless either: v The associated file is named in a SAME RECORD AREA clause (in which case, the record is also available as a record of the other files named in the SAME RECORD AREA clause) v The WRITE statement is unsuccessful because of a boundary violation. In either of these two cases, the logical record is still available in record-name-1. The file position indicator is not affected by execution of the WRITE statement. The number of character positions required to store the record in a file might or might not be the same as the number of character positions defined by the logical description of that record in the COBOL program. (See PICTURE clause editing on page 197 and USAGE clause on page 214.) If the FILE STATUS clause is specified in the file-control entry, the associated file status key is updated when the WRITE statement is executed, whether or not execution is successful. The WRITE statement can only be executed for a sequential file opened in OUTPUT or EXTEND mode for QSAM files.
Multivolume files
When end-of-volume is recognized for a multivolume OUTPUT file (tape or sequential direct-access file), the WRITE statement performs the following operations: v The standard ending volume label procedure v A volume switch v The standard beginning volume label procedure
441
Punch function files with the IBM 3525

When the punch function is used, the next I-O operation after the READ statement must be a WRITE statement for the punch function file. If you want to punch additional data into some of the cards and not into others, a dummy WRITE statement must be issued for the null cards, first filling the output area with SPACES. If stacker selection for the punch function file is desired, you can specify the appropriate stacker function-names in the SPECIAL-NAMES paragraph, and then issue WRITE ADVANCING statements using the associated mnemonic-names.
Print function files

After the punch function operations (if specified) are completed, you can issue WRITE statements for the print function file. If you wish to print additional data on some of the data cards and not on others, the WRITE statement for the null cards can be omitted. Any attempt to write beyond the limits of the card results in abnormal termination of the application, thus, the END-OF-PAGE phrase cannot be specified. Depending on the capabilities of the specific IBM 3525 model in use, the print file can be either a two-line print file or a multiline print file. Up to 64 characters can be printed on each line. v For a two-line print file, the lines are printed on line 1 (top edge of card) and line 3 (between rows 11 and 12). Line control cannot be specified. Automatic spacing is provided. v For a multiline print file, up to 25 lines of characters can be printed. Line control can be specified. If line control is not specified, automatic spacing is provided. Line control is specified by issuing WRITE AFTER ADVANCING statements for the print function file. If line control is used for one such statement, it must be used for all other WRITE statements issued to the file. The maximum number of printable characters, including any space characters, is 64. Such WRITE statements must not specify space suppression. Identifier and integer have the same meanings they have for other WRITE AFTER ADVANCING statements. However, such WRITE statements must not increase the line position on the card beyond the card limit, or abnormal termination results. The mnemonic-name option of the WRITE AFTER ADVANCING statement can also be specified. In the SPECIAL-NAMES paragraph, the environment-names can be associated with the mnemonic-names, as follows:
Table 51. Meanings of environment-names in SPECIAL NAMES paragraph environment-name C02 C03 C04 C05 ... C22 C12 Meaning Line 3 Line 5 Line 7 Line 9 ... Line 21 Line 23
442
Language Reference
Advanced Function Printing

When you use the WRITE ADVANCING phrase with a mnemonic-name associated with environment-name AFP-5A, a Print Services Facility (PSF) control character is placed in the control character position of the output record. This control character (X5A) allows Advanced Function Printing (AFP) services to be used. For more information, refer to the documentation for the Print Services Facility product: PSF for OS/390 & z/OS (5655-B17).
WRITE for indexed files

Before the WRITE statement is executed, you must set the prime record key (the RECORD KEY data item, as defined in the file-control entry) to the desired value. Note that RECORD KEY values must be unique within a file. If the ALTERNATE RECORD KEY clause is also specified in the file-control entry, each alternate record key must be unique, unless the DUPLICATES phrase is specified. If the DUPLICATES phrase is specified, alternate record key values might not be unique. In this case, the system stores the records so that later sequential access to the records allows retrieval in the same order in which they were stored. When ACCESS IS SEQUENTIAL is specified in the file-control entry, records must be released in ascending order of RECORD KEY values. When ACCESS IS RANDOM or ACCESS IS DYNAMIC is specified in the file-control entry, records can be released in any programmer-specified order.
WRITE for relative files

For OUTPUT files, the WRITE statement causes the following actions: v If ACCESS IS SEQUENTIAL is specified: The first record released has relative record number 1, the second record released has relative record number 2, the third number 3, and so on. If the RELATIVE KEY is specified in the file-control entry, the relative record number of the record just released is placed in the RELATIVE KEY during execution of the WRITE statement. v If ACCESS IS RANDOM or ACCESS IS DYNAMIC is specified, the RELATIVE KEY must contain the desired relative record number for this record before the WRITE statement is issued. When the WRITE statement is executed, this record is placed at the specified relative record number position in the file. For I-O files, either ACCESS IS RANDOM or ACCESS IS DYNAMIC must be specified; the WRITE statement inserts new records into the file. The RELATIVE KEY must contain the desired relative record number for this record before the WRITE statement is issued. When the WRITE statement is executed, this record is placed at the specified relative record number position in the file.
443
XML GENERATE statement

| The XML GENERATE statement converts data to XML format.
Format
XML GENERATE identifier-1 FROM identifier-2
COUNT IN
identifier-3
NOT ON
END-XML
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
identifier-1 The receiving area for a generated XML document. identifier-1 must be an alphanumeric or national data item. It must not be described with the JUSTIFIED clause, and cannot be a function identifier. identifier-1 can be subscripted or reference modified. identifier-1 must not overlap identifier-2 or identifier-3. If identifier-1 is alphanumeric, the generated XML document is encoded with the code page specified by the CODEPAGE compiler option in effect when the source code was compiled. If identifier-1 is a national data item, the generated XML document is encoded in UTF-16. A byte order mark is not generated. identifier-1 must be a national data item if the CODEPAGE compiler option specifies a DBCS code page or if the generated XML includes data from identifier-2 for: v Any national data item or DBCS data item v Any data item with a DBCS name (that is, a data item whose name contains DBCS characters) v An alphanumeric data item that contains DBCS characters identifier-1 must be large enough to contain the generated XML document. Typically, it should be from five to eight times the size of identifier-2, depending on the length of the data-name or data-names within identifier-2. If identifier-1 is not large enough, an error condition exists at the end of the XML GENERATE statement. identifier-2 The group or elementary data item to be converted to XML format. identifier-2 cannot be a function identifier or be reference modified, but it can be subscripted. identifier-2 must not overlap with identifier-1 or identifier-3. identifier-2 must not specify the RENAMES clause.
444
Language Reference
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
The following data items specified by identifier-2 are ignored by the XML GENERATE statement: v Any unnamed elementary data items or elementary FILLER data items v Any slack bytes inserted for SYNCHRONIZED items v Any data item subordinate to identifier-2 that is described with the REDEFINES clause or that is subordinate to such a redefining item v Any data item subordinate to identifier-2 that is described with the RENAMES clause v Any group data item all of whose subordinate data items are ignored All data items specified by identifier-2 that are not ignored according to the rules above must satisfy the following conditions: v Each elementary data item must either have class alphabetic, alphanumeric, numeric, or national, or be an index data item. (That is, no elementary data item can be described with the USAGE POINTER, USAGE FUNCTION-POINTER, USAGE PROCEDURE-POINTER, or USAGE OBJECT REFERENCE phrase.) v There must be at least one such elementary data item. v Each non-FILLER data-name must be unique within any immediately superordinate group data item. v Any DBCS data-names, when converted to Unicode, must be legal as names in the XML specification, version 1.0. v The data items must not specify the DATE FORMAT clause, or the DATEPROC compiler option must not be in effect. For example, given the following data declaration:
01 STRUCT. 02 STAT PIC X(4). 02 IN-AREA PIC X(100). 02 OK-AREA REDEFINES IN-AREA. 03 FLAGS PIC X. 03 PIC X(3). 03 COUNTER USAGE COMP-5 PIC S9(9). 03 ASFNPTR REDEFINES COUNTER USAGE FUNCTION-POINTER. 03 UNREFERENCED PIC X(92). 02 NG-AREA1 REDEFINES IN-AREA. 03 FLAGS PIC X. 03 PIC X(3). 03 PTR USAGE POINTER. 03 ASNUM REDEFINES PTR USAGE COMP-5 PIC S9(9). 03 PIC X(92). 02 NG-AREA2 REDEFINES IN-AREA. 03 FN-CODE PIC X. 03 UNREFERENCED PIC X(3). 03 QTYONHAND USAGE BINARY PIC 9(5). 03 DESC USAGE NATIONAL PIC N(40). 03 UNREFERENCED PIC X(12).
The following data items can be specified as identifier-2: v STRUCT, of which subordinate data items STAT and IN-AREA would be converted to XML format. (OK-AREA, NG-AREA1, and NG-AREA2 are ignored because they specify the REDEFINES clause.) v OK-AREA, of which subordinate data items FLAGS, COUNTER, and UNREFERENCED would be converted. (The item whose data description
445
| | | | | | | | | | | | | | | | | | | | | | | |
entry specifies 03 PIC X(3) is ignored because it is an elementary FILLER data item. ASFNPTR is ignored because it specifies the REDEFINES clause.) v Any of the elementary data items that are subordinate to STRUCT except: ASFNPTR or PTR (disallowed usage) UNREFERENCED OF NG-AREA2 (nonunique names for data items that are otherwise eligible) Any FILLER data items The following data items cannot be specified as identifier-2: v NG-AREA1, because subordinate data item PTR specifies USAGE POINTER but does not specify the REDEFINES clause. (PTR would be ignored if it specified the REDEFINES clause.) v NG-AREA2, because subordinate elementary data items have the nonunique name UNREFERENCED. COUNT IN If the COUNT IN phrase is specified, identifier-3 contains (after execution of the XML GENERATE statement) the count of generated XML character positions. If identifier-1 (the receiver) is a national data item, the count is in national character positions (UTF-16 character encoding units). Otherwise, the count is in bytes. identifier-3 The data count field. Must be an integer data item defined without the symbol P in its picture string. identifier-3 must not overlap identifier-1 or identifier-2.
| | | | | | | | | | | | | | | | | | | | | | |
ON EXCEPTION An exception condition exists when an error occurs during generation of the XML document, for example if identifier-1 is not large enough to contain the generated XML document. In this case, XML generation stops and the content of the receiver, identifier-1, is undefined. If the COUNT IN phrase is specified, identifier-3 contains the number of character positions that were generated, which can range from 0 to the length of identifier-1. If the ON EXCEPTION phrase is specified, control is transferred to imperative-statement-1. If the ON EXCEPTION phrase is not specified, the NOT ON EXCEPTION phrase, if any, is ignored, and control is transferred to the end of the XML GENERATE statement. Special register XML-CODE contains an exception code, as detailed in the Enterprise COBOL Programming Guide. NOT ON EXCEPTION If an exception condition does not occur during generation of the XML document, control is passed to imperative-statement-2, if specified, otherwise to the end of the XML GENERATE statement. The ON EXCEPTION phrase, if specified, is ignored. Special register XML-CODE contains zero after execution of the XML GENERATE statement. END-XML phrase This explicit scope terminator delimits the scope of XML GENERATE or XML PARSE statements. END-XML permits a conditional XML GENERATE or XML PARSE statement (that is, an XML GENERATE or XML PARSE
446
Language Reference
| | | | | | | | | | |
statement that specifies the ON EXCEPTION or NOT ON EXCEPTION phrase) to be nested in another conditional statement. The scope of a conditional XML GENERATE or XML PARSE statement can be terminated by: v An END-XML phrase at the same level of nesting v A separator period END-XML can also be used with an XML GENERATE or XML PARSE statement that does not specify either the ON EXCEPTION or the NOT ON EXCEPTION phrase. For more information on explicit scope terminators, see Delimited scope statements on page 271.
Nested XML GENERATE or XML PARSE statements

| | | | | | | | | | When a given XML GENERATE or XML PARSE statement appears as imperative-statement-1 or imperative-statement-2, or as part of imperative-statement-1 or imperative-statement-2 of another XML GENERATE or XML PARSE statement, that given XML GENERATE or XML PARSE statement is a nested XML GENERATE or XML PARSE statement. Nested XML GENERATE or XML PARSE statements are considered to be matched XML GENERATE and END-XML, or XML PARSE and END-XML combinations proceeding from left to right. Thus, any END-XML phrase that is encountered is matched with the nearest preceding XML GENERATE or XML PARSE statement that has not been implicitly or explicitly terminated.
Operation of XML GENERATE

| | | | | | | | | | | | | | | | | | | | | The content of each eligible elementary data item within identifier-2 is converted to character format as described under Format conversion of elementary data on page 448 and Trimming of generated XML data on page 449. Only the first definition of each storage area is processed. Redefinitions of data items are not included. Data items that are effectively defined by the RENAMES clause are also not included. The converted content is then inserted as element character content in XML markup. The XML element names are derived from the data-names within identifier-2 as described under XML element name formation on page 449. The names of group items that contain the selected elementary items are retained as parent elements. No extra white space (new lines, indentation, and so forth) is inserted to make the generated XML more readable. An XML declaration is not generated. If the receiving area specified by identifier-1 is not large enough to contain the resulting XML document, an error condition exists. See the description of the ON EXCEPTION phrase above for details. If identifier-1 is longer than the generated XML document, only that part of identifier-1 in which XML is generated is changed. The rest of identifier-1 contains the data that was present before this execution of the XML GENERATE statement. To avoid referring to that data, either initialize identifier-1 to spaces before the XML GENERATE statement or specify the COUNT IN phrase.
447
| | | | | | | | | | | | |
If the COUNT IN phrase is specified, identifier-3 contains (after execution of the XML GENERATE statement) the total number of character positions (UTF-16 encoding units or bytes) that were generated. You can use identifier-3 as a reference modification length field to refer to the part of identifier-2 that contains the generated XML document. After execution of the XML GENERATE statement, special register XML-CODE contains either zero, which indicates successful completion, or a nonzero exception code. (See also the Enterprise COBOL Programming Guide for details.) The XML PARSE statement also uses special register XML-CODE. Therefore if you code an XML GENERATE statement in the processing procedure of an XML PARSE statement, save the value of XML-CODE before that XML GENERATE statement executes and restore the saved value after the XML GENERATE statement terminates.
Format conversion of elementary data

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Elementary data items are converted to character format depending on the type of the data item: v Alphabetic, alphanumeric, alphanumeric-edited, DBCS, external floating-point, national, and numeric-edited items are not converted. v Fixed-point numeric data items other than COMPUTATIONAL-5 (COMP-5) binary data items or binary data items compiled with the TRUNC(BIN) compiler option are converted as if they were moved to a numeric-edited item that has: As many integer positions as the numeric item has, but with at least one integer position An explicit decimal point, if the numeric item has at least one decimal position The same number of decimal positions as the numeric item has A leading - picture symbol if the data item is signed (has an S in its PICTURE clause) v COMPUTATIONAL-5 (COMP-5) binary data items or binary data items compiled with the TRUNC(BIN) compiler option are converted in the same way as the other fixed-point numeric items, except for the number of integer positions. The number of integer positions is computed depending on the number of 9 symbols in the picture character string as follows: 5 minus the number of decimal places, if the data item has 1 to 4 9 picture symbols 10 minus the number of decimal places, if the data item has 5 to 9 9 picture symbols 20 minus the number of decimal places, if the data item has 10 to 18 9 picture symbols v Internal floating-point data items are converted as if they were moved to a data item as follows: For COMP-1: an external floating-point data item with PICTURE -9.9(8)E+99 For COMP-2: an external floating-point data item with PICTURE -9.9(17)E+99 (illegal because of the number of digit positions) v Index data items are converted as if they were declared USAGE COMP-5 PICTURE S9(9). After any conversion to character format, leading and trailing spaces and leading zeroes are eliminated, as described under Trimming of generated XML data on page 449.
448
Language Reference
| | | | | | | | | | | | | | | |
If a data item after any conversion contains any characters that are illegal in XML content, the original data value (that is, the value in the data item before any conversion or trimming) is represented in hexadecimal, and an element tag name with the prefix hex. is substituted for the regular tag name. For example, if data item Customer-Name is found at run time to contain LOW-VALUES, the XML element tag name hex.Customer-Name is used instead of the normal Customer-Name, and the content is represented as a string of pairs of zero digits. Any remaining instances of the five characters & (ampersand), (apostrophe), > (greater-than sign), < (less-than sign), and (quotation mark) are converted into the equivalent XML references &, ', >, <, and ", respectively. Then, if identifier-1 is a national data item, any nonnational values are converted to national format. Any remaining Unicode character represented by two UTF-16 encoding units (a surrogate pair) is replaced by an XML character reference. For example, the surrogate pair (NXD802, NXDC13) is replaced by the reference 𐠓.
Trimming of generated XML data

| | | | | | | | | | | | | | | | | | | | Trimming is performed on data values after their conversion to character format. (Conversion is described under Format conversion of elementary data on page 448.) For values converted from signed numeric values, the leading space is removed if the value is positive. For values converted from numeric items, leading zeroes (after any initial minus sign) up to but not including the digit immediately before the actual or implied decimal point are eliminated. Trailing zeroes after a decimal point are retained. For example: v -012.340 becomes -12.340. v 0000.45 becomes 0.45. v 0013 becomes 13. v 0000 becomes 0. Character values from alphabetic, alphanumeric, DBCS, and national data items have either trailing or leading spaces removed, depending on whether the corresponding data items have left (default) or right justification, respectively. That is, trailing spaces are removed from values whose corresponding data items do not specify the JUSTIFIED clause. Leading spaces are removed from values whose data items do specify the JUSTIFIED clause. If a character value consists only of spaces, one space remains as the value after trimming is finished.
XML element name formation

| | | | | | | | In the XML documents that are generated from identifier-2, the XML element tag names are derived from the name of the data item specified by identifier-2 and from any eligible data-names that are subordinate to identifier-2 as follows: v The exact mixed-case spelling of data-names from the data description entry is retained. The spellings from any references to that data item (for example, in an OCCURS DEPENDING ON clause) are not used. v Data-names that start with a digit are prefixed by an underscore. For example, the data-name 3D becomes XML tag name _3D.
449
| | | | | | | |
v Names of data items that are found at run time to contain characters that are illegal in XML version 1.0 content are prefixed by hex., and the content itself is expressed in hexadecimal. DBCS data-names, when translated to Unicode, must be legal as names in the XML specification, version 1.0. For a discussion of the exception codes that special register XML-CODE can contain after execution of the XML GENERATE statement, see the Enterprise COBOL Programming Guide.
450
Language Reference
XML PARSE statement

The XML PARSE statement is the Enterprise COBOL language interface to the high-speed XML parser that is part of the COBOL run time. The XML PARSE statement parses an XML document into its individual pieces and passes each piece, one at a time, to a user-written processing procedure.
Format
XML PARSE identifier-1 PROCESSING PROCEDURE IS procedure-name-1 THROUGH THRU procedure-name-2
NOT ON
END-XML
identifier-1 Must be an alphanumeric or national data item that contains the XML document character stream. identifier-1 cannot be a function-identifier. If identifier-1 is alphanumeric, its content must be encoded using one of the character sets listed in Coded character sets for XML documents in the Enterprise COBOL Programming Guide. If identifier-1 is alphanumeric and contains an XML document that does not specify an encoding declaration, the XML document is parsed with the code page specified by the CODEPAGE compiler option. If identifier-1 is a national data item, its content must be encoded using CCSID 1200 (Unicode UTF-16BE). It must not contain any character entities that are represented using multiple encoding units. Use a character reference, for example: | | v 𐠓 or v 𐠓 to represent any such characters. PROCESSING PROCEDURE phrase Specifies the name of a procedure to handle the various events that the XML parser generates. | | | | | procedure-name-1, procedure-name-2 Must name a section or paragraph in the procedure division. When both procedure-name-1 and procedure-name-2 are specified, if either is a procedure name in a declarative procedure, both must be procedure names in the same declarative procedure. procedure-name-1 Specifies the first (or only) section or paragraph in the processing procedure.
451
procedure-name-2 Specifies the last section or paragraph in the processing procedure. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For each XML event, the parser transfers control to the first statement of the procedure named procedure-name-1. Control is always returned from the processing procedure to the XML parser. The point from which control is returned is determined as follows: v If procedure-name-1 is a paragraph name and procedure-name-2 is not specified, the return is made after the execution of the last statement of the procedure-name-1 paragraph. v If procedure-name-1 is a section name and procedure-name-2 is not specified, the return is made after the execution of the last statement of the last paragraph in the procedure-name-1 section. v If procedure-name-2 is specified and it is a paragraph name, the return is made after the execution of the last statement of the procedure-name-2 paragraph. v If procedure-name-2 is specified and it is a section name, the return is made after the execution of the last statement of the last paragraph in the procedure-name-2 section. The only necessary relationship between procedure-name-1 and procedure-name-2 is that they define a consecutive sequence of operations to execute, beginning at the procedure named by procedure-name-1 and ending with the execution of the procedure named by procedure-name-2. If there are two or more logical paths to the return point, then procedure-name-2 can name a paragraph that consists only of an EXIT statement; all the paths to the return point must then lead to this paragraph. The processing procedure consists of all the statements at which XML events are handled. The range of the processing procedure includes all statements executed by CALL, EXIT, GO TO, GOBACK, INVOKE, MERGE, PERFORM, and SORT statements that are in the range of the processing procedure, as well as all statements in declarative procedures that are executed as a result of the execution of statements in the range of the processing procedure. The range of the processing procedure must not cause the execution of any GOBACK or EXIT PROGRAM statement, except to return control from a method or program to which control was passed by an INVOKE or CALL statement, respectively, that is executed in the range of the processing procedure. The range of the processing procedure must not cause the execution of an XML PARSE statement, unless the XML PARSE statement is executed in a method or outermost program to which control was passed by an INVOKE or CALL statement that is executed in the range of the processing procedure. A program executing on multiple threads can execute the same XML statement or different XML statements simultaneously. The processing procedure can terminate the run unit with a STOP RUN statement.
452
Language Reference
For more details about the processing procedure, see Control flow on page 454.
ON EXCEPTION The ON EXCEPTION phrase specifies imperative statements that are executed when the XML PARSE statement raises an exception condition. | | An exception condition exists when the XML parser detects an error in processing the XML document. The parser first signals an XML exception by passing control to the processing procedure with special register XML-EVENT containing EXCEPTION. The parser also provides a numeric error code in special register XML-CODE, as detailed in the Enterprise COBOL Programming Guide. An exception condition also exists if the parsing is deliberately terminated by the processing procedure setting XML-CODE to -1 before returning to the parser for any normal XML event. In this case, the parser does not signal an XML exception event. If the ON EXCEPTION phrase is specified, the parser then transfers control to imperative-statement-1. If the ON EXCEPTION phrase is not specified, the NOT ON EXCEPTION phrase, if any, is ignored, and control is transferred to the end of the XML PARSE statement. | | Special register XML-CODE contains the numeric error code for the XML exception or -1 after execution of the XML PARSE statement. If the processing procedure handles the XML exception event and sets XML-CODE to zero before returning control to the parser, the exception condition no longer exists. If no other unhandled exceptions occur prior to the termination of the parser, control is transferred to imperative-statement-2 of the NOT ON EXCEPTION phrase, if specified. NOT ON EXCEPTION The NOT ON EXCEPTION phrase specifies imperative statements that are executed when no exception condition exists at the termination of XML PARSE processing. If an exception condition does not exist at termination of XML PARSE processing, control is transferred to imperative-statement-2 of the NOT ON EXCEPTION phrase, if specified. If the NOT ON EXCEPTION phrase is not specified, control is transferred to the end of the XML PARSE statement. The ON EXCEPTION phrase, if specified, is ignored. Special register XML-CODE contains zero after execution of the XML PARSE statement. | | | | | | | | | END-XML phrase This explicit scope terminator delimits the scope of XML GENERATE or XML PARSE statements. END-XML permits a conditional XML GENERATE or XML PARSE statement (that is, an XML GENERATE or XML PARSE statement that specifies the ON EXCEPTION or NOT ON EXCEPTION phrase) to be nested in another conditional statement. The scope of a conditional XML GENERATE or XML PARSE statement can be terminated by: v An END-XML phrase at the same level of nesting v A separator period
| |
453
END-XML can also be used with an XML GENERATE or XML PARSE statement that does not specify either the ON EXCEPTION or NOT ON EXCEPTION phrase. For more information on explicit scope terminators, see Delimited scope statements on page 271.
| |
Nested XML GENERATE or XML PARSE statements

| | | | | | | | | | When a given XML GENERATE or XML PARSE statement appears as imperative-statement-1 or imperative-statement-2, or as part of imperative-statement-1 or imperative-statement-2 of another XML GENERATE or XML PARSE statement, that given XML GENERATE or XML PARSE statement is a nested XML GENERATE or XML PARSE statement. Nested XML GENERATE or XML PARSE statements are considered to be matched XML GENERATE and END-XML, or XML PARSE and END-XML combinations proceeding from left to right. Thus, any END-XML phrase that is encountered is matched with the nearest preceding XML GENERATE or XML PARSE statement that has not been implicitly or explicitly terminated.
Control flow
When the XML parser receives control from an XML PARSE statement, the parser analyzes the XML document and transfers control to procedure-name-1 at the following points in the process: v The start of the parsing process v When a document fragment is found v When the parser detects an error in parsing the XML document v The end of processing the XML document Control returns to the XML parser when the end of the processing procedure is reached. The exchange of control between the parser and the processing procedure continues until either: v The entire XML document has been parsed, ending with the END-OF-DOCUMENT event. v The parser detects an exception and the processing procedure does not reset special register XML-CODE to zero prior to returning to the parser. v The processing procedure terminates parsing deliberately by setting XML-CODE to -1 prior to returning to the parser. Then, the parser terminates and returns control to the XML PARSE statement with the XML-CODE special register containing the most recent value set by the parser or the processing procedure. For each XML event passed to the processing procedure, the XML-CODE, XML-EVENT, and XML-TEXT or XML-NTEXT special registers contain information about the particular event. The content of the XML-CODE special register is defined during and after execution of an XML PARSE statement. The contents of all other XML special registers are undefined outside the range of the processing procedure.
454
Language Reference
For normal XML events, special register XML-CODE contains zero when the processing procedure receives control. For XML exception events, XML-CODE contains one of the XML exception codes specified in the Enterprise COBOL Programming Guide. Special register XML-EVENT is set to the event name, such as START-OF-DOCUMENT. Either XML-TEXT or XML-NTEXT contains the piece of the document corresponding with the event, as described in XML-EVENT on page 22. For more information about the XML special registers, see Special registers on page 13. For all kinds of XML events, if XML-CODE is not zero when the processing procedure returns control to the parser, the parser terminates without a further EXCEPTION event. Setting XML-CODE to -1 before returning to the parser from the processing procedure for an event other than EXCEPTION forces the parser to terminate with a user-initiated exception condition. For some EXCEPTION events, the processing procedure can handle the event, then set XML-CODE to zero to force the parser to continue, although subsequent results are unpredictable. When XML-CODE is zero, parsing continues until the entire XML document has been parsed or an exception condition occurs. For more information about the EXCEPTION event and exception processing, see the Enterprise COBOL Programming Guide.
455
456
Language Reference
Part 7. Intrinsic functions

Chapter 22. Intrinsic functions . Specifying a function . . . . . Function definition and evaluation Types of functions . . . . . . Rules for usage . . . . . . . Arguments . . . . . . . . ALL subscripting . . . . . . Function definitions . . . . . ACOS . . . . . . . . . . ANNUITY . . . . . . . . ASIN . . . . . . . . . . ATAN . . . . . . . . . . CHAR . . . . . . . . . . COS . . . . . . . . . . CURRENT-DATE . . . . . . DATE-OF-INTEGER . . . . . DATE-TO-YYYYMMDD . . . . DATEVAL . . . . . . . . DAY-OF-INTEGER . . . . . DAY-TO-YYYYDDD . . . . . DISPLAY-OF . . . . . . . FACTORIAL. . . . . . . . INTEGER . . . . . . . . INTEGER-OF-DATE . . . . . INTEGER-OF-DAY . . . . . INTEGER-PART . . . . . . LENGTH . . . . . . . . . LOG . . . . . . . . . . LOG10 . . . . . . . . . LOWER-CASE . . . . . . . MAX . . . . . . . . . . MEAN . . . . . . . . . MEDIAN . . . . . . . . . MIDRANGE . . . . . . . . MIN . . . . . . . . . . MOD . . . . . . . . . . NATIONAL-OF . . . . . . NUMVAL . . . . . . . . NUMVAL-C . . . . . . . . ORD . . . . . . . . . . ORD-MAX . . . . . . . . ORD-MIN . . . . . . . . PRESENT-VALUE . . . . . . RANDOM . . . . . . . . RANGE . . . . . . . . . REM . . . . . . . . . . REVERSE. . . . . . . . . SIN . . . . . . . . . . . SQRT . . . . . . . . . . STANDARD-DEVIATION . . . SUM . . . . . . . . . . TAN . . . . . . . . . . UNDATE . . . . . . . . . UPPER-CASE . . . . . . . VARIANCE . . . . . . . . WHEN-COMPILED . . . . .
. . . . . . 459 . . . . . . 459 . . . . . . 460 . . . . . . 460 . . . . . . 461 . . . . . . 462 . . . . . . 464 . . . . . . 465 . . . . . . 469 . . . . . . 470 . . . . . . 470 . . . . . . 471 . . . . . . 471 . . . . . . 471 . . . . . . 472 . . . . . . 473 . . . . . . 474 . . . . . . 474 . . . . . . 475 . . . . . . 476 . . . . . . 477 . . . . . . 478 . . . . . . 479 . . . . . . 479 . . . . . . 480 . . . . . . 480 . . . . . . 481 . . . . . . 482 . . . . . . 482 . . . . . . 482 . . . . . . 483 . . . . . . 484 . . . . . . 484 . . . . . . 485 . . . . . . 485 . . . . . . 486 . . . . . . 487 . . . . . . 488 . . . . . . 489 . . . . . . 490 . . . . . . 491 . . . . . . 491 . . . . . . 492 . . . . . . 493 . . . . . . 493 . . . . . . 494 . . . . . . 494 . . . . . . 495 . . . . . . 495 . . . . . . 496 . . . . . . 496 . . . . . . 497 . . . . . . 497 . . . . . . 497 . . . . . . 498 . . . . . . 499
YEAR-TO-YYYY . YEARWINDOW .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. 500 . 501
457
458
Language Reference
Chapter 22. Intrinsic functions

Data processing problems often require the use of values that are not directly accessible in the data storage associated with the object program, but instead must be derived through performing operations on other data. An intrinsic function is a function that performs a mathematical, character, or logical operation, and thereby allows you to make reference to a data item whose value is derived automatically during execution. The functions can be grouped into six categories, based on the type of service performed: v Mathematical v Statistical v Date/time v Financial v Character-handling v General You can reference a function by specifying its name, along with any required arguments, in a procedure division statement. functions are elementary data items, and return alphanumeric, national, numeric, or integer values. Functions cannot serve as receiving operands.
Specifying a function
The general format of a function-identifier is:
Format
FUNCTION function-name-1
argument-1
reference-modifier
function-name-1 function-name-1 must be one of the intrinsic function names. argument-1 argument-1 must be an identifier, literal (other than a figurative constant), or arithmetic expression. argument-1 cannot be a windowed date field, except in the UNDATE intrinsic function. reference-modifier Can be specified only for functions of the category alphanumeric or national.
459
The following statements illustrate the use of an alphanumeric intrinsic function and a numeric intrinsic function. The statement
MOVE FUNCTION UPPER-CASE(hello) TO DATA-NAME.
uses the alphanumeric function UPPER-CASE to replace each lowercase letter in the argument with the corresponding uppercase letter, resulting in the movement of HELLO into DATA-NAME. The statement
COMPUTE NUM-ITEM = FUNCTION SUM(A B C)
uses the numeric function SUM to add the values of A, B, and C and places the result in NUM-ITEM. Within a procedure division statement, each function-identifier is evaluated at the same time as any reference modification or subscripting associated with an identifier in that same position would be evaluated.
Function definition and evaluation

The class and characteristics of a function, and the number and types of arguments it requires, are determined by its function definition. These characteristics include: v For alphanumeric and national functions, the size of the returned value v For numeric and integer functions, the sign of the returned value, and whether the function is integer v The actual value returned by the function For some functions, the class and characteristics are determined by the arguments to the function. The evaluation of any intrinsic function is not affected by the context in which it appears; in other words, function evaluation is not affected by operations or operands outside the function. However, evaluation of a function can be affected by the attributes of its arguments.
Types of functions
COBOL has the following types of functions: v Alphanumeric v National v Numeric v Integer Alphanumeric functions are of class and category alphanumeric. The value returned has an implicit usage of DISPLAY and is in standard data format characters. The number of character positions in the value returned is determined by the function definition. National functions are of class and category national. The value returned has an implicit usage of NATIONAL and is represented in national characters (UTF-16). The number of character positions in the value returned is determined by the function definition.
460
Language Reference
Numeric functions are of class and category numeric. The returned value is always considered to have an operational sign and is a numeric intermediate result. For more information, see the Enterprise COBOL Programming Guide. Integer functions are of class and category numeric. The returned value is always considered to have an operational sign and is an integer intermediate result. The number of digit positions in the value returned is determined by the function definition. For more information, see the Enterprise COBOL Programming Guide.
Rules for usage

Alphanumeric functions An alphanumeric function can be specified anywhere in the general formats that an identifier is permitted and where the rules associated with the general formats do not specifically prohibit reference to functions, except as noted below. An alphanumeric function can be used as an argument for any function that allows an alphanumeric argument. Reference modification of an alphanumeric function is allowed. If reference modification is specified for a function, the evaluation of the reference modification takes place immediately after the evaluation of the function; that is, the functions returned value is reference-modified. An alphanumeric function cannot be used: v As a receiving operand of any statement v Where the rules associated with the general formats require the data item being referenced to have particular characteristics (such as class and category, usage, size, and permissible values) and the evaluation of the function according to its definition and the particular arguments specified would not have these characteristics National functions A national function can be specified anywhere in the general formats that a national data item is permitted and where the rules associated with the general formats do not specifically prohibit reference to functions, except as noted below. A national function can be used as an argument for any function that allows a national argument. Reference modification of a national function is allowed. If reference modification is specified for a function, the evaluation of the reference modification takes place immediately after the evaluation of the function; that is, the functions returned value is reference-modified. A national function cannot be used: v As a receiving operand of any statement v Where the rules associated with the general formats require the data item being referenced to have particular characteristics (such as size and permissible values) and the evaluation of the function according to its definition and the particular arguments specified would not have those characteristics Numeric functions A numeric function can be used only where an arithmetic expression can be specified.
461
A numeric function can be referenced as an argument for a function that allows a numeric argument. A numeric function cannot be used where an integer operand is required, even if the particular reference would yield an integer value. The INTEGER or INTEGER-PART functions can be used to force the type of a numeric argument to be an integer. Integer functions An integer function can be used only where an arithmetic expression can be specified. An integer function can be referenced as an argument for a function that allows an integer argument. Usage notes: v identifier-2 of the CALL statement must not be a function-identifier. v The COPY statement accepts function-identifiers of all types in the REPLACING phrase.
Arguments
The values returned by some functions are determined by the arguments specified in the function-identifier when the functions are evaluated. Some functions require no arguments; others require a fixed number of arguments, and still others accept a variable number of arguments. An argument must be one of the following: v v v v v A data item identifier An arithmetic expression A function-identifier A literal other than a figurative constant A special-register
The argument to a function can be any function or an expression containing a function, including another evaluation of the same function, whose result meets the category requirement for the argument. See Function definitions on page 465 for function specific argument specifications. The types of arguments are: Alphabetic An elementary data item of the class alphabetic or an alphanumeric literal containing only alphabetic characters. The content of the argument will be used to determine the value of the function. The length of the argument can be used to determine the value of the function. Alphanumeric A data item of the class alphabetic or alphanumeric or an alphanumeric literal. The content of the argument will be used to determine the value of the function. The length of the argument can be used to determine the value of the function. DBCS A data item of the class DBCS or a DBCS literal. The content of the argument will be used to determine the value of the function. The length
462
Language Reference
of the argument can be used to determine the value of the function. (A DBCS data item or literal can be used as an argument only for the NATIONAL-OF function.) National A data item of the class national or a national literal. The content of the argument will be used to determine the value of the function. The length of the argument can be used to determine the value of the function. Integer An arithmetic expression that will always result in an integer value. The value of this expression, including its sign, is used to determine the value of the function. Numeric An arithmetic expression, whose value, including its sign, is used to determine the value of the function. Some functions place constraints on their arguments, such as the range of values acceptable. If the values assigned as arguments for a function do not comply with specified constraints, the returned value is undefined. If a nested function is used as an argument, the evaluation of its arguments will not be affected by the arguments in the outer function. Only those arguments at the same function level interact with each other. This interaction occurs in two areas: v The computation of an arithmetic expression that appears as a function argument will be affected by other arguments for that function. v The evaluation of the function takes into consideration the attributes of all of its arguments. When a function is evaluated, its arguments are evaluated individually in the order specified in the list of arguments, from left to right. The argument being evaluated can be a function-identifier, or it can be an expression containing function-identifiers. If an arithmetic expression is specified as an argument and if the first operator in the expression is a unary plus or a unary minus, the expression must be immediately preceded by a left parenthesis. Floating-point literals are allowed wherever a numeric argument is allowed, and in arithmetic expressions used in functions that allow a numeric argument. They are not allowed where an integer argument is required. External floating-point items are allowed wherever a numeric argument is allowed, and in arithmetic expressions used in functions that allow a numeric argument. External floating-point items are not allowed where an integer argument is required, or where an argument of alphanumeric class is allowed in a function-identifier, such as in the LOWER-CASE, REVERSE, UPPER-CASE, NUMVAL, and NUMVAL-C functions.
463
ALL subscripting
When a function allows an argument to be repeated a variable number of times, you can refer to a table by specifying the data-name and any qualifiers that identify the table. This can be followed immediately by subscripting where one or more of the subscripts is the word ALL. Tip: The evaluation of an ALL subscript must result in at least one argument or the value returned by the function will be undefined; however, the situation can be diagnosed at run time by specifying the SSRANGE compiler option and the CHECK run-time option. Specifying ALL as a subscript is equivalent to specifying all table elements possible using every valid subscript in that subscript position. For a table argument specified as Table-name(ALL), the order of the implicit specification of each table element as an argument is from left to right, where the first (or leftmost) argument is Table-name(1) and ALL has been replaced by 1. The next argument is Table-name(2), where the subscript has been incremented by 1. This process continues, with the subscript being incremented by 1 to produce an implicit argument, until the ALL subscript has been incremented through its range of values. For example,
FUNCTION MAX(Table(ALL))
is equivalent to
FUNCTION MAX(Table(1) Table(2) Table(3) ... Table(n))
where n is the number of elements in Table. If there are multiple ALL subscripts, Table-name(ALL, ALL, ALL), the first implicit argument is Table-name(1, 1, 1), where each ALL has been replaced by 1. The next argument is Table-name(1, 1, 2), where the rightmost subscript has been incremented by 1. The subscript represented by the rightmost ALL is incremented through its range of values to produce an implicit argument for each value. Once a subscript specified as ALL has been incremented through its range of values, the next subscript to the left that is specified as ALL is incremented by 1. Each subscript specified as ALL to the right of the newly incremented subscript is set to 1 to produce an implicit argument. Once again, the subscript represented by the rightmost ALL is incremented through its range of values to produce an implicit argument for each value. This process is repeated until each subscript specified as ALL has been incremented through its range of values. For example,
FUNCTION MAX(Table(ALL, ALL))
is equivalent to
FUNCTION MAX(Table(1, Table(2, Table(3, ... Table(m, 1) Table(1, 2) Table(1, 3) ... Table(1, n) 1) Table(2, 2) Table(2, 3) ... Table(2, n) 1) Table(3, 2) Table(3, 3) ... Table(3, n) 1) Table(m, 2) Table(m, 3) ... Table(m, n))
464
Language Reference
where n is the number of elements in the column dimension of Table, and m is the number of elements in the row dimension of Table. ALL subscripts can be combined with literal, data-name, or index-name subscripts to reference multidimensional tables. For example,
FUNCTION MAX(Table(ALL, 2))
is equivalent to
FUNCTION MAX(Table(1, Table(2, Table(3, ... Table(m, 2) 2) 2) 2))
where m is the number of elements in the row dimension of Table. If an ALL subscript is specified for an argument and the argument is reference-modified, then the reference-modifier is applied to each of the implicitly specified elements of the table. If an ALL subscript is specified for an operand that is reference-modified, the reference-modifier is applied to each of the implicitly specified elements of the table. If the ALL subscript is associated with an OCCURS DEPENDING ON clause, the range of values is determined by the object of the OCCURS DEPENDING ON clause. For example, given a payroll record definition such as:
01 PAYROLL. 02 PAYROLL-WEEK PIC 99. 02 PAYROLL-HOURS PIC 999 OCCURS 1 TO 52 DEPENDING ON PAYROLL-WEEK.
The following COMPUTE statements could be used to identify total year-to-date hours, the maximum hours worked in any week, and the specific week corresponding to the maximum hours:
COMPUTE YTD-HOURS = FUNCTION SUM (PAYROLL-HOURS(ALL)) COMPUTE MAX-HOURS = FUNCTION MAX (PAYROLL-HOURS(ALL)) COMPUTE MAX-WEEK = FUNCTION ORD-MAX (PAYROLL-HOURS(ALL))
In these function invocations the subscript ALL is used to reference all elements of the PAYROLL-HOURS array (depending on the execution time value of the PAYROLL-WEEK field).
Function definitions
Table of functions (Table 52 on page 466) provides an overview of the argument type, function type, and value returned for each of the intrinsic functions. Argument types and function types are abbreviated as follows:
Abbreviation A D I Meaning Alphabetic DBCS Integer
465
Abbreviation N X U O
Meaning Numeric Alphanumeric National Other, as specified in the function definition (pointer, function-pointer, procedure-pointer, or object reference)
The behavior of functions markedDP depends on whether the DATEPROC or NODATEPROC compiler option is in effect. If the DATEPROC compiler option is in effect, the following intrinsic functions return date fields:
Function DATE-OF-INTEGER DATE-TO-YYYYMMDD DAY-OF-INTEGER DAY-TO-YYYYDDD YEAR-TO-YYYY DATEVAL YEARWINDOW Returned value has implicit DATE FORMAT YYYYXXXX YYYYXXXX YYYYXXX YYYYXXX YYYY Depends on the format specified by DATEVAL YYYY
If the NODATEPROC compiler option is in effect: v The following intrinsic functions return the same values as when DATEPROC is in effect, but their returned values are nondates: DAY-OF-INTEGER DATE-TO-YYYYMMDD DAY-TO-YYYYDDD YEAR-TO-YYYY v The DATEVAL and UNDATE intrinsic functions have no effect, and simply return their (first) arguments unchanged v The YEARWINDOW intrinsic function returns 0 unconditionally Each intrinsic function is described in detail in the topics that follow the table below.
Table 52. Table of functions Function name ACOS ANNUITY ASIN ATAN CHAR COS CURRENT-DATE Arguments N1 N1, I2 N1 N1 I1 N1 None Function type N N N N X N X Value returned Arccosine of N1 Ratio of annuity paid for I2 periods at interest of N1 to initial investment of one Arcsine of N1 Arctangent of N1 Character in position I1 of program collating sequence Cosine of N1 Current date and time and difference from Greenwich mean time
466
Language Reference
Table 52. Table of functions (continued) Function name DATE-OF-INTEGER

DP
Arguments I1 I1, I2
Function type I I
Value returned Standard date equivalent (YYYYMMDD) of integer date Standard date equivalent (YYYYMMDD) of I1 (standard date with a windowed year, YYMMDD), according to the 100-year interval whose ending year is specified by the sum of I2 and the year at execution time Date field equivalent of I1 Date field equivalent of X1 Julian date equivalent (YYYYDDD) of integer date Julian date equivalent (YYYYDDD) of I1 (Julian date with a windowed year, YYDDD), according to the 100-year interval whose ending year is specified by the sum of I2 and the year at execution time Each character in U1 converted to a corresponding character representation using a code page identified by I2, if specified, or a default code page selected at compile time if I2 is unspecified Factorial of I1 The greatest integer not greater than N1 Integer date equivalent of standard date (YYYYMMDD) Integer date equivalent of Julian date (YYYYDDD) Integer part of N1 Length of argument in national character positions or in alphanumeric character positions or bytes, depending on the argument type Natural logarithm of N1 Logarithm to base 10 of N1 All letters in the argument set to lowercase All letters in the argument set to lowercase Value of maximum argument; note that the type of function depends on the arguments Value of maximum argument; note that the type of function depends on the arguments Value of maximum argument; note that the type of function depends on the arguments Value of maximum argument; note that the type of function depends on the arguments Value of maximum argument; note that the type of function depends on the arguments Arithmetic mean of arguments
DATE-TO-YYYYMMDDDP
DATEVALDP
DP
I1 X1
I X I I
DAY-OF-INTEGER
I1 I1, I2
DAY-TO-YYYYDDDDP
DISPLAY-OF
U1 or U1, I2
FACTORIAL INTEGER INTEGER-OF-DATE INTEGER-OF-DAY INTEGER-PART LENGTH
I1 N1 I1 I1 N1 A1, N1, O1, X1, or U1 N1 N1 A1 or X1 U1
I I I I I I
LOG LOG10 LOWER-CASE
N N X U X I N X U N
MAX
A1... I1... N1... X1... U1...
MEAN
N1...
467
Table 52. Table of functions (continued) Function name MEDIAN MIDRANGE MIN Arguments N1... N1... A1... I1... N1... X1... U1... MOD NATIONAL-OF I1, I2 A1, X1, or D1 Function type N N X I N X U I U Value returned Median of arguments Mean of minimum and maximum arguments Value of minimum argument; note that the type of function depends on the arguments Value of minimum argument; note that the type of function depends on the arguments Value of minimum argument; note that the type of function depends on the arguments Value of minimum argument; note that the type of function depends on the arguments Value of minimum argument; note that the type of function depends on the arguments I1 modulo I2 The characters in the argument converted to national characters, using the code page identified by I2, if specified, or a default code page selected at compile time if I2 is unspecified The characters in the argument converted to national characters, using the code page identified by I2, if specified, or a default code page selected at compile time if I2 is unspecified Numeric value of simple numeric string Numeric value of numeric string with optional commas and currency sign Ordinal position of the argument in collating sequence Ordinal position of maximum argument Ordinal position of minimum argument Present value of a series of future period-end amounts, N2, at a discount rate of N1 Random number Value of maximum argument minus value of minimum argument; note that the type of function depends on the arguments. Value of maximum argument minus value of minimum argument; note that the type of function depends on the arguments. Remainder of N1/N2 Reverse order of the characters of the argument Reverse order of the characters of the argument Sine of N1 Square root of N1
A1, X1, or D1; I2
NUMVAL NUMVAL-C ORD ORD-MAX ORD-MIN PRESENT-VALUE RANDOM RANGE
X1 X1 or X1, X2 A1 or X1 A1..., N1..., X1..., or U1... A1..., N1..., X1..., or U1... N1, N2... I1, none I1...
N N I I I N N I
N1...
REM REVERSE
N1, N2 A1 or X1 U1
N X U N N
SIN SQRT
N1 N1
468
Language Reference
Table 52. Table of functions (continued) Function name STANDARD-DEVIATION SUM Arguments N1... I1... N1... TAN UNDATE
DP
Function type N I N N I X X U N X I
Value returned Standard deviation of arguments Sum of arguments; note that the type of function depends on the arguments. Sum of arguments; note that the type of function depends on the arguments. Tangent of N1 Nondate equivalent of date field I1 or X1 Nondate equivalent of date field I1 or X1 All letters in the argument set to uppercase All letters in the argument set to uppercase Variance of arguments Date and time when program was compiled Expanded year equivalent (YYYY) of I1 (windowed year, YY), according to the 100-year interval whose ending year is specified by the sum of I2 and the year at execution time If the DATEPROC compiler option is in effect, returns the starting year (in the format YYYY) of the century window specified by the YEARWINDOW compiler option; if NODATEPROC is in effect, returns 0
N1 I1 X1
UPPER-CASE
A1 or X1 U1
VARIANCE WHEN-COMPILED YEAR-TO-YYYY

DP
N1... None I1, I2
YEARWINDOWDP
None
ACOS
The ACOS function returns a numeric value in radians that approximates the arccosine of the argument specified. The function type is numeric.
Format
FUNCTION ACOS ( argument-1 )
argument-1 Must be class numeric. The value of argument-1 must be greater than or equal to -1 and less than or equal to +1. The returned value is the approximation of the arccosine of the argument and is greater than or equal to zero and less than or equal to Pi.
469
ANNUITY
The ANNUITY function returns a numeric value that approximates the ratio of an annuity paid at the end of each period, for a given number of periods, at a given interest rate, to an initial value of one. The number of periods is specified by argument-2; the rate of interest is specified by argument-1. For example, if argument-1 is zero and argument-2 is four, the value returned is the approximation of the ratio 1 / 4. The function type is numeric.
Format
FUNCTION ANNUITY ( argument-1 argument-2 )
argument-1 Must be class numeric. The value of argument-1 must be greater than or equal to zero. argument-2 Must be a positive integer. When the value of argument-1 is zero, the value returned by the function is the approximation of: 1 / argument-2 When the value of argument-1 is not zero, the value of the function is the approximation of: argument-1 / (1 - (1 + argument-1) ** (- argument-2))
ASIN
The ASIN function returns a numeric value in radians that approximates the arcsine of the argument specified. The function type is numeric.
Format
FUNCTION ASIN ( argument-1 )
argument-1 Must be class numeric. The value of argument-1 must be greater than or equal to -1 and less than or equal to +1. The returned value is the approximation of the arcsine of argument-1 and is greater than or equal to -Pi/2 and less than or equal to +Pi/2.
470
Language Reference
ATAN
The ATAN function returns a numeric value in radians that approximates the arctangent of the argument specified. The function type is numeric.
Format
FUNCTION ATAN ( argument-1 )
argument-1 Must be class numeric. The returned value is the approximation of the arctangent of argument-1 and is greater than -Pi/2 and less than +Pi/2.
CHAR
The CHAR function returns a one-character alphanumeric value that is a character in the program collating sequence having the ordinal position equal to the value of the argument specified. The function type is alphanumeric.
Format
FUNCTION CHAR ( argument-1 )
| |
argument-1 Must be an integer. The value must be greater than zero and less than or equal to the number of positions in the collating sequence associated with alphanumeric data items (a maximum of 256). If more than one character has the same position in the program collating sequence, the character returned as the function value is that of the first literal specified for that character position in the ALPHABET clause. If the current program collating sequence was not specified by an ALPHABET clause, the single-byte EBCDIC collating sequence is used. (See Conditional expressions on page 246.)
COS
The COS function returns a numeric value that approximates the cosine of the angle or arc specified by the argument in radians. The function type is numeric.
471
Format
FUNCTION COS ( argument-1 )
argument-1 Must be class numeric. The returned value is the approximation of the cosine of the argument and is greater than or equal to -1 and less than or equal to +1.
CURRENT-DATE
The CURRENT-DATE function returns a 21-character alphanumeric value that represents the calendar date, time of day, and time differential from Greenwich mean time provided by the system on which the function is evaluated. The function type is alphanumeric.
Format
FUNCTION CURRENT-DATE
Reading from left to right, the 21 character positions of the returned value are as follows:
Character positions 1-4 5-6 Contents Four numeric digits of the year in the Gregorian calendar Two numeric digits of the month of the year, in the range 01 through 12 Two numeric digits of the day of the month, in the range 01 through 31 Two numeric digits of the hours past midnight, in the range 00 through 23 Two numeric digits of the minutes past the hour, in the range 00 through 59 Two numeric digits of the seconds past the minute, in the range 00 through 59 Two numeric digits of the hundredths of a second past the second, in the range 00 through 99. The value 00 is returned if the system on which the function is evaluated does not have the facility to provide the fractional part of a second. Either the character - or the character +. The character - is returned if the local time indicated in the previous character positions is behind Greenwich mean time. The character + is returned if the local time indicated is the same as or ahead of Greenwich mean time. The character 0 is returned if the system on which this function is evaluated does not have the facility to provide the local time differential factor.
7-8 9-10 11-12 13-14 15-16
17
472
Language Reference
Character positions 18-19
Contents If character position 17 is -, two numeric digits are returned in the range 00 through 12 indicating the number of hours that the reported time is behind Greenwich mean time. If character position 17 is +, two numeric digits are returned in the range 00 through 13 indicating the number of hours that the reported time is ahead of Greenwich mean time. If character position 17 is 0, the value 00 is returned. Two numeric digits are returned in the range 00 through 59 indicating the number of additional minutes that the reported time is ahead of or behind Greenwich mean time, depending on whether character position 17 is + or -, respectively. If character position 17 is 0, the value 00 is returned.
20-21
For more information, see the Enterprise COBOL Programming Guide.
DATE-OF-INTEGER
The DATE-OF-INTEGER function converts a date in the Gregorian calendar from integer date form to standard date form (YYYYMMDD). The function type is integer. The function result is an eight-digit integer. If the DATEPROC compiler option is in effect, the returned value is an expanded date field with implicit DATE FORMAT YYYYXXXX.
Format
FUNCTION DATE-OF-INTEGER ( argument-1 )
argument-1 A positive integer that represents a number of days succeeding December 31, 1600, in the Gregorian calendar. The valid range is 1 to 3,067,671, which corresponds to dates ranging from January 1, 1601 thru December 31, 9999. The INTDATE compiler option affects the starting date for the integer date functions. For details, see the Enterprise COBOL Programming Guide. The returned value represents the International Standards Organization (ISO) standard date equivalent to the integer specified as argument-1. The returned value is an integer of the form YYYYMMDD where YYYY represents a year in the Gregorian calendar; MM represents the month of that year; and DD represents the day of that month.
473
DATE-TO-YYYYMMDD
The DATE-TO-YYYYMMDD function converts argument-1 from a date with a two-digit year (YYnnnn) to a date with a four-digit year (YYYYnnnn). argument-2, when added to the year at the time of execution, defines the ending year of a 100-year interval, or sliding century window, into which the year of argument-1 falls. The function type is integer. If the DATEPROC compiler option is in effect, the returned value is an expanded date field with implicit DATE FORMAT YYYYXXXX.
Format
FUNCTION DATE-TO-YYYYMMDD ( argument-1 argument-2 )
argument-1 Must be zero or a positive integer less than 991232. Note: The COBOL run time does not verify that the value is a valid date. argument-2 Must be an integer. If argument-2 is omitted, the function is evaluated assuming the value 50 was specified. The sum of the year at the time of execution and the value of argument-2 must be less than 10,000 and greater than 1,699. The following are examples of returned values from the DATE-TO-YYYYMMDD function:
Current year 2002 2002 2002 1994 argument-1 value 851003 851003 851003 981002 argument-2 value 120 -20 10 -10 Returned value 20851003 18851003 19851003 18981002
DATEVAL
The DATEVAL function converts a nondate to a date field, for unambiguous use with date fields. If the DATEPROC compiler option is in effect, the returned value is a date field containing the value of argument-1 unchanged. For information about using the resulting date field: v In arithmetic, see Arithmetic with date fields on page 243 v In conditional expressions, see Date fields on page 251 If the NODATEPROC compiler option is in effect, the DATEVAL function has no effect, and returns the value of argument-1 unchanged.
474
Language Reference
The function type depends on the type of argument-1:

argument-1 type Alphanumeric Integer Function type Alphanumeric Integer
Format
FUNCTION DATEVAL ( argument-1 argument-2 )
argument-1 Must be one of the following: v A class alphanumeric item with the same number of characters as the date format specified by argument-2. v An integer. This can be used to specify values outside the range specified by argument-2, including negative values. The value of argument-1 represents a date of the form specified by argument-2. argument-2 Must be an alphanumeric literal specifying a date pattern, as defined in DATE FORMAT clause on page 174. The date pattern consists of YY or YYYY (representing a windowed year or expanded year, respectively), optionally preceded or followed by one or more Xs (representing other parts of a date, such as month and day), as shown below. Note that the values are case insensitive; the letters X and Y in argument-2 can be any mix of uppercase and lowercase.
Date-pattern string YY YYYY X XX XXX XXXX Specifies that argument-1 contains A windowed (two-digit) year An expanded (four-digit) year A single character; for example, a digit representing a semester or quarter (1-4) Two characters; for example, digits representing a month (01-12) Three characters; for example, digits representing a day of the year (001-366) Four characters; for example, two digits representing a month (01-12) and two digits representing a day of the month (01-31)
DAY-OF-INTEGER
The DAY-OF-INTEGER function converts a date in the Gregorian calendar from integer date form to Julian date form (YYYYDDD). The function type is integer. The function result is a seven-digit integer. If the DATEPROC compiler option is in effect, the returned value is an expanded date field with implicit DATE FORMAT YYYYXXX.
475
Format
FUNCTION DAY-OF-INTEGER ( argument-1 )
argument-1 A positive integer that represents a number of days succeeding December 31, 1600, in the Gregorian calendar. The valid range is 1 to 3,067,671, which corresponds to dates ranging from January 1, 1601 thru December 31, 9999. The INTDATE compiler option affects the starting date for the integer date functions. For details, see the Enterprise COBOL Programming Guide. The returned value represents the Julian equivalent of the integer specified as argument-1. The returned value is an integer of the form YYYYDDD where YYYY represents a year in the Gregorian calendar and DDD represents the day of that year.
DAY-TO-YYYYDDD
The DAY-TO-YYYYDDD function converts argument-1 from a date with a two-digit year (YYnnn) to a date with a four-digit year (YYYYnnn). argument-2, when added to the year at the time of execution, defines the ending year of a 100-year interval, or sliding century window, into which the year of argument-1 falls. The function type is integer. If the DATEPROC compiler option is in effect, the returned value is an expanded date field with implicit DATE FORMAT YYYYXXX.
Format
FUNCTION DAY-TO-YYYYDDD ( argument-1 argument-2 )
argument-1 Must be zero or a positive integer less than 99367. The COBOL run time does not verify that the value is a valid date. argument-2 Must be an integer. If argument-2 is omitted, the function is evaluated assuming the value 50 was specified. The sum of the year at the time of execution and the value of argument-2 must be less than 10,000 and greater than 1,699. Some examples of returned values from the DAY-TO-YYYYDDD function follow:
Current year 2002 2002 argument-1 value 10004 10004 argument-2 value -20 -120 Returned value 1910004 1810004
476
Language Reference
Current year 2002 2013
argument-1 value 10004 95005
argument-2 value 20 -10
Returned value 2010004 1995005
DISPLAY-OF
The DISPLAY-OF function returns an alphanumeric character string consisting of the content of argument-1 converted to a specific code page representation. The type of the function is alphanumeric.
Format
FUNCTION DISPLAY-OF ( argument-1 argument-2 )
argument-1 Must be of class national. argument-1 identifies the source string for the conversion. argument-2 Must be an integer. argument-2 identifies the output code page for the conversion. | | argument-2 must be a valid CCSID number and must identify an EBCDIC, ASCII, UTF-8, or EUC code page. An EBCDIC or ASCII code page can contain both single-byte and double-byte characters. If argument-2 is omitted, the output code page is the one in effect for the CODEPAGE compiler option when the source code was compiled. The returned value is an alphanumeric character string consisting of the characters of argument-1 converted to the output code page representation. When a source character cannot be converted to a character in the output code page, the source character is replaced with a substitution character. The following table shows substitution characters for some widely-used code pages: | | | | | | | | | | | | |
Output code page SBCS ASCII PC Windows SBCS EBCDIC SBCS ASCII DBCS EBCDIC DBCS (except for Thai) EBCDIC DBCS (Thai) PC DBCS (Japanese or Chinese) PC DBCS (Korean) EUC (Korean) EUC (Japanese) UTF-8 Substitution character X7F X3F XFCFC XFEFE X41B8 XFCFC XBFFC XAFFE X747E From SBCS: X1A From MBCS: XEFBFBD
477
| | |
Output code page UTF-16
Substitution character From SBCS: X001A From MBCS: XFFFD
No exception condition is raised. The length of the returned value depends on the content of argument-1 and the characteristics of the output code page. Usage notes v The CCSID for UTF-8 is 1208. v If the output code page is a mixed SBCS and DBCS code page, the returned value can be a mixed SBCS and DBCS string. v The DISPLAY-OF function, with argument-2 specified, can be used to generate character data represented in a code page that differs from that specified in the CODEPAGE compiler option. Subsequent COBOL operations on that data can involve implicit conversions that assume the data is represented in the EBCDIC code page specified in the CODEPAGE compiler option. See the Enterprise COBOL Programming Guide for examples and programming techniques for processing data represented using more than one code page within a single program. Exceptions: If the conversion fails, a severe run-time error occurs. Verify that the z/OS Unicode conversion services are installed and are configured to include the table for converting from CCSID 1200 to the output code page. See the Customization Guide for installation requirements to support the conversion.
FACTORIAL
The FACTORIAL function returns an integer that is the factorial of the argument specified. The function type is integer.
Format
FUNCTION FACTORIAL ( argument-1 )
argument-1 If the ARITH(COMPAT) compiler option is in effect, argument-1 must be an integer greater than or equal to zero and less than or equal to 28. If the ARITH(EXTEND) compiler option is in effect, argument-1 must be an integer greater than or equal to zero and less than or equal to 29. If the value of argument-1 is zero, the value 1 is returned; otherwise, the factorial of argument-1 is returned.
478
Language Reference
INTEGER
The INTEGER function returns the greatest integer value that is less than or equal to the argument specified. The function type is integer.
Format
FUNCTION INTEGER ( argument-1 )
argument-1 Must be class numeric. The returned value is the greatest integer less than or equal to the value of argument-1. For example, FUNCTION INTEGER (2.5) returns a value of 2 and FUNCTION INTEGER (-2.5) returns a value of -3.
INTEGER-OF-DATE
The INTEGER-OF-DATE function converts a date in the Gregorian calendar from standard date form (YYYYMMDD) to integer date form. The function type is integer. The function result is a seven-digit integer with a range from 1 to 3,067,671.
Format
FUNCTION INTEGER-OF-DATE ( argument-1 )
argument-1 Must be an integer of the form YYYYMMDD, whose value is obtained from the calculation (YYYY * 10,000) + (MM * 100) + DD, where: v YYYY represents the year in the Gregorian calendar. It must be an integer greater than 1600, but not greater than 9999. v MM represents a month and must be a positive integer less than 13. v DD represents a day and must be a positive integer less than 32, provided that it is valid for the specified month and year combination. The returned value is an integer that is the number of days that the date represented by argument-1 succeeds December 31, 1600 in the Gregorian calendar. The INTDATE compiler option affects the starting date for the integer date functions. For details, see the Enterprise COBOL Programming Guide.
479
INTEGER-OF-DAY
The INTEGER-OF-DAY function converts a date in the Gregorian calendar from Julian date form (YYYYDDD) to integer date form. The function type is integer. The function result is a seven-digit integer.
Format
FUNCTION INTEGER-OF-DAY ( argument-1 )
argument-1 Must be an integer of the form YYYYDDD whose value is obtained from the calculation (YYYY * 1000) + DDD, where: v YYYY represents the year in the Gregorian calendar. It must be an integer greater than 1600, but not greater than 9999. v DDD represents the day of the year. It must be a positive integer less than 367, provided that it is valid for the year specified. The returned value is an integer that is the number of days that the date represented by argument-1 succeeds December 31, 1600 in the Gregorian calendar. The INTDATE compiler option affects the starting date for the integer date functions. For details, see the Enterprise COBOL Programming Guide.
INTEGER-PART
The INTEGER-PART function returns an integer that is the integer portion of the argument specified. The function type is integer.
Format
FUNCTION INTEGER-PART ( argument-1 )
argument-1 Must be class numeric. If the value of argument-1 is zero, the returned value is zero. If the value of argument-1 is positive, the returned value is the greatest integer less than or equal to the value of argument-1. If the value of argument-1 is negative, the returned value is the least integer greater than or equal to the value of argument-1.
480
Language Reference
LENGTH
The LENGTH function returns an integer equal to the length of the argument in national character positions for arguments of class national and in alphanumeric character positions or bytes for all other arguments. An alphanumeric character position and a byte are equivalent. The type of the function is integer.
Format
FUNCTION LENGTH ( argument-1 )
argument-1 Can be: v An alphanumeric or national literal or a data item of any class or category except DBCS v A data item described with usage POINTER, PROCEDURE-POINTER, FUNCTION-POINTER, or OBJECT REFERENCE v The ADDRESS OF special register v The LENGTH OF special register v The XML-NTEXT special register v The XML-TEXT special register The returned value is a nine-digit integer determined as follows: v If argument-1 is an alphanumeric literal or an elementary alphanumeric data item, the value returned is equal to the number of alphanumeric character positions in the argument. If argument-1 is a null-terminated alphanumeric literal, the returned value is equal to the number of alphanumeric character positions in the literal excluding the null character at the end of the literal. The length of an alphanumeric data item or literal containing a mix of single-byte and double-byte characters is counted as though each byte were a single-byte character. v If argument-1 is a group data item, the value returned is equal to the length of argument-1 in alphanumeric character positions regardless of the content of the group. If any data item subordinate to argument-1 is described with the DEPENDING phrase of the OCCURS clause, the length of argument-1 is determined using the contents of the data item specified in the DEPENDING phrase. This evaluation is accomplished according to the rules in the OCCURS clause for a sending data item. For more information, see the discussions of the OCCURS clause and the USAGE clause. The returned value includes implicit FILLER positions, if any. v If argument-1 is a national literal or a national data item, the value returned is equal to the length of argument-1 in national character positions. For example, if argument-1 is defined as PIC N(3), the returned value is 3, although the storage size of the argument is 6 bytes. v Otherwise, the returned value is the number of bytes of storage occupied by argument-1.
481
LOG
The LOG function returns a numeric value that approximates the logarithm to the base e (natural log) of the argument specified. The function type is numeric.
Format
FUNCTION LOG ( argument-1 )
argument-1 Must be class numeric. The value of argument-1 must be greater than zero. The returned value is the approximation of the logarithm to the base e of argument-1.
LOG10
The LOG10 function returns a numeric value that approximates the logarithm to the base 10 of the argument specified. The function type is numeric.
Format
FUNCTION LOG10 ( argument-1 )
argument-1 Must be class numeric. The value of argument-1 must be greater than zero. The returned value is the approximation of the logarithm to the base 10 of argument-1.
LOWER-CASE
The LOWER-CASE function returns a character string that contains the characters in the argument with each lowercase letter replaced by the corresponding uppercase letter. The function type depends on the type of the argument, as follows:
Argument type Alphabetic Alphanumeric National Function type Alphanumeric Alphanumeric National
482
Language Reference
Format
FUNCTION LOWER-CASE ( argument-1 )
argument-1 Must be class alphabetic, alphanumeric, or national and must be at least one character position in length. The same character string as argument-1 is returned, except that each uppercase letter is replaced by the corresponding lowercase letter. If argument-1 is of class alphabetic or alphanumeric, the uppercase letters A through Z are replaced by the corresponding lowercase letters a through z, where the range of A through Z and the range of a through z are as shown in EBCDIC collating sequence (Table 56 on page 549), regardless of the code page in effect. If argument-1 is of class national, each uppercase letter is replaced by its corresponding lowercase letter based on the specification given in the Unicode database UnicodeData.txt, available from the Unicode Consortium at www.unicode.org/. The character string returned has the same length as argument-1.
MAX
The MAX function returns the content of the argument that contains the maximum value. The function type depends on the argument type, as follows:
Argument type Alphabetic Alphanumeric National All arguments integer Numeric (some arguments can be integer) Function type Alphanumeric Alphanumeric National Integer Numeric
Format
FUNCTION MAX (
argument-1
argument-1 Must be class alphabetic, alphanumeric, national, or numeric. All arguments must be of the same class, except that a combination of alphabetic and alphanumeric arguments is allowed.
483
The returned value is the content of argument-1 having the greatest value. The comparisons used to determine the greatest value are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246. If more than one argument-1 has the same greatest value, the leftmost argument-1 having that value is returned. If the type of the function is alphanumeric or national, the size of the returned value is the size of the selected argument-1.
MEAN
The MEAN function returns a numeric value that approximates the arithmetic average of its arguments. The function type is numeric.
Format
FUNCTION MEAN (
argument-1
argument-1 Must be class numeric. The returned value is the arithmetic mean of the argument-1 series. The returned value is defined as the sum of the argument-1 series divided by the number of occurrences referenced by argument-1.
MEDIAN
The MEDIAN function returns the content of the argument whose value is the middle value in the list formed by arranging the arguments in sorted order. The function type is numeric.
Format
FUNCTION MEDIAN (
argument-1
argument-1 Must be class numeric. The returned value is the content of argument-1 having the middle value in the list formed by arranging all argument-1 values in sorted order.
484
Language Reference
If the number of occurrences referenced by argument-1 is odd, the returned value is such that at least half of the occurrences referenced by argument-1 are greater than or equal to the returned value and at least half are less than or equal. If the number of occurrences referenced by argument-1 is even, the returned value is the arithmetic mean of the values referenced by the two middle occurrences. The comparisons used to arrange the argument values in sorted order are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246.
MIDRANGE
The MIDRANGE function returns a numeric value that approximates the arithmetic average of the values of the minimum argument and the maximum argument. The function type is numeric.
Format
FUNCTION MIDRANGE (
argument-1
argument-1 Must be class numeric. The returned value is the arithmetic mean of the value of the greatest argument-1 and the value of the least argument-1. The comparisons used to determine the greatest and least values are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246.
MIN
The MIN function returns the content of the argument that contains the minimum value. The function type depends on the argument type, as follows:
Argument type Alphabetic Alphanumeric National All arguments integer Numeric (some arguments can be integer) Function type Alphanumeric Alphanumeric National Integer Numeric
485
Format
FUNCTION MIN (
argument-1
argument-1 Must be class alphabetic, alphanumeric, national, or numeric. All arguments must be of the same class, except that a combination of alphabetic and alphanumeric arguments is allowed. The returned value is the content of argument-1 having the least value. The comparisons used to determine the least value are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246. If more than one argument-1 has the same least value, the leftmost argument-1 having that value is returned. If the type of the function is alphanumeric or national, the size of the returned value is the size of the selected argument-1.
MOD
The MOD function returns an integer value that is argument-1 modulo argument-2. The function type is integer. The function result is an integer with as many digits as the shorter of argument-1 and argument-2.
Format
FUNCTION MOD ( argument-1 argument-2 )
argument-1 Must be an integer. argument-2 Must be an integer. Must not be zero. The returned value is argument-1 modulo argument-2. The returned value is defined as: argument-1 - (argument-2 * FUNCTION INTEGER (argument-1 / argument-2)) The following are expected results for some values of argument-1 and argument-2.
486
Language Reference
argument-1 11 -11 11 -11
argument-2 5 5 -5 -5
Returned value 1 4 -4 -1
NATIONAL-OF
The NATIONAL-OF function returns a national character string consisting of the UTF-16 representation of the characters in argument-1. The type of the function is national.
Format
FUNCTION NATIONAL-OF ( argument-1 argument-2 )
argument-1 Must be of class alphabetic, alphanumeric, or DBCS. argument-1 specifies the source string for the conversion. argument-2 Must be an integer. argument-2 identifies the source code page for the conversion. | | argument-2 must be a valid CCSID number and must identify an EBCDIC, ASCII, UTF-8, or EUC code page. An EBCDIC or ASCII code page can contain both single-byte and double-byte characters. If argument-2 is omitted, the source code page is the one in effect for the CODEPAGE compiler option when the source code was compiled. The returned value is a national character string consisting of the characters of argument-1 converted to national character representation. When a source character cannot be converted to a national character, the source character is converted to a substitution character. The substitution character is: v X001A if converting a single-byte character v XFFFD if converting a multi-byte character No exception condition is raised. The length of the returned value depends on the content of argument-1 and the characteristics of the source code page. Usage note: The CCSID for UTF-8 is 1208. Exceptions: If the conversion fails, a severe run-time error occurs. Verify that the z/OS Unicode conversion services are installed and are configured to include the table for converting from the source code page to CCSID 1200. See the Customization Guide for installation requirements to support the conversion.
487
NUMVAL
The NUMVAL function returns the numeric value represented by the alphanumeric character string specified in an argument. The function strips away any leading or trailing blanks in the string, producing a numeric value that can be used in an arithmetic expression. The function type is numeric.
Format
FUNCTION NUMVAL ( argument-1 )
argument-1 must be an alphanumeric literal or an alphanumeric data item whose content has either of the following formats:
Format 1: argument-1
digit space + space . digit . digit
space
digit space . digit . digit space + CR DB
space
space digit
A string of one or more spaces. A string of one or more digits. If the ARITH(COMPAT) compiler option is in effect, the total number of digits must not exceed 18. If the ARITH(EXTEND) compiler option is in effect, the total number of digits must not exceed 31.
If the DECIMAL-POINT IS COMMA clause is specified in the SPECIAL-NAMES paragraph, a comma must be used in argument-1 rather than a decimal point. The returned value is an approximation of the numeric value represented by argument-1.
488
Language Reference
NUMVAL-C
The NUMVAL-C function returns the numeric value represented by the alphanumeric character string specified as argument-1. Any optional currency sign specified by argument-2 and any optional commas preceding the decimal point are stripped away, producing a numeric value that can be used in an arithmetic expression. The function type is numeric. The NUMVAL-C function cannot be used if any of the following are true: v The program contains more than one CURRENCY SIGN clause in the SPECIAL-NAMES paragraph of the environment division. v literal-6 in the CURRENCY SIGN clause is a lowercase letter. v The PICTURE SYMBOL paragraph is specified in the CURRENCY SIGN clause.
Format
FUNCTION NUMVAL-C ( argument-1 argument-2 )
argument-1 Must be an alphanumeric literal or an alphanumeric data item whose content has either of the following formats:
space
space
cs
space
digit . digit , digit . digit space
489
space digit
cs
space
. digit , . digit digit
space
+ CR DB
space
space cs digit
A string of one or more spaces. The string of one or more characters specified by argument-2. At most one copy of the characters specified by cs can occur in argument-1. A string of one or more digits. If the ARITH(COMPAT) compiler option is in effect, the total number of digits must not exceed 18. If the ARITH(EXTEND) compiler option is in effect, the total number of digits must not exceed 31.
If the DECIMAL-POINT IS COMMA clause is specified in the SPECIAL-NAMES paragraph, the functions of the comma and decimal point in argument-1 are reversed. argument-2 Specifies the currency string value. v If argument-2 is specified, it must be an alpahnumeric literal or alphanumeric data item, subject to the following rules: argument-2 must not contain any of the digits 0 through 9, any leading or trailing spaces, or any of the special characters +, -, ., or ,. argument-2 can be of any length valid for an elementary or group data item, including zero. Matching of argument-2 is case sensitive. For example, if you specify argument-2 as CHF, it will not match ChF, chf or chF. v If argument-2 is not specified, the character used for cs is the currency symbol specified for the program. The returned value is an approximation of the numeric value represented by argument-1.
ORD
The ORD function returns an integer value that is the ordinal position of its argument in the collating sequence for the program. The lowest ordinal position is 1. The function type is integer. The function result is a three-digit integer.
490
Language Reference
Format
FUNCTION ORD ( argument-1 )
argument-1 Must be one character in length and must be class alphabetic or alphanumeric. The returned value is the ordinal position of argument-1 in the collating sequence for the program; it ranges from 1 to 256 depending on the collating sequence.
ORD-MAX
The ORD-MAX function returns a value that is the ordinal number position, in the argument list, of the argument that contains the maximum value. The function type is integer.
Format
FUNCTION ORD-MAX (
argument-1
argument-1 Must be class alphabetic, alphanumeric, national, or numeric. All arguments must be of the same class, except that a combination of alphabetic and alphanumeric arguments is allowed. The returned value is the ordinal number that corresponds to the position of the argument-1 having the greatest value in the argument-1 series. The comparisons used to determine the greatest-valued argument-1 are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246. If more than one argument-1 has the same greatest value, the number returned corresponds to the position of the leftmost argument-1 having that value.
ORD-MIN
The ORD-MIN function returns a value that is the ordinal number of the argument that contains the minimum value. The function type is integer.
491
Format
FUNCTION ORD-MIN (
argument-1
argument-1 Must be class alphabetic, alphanumeric, national, or numeric. All arguments must be of the same class, except that a combination of alphabetic and alphanumeric arguments is allowed. The returned value is the ordinal number that corresponds to the position of the argument-1 having the least value in the argument-1 series. The comparisons used to determine the least-valued argument-1 are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246. If more than one argument-1 has the same least value, the number returned corresponds to the position of the leftmost argument-1 having that value.
PRESENT-VALUE
The PRESENT-VALUE function returns a value that approximates the present value of a series of future period-end amounts specified by argument-2 at a discount rate specified by argument-1. The function type is numeric.
Format
FUNCTION PRESENT-VALUE ( argument-1
argument-2
argument-1 Must be class numeric. Must be greater than -1. argument-2 Must be class numeric. The returned value is an approximation of the summation of a series of calculations with each term in the following form: argument-2 / (1 + argument-1) ** n There is one term for each occurrence of argument-2. The exponent n is incremented from 1 by 1 for each term in the series.
492
Language Reference
RANDOM
The RANDOM function returns a numeric value that is a pseudorandom number from a rectangular distribution. The function type is numeric.
Format
FUNCTION RANDOM ( argument-1 )
argument-1 If argument-1 is specified, it must be zero or a positive integer. However, only values in the range from zero up to and including 2,147,483,645 yield a distinct sequence of pseudorandom numbers. If a subsequent reference specifies argument-1, a new sequence of pseudorandom numbers is started. If the first reference to this function in the run unit does not specify argument-1, the seed value used will be zero. In each case, subsequent references without specifying argument-1 return the next number in the current sequence. The returned value is exclusively between zero and one. For a given seed value, the sequence of pseudorandom numbers is always the same. The RANDOM function can be used in threaded programs. For an initial seed, a single sequence of pseudorandom numbers is returned, regardless of the thread that is running when RANDOM is invoked.
RANGE
The RANGE function returns a value that is equal to the value of the maximum argument minus the value of the minimum argument. The function type depends on the argument types, as follows:
Argument type All arguments integer Numeric (some arguments can be integer) Function type Integer Numeric
493
Format
FUNCTION RANGE (
argument-1
argument-1 Must be class numeric. The returned value is equal to argument-1 with the greatest value minus the argument-1 with the least value. The comparisons used to determine the greatest and least values are made according to the rules for simple conditions. For more information, see Conditional expressions on page 246.
REM
The REM function returns a numeric value that is the remainder of argument-1 divided by argument-2. The function type is numeric.
Format
FUNCTION REM ( argument-1 argument-2 )
argument-1 Must be class numeric. argument-2 Must be class numeric. Must not be zero. The returned value is the remainder of argument-1 divided by argument-2. It is defined as the expression: argument-1 - (argument-2 * FUNCTION INTEGER-PART (argument-1 / argument-2))
REVERSE
The REVERSE function returns a character string of exactly the same length as the argument, whose characters are exactly the same as those specified in the argument except that they are in reverse order. For national arguments, national character positions are reversed. The function type depends on the type of the argument, as follows:
Argument type Alphabetic Alphanumeric National Function type Alphanumeric Alphanumeric National
494
Language Reference
Format
FUNCTION REVERSE ( argument-1 )
argument-1 Must be class alphabetic, alphanumeric, or national and must be at least one character in length. If argument-1 is a character string of length n, the returned value is a character string of length n such that, for 1 <= j <= n, the character in character position j of the returned value is the character from character position n-j+1 of argument-1.
SIN
The SIN function returns a numeric value that approximates the sine of the angle or arc specified by the argument in radians. The function type is numeric.
Format
FUNCTION SIN ( argument-1 )
argument-1 Must be class numeric. The returned value is the approximation of the sine of argument-1 and is greater than or equal to -1 and less than or equal to +1.
SQRT
The SQRT function returns a numeric value that approximates the square root of the argument specified. The function type is numeric.
Format
FUNCTION SQRT ( argument-1 )
argument-1 Must be class numeric. The value of argument-1 must be zero or positive. The returned value is the absolute value of the approximation of the square root of argument-1.
495
STANDARD-DEVIATION
The STANDARD-DEVIATION function returns a numeric value that approximates the standard deviation of its arguments. The function type is numeric.
Format
FUNCTION STANDARD-DEVIATION (
argument-1
argument-1 Must be class numeric. The returned value is the approximation of the standard deviation of the argument-1 series. The returned value is calculated as follows: 1. The difference between each argument-1 and the arithmetic mean of the argument-1 series is calculated and squared. 2. The values obtained are then added together. This quantity is divided by the number of values in the argument-1 series. 3. The square root of the quotient obtained is then calculated. The returned value is the absolute value of this square root. If the argument-1 series consists of only one value, or if the argument-1 series consists of all variable-occurrence data items and the total number of occurrences for all of them is one, the returned value is zero.
SUM
The SUM function returns a value that is the sum of the arguments. The function type depends on the argument types, as follows:
Argument type All arguments integer Numeric (some arguments can be integer) Function type Integer Numeric
Format
FUNCTION SUM (
argument-1
argument-1 Must be class numeric.
496
Language Reference
The returned value is the sum of the arguments. If the argument-1 series are all integers, the value returned is an integer. If the argument-1 series are not all integers, a numeric value is returned.
TAN
The TAN function returns a numeric value that approximates the tangent of the angle or arc that is specified by the argument in radians. The function type is numeric.
Format
FUNCTION TAN ( argument-1 )
argument-1 Must be class numeric. The returned value is the approximation of the tangent of argument-1.
UNDATE
The UNDATE function converts a date field to a nondate for unambiguous use with nondates. If the NODATEPROC compiler option is in effect, the UNDATE function has no effect. The function type depends on the type of argument-1:
argument-1 type Alphanumeric Integer Function type Alphanumeric Integer
Format
FUNCTION UNDATE ( argument-1 )
argument-1 A date field. The returned value is a nondate that contains the value of argument-1 unchanged.
UPPER-CASE
The UPPER-CASE function returns a character string that contains the characters in the argument with each lowercase letter replaced by the corresponding uppercase letter. The function type depends on the type of the argument, as follows:
497
Argument type Alphabetic Alphanumeric National
Function type Alphanumeric Alphanumeric National
Format
FUNCTION UPPER-CASE ( argument-1 )
argument-1 Must be class alphabetic, alphanumeric, or national and must be at least one character position in length. The same character string as argument-1 is returned, except that each lowercase letter is replaced by the corresponding uppercase letter. If argument-1 is alphabetic or alphanumeric, the lowercase letters a through z are replaced by the corresponding uppercase letters A through Z, where the range of a through z and the range of A through Z are as shown in EBCDIC collating sequence (Table 56 on page 549), regardless of the code page in effect. If argument-1 is national, each lowercase letter is replaced by its corresponding uppercase letter based on the specification given in the Unicode database UnicodeData.txt, available from the Unicode Consortium at www.unicode.org/. The returned character string has the same length as argument-1.
VARIANCE
The VARIANCE function returns a numeric value that approximates the variance of its arguments. The function type is numeric.
Format
FUNCTION VARIANCE (
argument-1
argument-1 Must be class numeric. The returned value is the approximation of the variance of the argument-1 series. The returned value is defined as the square of the standard deviation of the argument-1 series. This value is calculated as follows: 1. The difference between each argument-1 value and the arithmetic mean of the argument-1 series is calculated and squared.
498
Language Reference
2. The values obtained are then added together. This quantity is divided by the number of values in the argument series. If the argument-1 series consists of only one value, or if the argument-1 series consists of all variable-occurrence data items and the total number of occurrences for all of them is one, the returned value is zero.
WHEN-COMPILED
The WHEN-COMPILED function returns the date and time that the program was compiled as provided by the system on which the program was compiled. The function type is alphanumeric.
Format
FUNCTION WHEN-COMPILED
Reading from left to right, the 21 character positions of the returned value are as follows:
Character positions 1-4 5-6 Contents Four numeric digits of the year in the Gregorian calendar Two numeric digits of the month of the year, in the range 01 through 12 Two numeric digits of the day of the month, in the range 01 through 31 Two numeric digits of the hours past midnight, in the range 00 through 23 Two numeric digits of the minutes past the hour, in the range 00 through 59 Two numeric digits of the seconds past the minute, in the range 00 through 59 Two numeric digits of the hundredths of a second past the second, in the range 00 through 99. The value 00 is returned if the system on which the function is evaluated does not have the facility to provide the fractional part of a second. Either the character - or the character +. The character - is returned if the local time indicated in the previous character positions is behind Greenwich mean time. The character + is returned if the local time indicated is the same as or ahead of Greenwich mean time. The character 0 is returned if the system on which this function is evaluated does not have the facility to provide the local time differential factor. If character position 17 is -, two numeric digits are returned in the range 00 through 12 indicating the number of hours that the reported time is behind Greenwich mean time. If character position 17 is +, two numeric digits are returned in the range 00 through 13 indicating the number of hours that the reported time is ahead of Greenwich mean time. If character position 17 is 0, the value 00 is returned.
7-8 9-10 11-12 13-14 15-16
17
18-19
499
Character positions 20-21
Contents Two numeric digits are returned in the range 00 through 59 indicating the number of additional minutes that the reported time is ahead of or behind Greenwich mean time, depending on whether character position 17 is + or -, respectively. If character position 17 is 0, the value 00 is returned.
The returned value is the date and time of compilation of the source unit that contains this function. If a program is a contained program, the returned value is the compilation date and time associated with the containing program.
YEAR-TO-YYYY
The YEAR-TO-YYYY function converts argument-1, a two-digit year, to a four-digit year. argument-2, when added to the year at the time of execution, defines the ending year of a 100-year interval, or sliding century window, into which the year of argument-1 falls. The function type is integer. If the DATEPROC compiler option is in effect, then the returned value is an expanded date field with implicit DATE FORMAT YYYY.
Format
FUNCTION YEAR-TO-YYYY ( argument-1 argument-2 )
argument-1 Must be a non-negative integer that is less than 100. argument-2 Must be an integer. If argument-2 is omitted, the function is evaluated assuming the value 50 was specified. The sum of the year at the time of execution and the value of argument-2 must be less than 10,000 and greater than 1,699. Examples of return values from the YEAR-TO-YYYY function are shown in the following table.
Current year 1995 1995 2008 2008 argument-1 value 4 4 98 98 argument-2 value 23 -15 23 -15 Returned value 2004 1904 1998 1898
500
Language Reference
YEARWINDOW
If the DATEPROC compiler option is in effect, the YEARWINDOW function returns the starting year of the century window specified by the YEARWINDOW compiler option. The returned value is an expanded date field with implicit DATE FORMAT YYYY. If the NODATEPROC compiler option is in effect, the YEARWINDOW function returns 0. The function type is integer.
Format
FUNCTION YEARWINDOW
501
502
Language Reference
Part 8. Compiler-directing statements

Chapter 23. Compiler-directing statements . . 505 BASIS statement . . . . . . . . . . . . 505 CBL (PROCESS) statement . . . . . . . . . 506 *CONTROL (*CBL) statement . . . . . . . . 506 Source code listing . . . . . . . . . . . 507 Object code listing . . . . . . . . . . . . 508 Storage map listing . . . . . . . . . . . 508 COPY statement . . . . . . . . . . . . 508 SUPPRESS phrase . . . . . . . . . . . 511 REPLACING phrase . . . . . . . . . . 511 Replacement and comparison rules . . . . . 512 DELETE statement . . . . . . . . . . . 515 EJECT statement . . . . . . . . . . . . 516 ENTER statement . . . . . . . . . . . . 516 INSERT statement . . . . . . . . . . . . 517 READY or RESET TRACE statement . . . . . 517 REPLACE statement . . . . . . . . . . . 518 Continuation rules for pseudo-text . . . . . . 520 Comparison operation . . . . . . . . . . 520 REPLACE statement notes . . . . . . . . . 521 SERVICE LABEL statement . . . . . . . . . 522 SERVICE RELOAD statement . . . . . . . . 522 SKIP statements . . . . . . . . . . . . 522 TITLE statement . . . . . . . . . . . . 523 USE statement . . . . . . . . . . . . . 524 EXCEPTION/ERROR declarative . . . . . . . 524 Precedence rules for nested programs . . . . . 526 LABEL declarative. . . . . . . . . . . . 526 DEBUGGING declarative . . . . . . . . . 528
503
504
Language Reference
Chapter 23. Compiler-directing statements

A compiler-directing statement is a statement that causes the compiler to take a specific action during compilation. You can use compiler-directing statements for the following: v Extended source library control (BASIS, DELETE, and INSERT statements) v Source text manipulation (COPY and REPLACE statements) v Exception handling and label handling (USE statement) v Controlling compiler listings (*CONTROL, *CBL, EJECT, TITLE, SKIP1, SKIP2, and SKIP3 statements) v Specifying compiler options (CBL and PROCESS statements) v Specifying COBOL exception handling procedures (USE statements) The SERVICE LABEL statement is used with Language Environment condition handling. It is also generated by the CICS preprocessor. The following compiler directives have no effect: ENTER, READY or RESET TRACE, and SERVICE RELOAD.
BASIS statement
The BASIS statement is an extended source text library statement. It provides a complete COBOL program as the source for a compilation. A complete program can be stored as an entry in a users library and can be used as the source for a compilation. Compiler input is a BASIS statement, optionally followed by any number of INSERT and DELETE statements.
Format
BASIS sequence-number basis-name literal-1
sequence-number Can optionally appear in columns 1 through 6, followed by a space. The content of this field is ignored. BASIS Can appear anywhere in columns 1 through 72, followed by basis-name. There must be no other text in the statement. basis-name, literal-1 Is the name by which the library entry is known to the system environment. For rules of formation and processing rules, see the description under literal-1 and text-name of the COPY statement on page 508. The source file remains unchanged after execution of the BASIS statement.
505
Usage note: If INSERT or DELETE statements are used to modify the COBOL source text provided by a BASIS statement, the sequence field of the COBOL source text must contain numeric sequence numbers in ascending order.
CBL (PROCESS) statement

With the CBL (PROCESS) statement, you can specify compiler options to be used in the compilation of the program. The CBL (PROCESS) statement is placed before the identification division header of an outermost program.
Format
CBL PROCESS
options-list
options-list A series of one or more compiler options, each one separated by a comma or a space. For more information about compiler options, see the Enterprise COBOL Programming Guide. The CBL (PROCESS) statement can be preceded by a sequence number in columns 1 through 6. The first character of the sequence number must be numeric, and CBL or PROCESS can begin in column 8 or after; if a sequence number is not specified, CBL or PROCESS can begin in column 1 or after. The CBL (PROCESS) statement must end before or at column 72, and options cannot be continued across multiple CBL (PROCESS) statements. However, you can use more than one CBL (PROCESS) statement. Multiple CBL (PROCESS) statements must follow one another with no intervening statements of any other type. The CBL (PROCESS) statement must be placed before any comment lines or other compiler-directing statements.
*CONTROL (*CBL) statement

With the *CONTROL (or *CBL) statement, you can selectively display or suppress the listing of source code, object code, and storage maps throughout the source text.
Format
*CONTROL *CBL
SOURCE NOSOURCE LIST NOLIST MAP NOMAP
506
Language Reference
For a complete discussion of the output produced by these options, see the Enterprise COBOL Programming Guide. The *CONTROL and *CBL statements are synonymous. *CONTROL is accepted anywhere that *CBL is accepted. The characters *CONTROL or *CBL can start in any column beginning with column 7, followed by at least one space or comma and one or more option keywords. The option keywords must be separated by one or more spaces or commas. This statement must be the only statement on the line, and continuation is not allowed. The statement can be terminated with a period. The *CONTROL and *CBL statements must be embedded in a program source. For example, in the case of batch applications, the *CONTROL and *CBL statements must be placed between the PROCESS (CBL) statement and the end of the program (or END PROGRAM marker, if specified). The source line containing the *CONTROL (*CBL) statement will not appear in the source listing. If an option is defined at installation as a fixed option, that fixed option takes precedence over all of the following: v PARM (if available) v CBL statement v *CONTROL (*CBL) statement The requested options are handled in the following manner: 1. If an option or its negation appears more than once in a *CONTROL statement, the last occurrence of the option word is used. 2. If the CORRESPONDING option has been requested as a parameter to the compiler, then a *CONTROL statement with the negation of the option word must precede the portions of the source text for which listing output is to be inhibited. Listing output then resumes when a *CONTROL statement with the affirmative option word is encountered. 3. If the negation of the CORRESPONDING option has been requested as a parameter to the compiler, then that listing is always inhibited. 4. The *CONTROL statement is in effect only within the source program in which it is written, including any contained programs. It does not remain in effect across batch compiles of two or more COBOL source programs.
Source code listing

Listing of the input source text lines is controlled by any of the following statements:
*CONTROL SOURCE *CONTROL NOSOURCE [*CBL SOURCE] [*CBL NOSOURCE]
If a *CONTROL NOSOURCE statement is encountered and SOURCE has been requested as a compilation option, printing of the source listing is suppressed from this point on. An informational (I-level) message is issued stating that printing of the source has been suppressed.
507
Object code listing

Listing of generated object code is controlled by any of the following statements occurring in the procedure division:
*CONTROL LIST *CONTROL NOLIST [*CBL LIST] [*CBL NOLIST]
If a *CONTROL NOLIST statement is encountered, and LIST has been requested as a compilation option, listing of generated object code is suppressed from this point on.
Storage map listing

Listing of storage map entries is controlled by any of the following statements occurring in the data division:
*CONTROL MAP *CONTROL NOMAP [*CBL MAP] [*CBL NOMAP]
If a *CONTROL NOMAP statement is encountered, and MAP has been requested as a compilation option, listing of storage map entries is suppressed from this point on. For example, either of the following sets of statements produces a storage map listing in which A and B will not appear:
*CONTROL NOMAP 01 A 02 B *CONTROL MAP *CBL NOMAP 01 A 02 B *CBL MAP
COPY statement
The COPY statement is a library statement that places prewritten text in a COBOL compilation unit. Prewritten source code entries can be included in a compilation unit at compile time. Thus, an installation can use standard file descriptions, record descriptions, or procedures without recoding them. These entries and procedures can then be saved in user-created libraries; they can then be included in programs and class definitions by means of the COPY statement. Compilation of the source code containing COPY statements is logically equivalent to processing all COPY statements before processing the resulting source text. The effect of processing a COPY statement is that the library text associated with text-name is copied into the compilation unit, logically replacing the entire COPY statement, beginning with the word COPY and ending with the period, inclusive. When the REPLACING phrase is not specified, the library text is copied unchanged.
508
Language Reference
Format
COPY text-name literal-1
OF IN
library-name literal-2 .
SUPPRESS
REPLACING
operand-1 BY operand-2
text-name, library-name text-name identifies the copy text. library-name identifies where the copy text exists. v Can be from 1-30 characters in length v Can contain characters: A-Z, a-z, 0-9, hyphen v The first character must be alphabetic v The last character must not be a hyphen text-name and library-name can be the same as a user-defined word. text-name need not be qualified. If text-name is not qualified, a library-name of SYSLIB is assumed. When compiling from JCL or TSO, only the first eight characters are used as the identifying name. When compiling with the cob2 command and processing COPY text residing in the Hierarchical File System (HFS), all characters are significant. literal-1, literal-2 Must be alphanumeric literals. literal-1 identifies the copy text. literal-2 identifies where the copy text exists. When compiling from JCL or TSO: v Literals can be from 1-30 characters in length. v Literals can contain characters: A-Z, a-z, 0-9, hyphen. v The first character must be alphabetic. v The last character must not be a hyphen. v Only the first eight characters are used as the identifying name. When compiling with the cob2 command and processing COPY text residing in the HFS, the literal can be from 1 to 160 characters in length. The uniqueness of text-name and library-name is determined after the formation and conversion rules for a system-dependent name have been applied. For information about processing rules, see the Enterprise COBOL Programming Guide. operand-1, operand-2 Can be either pseudo-text, an identifier, a function-identifier, a literal, or a COBOL word (except the word COPY).
509
Library text and pseudo-text can consist of or include any words (except COPY), identifiers, or literals that can be written in the source text. This includes DBCS user-defined words, DBCS literals, and national literals. DBCS user-defined words must be wholly formed; that is, there is no partial-word replacement for DBCS words. Words or literals containing DBCS characters cannot be continued across lines. Each COPY statement must be preceded by a space and ended with a separator period. A COPY statement can appear in the source text anywhere a character string or a separator can appear. COPY statements can be nested. However, nested COPY statements cannot contain the REPLACING phrase, and a COPY statement with the REPLACING phrase cannot contain nested COPY statements. A nested COPY statement cannot cause recursion. That is, a COPY member can be named only once in a set of nested COPY statements until the end-of-file for that COPY member is reached. For example, assume that the source text contains the statement: COPY X. and library text X contains the statement: COPY Y.. In this case, library text Y must not have a COPY X or a COPY Y statement. Debugging lines are permitted within library text and pseudo-text. Text words within a debugging line participate in the matching rules as if the D did not appear in the indicator area. A debugging line is specified within pseudo-text if the debugging line begins in the source text after the opening pseudo-text delimiter but before the matching closing pseudo-text delimiter. If additional lines are introduced into the source text as a result of a COPY statement, each text word introduced appears on a debugging line if the COPY statement begins on a debugging line or if the text word being introduced appears on a debugging line in library text. When a text word specified in the BY phrase is introduced, it appears on a debugging line if the first library text word being replaced is specified on a debugging line. When a COPY statement is specified on a debugging line, the copied text is treated as though it appeared on a debugging line, except that comment lines in the text appear as comment lines in the resulting source text. If the word COPY appears in a comment-entry, or in the place where a comment-entry can appear, it is considered part of the comment-entry. After all COPY and REPLACE statements have been processed, a debugging line will be considered to have all the characteristics of a comment line, if the WITH DEBUGGING MODE clause is not specified in the SOURCE-COMPUTER paragraph. Comment lines or blank lines can occur in library text. Comment lines or blank lines appearing in library text are copied into the resultant source text unchanged with the following exception: a comment line or blank line in library text is not
510
Language Reference
copied if that comment line or blank line appears within the sequence of text words that match operand-1 (see Replacement and comparison rules on page 512). Lines containing *CONTROL (*CBL), EJECT, SKIP1, SKIP2, SKIP3, or TITLE statements can occur in library text. Such lines are treated as comment lines during COPY statement processing. The syntactic correctness of the entire COBOL source text cannot be determined until all COPY and REPLACE statements have been completely processed, because the syntactic correctness of the library text cannot be independently determined. Library text copied from the library is placed into the same area of the resultant program as it is in the library. Library text must conform to the rules for Standard COBOL 85 format. Note: Characters outside those defined for COBOL words and separators must not appear in library text or pseudo-text except in comment lines, comment-entries, alphanumeric literals, DBCS literals, or national literals.
SUPPRESS phrase
The SUPPRESS phrase specifies that the library text is not to be printed on the source listing.
REPLACING phrase
In the discussion that follows, each operand can consist of one of the following: v Pseudo-text v An identifier v A literal v A COBOL word (except the word COPY) v Function identifier When the REPLACING phrase is specified, the library text is copied, and each properly matched occurrence of operand-1 within the library text is replaced by the associated operand-2. pseudo-text A sequence of character-strings or separators, or both, bounded by, but not including, pseudo-text delimiters (==). Both characters of each pseudo-text delimiter must appear on one line; however, character-strings within pseudo-text can be continued. Individual character-strings within pseudo-text can be up to 322 characters long; they can be continued subject to the normal continuation rules for source code format. Keep in mind that a character-string must be delimited by separators. For more information, see Chapter 1, Characters, on page 3. pseudo-text-1 refers to pseudo-text when used for operand-1, and pseudo-text-2 refers to pseudo-text when used for operand-2. pseudo-text-1 can consist solely of the separator comma or separator semicolon. pseudo-text-2 can be null; it can consist solely of space characters or comment lines. Pseudo-text must not contain the word COPY.
511
Each text word in pseudo-text-2 that is to be copied into the program is placed in the same area of the resultant program as the area in which it appears in pseudo-text-2. Pseudo-text can consist of or include any words (except COPY), identifiers, or literals that can be written in the source text. This includes DBCS user-defined words, DBCS literals, and national literals. DBCS user-defined words must be wholly formed; that is, there is no partial-word replacement for DBCS words. Words or literals containing DBCS characters cannot be continued across lines. identifier Can be defined in any section of the data division. literal Can be numeric, alphanumeric, DBCS, or national. word Can be any single COBOL word (except COPY), including DBCS user-defined words. DBCS DBCS user-defined words must be wholly formed. You cannot replace part of a DBCS word. You can include the nonseparator COBOL characters (for example, +, *, /, $, <, >, and =) as part of a COBOL word when used as REPLACING operands. In addition, the hyphen character can be at the beginning or end of the word. For purposes of matching, each identifier-1, literal-1, or word-1 is treated as pseudo-text containing only identifier-1, literal-1, or word-1, respectively.
Replacement and comparison rules

1. Arithmetic and logical operators are considered text words and can be replaced only through the pseudo-text option. 2. Beginning and ending blanks are not included in the text comparison process. Embedded blanks are used in the text comparison process to separate multiple text words. 3. When operand-1 is a figurative constant, operand-1 matches only the same exact figurative constant. For example, if ALL AB is specified in the library text, then ABAB is not considered a match; only ALL AB is considered a match. 4. When replacing a PICTURE character-string, the pseudo-text option should be used; to avoid ambiguities, pseudo-text-1 should specify the entire PICTURE clause, including the keyword PICTURE or PIC. 5. Any separator comma, semicolon, and/or space preceding the leftmost word in the library text is copied into the source text. Beginning with the leftmost library text word and the first operand-1 specified in the REPLACING option, the entire REPLACING operand that precedes the keyword BY is compared to an equivalent number of contiguous library text words. 6. operand-1 matches the library text if, and only if, the ordered sequence of text words in operand-1 is equal, character for character, to the ordered sequence of library words. For national characters, the sequence of national characters must be equal, national character for national character, to the ordered sequence of library words. For matching purposes, each occurrence of a comma or semicolon separator and each sequence of one or more space separators is considered to be a single space. However, when operand-1 consists solely of a separator comma or semicolon, it participates in the match as a text word (in this case, the space following the comma or semicolon separator can be omitted).
512
Language Reference
When the library text contains a closing quotation mark that is not immediately followed by a separator space, comma, semicolon, or period, the closing quotation mark is considered a separator quotation mark. 7. If no match occurs, the comparison is repeated with each successive operand-1, if specified, until either a match is found or there are no further REPLACING operands. 8. Whenever a match occurs between operand-1 and the library text, the associated operand-2 is copied into the source text. 9. The COPY statement with REPLACING phrase can be used to replace parts of words. By inserting a dummy operand delimited by colons into the program text, the compiler will replace the dummy operand with the desired text. Example 3 shows how this is used with the dummy operand :TAG:. The colons serve as separators and make TAG a stand-alone operand. 10. When all operands have been compared and no match is found, the leftmost library text word is copied into the source text. 11. The next successive uncopied library text word is then considered to be the leftmost text word, and the comparison process is repeated, beginning with the first operand-1. The process continues until the rightmost library text word has been compared. 12. Comment lines or blank lines occurring in the library text and in pseudo-text-1 are ignored for purposes of matching; and the sequence of text words in the library text and in pseudo-text-1 is determined by the rules for reference format. Comment lines or blank lines appearing in pseudo-text-2 are copied into the resultant program unchanged whenever pseudo-text-2 is placed into the source text as a result of text replacement. Comment lines or blank lines appearing in library text are copied into the resultant source text unchanged with the following exception: a comment line or blank line in library text is not copied if that comment line or blank line appears within the sequence of text words that match pseudo-text-1. 13. Text words, after replacement, are placed in the source text according to Standard COBOL 85 format rules. 14. When text words are placed in the source text, additional spaces are introduced only between text words where there already exists a space (including the assumed space between source lines). 15. COPY REPLACING does not affect the EJECT, SKIP1, SKIP2, SKIP3, or TITLE compiler-directing statements. Sequences of code (such as file and data descriptions, error and exception routines) that are common to a number of programs can be saved in a library, and then used in conjunction with the COPY statement. If naming conventions are established for such common code, then the REPLACING phrase need not be specified. If the names will change from one program to another, then the REPLACING phrase can be used to supply meaningful names for this program. Example 1 In this example, the library text PAYLIB consists of the following data division entries:
01 A. 02 B PIC S99. 02 C PIC S9(5)V99. 02 D PIC S9999 OCCURS 1 TO 52 TIMES DEPENDING ON B OF A.
513
The programmer can use the COPY statement in the data division of a program as follows:
COPY PAYLIB.
In this program, the library text is copied; the resulting text is treated as if it had been written as follows:
01 A. 02 B PIC S99. 02 C PIC S9(5)V99. 02 D PIC S9999 OCCURS 1 TO 52 TIMES DEPENDING ON B OF A.
Example 2 To change some (or all) of the names within the library text, the programmer can use the REPLACING phrase:
COPY PAYLIB REPLACING A B C D BY BY BY BY PAYROLL PAY-CODE GROSS-PAY HOURS.
In this program, the library text is copied; the resulting text is treated as if it had been written as follows:
01 PAYROLL. 02 PAY-CODE PIC S99. 02 GROSS-PAY PIC S9(5)V99. 02 HOURS PIC S9999 OCCURS 1 TO 52 TIMES DEPENDING ON PAY-CODE OF PAYROLL.
The changes shown are made only for this program. The text, as it appears in the library, remains unchanged. Example 3 If the following conventions are followed in library text, then parts of names (for example the prefix portion of data names) can be changed with the REPLACING phrase. In this example, the library text PAYLIB consists of the following data division entries:
01 :TAG:. 02 :TAG:-WEEK PIC S99. 02 :TAG:-GROSS-PAY PIC S9(5)V99. 02 :TAG:-HOURS PIC S999 OCCURS 1 TO 52 TIMES DEPENDING ON :TAG:-WEEK OF :TAG:.
The programmer can use the COPY statement in the data division of a program as follows:
COPY PAYLIB REPLACING ==:TAG:== BY ==Payroll==.
Note: It is important to notice in this example the required use of colons or parentheses as delimiters in the library text. Colons are recommended for clarity because parentheses can be used for a subscript, for instance in referencing a table element. In this program, the library text is copied; the resulting text is treated as if it had been written as follows:
514
Language Reference
01 PAYROLL. 02 PAYROLL-WEEK PIC S99. 02 PAYROLL-GROSS-PAY PIC S9(5)V99. 02 PAYROLL-HOURS PIC S999 OCCURS 1 TO 52 TIMES DEPENDING ON PAYROLL-WEEK OF PAYROLL.
The changes shown are made only for this program. The text, as it appears in the library, remains unchanged. Example 4 This example shows how to selectively replace level numbers without replacing the numbers in the PICTURE clause:
COPY xxx REPLACING ==(01)== BY ==(01)== == 01 == BY == 05 ==.
DELETE statement
The DELETE statement is an extended source library statement. It removes COBOL statements from a source program that was included by a BASIS statement.
Format
DELETE sequence-number-field sequence-number
sequence-number Can optionally appear in columns 1 through 6, followed by a space. The content of this field is ignored. DELETE Can appear anywhere within columns 1 through 72. It must be followed by a space and the sequence-number-field. There must be no other text in the statement. sequence-number-field Each number must be equal to a sequence-number in the BASIS source program. This sequence-number is the six-digit number the programmer assigns in columns 1 through 6 of the COBOL coding form. The numbers referenced in the sequence-number-field of INSERT or DELETE statements must always be specified in ascending numeric order. The sequence-number-field must be one of the following: v A single number v A series of single numbers v A range of numbers (indicated by separating the two bounding numbers of the range by a hyphen) v A series of ranges of numbers v Any combination of one or more single numbers and one or more ranges of numbers Each entry in the sequence-number-field must be separated from the preceding entry by a comma followed by a space. For example:
000250 DELETE 000010-000050, 000400, 000450
515
Source program statements can follow a DELETE statement. These source program statements are then inserted into the BASIS source program before the statement following the last statement deleted (that is, in the example above, before the next statement following deleted statement 000450). If a DELETE statement begins in column 12 or higher and a valid sequence-number-field does not follow the keyword DELETE, the compiler assumes that this DELETE statement is a COBOL DELETE statement. Usage note: If INSERT or DELETE statements are used to modify the COBOL source program provided by a BASIS statement, the sequence field of the COBOL source program must contain numeric sequence numbers in ascending order. The source file remains unchanged. Any INSERT or DELETE statements referring to these sequence numbers must occur in ascending order.
EJECT statement
The EJECT statement specifies that the next source statement is to be printed at the top of the next page.
Format
EJECT .
The EJECT statement must be the only statement on the line. It can be written in either Area A or Area B, and can be terminated with a separator period. The EJECT statement must be embedded in a program source. For example, in the case of batch applications, the EJECT statement must be placed between the CBL (PROCESS) statement and the end of the program (or the END PROGRAM marker, if specified). The EJECT statement has no effect on the compilation of the source unit itself.
ENTER statement
The ENTER statement is designed to facilitate the use of more than one source language in the same source program. However, in Enterprise COBOL, only COBOL is allowed in the source program. The ENTER statement is syntax checked but has no effect on the execution of the program.
Format
ENTER language-name-1 routine-name-1 .
516
Language Reference
language-name-1 A system name that has no defined meaning. It must be either a correctly formed user-defined word or the word COBOL. At least one character must be alphabetic. routine-name-1 Must follow the rules for formation of a user-defined word. At least one character must be alphabetic.
INSERT statement
The INSERT statement is a library statement that adds COBOL statements to a source program that was included by a BASIS statement.
Format
INSERT sequence-number-field sequence-number
sequence-number Can optionally appear in columns 1 through 6, followed by a space. The content of this field is ignored. INSERT Can appear anywhere within columns 1 through 72, followed by a space and the sequence-number-field. There must be no other text in the statement. sequence-number-field A number that must be equal to a sequence-number in the BASIS source program. This sequence-number is a six-digit number that the programmer assigns in columns 1 through 6 of the COBOL source line. The numbers referenced in the sequence-number-field of INSERT or DELETE statements must always be specified in ascending numeric order. The sequence-number-field must be a single number (for example, 000130). At least one new source program statement must follow the INSERT statement for insertion after the statement number specified by the sequence-number-field. New source program statements following the INSERT statement can include DBCS data items. Usage note: If INSERT or DELETE statements are used to modify the COBOL source program provided by a BASIS statement, the sequence field of the COBOL source program must contain numeric sequence numbers in ascending order. The source file remains unchanged. Any INSERT or DELETE statements referring to these sequence numbers must occur in ascending order.
READY or RESET TRACE statement

The READY or RESET TRACE statement can appear only in the procedure division, but has no effect on your program.
517
Format
READY RESET TRACE .
You can reproduce the function of READY TRACE by using the USE FOR DEBUGGING declarative, the DISPLAY statement, and the DEBUG-ITEM special register. For example:
... ENVIRONMENT DIVISION. CONFIGURATION SECTION. SOURCE-COMPUTER. IBM-zSeries ... DATA DIVISION. ... WORKING-STORAGE SECTION. 01 TRACE-SWITCH PIC 9 88 READY-TRACE 88 RESET-TRACE ... PROCEDURE DIVISION. DECLARATIVES. COBOL-II-DEBUG SECTION. USE FOR DEBUGGING ON ALL COBOL-II-DEBUG-PARA. IF READY-TRACE THEN DISPLAY DEBUG-NAME END-IF. END DECLARATIVES. MAIN-PROCESSING SECTION. ... PARAGRAPH-3. ... SET READY-TRACE TO TRUE. PARAGRAPH-4. ... PARAGRAPH-6. ... SET RESET-TRACE TO TRUE. PARAGRAPH-7.
WITH DEBUGGING MODE.
VALUE 0. VALUE 1. VALUE 0.
PROCEDURES.
where DEBUG-NAME is a field of the DEBUG-ITEM special register that displays the name of the procedure that caused execution of the debugging procedure. In this example, the object program displays the names of procedures PARAGRAPH-4 through PARAGRAPH-6 as control reaches each procedure within the range. At run time, you must specify the DEBUG run-time option to activate this debugging procedure. In this way, you have no need to recompile the program to activate or deactivate the debugging declarative.
REPLACE statement
The REPLACE statement is used to replace source text.
518
Language Reference
A REPLACE statement can occur anywhere in the source text that a character-string can occur. It must be preceded by a separator period except when it is the first statement in a separately compiled program. It must be terminated by a separator period. The REPLACE statement provides a means of applying a change to an entire COBOL compilation group, or part of a compilation group, without manually having to find and modify all places that need to be changed. It is an easy method of doing simple string substitutions. It is similar in action to the REPLACING phrase of the COPY statement, except that it acts on the entire source text, not just on the text in COPY libraries. If the word REPLACE appears in a comment-entry or in the place where a comment-entry can appear, it is considered part of the comment-entry.
Format 1
REPLACE
==
pseudo-text-1
==
BY
==
pseudo-text-2
==
Each matched occurrence of pseudo-text-1 in the source text is replaced by the corresponding pseudo-text-2.
Format 2
REPLACE OFF.
Any text replacement currently in effect is discontinued with the format-2 form of REPLACE. If format 2 is not specified, a given occurrence of the REPLACE statement is in effect from the point at which it is specified until the next occurrence of a REPLACE statement or the end of the separately compiled program. pseudo-text-1 Must contain one or more text words. Character-strings can be continued in accordance with normal source code rules. pseudo-text-1 can consist solely of a separator comma or a separator semicolon. pseudo-text-2 Can contain zero, one, or more text words. Character strings can be continued in accordance with normal source code rules. pseudo-text-1 and pseudo-text-2 can contain any text words (except the word COPY) that can be written in source text, including national literals, DBCS literals, and DBCS user-defined words.
519
Characters outside those allowed for COBOL words and separators must not appear in library text or pseudo-text except in comment lines, comment-entries, alphanumeric literals, DBCS literals, or national literals. DBCS user-defined words must be wholly formed; that is, there is no partial-word replacement for DBCS words. pseudo-text-1 and pseudo-text-2 can contain single-byte and DBCS characters in comment lines and comment entries. Individual character-strings within pseudo-text can be up to 322 characters long, except that strings containing DBCS characters cannot be continued. The compiler processes REPLACE statements in source text after the processing of any COPY statements. COPY must be processed first, to assemble complete source text. Then REPLACE can be used to modify that source text, performing simple string substitution. REPLACE statements cannot themselves contain COPY statements. The text produced as a result of the processing of a REPLACE statement must not contain a REPLACE statement.
Continuation rules for pseudo-text

The character-strings and separators comprising pseudo-text can start in either area A or area B. If, however, there is a hyphen in the indicator area of a line that follows the opening pseudo-text delimiter, area A of the line must be blank; and the normal rules for continuation of lines apply to the formation of text words. (See Continuation lines on page 44.)
Comparison operation
The comparison operation to determine text replacement starts with the leftmost source text word following the REPLACE statement, and with the first pseudo-text-1. pseudo-text-1 is compared to an equivalent number of contiguous source text words. pseudo-text-1 matches the source text if, and only if, the ordered sequence of text words that forms pseudo-text-1 is equal, character for character, to the ordered sequence of source text words. For national characters, the sequence of national characters must be equal, national character for national character, to the ordered sequence of library words. For purposes of matching, each occurrence of a separator comma, semicolon, and space, and each sequence of one or more space separators is considered to be a single space. However, when pseudo-text-1 consists solely of a separator comma or semicolon, the comma or semicolon participates in the match as a text word (in this case, the space following the comma or semicolon separator can be omitted). If no match occurs, the comparison is repeated with each successive occurrence of pseudo-text-1, until either a match is found or there is no next successive occurrence of pseudo-text-1.
520
Language Reference
When all occurrences of pseudo-text-1 have been compared and no match has occurred, the next successive source text word is then considered as the leftmost source text word, and the comparison cycle starts again with the first occurrence of pseudo-text-1. Whenever a match occurs between pseudo-text-1 and the source text, the corresponding pseudo-text-2 replaces the matched text in the source text. The source text word immediately following the rightmost text word that participated in the match is then considered as the leftmost source text word. The comparison cycle starts again with the first occurrence of pseudo-text-1. The comparison operation continues until the rightmost text word in the source text that is within the scope of the REPLACE statement has either participated in a match or been considered as a leftmost source text word and participated in a complete comparison cycle.
REPLACE statement notes

Comment lines or blank lines occurring in the source text and in pseudo-text-1 are ignored for purposes of matching. The sequence of text words in the source text and in pseudo-text-1 is determined by the rules for reference format (see Chapter 6, Reference format, on page 41). Comment lines or blank lines in pseudo-text-2 are placed into the resultant program unchanged whenever pseudo-text-2 is placed into the source text as a result of text replacement. Comment lines or blank lines appearing in source text are retained unchanged with the following exception: a comment line or blank line in source text is not retained if that comment line or blank line appears within the sequence of text words that match pseudo-text-1. Lines containing *CONTROL (*CBL), EJECT, SKIP1/2/3, or TITLE statements can occur in source text. Such lines are treated as comment lines during REPLACE statement processing. Debugging lines are permitted in pseudo-text. Text words within a debugging line participate in the matching rules as if the letter D did not appear in the indicator area. When a REPLACE statement is specified on a debugging line, the statement is treated as if the letter D did not appear in the indicator area. After all COPY and REPLACE statements have been processed, a debugging line will be considered to have all the characteristics of a comment line if the WITH DEBUGGING MODE clause is not specified in the SOURCE-COMPUTER paragraph. Except for COPY and REPLACE statements, the syntactic correctness of the source text cannot be determined until after all COPY and REPLACE statements have been completely processed. Text words inserted into the source text as a result of processing a REPLACE statement are placed in the source text according to the rules for reference format. When inserting text words of pseudo-text-2 into the source text, additional spaces are introduced only between text words where there already exists a space (including the assumed space between source lines). If additional lines are introduced into the source text as a result of the processing of REPLACE statements, the indicator area of the introduced lines contains the
521
same character as the line on which the text being replaced begins, unless that line contains a hyphen, in which case the introduced line contains a space. If any literal within pseudo-text-2 is of a length too great to be accommodated on a single line without continuation to another line in the resultant program and the literal is not being placed on a debugging line, additional continuation lines are introduced that contain the remainder of the literal. If replacement requires the continued literal to be continued on a debugging line, the program is in error. Each word in pseudo-text-2 that is to be placed into the resultant program begins in the same area of the resultant program as it appears in pseudo-text-2.
SERVICE LABEL statement

This statement is generated by the CICS preprocessor to indicate control flow. It is also used after calls to CEE3SRP when using Language Environment condition handling. For more information about CEE3SRP, see the Language Environment Programming Guide.
Format
SERVICE LABEL
The SERVICE LABEL statement can appear only in the procedure division, not in the declaratives section. At the statement following the SERVICE LABEL statement, all registers that might no longer be valid are reloaded.
SERVICE RELOAD statement

The SERVICE RELOAD statement is treated as a comment.
Format
SERVICE RELOAD identifier-1
SKIP statements
The SKIP1, SKIP2, and SKIP3 statements specify blank lines that the compiler should add when printing the source listing. SKIP statements have no effect on the compilation of the source text itself.
522
Language Reference
Format
SKIP1 SKIP2 SKIP3
SKIP1 Specifies a single blank line to be inserted in the source listing. SKIP2 Specifies two blank lines to be inserted in the source listing. SKIP3 Specifies three blank lines to be inserted in the source listing. SKIP1, SKIP2, or SKIP3 can be written anywhere in either Area A or Area B, and can be terminated with a separator period. It must be the only statement on the line. The SKIP statements must be embedded in a program source. For example, in the case of batch applications, a SKIP1, SKIP2, or SKIP3 statement must be placed between the CBL (PROCESS) statement and the end of the program or class (or the END CLASS marker or END PROGRAM marker, if specified).
TITLE statement
The TITLE statement specifies a title to be printed at the top of each page of the source listing produced during compilation. If no TITLE statement is found, a title containing the identification of the compiler and the current release level is generated. The title is left-justified on the title line.
Format
TITLE literal .
literal Must be an alphanumeric, DBCS, or national literal and can be followed by a separator period. Must not be a figurative constant. In addition to the default or chosen title, the right side of the title line contains the following: v For programs, the name of the program from the PROGRAM-ID paragraph for the outermost program. (This space is blank on pages preceding the PROGRAM-ID paragraph for the outermost program.) v For classes, the name of the class from the CLASS-ID paragraph. v Current page number. v Date and time of compilation. The TITLE statement: v Forces a new page immediately, if the SOURCE compiler option is in effect v Is not itself printed on the source listing
523
v v v v
Has no other effect on compilation Has no effect on program execution Cannot be continued on another line Can appear anywhere in any of the divisions
A title line is produced for each page in the listing produced by the LIST option. This title line uses the last TITLE statement found in the source statements or the default. The word TITLE can begin in either Area A or Area B. The TITLE statement must be embedded in a class or program source. For example, in the case of batch applications, the TITLE statement must be placed between the CBL (PROCESS) statement and the end of the class or program (or the END CLASS marker or END PROGRAM marker, if specified). No other statement can appear on the same line as the TITLE statement.
USE statement
The formats for the USE statement are: v EXCEPTION/ERROR declarative v LABEL declarative v DEBUGGING declarative For general information about declaratives, see Declaratives on page 238.
EXCEPTION/ERROR declarative
The EXCEPTION/ERROR declarative specifies procedures for input/output exception or error handling that are to be executed in addition to the standard system procedures. The words EXCEPTION and ERROR are synonymous and can be used interchangeably.
Format 1: USE (EXCEPTION ERROR declarative)

USE GLOBAL AFTER STANDARD EXCEPTION ERROR PROCEDURE
ON
file-name-1 INPUT OUTPUT I-O EXTEND
file-name-1 Valid for all files. When this option is specified, the procedure is executed
524
Language Reference
only for the files named. No file-name can refer to a sort or merge file. For any given file, only one EXCEPTION/ERROR procedure can be specified; thus, file-name specification must not cause simultaneous requests for execution of more than one EXCEPTION/ERROR procedure. A USE AFTER EXCEPTION/ERROR declarative statement specifying the name of a file takes precedence over a declarative statement specifying the open mode of the file. INPUT Valid for all files. When this option is specified, the procedure is executed for all files opened in INPUT mode or in the process of being opened in INPUT mode that get an error. OUTPUT Valid for all files. When this option is specified, the procedure is executed for all files opened in OUTPUT mode or in the process of being opened in OUTPUT mode that get an error. I-O Valid for all direct-access files. When this option is specified, the procedure is executed for all files opened in I-O mode or in the process of being opened in I-O mode that get an error.
EXTEND Valid for all files. When this option is specified, the procedure is executed for all files opened in EXTEND mode or in the process of being opened in EXTEND mode that get an error. The EXCEPTION/ERROR procedure is executed: v Either after completing the system-defined input/output error routine, or v Upon recognition of an INVALID KEY or AT END condition when an INVALID KEY or AT END phrase has not been specified in the input/output statement, or v Upon recognition of an IBM-defined condition that causes file status key 1 to be set to 9. (See File status key on page 278.) After execution of the EXCEPTION/ERROR procedure, control is returned to the invoking routine in the input/output control system. If the input/output status value does not indicate a critical input/output error, the input/output control system returns control to the next executable statement following the input/output statement whose execution caused the exception. An applicable EXCEPTION/ERROR procedure is activated when an input/output error occurs during execution of a READ, WRITE, REWRITE, START, OPEN, CLOSE, or DELETE statement. To determine what conditions are errors, see Common processing facilities on page 278. The following rules apply to declarative procedures: v A declarative procedure can be performed from a nondeclarative procedure. v A nondeclarative procedure can be performed from a declarative procedure. v A declarative procedure can be referenced in a GO TO statement in a declarative procedure. v A nondeclarative procedure can be referenced in a GO TO statement in a declarative procedure. You can include a statement that executes a previously called USE procedure that is still in control. However, to avoid an infinite loop, you must be sure that there is an eventual exit at the bottom.
525
EXCEPTION/ERROR procedures can be used to check the file status key values whenever an input/output error occurs.
Precedence rules for nested programs

Special precedence rules are followed when programs are contained within other programs. In applying these rules, only the first qualifying declarative is selected for execution. The order of precedence for selecting a declarative is: 1. A file-specific declarative (that is, a declarative of the form USE AFTER ERROR ON file-name-1) within the program that contains the statement that caused the qualifying condition. 2. A mode-specific declarative (that is, a declarative of the form USE AFTER ERROR ON INPUT) within the program that contains the statement that caused the qualifying condition. 3. A file-specific declarative that specifies the GLOBAL phrase and is within the program directly containing the program that was last examined for a qualifying declarative. 4. A mode-specific declarative that specifies the GLOBAL phrase and is within the program directly containing the program that was last examined for a qualifying condition. Steps 3. and 4. are repeated until the last examined program is the outermost program, or until a qualifying declarative has been found.
LABEL declarative
The LABEL declarative provides user label-handling procedures.
Format 2: USE (LABEL declarative)

USE GLOBAL AFTER STANDARD BEGINNING ENDING FILE REEL UNIT
LABEL PROCEDURE ON
file-name-1 INPUT OUTPUT I-O EXTEND
AFTER User labels follow standard file labels, and are to be processed. The labels must be listed as data names in the LABEL RECORDS clause in the file description entry for the file, and must be described as level-01 data items subordinate to the file entry. If neither BEGINNING nor ENDING is specified, the designated procedures are executed for both beginning and ending labels.
526
Language Reference
If FILE, REEL, or UNIT is not included, the designated procedures are executed both for REEL or UNIT, whichever is appropriate, and for FILE labels. FILE REEL The designated procedures are executed at beginning-of-file (on the first volume) and/or at end-of-file (on the last volume) only. The designated procedures are executed at beginning-of-volume (on each volume except the first) and/or at end-of-volume (on each volume except the last). The REEL option is not applicable to direct-access files. UNIT The designated procedures are executed at beginning-of-volume (on each volume except the first) and/or at end-of-volume (on each volume except the last). The UNIT phrase is not applicable to files in the random access mode, because only FILE labels are processed in this mode. file-name-1 Can appear in different specific arrangements of the format. However, appearance of a file-name in a USE statement must not cause the simultaneous request for execution of more than one USE declarative. file-name-1 must not represent a sort file. If the file-name-1 option is used, the file description entry for file-name must not specify a LABEL RECORDS ARE OMITTED clause. When the INPUT, OUTPUT, or I-O options are specified, user label procedures are executed as follows: v When INPUT is specified, only for files opened as input v When OUTPUT is specified, only for files opened as output v When I-O is specified, only for files opened as I-O v When EXTEND is specified, only for files opened EXTEND If the INPUT, OUTPUT, or I-O phrase is specified, and an input, output, or I-O file, respectively, is described with a LABEL RECORDS ARE OMITTED clause, the USE procedures do not apply. The standard system procedures are performed: v Before the beginning or ending input label check procedure is executed v Before the beginning or ending output label is created v After the beginning or ending output label is created, but before it is written on tape v Before the beginning or ending input-output label check procedure is executed Within the procedures of a USE declarative in which the USE sentence specifies an option other than file-name, references to common label items need not be qualified by a file-name. A common label item is an elementary data item that appears in every label record of the program, but does not appear in any data records of this program. Such items must have identical descriptions and positions within each label record. Within a declarative section there must be no reference to any nondeclarative procedure. Conversely, in the nondeclarative portion there must be no reference to procedure-names that appear in the declarative section, except that the PERFORM statement can refer to a USE procedure, or to procedures associated with it.
527
The exit from a declarative section is inserted by the compiler following the last statement in the section. All logical processing paths within the section must lead to the exit point. There is one exception: A special exit can be specified by the statement GO TO MORE-LABELS. When an exit is made from a declarative section by means of this statement, the system will do one of the following: v Write the current beginning or ending label and then reenter the USE section at its beginning for further creating of labels. After creating the last label, the user must exit by executing the last statement of the section. v Read an additional beginning or ending label, and then reenter the USE section at its beginning for further checking of labels. When processing user labels, the section will be reentered only if there is another user label to check. Hence, there need not be a program path that flows through the last statement in the section. If a GO TO MORE-LABELS statement is not executed for a user label, the declarative section is not reentered to check or create any immediately succeeding user labels.
DEBUGGING declarative
Debugging sections are permitted only in the outermost program; they are not valid in nested programs. Debugging sections are never triggered by procedures contained in nested programs. Debugging sections are not permitted in: v A method v A program defined with the recursive attribute v A program compiled with the THREAD compiler option The WITH DEBUGGING MODE clause of the SOURCE-COMPUTER paragraph activates all debugging sections and lines that have been compiled into the object code. See Appendix D, Source language debugging, on page 557 for additional details. When the debugging mode is suppressed by not specifying the WITH DEBUGGING MODE clause, all USE FOR DEBUGGING declarative procedures and all debugging lines are inhibited. Automatic execution of a debugging section is not caused by a statement that appears in a debugging section.
Format 3: USE (Debugging declarative)
USE FOR
DEBUGGING ON
procedure-name-1 ALL PROCEDURES
USE FOR DEBUGGING All debugging statements must be written together in a section immediately after the DECLARATIVES header.
528
Language Reference
Except for the USE FOR DEBUGGING sentence itself, within the debugging procedure there must be no reference to any nondeclarative procedures. procedure-name-1 Must not be defined in a debugging session. Execution of debugging declaratives (Table 53) shows, for each valid option, the points during execution when the USE FOR DEBUGGING procedures are executed. Any given procedure-name can appear in only one USE FOR DEBUGGING sentence, and only once in that sentence. All procedures must appear in the outermost program. ALL PROCEDURES procedure-name-1 must not be specified in any USE FOR DEBUGGING sentences. The ALL PROCEDURES phrase can be specified only once in a program. Only the procedures contained in the outermost program will trigger execution of the debugging section.
Table 53. Execution of debugging declaratives USE FOR DEBUGGING operand procedure-name-1 Upon execution of the following, the USE FOR DEBUGGING procedures are executed immediately Before each execution of the named procedure After the execution of an ALTER statement referring to the named procedure ALL PROCEDURES Before each execution of every nondebugging procedure in the outermost program After the execution of every ALTER statement in the outermost program (except ALTER statements in declarative procedures)
529
530
Language Reference
Part 9. Appendixes
531
532
Language Reference
Appendix A. IBM extensions

IBM extensions are features, syntax rules, or behavior defined by IBM rather than by the COBOL standards listed in Appendix G, Industry specifications, on page 577. IBM extension language elements (Table 54) lists IBM extensions with a brief description. Standard behavior is shown in brackets, [ ], when the standard behavior is not obvious. Extensions are described in more detail throughout this document, but they are not further identified as extensions. Many IBM extensions are distinguished from standard language by their syntax. For others, you use compiler options to choose between standard and extension behavior. Generally, the related compiler options are noted in the detailed rules. You can find information about compiler options in the Enterprise COBOL Programming Guide. If an item is listed as an extension, all related rules are also extensions. For example, USAGE DISPLAY-1 for DBCS characters is listed as an extension; its many uses in statements and clauses are also extensions, but are not listed separately.
Table 54. IBM extension language elements Language area COBOL words Extension elements User-defined words written in DBCS characters Computer-name written in DBCS characters Class-names (for object orientation) Method-names National character support (Unicode support) Support for UTF-16 with USAGE NATIONAL Allowance of UTF-8 with USAGE DISPLAY National literals (basic and hexadecimal) Figurative constants SPACE, ZERO, QUOTE, ALL literal Intrinsic functions for data conversion: v DISPLAY-OF v NATIONAL-OF Extended case mapping with UPPER-CASE and LOWER-CASE functions
533
Table 54. IBM extension language elements (continued) Language area Implicit items Extension elements Special object references: v SELF v SUPER Special registers: v ADDRESS OF v JNIENVPTR v LENGTH OF v RETURN-CODE v SHIFT-IN v SHIFT-OUT v SORT-CONTROL v SORT-CORE-SIZE v SORT-FILE-SIZE v SORT-MESSAGE v SORT-MODE-SIZE v SORT-RETURN v TALLY v WHEN-COMPILED v XML-CODE v XML-EVENT v XML-NTEXT v XML-TEXT Figurative constants Selection of apostrophe () as the value of the figurative constant QUOTE NULL/NULLS for pointers and object references Literals Use of apostrophe () as an alternative to the quotation mark () in opening and closing delimiters Mixed single-byte and double-byte characters in alphanumeric literals (mixed literals) Hexadecimal notation for alphanumeric literals, defined by opening delimiters X and X Null-terminated alphanumeric literals, defined by opening delimiters Z and Z DBCS literals, defined by opening delimiters N, N, G, and G. N and N are defined as DBCS when the NSYMBOL(DBCS) compiler option is in effect. Consecutive alphanumeric literals (coding two consecutive alphanumeric literals by ending the first literal in column 72 of a continued line and starting the next literal with a single quotation mark in the continuation line) National literals N, N, NX, NX for storing literal content as national characters. N and N are defined as national when the NSYMBOL(NATIONAL) compiler option is in effect. 19- to 31-digit fixed-point numeric literals. [Standard COBOL 85 specifies a maximum of 18 digits.] Floating-point numeric literals
534
Language Reference
Table 54. IBM extension language elements (continued) Language area Comments Extension elements Comment lines before the identification division header Comment lines and comment entries containing DBCS characters End markers The following end markers: v END CLASS v END FACTORY v END METHOD v END OBJECT Indexing and subscripting Referencing a table with an index-name defined for a different table Specifying a positive signed integer literal following the operator + or - in relative subscripting Millennium language extensions and date fields. DATE FORMAT clause Windowed date fields, expanded date fields, year-last date fields, compatible date fields, date formats, and century window The following intrinsic functions: v DATEVAL v UNDATE v YEARWINDOW v DATE-TO-YYYYMMDD v DAY-TO-YYYYDDD v YEAR-TO-YYYY Identification division for programs Abbreviation ID for IDENTIFICATION RECURSIVE clause An optional separator period following PROGRAM-ID, AUTHOR, INSTALLATION, DATE-WRITTEN, and SECURITY paragraph headers. [Standard COBOL 85 requires a period following each of these paragraph headers.] An optional separator period following program-name in the PROGRAM-ID paragraph. [Standard COBOL 85 requires a period following program-name.] An alphanumeric literal for program-name in the PROGRAM-ID paragraph; characters $, #, and @ in the name of the outermost program; program-name up to 160 characters in length. [Standard COBOL 85 requires that program-name be specified as a user-defined word.] End markers Object-oriented structure Program-name in a literal. [Standard COBOL 85 requires that program-name be specified as a user-defined word.] In a class definition: v CLASS-ID paragraph v INHERITS clause v END CLASS marker In a method definition: v METHOD-ID paragraph v EXIT METHOD statement v END METHOD marker Configuration section Repository paragraph
535
Table 54. IBM extension language elements (continued) Language area SPECIAL-NAMES paragraph Extension elements The optional order of clauses. [Standard COBOL 85 requires that the clauses be coded in the order presented in the syntax diagram.] Optionality of a period after the last clause when no clauses are coded. [Standard COBOL 85 requires a period, even when no clauses are coded.] Multiple CURRENCY SIGN clauses. [Standard COBOL 85 allows a single CURRENCY SIGN clause.] WITH PICTURE SYMBOL phrase in the CURRENCY SIGN clause Multiple-character and mixed-case currency signs in the CURRENCY SIGN clause (when the WITH PICTURE SYMBOL phrase is specified). [Standard COBOL 85 allows only one character, and it is both the currency sign and the currency picture symbol. The standard currency sign must not be: v The same character as any standard picture symbol v A digit 0-9 v One of the special characters * + - , ; ( ) = / v A space ] Use of lower-case alphabetic characters as a currency sign. [Standard COBOL 85 allows only uppercase characters.] INPUT-OUTPUT SECTION, FILE-CONTROL paragraph Optionality of FILE-CONTROL. when the INPUT-OUTPUT SECTION is specified, no file-control-paragraph is specified, and there are no files defined in the compilation unit. [Standard COBOL 85 requires that FILE-CONTROL. be coded if INPUT-OUTPUT SECTION. is coded.] Optionality of the file-control-paragraph when the FILE CONTROL. syntax is specified and there are no files defined in the compilation unit. [Standard COBOL 85 requires that a file-control-paragraph be coded if INPUT-OUTPUT SECTION. is coded.] PASSWORD clause The second data-name in the FILE STATUS clause Optionality of RECORD in the ALTERNATE RECORD KEY clause. [Standard COBOL 85 requires the word RECORD.] A numeric, numeric-edited, alphanumeric-edited, alphabetic, internal floating-point, external floating-point, national, or DBCS primary or alternate record key data item. [Standard COBOL 85 requires that the key be alphanumeric.] A primary or alternate record key defined outside the minimum record size for indexed files containing variable-length records. [Standard COBOL 85 requires that the primary and alternate record keys be within the minimum record size.] A numeric data item of usage DISPLAY in the FILE STATUS clause. [Standard COBOL 85 requires an alphanumeric file status data item.] The ORGANIZATION IS LINE SEQUENTIAL clause and line-sequential file control format
536
Language Reference
Table 54. IBM extension language elements (continued) Language area INPUT-OUTPUT SECTION, I-O-CONTROL paragraph Extension elements APPLY WRITE-ONLY clause Specifying only one file-name in the SAME clause in the sequential, indexed, and sort-merge formats of the I-O-control entry. [Standard COBOL 85 requires at least two file-names.] Optionality of the keyword ON in the RERUN clause. [Standard COBOL 85 requires that ON be coded.] The line-sequential format I-O-control entry The RERUN clause in the sort-merge I-O-control entry DATA DIVISION LOCAL-STORAGE SECTION The GLOBAL clause in the linkage section Specifying level numbers that are lower than other level numbers at the same hierarchical level in a data description entry. [Standard COBOL 85 requires that all elementary or group items at the same level in the hierarchy be assigned identical level numbers.] Data categories internal floating-point, external floating-point, DBCS, and national File section data-name in the LABEL RECORDS clause, for specifying user labels RECORDING MODE clause Line-sequential format file description entry Sort/merge file description entry The following clauses: v BLOCK CONTAINS v LABEL RECORDS v VALUE OF v LINAGE v CODE-SET v WITH FOOTING v LINES AT BLOCK CONTAINS clause VALUE OF clause DATA RECORDS clause LINAGE clause Data Description Entry BLANK WHEN ZERO clause GLOBAL clause INDEXED BY phrase BLOCK CONTAINS 0 for QSAM files. [Standard COBOL 85 requires that at least 1 CHARACTER or RECORD be specified in the BLOCK CONTAINS clause.] The lack of VALUE clause effect on execution when specified under an SD Optionality of an 01 record description entry for a specified data-name. [Standard COBOL 85 requires that an 01 record with the same data-name be specified.] Specifying LINAGE for files opened in EXTEND mode DATE-FORMAT clause Alternative spellings ZEROS and ZEROES for ZERO Specifying GLOBAL in the linkage section Nonunique unreferenced index names
537
Table 54. IBM extension language elements (continued) Language area OCCURS clause Extension elements Omission of integer-1 TO for variable-length tables Complex OCCURS DEPENDING ON. [Standard COBOL 85 requires that an entry containing OCCURS DEPENDING ON be followed only by subordinate entries, and that no entry containing OCCURS DEPENDING ON be subordinate to an entry containing OCCURS DEPENDING ON.] Implicit qualification of a key specified without qualifiers when the key name is not unique Reference to a table through indexing when no INDEXED BY phrase is specified Keys of usages COMPUTATIONAL-1, COMPUTATIONAL-2, COMPUTATIONAL-3, COMPUTATIONAL-4, and COMPUTATIONAL-5 in the ASCENDING/DESCENDING KEY phrase Acceptance of nonunique index-names that are not referenced PICTURE clause A picture character-string containing 31 to 50 characters. [Standard COBOL 85 allows a maximum of 30 characters.] Picture symbols G and N Picture symbol E and the external floating-point picture format Coding a trailing comma insertion character or trailing period insertion character immediately followed by a separator comma or separator semicolon in a PICTURE clause that is not the last clause of a data description entry. [Standard COBOL 85 requires that a PICTURE clause containing a picture ending with a comma or period be the last clause in the entry and that it be followed immediately by a separator period.] Selecting a currency sign and currency symbol with the CURRENCY compiler option Case-sensitive currency symbols The maximum of 31 digits for numeric items of usages DISPLAY and PACKED-DECIMAL and for numeric-edited items of USAGE DISPLAY The effect of the TRUNC compiler option on the value of data items described with a usage of BINARY, COMPUTATIONAL, or COMPUTATIONAL-4 REDEFINES clause SYNCHRONIZED clause Specifying REDEFINES of a redefined data item Specifying SYNCHRONIZED for a level 01 entry
538
Language Reference
Table 54. IBM extension language elements (continued) Language area USAGE clause Extension elements The phrases: v NATIVE v COMP-1 and COMPUTATIONAL-1 v COMP-2 and COMPUTATIONAL-2 v COMP-3 and COMPUTATIONAL-3 v COMP-4 and COMPUTATIONAL-4 v COMP-5 and COMPUTATIONAL-5 v DISPLAY-1 v OBJECT REFERENCE v NATIONAL v POINTER v PROCEDURE-POINTER v FUNCTION-POINTER Use of the SYNCHRONIZED clause for items of usage INDEX VALUE clause for condition-name entries A VALUE clause in file and linkage sections in other than condition-name entries A VALUE clause for a condition-name entry on a group that has usages other than DISPLAY VALUE IS NULL and VALUE IS NULLS Procedure division Omission of a section-name Omission of a paragraph-name when a section-name is omitted A method, factory, or object procedure division Referencing data items in the linkage section without a USING phrase in the procedure division header (when those data-names are the operand of an ADDRESS OF phrase or ADDRESS OF special register) The statements: v ENTRY v EXIT METHOD v GOBACK v INVOKE v XML PARSE
|
Procedure division header
v XML GENERATE The BY VALUE phrase The RETURNING phrase Specifying a data item in the USING phrase when the data item has a REDEFINES clause in its description Specifying multiple instances of a given data item in the USING phrase The formats for method, factory, and object definitions
539
Table 54. IBM extension language elements (continued) Language area Declarative Procedures Extension elements The LABEL declarative Performing a nondeclarative procedure from a declarative procedure Referencing a declarative procedure or nondeclarative procedure in a GO TO statement from a declarative procedure. [Standard COBOL 85 specifies that a declarative procedure must not reference a nondeclarative procedure. A reference to a declarative procedure from either another declarative procedure or a nondeclarative procedure is allowed only with a PERFORM statement.] Executing an active declarative Procedures Specifying priority number as a positive signed numeric literal. [Standard COBOL 85 requires an unsigned integer.] Omitting the section-header after the declaratives or when there are no declaratives. [Standard COBOL 85 requires a section-header following the DECLARATIVES. syntax and following the END DECLARATIVES. syntax.] Omitting an initial paragraph-name if there are no declaratives. [Standard COBOL 85 requires a paragraph-name in the following circumstances: v After the USE statement if there are statements in the declarative procedure v Following a section header outside declarative procedures v Before any procedural statement if there are no declaratives and Standard COBOL 85 requires that procedural statements be within a paragraph.] Specifying paragraphs that are not contained within a section, even if some paragraphs are so contained. [Standard COBOL 85 requires that paragraphs be within a section except when there are no declaratives. Standard COBOL 85 requires that either all paragraphs be in sections or that none be.] Conditional expressions DBCS and KANJI class conditions Specifying data items of usage COMPUTATIONAL-3 or usage PACKED-DECIMAL in a NUMERIC class test Relation condition Enclosing an alphanumeric, DBCS, or national literal in parentheses The data-pointer format, the procedure-pointer and function-pointer format, and the object-reference format Comparison of an index-name with an arithmetic expression Use of parentheses within abbreviated combined relation conditions CORRESPONDING phrase INVALID KEY phrase ACCEPT statement Specifying an identifier that is subordinate to a filler item Omission of both the INVALID KEY phrase and an applicable EXCEPTION/ERROR procedure. [Standard COBOL 85 requires at least one of them.] The environment-name operand of the FROM phrase The DATE YYYYMMDD phrase The DAY YYYYDDD phrase ADD statement A composite of operands greater than 18 digits
540
Language Reference
Table 54. IBM extension language elements (continued) Language area CALL statement Extension elements The procedure-pointer and function-pointer operands for identifying the program to be called The following phrases: v ADDRESS OF v LENGTH OF v OMITTED v BY VALUE v RETURNING Specifying a file-name as an argument Specifying the called program-name in an alphabetic or zoned-decimal data item
Specifying an argument defined as a subordinate group item. [Standard COBOL 85 requires that arguments be an elementary data item or a group item defined with level 01.] CANCEL statement Specifying the name of the program to be canceled in an alphabetic or zoned-decimal data item The effect of the PGMNAME compiler option on the name of the program to be canceled CLOSE statement WITH NO REWIND phrase The line-sequential format COMPUTE statement DISPLAY statement The use of the word EQUAL in place of the equal sign (=) The environment-name operand of the UPON phrase Displaying signed numeric literals and noninteger numeric literals DIVIDE statement EXIT statement EXIT PROGRAM statement A composite of operands greater than 18 digits Specifying EXIT in a sentence that has statements after the EXIT statement. [Standard COBOL 85 requires that EXIT be specified in a sentence by itself.] Specifying EXIT PROGRAM before the last statement in a sequence of imperative statements. [Standard COBOL 85 requires that the EXIT PROGRAM statement be specified as the last statement in a sequence of imperative statements.] Coding the unconditional format before the last statement in a sequence of imperative statements. [Standard COBOL 85 requires that an unconditional GO TO be coded: v Only in a single-statement paragraph if no procedure-name is specified v Otherwise, as the last statement of a sentence.] The MORE-LABELS format IF statement INITIALIZE statement The use of END-IF with the NEXT SENTENCE phrase. [Standard COBOL 85 disallows use of END-IF with NEXT SENTENCE.] DBCS, EGCS, and NATIONAL in the REPLACING phrase Initializing a data item that contains the DEPENDING phrase of the OCCURS clause MERGE statement MULTIPLY statement OPEN statement Specifying file-names in a SAME clause A composite of operands greater than 18 digits The line-sequential format Specifying the EXTEND phrase for files that have a LINAGE clause
GO TO statement
541
Table 54. IBM extension language elements (continued) Language area PERFORM statement Extension elements An empty in-line PERFORM statement A common exit for two or more active PERFORMS READ statement Omission of both the AT END phrase and an applicable declarative procedure Omission of both the INVALID KEY phrase and an applicable declarative procedure Read into an item that is neither a group item nor an elementary alphanumeric item RETURN statement REWRITE statement Return into an item that is neither a group item nor an elementary alphanumeric item Omission of both the INVALID KEY phrase and an applicable declarative procedure Rewriting a record with a different number of character positions than the number of character positions in the record being rewritten SEARCH statement Specifying END SEARCH with NEXT SENTENCE Omission of both the NEXT SENTENCE phrase and imperative statements in the binary search format SET statement The data-pointer format The procedure-pointer and function-pointer format The object reference format SORT statement START statement Specifying GIVING file-names in the SAME clause Omission of both the INVALID KEY phrase and an applicable exception procedure Use of a key of a category other than alphanumeric STOP statement Specifying a noninteger fixed-point literal or a signed numeric integer or noninteger fixed-point literal Coding STOP as other than the last statement in a sentence STRING statement SUBTRACT statement UNSTRING statement WRITE statement Reference modification of the data item specified in the INTO phrase A composite of operands greater than 18 digits Reference modification of the sending field INVALID KEY and NOT ON INVALID KEY phrases The line-sequential format For a relative file, writing a different number of character positions than the number of character positions in the record being replaced Specifying both the ADVANCING PAGE and END-OF-PAGE phrases in a single WRITE statement The effect of the ADV compiler option on the length of the record written to a file Using WRITE ADVANCING with stacker selection for a card punch file For a relative or indexed file, omission of both the INVALID KEY phrase and an applicable exception procedure
542
Language Reference
Table 54. IBM extension language elements (continued) Language area Intrinsic functions Extension elements The effect of the DATEPROC and INTDATE compiler options on the DATE-OF-INTEGER and DAY-OF-INTEGER functions The following functions: v DATE-TO-YYYYMMDD v DATEVAL v DAY-TO-YYYYDDD v DISPLAY-OF v NATIONAL-OF v UNDATE v YEAR-TO-YYYY v YEARWINDOW FACTORIAL function INTEGER-OF-DATE function INTEGER-OF-DAY function LENGTH function NUMVAL function NUMVAL-C function Compiler-directing statements The effect of the ARITH(EXTEND) compiler option on the range of values permitted in the argument The effect of the INTDATE compiler option on the starting date for the function The effect of the INTDATE compiler option on the starting date for the function Specifying a pointer, the ADDRESS OF special register, or the LENGTH OF special register as an argument to the function The effect of the ARITH(EXTEND) compiler option on the maximum number of digits allowed in the argument The effect of the ARITH(EXTEND) compiler option on the maximum number of digits allowed in the argument The following statements: v BASIS v CBL(PROCESS) v *CONTROL and *CBL v DELETE v EJECT v INSERT v READY or RESET TRACE v SERVICE LABEL v SERVICE RELOAD v SKIP1, SKIP2, and SKIP3 v TITLE COPY statement The optionality of the syntax OF library-name for specifying a text-name qualifier Literals for specifying text-name and library-name SUPPRESS phrase Nested COPY statements Hyphen as the first or last character in the word form of REPLACING operands The use of any character (other than a COBOL separator) in the word form of REPLACING operands. [Standard COBOL 85 accepts only the characters used in formation of user-defined words.] USE statement The LABEL declarative format
543
544
Language Reference
Appendix B. Compiler limits

The following table lists the compiler limits for Enterprise COBOL programs.
Table 55. Compiler limits Language element Compiler limit 30 bytes 999,999 lines 4,194,3031 4,194,303 bytes1 1536 No limit No limit 32,767 bytes
| |
Maximum length of user-defined words (for example, data-name, file-name, class-name) Size of program Number of literals Total length of literals Reserved word table entries COPY REPLACING . . . BY . . . (items per COPY statement) Number of COPY libraries Block size of COPY library Identification division Environment division Configuration section Special-names paragraph mnemonic-name IS UPSI-n . . . (switches) alphabet-name IS . . . Literal THRU . . . or ALSO . . . Input-Output section File-control paragraph SELECT file-name . . . ASSIGN system-name . . . ALTERNATE RECORD KEY data-name . . . RECORD KEY length RESERVE integer (buffers) I-O-control paragraph RERUN ON system-name . . . RERUN integer RECORDS SAME RECORD AREA SAME RECORD AREA FOR file-name . . . SAME SORT/MERGE AREA MULTIPLE FILE file-name . . . Data division 77 data-names 01-49 data-names
18 0-7 No limit 256
A maximum of 65,535 file names can be assigned external names No limit 253 No limit3 2554
32,767 16,777,215 255 255 No limit2 No limit2
16,777,215 bytes 16,777,215 bytes
545
Table 55. Compiler limits (continued) Language element Total 01 + 77 (data items) 88 condition-names . . . VALUE literal . . . 66 RENAMES . . . PICTURE clause, number of characters in character-string PICTURE clause, numeric item digit positions Compiler limit No limit No limit No limit No limit 50 If the ARITH(COMPAT) compiler option is in effect: 18 If the ARITH(EXTEND) compiler option is in effect: 31 PICTURE clause, numeric-edited character positions Picture symbol replication ( ) Picture symbol replication (editing) Picture symbol replication ( ), DBCS items Picture symbol replication ( ), national items Group item size: file section Elementary item size VALUE initialization (total length of all value literals) OCCURS integer Total number of ODOs Table size Table element size ASCENDING or DESCENDING KEY . . . (per OCCURS clause) Total length of keys (per OCCURS clause) INDEXED BY . . . (index names per OCCURS clause) Total number of indexes (index names) per class or program Size of relative index File section FD file-name . . . LABEL data-name . . . (if no optional clauses) Label record length DATA RECORD data-name . . . BLOCK CONTAINS integer RECORD CONTAINS integer Item length LINAGE clause values SD file-name . . . DATA RECORD data-name . . . Sort record length Working-storage section Items without the external attribute 134,217,727 bytes 65,535 255 80 bytes No limit2 2,147,483,6478 1,048,5755 1,048,575 bytes5 99,999,999 65,535 No limit2 32,751 bytes 249 16,777,215 32,767 8,388,607 8,388,607 1,048,575 bytes 16,777,215 bytes 16,777,215 bytes 16,777,215 4,194,3031 16,777,215 bytes 8,388,607 bytes 12 KEYS 256 bytes 12 65,535 32,765
546
Language Reference
Table 55. Compiler limits (continued) Language element Items with the external attribute Procedure division Procedure and constant area Procedure division USING identifier . . . Procedure-names Subscripted data-names per statement Verbs per line (TEST) ACCEPT statement, record length on input device ADD identifier . . . ALTER procedure-name-1 TO procedure-name-2 . . . CALL . . . BY CONTENT identifier CALL identifier or literal USING identifier or literal . . . CALL literal . . . Active programs in a run unit Number of names called (DYN option) CANCEL identifier or literal . . . CLOSE file-name . . . COMPUTE identifier . . . DISPLAY identifier or literal . . . DIVIDE identifier . . . ENTRY USING identifier or literal . . . EVALUATE . . . subjects EVALUATE . . . WHEN clauses GO procedure-name . . . DEPENDING INSPECT TALLYING and REPLACING clauses MERGE file-name ASC or DES KEY . . . Total merge key length MERGE USING file-name . . . MOVE identifier or literal TO identifier . . . MULTIPLY identifier . . . OPEN file-name . . . PERFORM SEARCH . . . WHEN . . . SET index or identifier . . . TO SET index . . . UP/DOWN SORT file-name ASC or DES KEY Total sort key length SORT USING file-name . . . STRING identifier . . . STRING DELIMITED identifier or literal . . . 4,194,303 bytes1 32,767 1,048,5751 32,767 7 32,760 No limit 4,194,3031 2,147,483,647 bytes 16,380 4,194,3031 32,767 No limit No limit No limit No limit No limit No limit No limit 64 256 255 No limit No limit 4,092 bytes6 167 No limit No limit No limit 4,194,303 No limit No limit No limit No limit 4,092 bytes6 167 No limit No limit
Appendix B. Compiler limits
Compiler limit 134,217,727 bytes
547
Table 55. Compiler limits (continued) Language element UNSTRING DELIMITED identifier or literal OR identifier or literal . . . UNSTRING INTO identifier or literal . . . USE . . . ON file-name . . . Compiler limit 255 No limit No limit
1. Items included in 4,194,303 byte limit for procedure plus constant area. 2. Syntax checked, but has no effect on the execution of the program; there is no limit. 3. No compiler limit, but VSAM limits it to 255 bytes. 4. QSAM. 5. Compiler limit shown, but QSAM limits it to 32,767 bytes. 6. For QSAM and VSAM, the limit is 4088 bytes if EQUALS is coded on the OPTION control statement. 7. SORT limit for QSAM and VSAM. 8. Requires large block interface (LBI) support provided by OS/390 DFSMS Version 2 Release 10.0 or later. On OS/390 systems with earlier releases of DFSMS, the limit is 32,767 bytes. For more information about using large block sizes, see Enterprise COBOL Programming Guide.
548
Language Reference
Appendix C. EBCDIC and ASCII collating sequences

The ascending collating sequences for both the single-byte EBCDIC (Extended Binary Coded Decimal Interchange Code) and single-byte ASCII (American National Standard Code for Information Interchange) character sets are shown in this appendix. The collating sequence is defined by the ordinal number of characters in the character set, relative to 1. The symbols and associated meanings shown for the EBCDIC collating sequence are those defined in the EBCDIC code page defined with CCSID 1140. Symbols and meanings can vary for other EBCDIC code pages, but the collating sequence is unchanged.
EBCDIC collating sequence

The following table presents the collating sequence for single-byte EBCDIC code page 1140. Ellipsis (. . .) indicates omission of a range of ordinal numbers between predecessor and successor ordinal numbers.
Table 56. EBCDIC collating sequence Ordinal number ... 65 ... 75 76 77 78 79 80 81 ... 91 92 93 94 95 96 97 98 ... 108 , Comma 107 6B / ! $ * ) ; Exclamation point Dollar sign Asterisk Right parenthesis Semicolon Logical NOT Minus, hyphen Slash 90 91 92 93 94 95 96 97 5A 5B 5C 5D 5E 5F 60 61 . < ( + | & Cent sign Period, decimal point Less than sign Left parenthesis Plus sign Vertical bar, logical OR Ampersand 74 75 76 77 78 79 80 4A 4B 4C 4D 4E 4F 50 Space 64 40 Symbol Meaning Decimal representation Hex representation
549
Table 56. EBCDIC collating sequence (continued) Ordinal number 109 110 111 112 ... 122 123 124 125 126 127 128 ... 130 131 132 133 134 135 136 137 138 ... 146 147 148 149 150 151 152 153 154 ... 160 ... 162 163 164 ~ s t Tilde 161 162 163 A1 A2 A3 Euro currency sign 159 9F j k l m n o p q r 145 146 147 148 149 150 151 152 153 91 92 93 94 95 96 97 98 99 a b c d e f g h i 129 130 131 132 133 134 135 136 137 81 82 83 84 85 86 87 88 89 ` : # @ = Grave accent Colon Number sign, pound sign At sign Apostrophe, prime sign Equal sign Quotation marks 121 122 123 124 125 126 127 79 7A 7B 7C 7D 7E 7F Symbol % _ > ? Meaning Percent sign Underscore Greater than sign Question mark Decimal representation 108 109 110 111 Hex representation 6C 6D 6E 6F
550
Language Reference
Table 56. EBCDIC collating sequence (continued) Ordinal number 165 166 167 168 169 170 ... 177 ... 188 189 ... 193 194 195 196 197 198 199 200 201 202 ... 209 210 211 212 213 214 215 216 217 218 ... 225 ... 227 228 229 S T U 226 227 228 E2 E3 E4 \ Backslash 224 E0 } J K L M N O P Q R Closing brace 208 209 210 211 212 213 214 215 216 217 D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 { A B C D E F G H I Opening brace 192 193 194 195 196 197 198 199 200 201 C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 [ ] Opening square bracket Closing square bracket 187 188 BA BB ^ Caret 176 B0 Symbol u v w x y z Meaning Decimal representation 164 165 166 167 168 169 Hex representation A4 A5 A6 A7 A8 A9
551
Table 56. EBCDIC collating sequence (continued) Ordinal number 230 231 232 233 234 ... 241 242 243 244 245 246 247 248 249 250 ... 0 1 2 3 4 5 6 7 8 9 240 241 242 243 244 245 246 247 248 249 F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 Symbol V W X Y Z Meaning Decimal representation 229 230 231 232 233 Hex representation E5 E6 E7 E8 E9
US English ASCII code page

The following table presents the collating sequence for the US English ASCII code page. The collating sequence is the order in which characters are defined in ANSI INCITS 4, the 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII), and in the International Reference Version of ISO/IEC 646, 7-Bit Coded Character Set for Information Interchange. Ellipsis (. . .) indicates omission of a range of ordinal numbers between predecessor and successor ordinal numbers.
Table 57. ASCII collating sequence Ordinal number 1 ... 33 34 35 36 37 38 39 40 ! # $ % & Space Exclamation point Quotation mark Number sign Dollar sign Percent sign Ampersand Apostrophe, prime sign 32 33 34 35 36 37 38 39 20 21 22 23 24 25 26 27 Symbol Meaning Null Decimal representation 0 Hex representation 0
552
Language Reference
Table 57. ASCII collating sequence (continued) Ordinal number 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 Symbol ( ) * + , . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N Colon Semicolon Less than sign Equal sign Greater than sign Question mark Commercial At sign Meaning Opening parenthesis Closing parenthesis Asterisk Plus sign Comma Hyphen, minus Period, decimal point Slash, solidus Decimal representation 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 Hex representation 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E
553
Table 57. ASCII collating sequence (continued) Ordinal number 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 Symbol O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u Opening bracket Backslash, reverse solidus Closing bracket Caret Underscore Grave accent Meaning Decimal representation 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 Hex representation 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75
554
Language Reference
Table 57. ASCII collating sequence (continued) Ordinal number 119 120 121 122 123 124 125 126 127 Symbol v w x y z { | } ~ Opening brace Vertical bar Closing brace Tilde Meaning Decimal representation 118 119 120 121 122 123 124 125 126 Hex representation 76 77 78 79 7A 7B 7C 7D 7E
555
556
Language Reference
Appendix D. Source language debugging

COBOL language elements that implement the debugging feature are: v Debugging lines v Debugging sections v DEBUG-ITEM special register v Compile-time switch (WITH DEBUGGING MODE clause) v Object-time switch
Coding debugging lines

A debugging line is a statement that is compiled only when the compile-time switch is activated. Debugging lines allow you, for example, to check the value of a data item at certain points in a procedure. To specify a debugging line in your program, code a D in column 7 (the indicator area). You can include successive debugging lines, but each must have a D in column 7. You cannot break character-strings across two lines. All your debugging lines must be written so that the program is syntactically correct, whether the debugging lines are compiled or treated as comments. You can code debugging lines anywhere in your program after the OBJECT-COMPUTER paragraph. A debugging line that contains only spaces in Area A and in Area B is treated as a blank line.
Coding debugging sections

Debugging sections are permitted only in the outermost program; they are not valid in nested programs. Debugging sections are never triggered by procedures contained in nested programs. Debugging sections are declarative procedures. Declarative procedures are described under USE statement on page 524. A debugging section can be called, for example, by a PERFORM statement that causes repeated execution of a procedure. Any associated procedure-name debugging declarative section is executed once for each repetition. A debugging section executes only if both the compile-time switch and the object-time switch are activated. The debug feature recognizes each separate occurrence of an imperative statement within an imperative statement as the beginning of a separate statement. You cannot refer to a procedure defined within a debugging section from a statement outside of the debugging section. References to the DEBUG-ITEM special register can be made only from within a debugging declarative procedure.
557
DEBUG-ITEM special register

For information about the DEBUG-ITEM special register, see DEBUG-ITEM on page 14.
Activate compile-time switch

The compile-time switch activates the debugging lines and sections. To place the compile-time switch in effect, specify WITH DEBUGGING MODE in the SOURCE COMPUTER paragraph of the configuration section.
Format
SOURCE-COMPUTER. computer-name DEBUGGING MODE WITH .
WITH DEBUGGING MODE When WITH DEBUGGING MODE is specified, all debugging sections and debugging lines are compiled. When WITH DEBUGGING MODE is omitted, all debugging sections and debugging lines are treated as comments. Usage note: If you include a COPY statement as a debugging line, the letter D must appear on the first line of the COPY statement. The compiler treats the copied text as the debugging line or lines. The COPY statement is executed, regardless of whether WITH DEBUGGING MODE is specified or not.
Activate object-time switch

The object-time switch is set when the run-time option DEBUG or NODEBUG is specified. (NODEBUG is the default supplied by IBM.) For details on the format, see the Language Environment Programming Guide. The USE FOR DEBUGGING declarative procedures are activated when DEBUG is in effect and inhibited when NODEBUG is in effect. The debugging lines (lines with D or d in column 7) are not affected by the DEBUG or NODEBUG option; they are always active if they have been compiled. When WITH DEBUGGING MODE is not specified in the SOURCE-COMPUTER paragraph, the object-time switch has no effect on execution of the object program. You do not have to recompile the source unit to activate or deactivate the object-time switch.
558
Language Reference

| The following table identifies words that are reserved in Enterprise COBOL and words that you should avoid because they might be reserved in a future release of Enterprise COBOL. v Words marked X under Enterprise COBOL are reserved for function implemented in Enterprise COBOL. If used as user-defined names, these words are flagged with an S-level message. v Words marked X under Standard only are Standard COBOL 85 reserved words for function not implemented in Enterprise COBOL. (Some of the function is implemented in the Report Writer Precompiler.) Use of these words as user-defined names is flagged with an S-level message. v Words marked X under Potential reserved words are words that might be reserved in a future release of Enterprise COBOL. IBM recommends that you not use these words as user-defined names. Use of these words as user-defined names is flagged with an I-level message. This column includes words reserved in Standard COBOL 2002. The default reserved word table is shown below. You can select a different reserved word table by using the WORD compiler option. For details, see the Enterprise COBOL Programming Guide.
Table 58. Reserved words Reserved in Enterprise COBOL X X X X X X X X X X X X X X X X X X X Potential Standard only reserved words
| | | |
Word ACCEPT ACCESS ACTIVE-CLASS ADD ADDRESS ADVANCING AFTER ALIGNED ALL ALLOCATE ALPHABET ALPHABETIC ALPHABETIC-LOWER ALPHABETIC-UPPER ALPHANUMERIC ALPHANUMERIC-EDITED ALSO ALTER ALTERNATE
559
Table 58. Reserved words (continued) Reserved in Enterprise COBOL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Potential Standard only reserved words
Word AND ANY ANYCASE APPLY ARE AREA AREAS AS ASCENDING ASSIGN AT AUTHOR B-AND B-NOT B-OR B-XOR BASED BASIS BEFORE BEGINNING BINARY BINARY-CHAR BINARY-DOUBLE BINARY-LONG BINARY-SHORT BIT BLANK BLOCK BOOLEAN BOTTOM BY CALL CANCEL CBL CD CF CH CHARACTER
560
Language Reference
Word CHARACTERS CLASS CLASS-ID CLOCK-UNITS CLOSE COBOL CODE CODE-SET COL COLLATING COLS COLUMN COLUMNS COM-REG COMMA COMMON COMMUNICATION COMP COMP-1 COMP-2 COMP-3 COMP-4 COMP-5 COMPUTATIONAL COMPUTATIONAL-1 COMPUTATIONAL-2 COMPUTATIONAL-3 COMPUTATIONAL-4 COMPUTATIONAL-5 COMPUTE CONDITION CONFIGURATION CONSTANT CONTAINS CONTENT CONTINUE CONTROL CONTROLS
561
Word CONVERTING COPY CORR CORRESPONDING COUNT CRT CURRENCY CURSOR DATA DATA-POINTER DATE DATE-COMPILED DATE-WRITTEN DAY DAY-OF-WEEK DBCS DE DEBUG-CONTENTS DEBUG-ITEM DEBUG-LINE DEBUG-NAME DEBUG-SUB-1 DEBUG-SUB-2 DEBUG-SUB-3 DEBUGGING DECIMAL-POINT DECLARATIVES DEFAULT DELETE DELIMITED DELIMITER DEPENDING DESCENDING DESTINATION DETAIL DISABLE DISPLAY DISPLAY-1
562
Language Reference
Word DIVIDE DIVISION DOWN DUPLICATES DYNAMIC EC EGCS EGI EJECT ELSE EMI ENABLE END END-ACCEPT END-ADD END-CALL END-COMPUTE END-DELETE END-DISPLAY END-DIVIDE END-EVALUATE END-EXEC END-IF END-INVOKE END-MULTIPLY END-OF-PAGE END-PERFORM END-READ END-RECEIVE END-RETURN END-REWRITE END-SEARCH END-START END-STRING END-SUBTRACT END-UNSTRING END-WRITE END-XML
563
Word ENDING ENTER ENTRY ENVIRONMENT EO EOP EQUAL ERROR ESI EVALUATE EVERY EXCEPTION EXCEPTION-OBJECT EXEC EXECUTE EXIT EXTEND EXTERNAL FACTORY FALSE FD FILE FILE-CONTROL FILLER FINAL FIRST FLOAT-EXTENDED FLOAT-LONG FLOAT-SHORT FOOTING FOR FORMAT FREE FROM FUNCTION FUNCTION-ID FUNCTION-POINTER
GENERATE
564
Language Reference
Table 58. Reserved words (continued) Reserved in Enterprise COBOL Potential Standard only reserved words X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Word GET GIVING GLOBAL GO GOBACK GREATER GROUP GROUP-USAGE HEADING HIGH-VALUE HIGH-VALUES I-O I-O-CONTROL ID IDENTIFICATION IF IN INDEX INDEXED INDICATE INHERITS INITIAL INITIALIZE INITIATE INPUT INPUT-OUTPUT INSERT INSPECT INSTALLATION INTERFACE INTERFACE-ID INTO INVALID INVOKE IS JNIENVPTR JUST JUSTIFIED
565
Word KANJI KEY LABEL LAST LEADING LEFT LENGTH LESS LIMIT LIMITS LINAGE LINAGE-COUNTER LINE LINE-COUNTER LINES LINKAGE LOCAL-STORAGE LOCALE LOCK LOW-VALUE LOW-VALUES MEMORY MERGE MESSAGE METHOD METHOD-ID MINUS MODE MODULES MORE-LABELS MOVE MULTIPLE MULTIPLY NATIONAL NATIONAL-EDITED NATIVE NEGATIVE NESTED
566
Language Reference
Word NEXT NO NOT NULL NULLS NUMBER NUMERIC NUMERIC-EDITED OBJECT OBJECT-COMPUTER OBJECT-REFERENCE OCCURS OF OFF OMITTED ON OPEN OPTIONAL OPTIONS OR ORDER ORGANIZATION OTHER OUTPUT OVERFLOW OVERRIDE PACKED-DECIMAL PADDING PAGE PAGE-COUNTER PASSWORD PERFORM PF PH PIC PICTURE PLUS POINTER
567
Word POSITION POSITIVE PRESENT PRINTING PROCEDURE PROCEDURE-POINTER PROCEDURES PROCEED PROCESSING PROGRAM PROGRAM-ID PROGRAM-POINTER PROPERTY PROTOTYPE PURGE QUEUE QUOTE QUOTES RAISE RAISING RANDOM RD READ READY RECEIVE RECORD RECORDING RECORDS RECURSIVE REDEFINES REEL REFERENCE REFERENCES RELATIVE RELEASE RELOAD REMAINDER REMOVAL
568
Language Reference
Word RENAMES REPLACE REPLACING REPORT REPORTING REPORTS REPOSITORY RERUN RESERVE RESET RESUME RETRY RETURN RETURN-CODE RETURNING REVERSED REWIND REWRITE RF RH RIGHT ROUNDED RUN SAME SCREEN SD SEARCH SECTION SECURITY SEGMENT SEGMENT-LIMIT SELECT SELF SEND SENTENCE SEPARATE SEQUENCE SEQUENTIAL
569
Word SERVICE SET SHARING SHIFT-IN SHIFT-OUT SIGN SIZE SKIP1 SKIP2 SKIP3 SORT SORT-CONTROL SORT-CORE-SIZE SORT-FILE-SIZE SORT-MERGE SORT-MESSAGE SORT-MODE-SIZE SORT-RETURN SOURCE SOURCE-COMPUTER SOURCES SPACE SPACES SPECIAL-NAMES SQL STANDARD STANDARD-1 STANDARD-2 START STATUS STOP STRING SUB-QUEUE-1 SUB-QUEUE-2 SUB-QUEUE-3 SUBTRACT SUM SUPER
570
Language Reference
Word SUPPRESS SYMBOLIC SYNC SYNCHRONIZED SYSTEM-DEFAULT TABLE TALLY TALLYING TAPE TERMINAL TERMINATE TEST TEXT THAN THEN THROUGH THRU TIME TIMES TITLE TO TOP TRACE TRAILING TRUE TYPE TYPEDEF UNIT UNIVERSAL UNLOCK UNSTRING UNTIL UP UPON USAGE USE USER-DEFAULT USING
571
Table 58. Reserved words (continued) Reserved in Enterprise COBOL Potential Standard only reserved words X X X X X X X X X X X X X X X X X X X X X X
Word VAL-STATUS VALID VALIDATE VALIDATE-STATUS VALUE VALUES VARYING WHEN WHEN-COMPILED WITH WORDS WORKING-STORAGE WRITE WRITE-ONLY XML XML-CODE XML-EVENT XML-NTEXT XML-TEXT ZERO ZEROES ZEROS
572
Language Reference
Appendix F. ASCII considerations

The compiler supports the American National Standard Code for Information Interchange (ASCII). Thus, the programmer can create and process tape files recorded in accordance with the following standards: v American National Standard Code for Information Interchange, X3.4-1977 v American National Standard Magnetic Tape Labels for Information Interchange, X3.27-1978 v American National Standard Recorded Magnetic Tape for Information Interchange (800 CPI, NRZI), X3.22-1967 Single-byte ASCII-encoded tape files, when read into the system, are automatically translated in the buffers into single-byte EBCDIC. Internal manipulation of data is performed exactly as if the ASCII files were single-byte EBCDIC-encoded files. For an output file, the system translates the EBCDIC characters into single-byte ASCII in the buffers before writing the file on tape. Therefore, there are special considerations concerning ASCII-encoded files when they are processed in COBOL. This appendix also applies (with appropriate modifications) to the International Reference Version of the ISO 7-bit code defined in International Standard 646, 7-Bit Coded Character Set for Information Processing Interchange (ISCII). The ISCII code set differs from ASCII only in the graphic representation of two code points: v Ordinal number 37, which is a dollar sign in ASCII, but a lozenge in ISCII v Ordinal number 127, which is a tilde (~) in ASCII, but an overline (or optionally a tilde) in ISCII. The following paragraphs discuss the special considerations concerning ASCII-encoded (or ISCII-encoded) files. The information given for STANDARD-1 also applies to STANDARD-2 except where otherwise specified.
Environment division
In the environment division, the OBJECT-COMPUTER, SPECIAL-NAMES, and FILE-CONTROL paragraphs are affected by the use of ASCII-encoded files.
OBJECT-COMPUTER and SPECIAL-NAMES paragraphs

When at least one file in the program is an ASCII-encoded file, the alphabet-name clause of the SPECIAL-NAMES paragraph must be specified; the alphabet-name must be associated with STANDARD-1 or STANDARD-2 (for ASCII or ISCII collating sequence or CODE SET, respectively). When alphanumeric comparisons within the object program are to use the ASCII collating sequence, the PROGRAM COLLATING SEQUENCE clause of the OBJECT-COMPUTER paragraph must be specified; the alphabet-name used must also be specified as an alphabet-name in the SPECIAL-NAMES paragraph, and associated with STANDARD-1. For example:
Object-computer. IBM-zSeries Program collating sequence is ASCII-sequence. Special-names. Alphabet ASCII-sequence is standard-1.
573
When both clauses are specified, the ASCII collating sequence is used in this program to determine the truth value of the following alphanumeric comparisons: v Those explicitly specified in relation conditions v Those explicitly specified in condition-name conditions v Any alphanumeric sort or merge keys (unless the COLLATING SEQUENCE phrase is specified in the MERGE or SORT statement). When the PROGRAM COLLATING SEQUENCE clause is omitted, the EBCDIC collating sequence is used for such comparisons. The PROGRAM COLLATING SEQUENCE clause, in conjunction with the alphabet-name clause, can be used to specify EBCDIC alphanumeric comparisons for an ASCII-encoded tape file or ASCII alphanumeric comparisons for an EBCDIC-encoded tape file. The literal option of the alphabet-name clause can be used to process internal data in a collating sequence other than NATIVE or STANDARD-1.
FILE-CONTROL paragraph
For ASCII files, the ASSIGN clause assignment-name has the following format:
Format: QSAM file

name labelS-
The file must be a QSAM file assigned to a magnetic tape device. labelSname Documents the device and device class to which a file is assigned. If specified, it must end with a hyphen. The organization field. Optional for QSAM files, which always have sequential organization. A required one-character to eight-character field that specifies the external name for this file.
I-O-CONTROL paragraph
The assignment-name in a RERUN clause must not specify an ASCII-encoded file. ASCII-encoded files that contain checkpoint records cannot be processed.
Data division
In the data division, there are special considerations for the FD entry and for data description entries. For each logical file defined in the environment division, there must be a corresponding FD entry and level-01 record description entry in the file section of the data division.
574
Language Reference
FD EntryCODE-SET clause
The FD Entry for an ASCII-encoded file must contain a CODE-SET clause; the alphabet-name must be associated with STANDARD-1 (for the ASCII code set) in the SPECIAL-NAMES paragraph. For example:
Special-names. Alphabet ASCII-sequence is standard-1. ... FD ASCII-file label records standard Recording mode is f Code-set is ASCII-sequence.
Data description entries

For ASCII files, the following data description considerations apply: v PICTURE clause specifications are valid for the following categories of data: Alphabetic Alphanumeric Alphanumeric-edited Numeric Numeric-edited v For signed numeric items, the SIGN clause with the SEPARATE CHARACTER phrase must be specified. v For the USAGE clause, only the DISPLAY phrase is valid.
Procedure division
An ASCII-collated sort or merge operation can be specified in two ways: v Through the PROGRAM COLLATING SEQUENCE clause in the OBJECT-COMPUTER paragraph. In this case, the ASCII collating sequence is used for alphanumeric comparisons explicitly specified in relation conditions and condition-name conditions. v Through the COLLATING SEQUENCE phrase of the SORT or MERGE statement. In this case, only this sort or merge operation uses the ASCII collating sequence. In either case, alphabet-name must be associated with STANDARD-1 (for ASCII collating sequence) in the SPECIAL-NAMES paragraph. For this sort or merge operation, the COLLATING SEQUENCE phrase of the SORT or MERGE statement takes precedence over the PROGRAM COLLATING SEQUENCE clause in the OBJECT-COMPUTER paragraph. If both the PROGRAM COLLATING SEQUENCE clause and the COLLATING SEQUENCE phrase are omitted (or if the one in effect specifies an EBCDIC collating sequence), the sort or merge is performed using the EBCDIC collating sequence.
Appendix F. ASCII considerations
575
576
Language Reference
Appendix G. Industry specifications

Enterprise COBOL supports the following industry standards: Enterprise COBOL supports the following industry standards: v ISO COBOL standards ISO 1989:1985, Programming languages - COBOL ISO 1989:1985 is identical to ANSI INCITS 23-1985 (R2001), Programming Languages - COBOL . ISO/IEC 1989/AMD1:1992, Programming languages - COBOL: Intrinsic function module ISO/IEC 1989/AMD1:1992 is identical to ANSI INCITS 23a-1989 (R2001), Programming Languages - Intrinsic Function Module for COBOL . ISO/IEC 1989/AMD2:1994, Programming languages - Correction and clarification amendment for COBOL ISO/IEC 1989/AMD2:1994 is identical to ANSI INCITS 23b-1993 (R2001), Programming Language - Correction Amendment for COBOL. All required modules are supported at the highest level defined by the standard. The following optional modules of the standard are supported: Intrinsic Functions (1 ITR 0,1) Debug (1 DEB 0,2) Segmentation (2 SEG 0,2) The Report Writer optional module of the standard is supported with the optional IBM COBOL Report Writer Precompiler and Libraries (5798-DYR). The following optional modules of the standard are not supported: Communications Debug (2 DEB 0,2) v ANSI COBOL standards ANSI INCITS 23-1985 (R2001), Programming Languages - COBOL ANSI INCITS 23a-1989 (R2001), Programming Languages - Intrinsic Function Module for COBOL ANSI INCITS 23b-1993 (R2001), Programming Language - Correction Amendment for COBOL All required modules are supported at the highest level defined by the standard. The following optional modules of the standard are supported: - Intrinsic Functions (1 ITR 0,1) - Debug (1 DEB 0,2) - Segmentation (2 SEG 0,2) The following optional modules of the standard are not supported: Communications Debug (2 DEB 0,2) v International Reference Version of ISO/IEC 646, 7-Bit Coded Character Set for Information Interchange v The 7-bit coded character set defined in American National Standard X3.4-1977, Code for Information Interchange.
577
Enterprise COBOL has the following restrictions related to COBOL standards: v OPEN EXTEND is not supported for ASCII-encoded tapes (CODE-SET STANDARD-1 or STANDARD-2). v When division by zero occurs in an arithmetic expression and an ON SIZE ERROR phrase is not specified, processing abnormally terminates. See the Enterprise COBOL Programming Guide for specification of the compiler options and Language Environment run-time options that are required to support the above standards.
578
Language Reference
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
579
Programming interface information

This Language Reference documents intended Programming Interfaces that allow the customer to write programs to obtain the services of IBM Enterprise COBOL for z/OS.
Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, or other countries, or both: Advanced Function Printing AFP AIX BookManager CICS DB2 DFSMS DFSORT IBM IMS Language Environment MVS OS/390 Print Services Facility SOM WebSphere z/OS zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Unicode is a trademark of the Unicode Consortium. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product or service names may be the trademarks or service marks of others.
580
Language Reference
Glossary
The terms in this glossary are defined in accordance with their meaning in COBOL. These terms might or might not have the same meaning in other languages. This glossary includes terms and definitions from the following publications: v ANSI INCITS 23-1985, Programming Languages COBOL as amended by: ANSI INCITS 23a-1989, Programming Languages - Intrinsic Function Module for COBOL, ANSI INCITS 23b-1993, Programming Language - Correction Amendment for COBOL v ANSI INCITS 172-2002 American National Standard Dictionary of Information Technology. American National Standard definitions are preceded by an asterisk (*).
* alphanumeric function. A function whose value is composed of a string of one or more characters from the computers alphanumeric character set. alphanumeric literal. A literal that has an opening delimiter from the following set: v v v X v X v Z v Z The literal content can include any character in the character set of the computer. * alternate record key. A key, other than the prime record key, whose contents identify a record within an indexed file. ANSI (American National Standards Institute). An organization consisting of producers, consumers, and general interest groups, that establishes the procedures by which accredited organizations create and maintain voluntary industry standards in the United States. argument. (1) An identifier, a literal, an arithmetic expression, or a function-identifier that specifies a value to be used in the evaluation of a function. (2) An operand of the USING phrase of a CALL or INVOKE statement, used for passing values to a called program or an invoked method. * arithmetic expression. An identifier of a numeric elementary item, a numeric literal, such identifiers and literals separated by arithmetic operators, two arithmetic expressions separated by an arithmetic operator, or an arithmetic expression enclosed in parentheses. * arithmetic operation. The process caused by the execution of an arithmetic statement, or the evaluation of an arithmetic expression, that results in a mathematically correct solution to the arguments presented. * arithmetic operator. A single character, or a fixed two-character combination that belongs to the following set: Character + * / Meaning Addition Subtraction Multiplication Division
A
* abbreviated combined relation condition. The combined condition that results from the explicit omission of a common subject or a common subject and common relational operator in a consecutive sequence of relation conditions. abend. Abnormal termination of program. * access mode. The manner in which records are to be operated upon within a file. * actual decimal point. The physical representation, using the decimal point characters period (.) or comma (,), of the decimal point position in a data item. * alphabet-name. A user-defined word, defined in the SPECIAL-NAMES paragraph of the environment division, that names a specific character set or collating sequence, or both. * alphabetic character. A letter or a space character. alphanumeric character. Any character in the computers single-byte character set. alphanumeric character position. See character position. * alphanumeric data item. A data item described with both USAGE DISPLAY and a PICTURE character-string that includes the symbol X.
581
Character **
Meaning Exponentiation
single-byte EBCDIC. . The extended character set includes DBCS characters, which can be used in comments, literals, and user-defined words. Synonymous with COBOL character set in Standard COBOL 85. big-endian. The default format used by the mainframe to store binary data. In this format, the least significant digit is on the highest address. See also little-endian. binary item. A numeric data item represented in binary notation (on the base 2 numbering system). Binary items have a decimal equivalent consisting of the decimal digits 0 through 9, plus an operational sign. The leftmost bit of the item is the operational sign. binary search. A dichotomizing search in which, at each step of the search, the set of data elements is divided by two; some appropriate action is taken in the case of an odd number. * block. A physical unit of data that is normally composed of one or more logical records. For mass storage files, a block can contain a portion of a logical record. The size of a block has no direct relationship to the size of the file within which the block is contained or to the size of the logical records that are either contained within the block or that overlap the block. The term is synonymous with physical record. buffer. A portion of storage used to hold input or output data temporarily. byte. A string consisting of a certain number of bits, usually eight, treated as a unit. byte order mark (BOM). A Unicode character that can be used at the start of UTF-16 or UTF-32 text to indicate the byte order of subsequent text; the byte order can be either big endian or little endian.
* arithmetic statement. A statement that causes an arithmetic operation to be executed. The arithmetic statements are the ADD, COMPUTE, DIVIDE, MULTIPLY, and SUBTRACT statements. array. In Language Environment, an aggregate consisting of data objects, each of which can be uniquely referenced by subscripting. Roughly analogous to a COBOL table. * ascending key. A key, upon the values of which data is ordered starting with the lowest value of the key up to the highest value of the key, in accordance with the rules for comparing data items. ASCII. American National Standard Code for Information Interchange. A standard code, using a coded character set consisting of 7-bit coded characters (8 bits including parity check), used for information interchange between data processing systems, data communication systems, and associated equipment. The ASCII set consists of control characters and graphic characters. IBM has defined an extension to ASCII (characters 128-255). assignment-name. A name that identifies the organization of a COBOL file and the name by which it is known to the system. * assumed decimal point. A decimal point position that does not involve the existence of an actual character in a data item. The assumed decimal point has logical meaning with no physical representation. * AT END condition. A condition that exists in the following circumstances: v During the execution of a READ statement for a sequentially accessed file, when no next logical record exists in the file, or when the number of significant digits in the relative record number is larger than the size of the relative key data item, or when an optional input file is not present. v During the execution of a RETURN statement, when no next logical record exists for the associated sort or merge file. v During the execution of a SEARCH statement, when the search operation terminates without satisfying the condition specified in any of the associated WHEN phrases.
C
cataloged procedure. A set of job control statements placed in a partitioned data set called the procedure library (SYS1.PROCLIB). You can use cataloged procedures to save time and reduce errors coding JCL. CCSID. See coded character set identifier. century window. A 100-year interval within which any two-digit year is unique. There are several types of century window available to COBOL programmers: 1. For windowed date fields, it is specified by the YEARWINDOW compiler option. 2. For windowing intrinsic functions DATE-TO-YYYYMMDD, DAY-TO-YYYYDDD, and YEAR-TO-YYYY, it is specified by argument-2. 3. For Language Environment callable services, it is specified in CEESCEN.
B
basic character set. The basic set of characters used in writing words, character-strings, and separators of the language. The basic character set is implemented in
582
Language Reference
* character. The basic indivisible unit of the language. character encoding unit. A unit of data that corresponds to one code point in a coded character set. One or more character encoding units are used to represent a character in a coded character set. Also known as encoding unit. For usage NATIONAL, a character encoding unit corresponds to one 2-byte code point of UTF-16. For usage DISPLAY, a character encoding unit corresponds to a byte. For usage DISPLAY-1, a character encoding unit corresponds to a 2-byte code point in the DBCS character set. character position. The amount of physical storage or presentation space required for holding or presenting one character. The term applies to any class of character. For specific classes of characters, the following terms apply: v Alphanumeric character position, for characters represented in usage DISPLAY v DBCS character position, for DBCS characters represented in usage DISPLAY-1 v National character position, for characters represented in usage NATIONAL; synonymous with character encoding unit for UTF-16 character set. See basic character set and coded character set. * character-string. A sequence of contiguous characters that forms a COBOL word, a literal, a PICTURE character-string, or a comment-entry. Must be delimited by separators. checkpoint. A point at which information about the status of a job and the system can be recorded so that the job step can be restarted later. class (object-oriented). The entity that defines common behavior and implementation for zero, one, or more objects. The objects that share the same implementation are considered to be objects of the same class. * class condition. The proposition (for which a truth value can be determined) that the content of an item is wholly alphabetic, is wholly numeric, is wholly DBCS, is wholly Kanji, or consists exclusively of the characters that are listed in the definition of a class-name. class definition. The COBOL source unit that defines a class. class-name (object-oriented). The name of an object-oriented class definition. Class-name can refer to a COBOL class-name or a Java class-name. * class-name (of data). A user-defined word, defined in the SPECIAL-NAMES paragraph, that refers to the
proposition for which a truth value can be defined, that the content of a data item consists exclusively of those characters listed in the definition of the class-name. * clause. An ordered set of consecutive COBOL character-strings whose purpose is to specify an attribute of an entry. COBOL character set. See basic character set. * COBOL word. See word. code page. An assignment of graphic characters and control character meanings to the code points in a coded character set; for example, assignment of characters and meanings to the 256 code points in single-byte EBCDIC or ASCII. The terms coded character set and code page can be used interchangeably. code point. A unique bit pattern defined in a code page. Graphic symbols and control characters are assigned to code points. coded character set. A set of graphic characters and control characters along with their unambiguous assignment to specific code points (their encodings). EBCDIC is an example of a coded character set. A specific instance of encodings is called a code page. A code page specified by IBM is identified by a CCSID. coded character set identifier (CCSID). An IBM-defined number that identifies a specific code page. A CCSID is represented in 16 bits internally. * collating sequence. The sequence in which the characters that are acceptable to a computer are ordered for purposes of sorting, merging, comparing, and for processing indexed files sequentially. column. A byte position within a print line or within a reference format line. The columns are numbered from 1, by 1, starting at the leftmost position of the line and extending to the rightmost position of the line. A column holds one single-byte character. * combined condition. A condition that is the result of connecting two or more conditions with the AND or the OR logical operator. * comment-entry. An entry in the identification division that is used for documentation and has no effect on execution. * comment line. A source text line represented by an asterisk (*) in the indicator area of the line and any characters from the computers character set in area A and area B of that line. The comment line serves only for documentation. A special form of comment line represented by a forward slash (/) in the indicator area of the line and any characters from the computers character set in area A and area B of that line causes page ejection prior to printing the comment.
Glossary
583
* common program. A program that, despite being directly contained within another program, is permitted to be called from any program directly or indirectly contained in that other program. compatible date field. The meaning of the term compatible, when applied to date fields, depends on the COBOL division in which the usage occurs: v data division Two date fields are compatible if they have identical USAGE and meet at least one of the following conditions: They have the same date format. Both are windowed date fields, where one consists only of a windowed year, DATE FORMAT YY. Both are expanded date fields, where one consists only of an expanded year, DATE FORMAT YYYY. One has DATE FORMAT YYXXXX, the other, YYXX. One has DATE FORMAT YYYYXXXX, the other, YYYYXX. A windowed date field can be subordinate to an expanded date group data item. The two date fields are compatible if the subordinate date field has USAGE DISPLAY, starts two bytes after the start of the group expanded date field, and the two fields meet at least one of the following conditions: The subordinate date field has a DATE FORMAT pattern with the same number of Xs as the DATE FORMAT pattern of the group date field. The subordinate date field has DATE FORMAT YY. The group date field has DATE FORMAT YYYYXXXX and the subordinate date field has DATE FORMAT YYXX. v procedure division Two date fields are compatible if they have the same date format except for the year part, which can be windowed or expanded. For example, a windowed date field with DATE FORMAT YYXXX is compatible with: Another windowed date field with DATE FORMAT YYXXX An expanded date field with DATE FORMAT YYYYXXX * compile time. The time at which COBOL source code is translated by a COBOL compiler to a COBOL object program. compiler-directing statement. A statement that causes the compiler to take a specific action during compilation. The compiler-directing statements are COPY, REPLACE, and USE. * complex condition. A condition in which one or more logical operators act upon one or more
conditions. See also negated simple condition, combined condition, and negated combined condition. complex ODO. Certain forms of the OCCURS DEPENDING ON clause: v A variably located item or group: A data item described with an OCCURS clause with the DEPENDING ON phrase, followed by a nonsubordinate data item or group. v A variably located table: A data item described with an OCCURS clause with the DEPENDING ON phrase, followed by a nonsubordinate data item described with an OCCURS clause. v A table with variable-length elements: A data item described with an OCCURS clause, where a subordinate data item is described with an OCCURS clause with the DEPENDING ON phrase. v An index name for a table with variable-length elements. v An element of a table with variable-length elements. condition (exception). An exception that has been enabled, or recognized, by Language Environment and thus is eligible to activate user and language condition handlers. Any alteration to the normal programmed flow of an application. Conditions can be detected by the hardware or operating system and result in an interrupt. They can also be detected by language-specific generated code or language library code. * condition (expression). A status of data at run time for which a truth value can be determined. Where the term condition (condition-1, condition-2,...) appears in these language specifications in or in reference to condition (condition-1, condition-2,...) of a general format, it is a conditional expression consisting of either a simple condition optionally parenthesized, or a combined condition consisting of the syntactically correct combination of simple conditions, logical operators, and parentheses, for which a truth value can be determined. * conditional expression. A simple condition or a complex condition specified in an EVALUATE, IF, PERFORM, or SEARCH statement. See also simple condition and complex condition. * conditional phrase. A conditional phrase specifies the action to be taken upon determination of the truth value of a condition resulting from the execution of a conditional statement. * conditional statement. A statement specifying 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. * conditional variable. A data item one or more values of which has a condition-name assigned to it.
584
Language Reference
* condition-name. A user-defined word that assigns a name to a subset of values that a conditional variable is permitted to assume; or a user-defined word assigned to a status of an implementor defined switch or device. * condition-name condition. The proposition, for which a truth value can be determined, that the value of a conditional variable is a member of the set of values attributed to a condition-name associated with the conditional variable. * configuration section. A section of the environment division that describes overall specifications of source and object programs, method definitions, and class definitions. CONSOLE. A COBOL environment-name associated with the operator console. * contiguous items. Items that are described by consecutive entries in the data division, and that bear a definite hierarchic relationship to each other. copy file. A file or library member containing a sequence of code that is included in the source text at compile time using the COPY statement. The file can be created by the user, supplied by COBOL, or supplied by another product. * counter. A data item used for storing numbers or number representations in a manner that permits these numbers to be increased or decreased by the value of another number, or to be changed or reset to zero or to an arbitrary positive or negative value. cs. See currency symbol. currency sign value. A character-string that identifies the monetary units stored in a numeric-edited item. Some examples are $, USD, JPY, and EUR. A currency sign value can be defined by either the CURRENCY compiler option or the CURRENCY SIGN clause in the SPECIAL-NAMES paragraph of the environment division. If the CURRENCY SIGN clause is not specified and the NOCURRENCY compiler option is in effect, the dollar sign ($) is used as the default currency sign value. See also currency symbol. currency symbol. A character used in a PICTURE clause to indicate the position of a currency sign value in a numeric-edited item. A currency symbol can be defined by either the CURRENCY compiler option or by the CURRENCY SIGN clause in the SPECIAL-NAMES paragraph of the environment division. If the CURRENCY SIGN clause is not specified and the NOCURRENCY compiler option is in effect, the dollar sign ($) is used as the default currency sign value and currency symbol. Multiple currency symbols and currency sign values can be defined. See also currency sign value. * current record. In file processing, the record that is available in the record area associated with a file.
* current volume pointer. A conceptual entity that points to the current volume of a sequential file.
D
* data description entry. An entry in the data division composed of a level-number followed by a data-name, if required, and then followed by a set of clauses that describe the attributes of a data item or record. * data division. A COBOL division that describes data and files to be processed at run time. * data item. A unit of data (excluding literals) defined by a COBOL program or by the rules for function evaluation. * data-name. A user-defined word that names a data item described in a data description entry. The maximum length of a data-name is 30 bytes. When used in the general formats, data-name represents a word that must not be reference-modified, subscripted or qualified unless specifically permitted by the rules for the format. date field. Any of the following: v A data item whose data description entry includes a DATE FORMAT clause. v A value returned by one of the following intrinsic functions: DATE-OF-INTEGER DATE-TO-YYYYMMDD DATEVAL DAY-OF-INTEGER DAY-TO-YYYYDDD YEAR-TO-YYYY YEARWINDOW v The conceptual data items DATE, DATE YYYYMMDD, DAY, and DAY YYYYDDD of the ACCEPT statement. v The result of certain arithmetic operations (for details, see Arithmetic with date fields on page 243). The term date field refers to both expanded date field and windowed date field. See also nondate. date format. The date pattern of a date field, specified either: v Explicitly, by the DATE FORMAT clause or DATEVAL intrinsic function argument-2 v Implicitly, by statements and intrinsic functions that return date fields (for details, see Date field on page 72). DBCS. See Double-Byte Character Set (DBCS).
Glossary
585
DBCS character. Any character defined in IBMs double-byte character set. DBCS character position. See character position. * debugging line. A debugging line is any line with a D in the indicator area of the line. * debugging section. A section that contains a USE FOR DEBUGGING statement. * declaratives. A set of one or more special purpose sections, written at the beginning of the procedure division, the first of which is preceded by the keyword DECLARATIVES and the last of which is followed by the keyword END DECLARATIVES. A declarative is composed of a section header, followed by a USE compiler-directing sentence, followed by a set of zero, one, or more associated paragraphs. * de-edit. The logical removal of all editing characters from a numeric-edited data item in order to determine that items unedited numeric value. * delimited scope statement. Any statement that includes its explicit scope terminator. * delimiter. A character or a sequence of contiguous characters that identify the end of a string of characters and separate that string of characters from the following string of characters. A delimiter is not part of the string of characters that it delimits. * descending key. A key upon the values of which data is ordered starting with the highest value of key down to the lowest value of key, in accordance with the rules for comparing data items. digit. Any of the numerals from 0 through 9. In COBOL, the term is not used in reference to any other symbol. * digit position. The amount of physical storage required to store a single digit. This amount can vary depending on the usage specified in the data description entry that defines the data item. * direct access. The facility to obtain data from storage devices or to enter data into a storage device in such a way that the process depends only on the location of that data and not on a reference to data previously accessed. * division. There are four divisions in a COBOL program: identification, environment, data, and procedure. * division header. A combination of words followed by a separator period that indicates the beginning of a division. The division headers are: v IDENTIFICATION DIVISION. v ENVIRONMENT DIVISION. v DATA DIVISION.
v PROCEDURE DIVISION. do-until. In structured programming, a do-until loop will be executed at least once, and until a given condition is true. In COBOL, a TEST AFTER phrase used with the PERFORM statement functions in the same way. do-while. In structured programming, a do-while loop will be executed if, and while, a given condition is true. In COBOL, a TEST BEFORE phrase used with the PERFORM statement functions in the same way. double-byte ASCII. An IBM character set that contains DBCS and single-byte ASCII characters. (Also known as ASCII DBCS.) double-byte EBDIC. An IBM character set that contains DBCS and single-byte EBDIC characters. (Also known as EBCDIC DBCS.) Double-Byte Character Set (DBCS). An IBM coded character set in which each character is represented by two bytes. Languages such as Japanese, Chinese, and Korean, which contain more symbols than can be represented by 256 code points, require double-byte character sets. Because each character requires two bytes, entering, displaying, and printing DBCS characters requires hardware and supporting software that are DBCS-capable. * dynamic access. An access mode in which specific logical records can be obtained from or placed into a mass storage file in a nonsequential manner and obtained from a file in a sequential manner during the scope of the same OPEN statement.
E
EBCDIC (Extended Binary-Coded Decimal Interchange Code). A coded character set consisting of 8-bit coded characters. EBCDIC character. Any one of the graphic characters or control characters encoded in EBCDIC. encoding unit. See character encoding unit. edited data item. A data item that has been modified by suppressing zeroes and/or inserting editing characters. * editing character. A single character or a fixed two-character combination belonging to the following set: Character 0 + CR Meaning Space Zero Plus Minus Credit
586
Language Reference
Character DB Z * $ , . /
Meaning Debit Zero suppress Check protect Currency sign Comma (decimal point) Period (decimal point) Forward slash
environment variable. Any of a number of variables that define some aspect of the computing environment, and are accessible to programs that operate in that environment. Environment variables can affect the behavior of programs that are sensitive to the environment in which they operate. execution time. See run time. execution-time environment. See run-time environment. expanded date field. A date field containing an expanded (four-digit) year. See also date field and expanded year. expanded year. A date field that consists only of a four-digit year. Its value includes the century: for example, 1998. Compare with windowed year. * explicit scope terminator. A reserved word that terminates the scope of a particular procedure division statement. For example, END-READ. exponent. A number, indicating the power to which another number (the base) is to be raised. Positive exponents denote multiplication, negative exponents denote division, fractional exponents denote a root of a quantity. In COBOL, an exponential expression is indicated with the symbol ** followed by the exponent. * expression. An arithmetic or conditional expression. * extend mode. The state of a file after execution of an OPEN statement, with the EXTEND phrase specified for that file, and before the execution of a CLOSE statement, without the REEL or UNIT phrase for that file. Extensible Markup Language. See XML. * external data. The data described in a program as external data items and external file connectors. * external data item. A data item that is described as part of an external record in one or more programs of a run unit and that itself is permitted to be referenced from any program in which it is described. * external data record. A logical record which is described in one or more programs of a run unit and whose constituent data items are permitted to be referenced from any program in which they are described. external decimal item. A format for representing numbers in which the digit is contained in bits 4 through 7 and the sign is contained in bits 0 through 3 of the rightmost byte. Bits 0 through 3 of all other bytes contain 1s (hex F). For example, the decimal value of +123 is represented as 1111 0001 1111 0010 1111 0011. (Also known as zoned decimal item.)
* elementary item. A data item that is described as not being further logically subdivided. enclave. When running under the Language Environment product, an enclave is analogous to a run unit. An enclave can create other enclaves by a LINK and by the use of the system() function of C. encoding unit. See character encoding unit. * end class marker. A combination of words, followed by a separator period, that indicates the end of a COBOL class definition. The end class marker is: END CLASS class-name. * end method marker. A combination of words, followed by a separator period, that indicates the end of a COBOL method definition. The end method marker is: END METHOD method-name. * end of procedure division. The physical position of a COBOL procedure division after which no further procedures appear. * end program marker. A combination of words, followed by a separator period, that indicates the end of a COBOL source program. The end program marker is: END PROGRAM program-name. * entry. Any descriptive set of consecutive clauses written in the identification division, environment division, or data division of a COBOL program. * environment division. A division of a COBOL source unit that describes the computers upon which the source code is compiled and those on which the object code is run. It provides a linkage between the logical concept of files and their records and the physical aspects of the devices on which files are stored. environment-name. A name, specified by IBM, that identifies system logical units, printer and card punch control characters, report codes, and/or program switches. When an environment-name is associated with a mnemonic-name in the environment division, the mnemonic-name can then be substituted in any format in which such substitution is valid.
Glossary
587
* external file connector. A file connector which is accessible to one or more object programs in the run unit. external floating-point item. A format for representing numbers in which a real number is represented by a pair of distinct numerals. In a floating-point representation, the real number is the product of the fixed-point part (the first numeral), and a value obtained by raising the implicit floating-point base to a power denoted by the exponent (the second numeral). For example, a floating-point representation of the number 0.0001234 is: 0.1234 -3, where 0.1234 is the mantissa and -3 is the exponent. * external switch. A hardware or software device, defined and named by the implementor, which is used to indicate that one of two alternate states exists.
FD, followed by a file-name, and then followed by a set of clauses that include the attributes of the file. * file-name. A user-defined word that names a file connector described in a file description entry or a sort-merge file description entry within the file section of the data division. * file organization. The permanent logical file structure established at the time that a file is created. *file position indicator. A conceptual entity that contains the value of the current key within the key of reference for an indexed file, or the record number of the current record for a sequential file, or the relative record number of the current record for a relative file, or indicates that no next logical record exists, or that an optional input file is not present, or that the at end condition already exists, or that no valid next record has been established. * file section. The section of the data division that contains file description entries and sort-merge file description entries together with their associated record descriptions. file system. The collection of files and file management structures on a physical or logical mass storage device, such as a diskette or minidisk. * fixed file attributes. Information about a file which is established when a file is created and cannot subsequently be changed during the existence of the file. These attributes include the organization of the file (sequential, relative, or indexed), the prime record key, the alternate record keys, the code set, the minimum and maximum record size, the record type (fixed or variable), the collating sequence of the keys for indexed files, the blocking factor, the padding character, and the record delimiter. * fixed-length record. A record associated with a file whose file description or sort-merge description entry requires that all records contain the same number of bytes. fixed-point item. A numeric data item defined with a PICTURE clause that specifies the location of an optional sign, the number of digits it contains, and the location of an optional decimal point. The format can be either binary, packed decimal, or external decimal. floating-point item. A numeric data item containing a fraction and an exponent. Its value is obtained by multiplying the fraction by the base of the numeric data item raised to the power specified by the exponent. * format. A specific arrangement of a set of data. * function. A temporary data item whose value is determined at the time the function is referenced during the execution of a statement.
F
factory data. Data of a factory object. Factory data is allocated once for a class and shared by all instances of the class. Factory data is declared in the working-storage section in the factory paragraph of a class definition. Factory data is equivalent to private static data in Java. factory method. A method that is supported by a class independently of any object instance. Factory methods are defined in the factory paragraph of the class definition, and are equivalent to public static methods in Java. They are typically used to customize the creation of objects. * figurative constant. A compiler-generated value referenced through the use of certain reserved words. * file. A collection of logical records. * file attribute conflict condition. An unsuccessful attempt has been made to execute an input-output operation on a file and the file attributes, as specified for that file in the program, do not match the fixed attributes for that file. * file connector. A storage area which contains information about a file and is used as the linkage between a file-name and a physical file and between a file-name and its associated record area. * file control entry. A SELECT clause and all its subordinate clauses which declare the relevant physical attributes of a file. file-control paragraph. A paragraph in the environment division in which the data files for a given source unit are declared. * file description entry. An entry in the file section of the data division that is composed of the level indicator
588
Language Reference
* function-identifier. A syntactically correct combination of character-strings and separators that references a function. The data item represented by a function is uniquely identified by a function-name with its arguments, if any. A function-identifier can include a reference-modifier. A function-identifier that references an alphanumeric function can be specified anywhere in the general formats that an identifier can be specified, subject to certain restrictions. A function-identifier that references an integer or numeric function can be referenced anywhere in the general formats that an arithmetic expression can be specified. function-name. A word that names the mechanism whose invocation, along with required arguments, determines the value of a function. function-pointer. A data item that can contain the address of a procedure or function, described with a usage of FUNCTION-POINTER.
identification division can include the following documentation: author name, installation, or date. * identifier. Syntax that references a resource, such as a data item. An identifier that refers to data item includes the data-name and optionally includes qualifiers, subscripting, and reference modification. * imperative statement. A statement that specifies an unconditional action to be taken or a conditional statement that is delimited by its explicit scope terminator (a delimited scope statement). An imperative statement can consist of a sequence of imperative statements. * implicit scope terminator. A separator period that terminates the scope of any preceding unterminated statement, or a phrase of a statement that by its occurrence indicates the end of the scope of any statement contained within the preceding phrase. * index. A computer storage area or register, the content of which represents the identification of a particular element in a table. * index data item. A data item in which the values associated with an index-name can be stored in a form specified by the implementor. indexed data-name. An identifier that is composed of a data-name, followed by one or more index-names enclosed in parentheses. * indexed file. A file with indexed organization. * indexed organization. The permanent logical file structure in which each record is identified by the value of one or more keys within that record. indexing. Subscripting using index-names. * index-name. A user-defined word that names an index associated with a specific table. * inheritance. A mechanism for using the implementation of a class (the superclass) as the basis for a new class (a subclass). Each subclass inherits from exactly one class. The inherited class can itself be a subclass that inherits from another class. Enterprise COBOL does not support multiple inheritance. It supports the Java object model, which provides single inheritance. * initial program. A program that is placed into an initial state every time the program is called in a run unit. * initial state. The state of a program when it is first called in a run unit. inline. In a program, instructions that are executed sequentially, without branching to routines, subroutines, or other programs.
Glossary
G
garbage collection. The automatic freeing by the Java run-time system of the memory for objects that are no longer referenced. * global name. A name that is declared in only one program but which can be referenced from that program and from any program contained within that program. Condition-names, data-names, file-names, record-names, report-names, and some special registers can be global names. * group item. A data item that is composed of subordinate data items.
H
header label. (1) A file label or data set label that precedes the data records on a unit of recording media. (2) Synonym for beginning-of-file label. hide (a method). To redefine (in a subclass) a factory or static method defined with the same method-name in a parent class. Thus, the method in the subclass hides the method in the parent class. * high order end. The leftmost character of a string of characters.
I
IBM extensions. COBOL syntax and semantics specified by IBM, rather than by Standard COBOL 85 identification division. One of the four main component parts of a COBOL program, class definition, or method definition. The identification division identifies the program, class, or method. The
589
* input file. A file that is opened in the INPUT mode. * input mode. The state of a file after execution of an OPEN statement, with the INPUT phrase specified, for that file and before the execution of a CLOSE statement, without the REEL or UNIT phrase for that file. * input-output file. A file that is opened in the I-O mode. * input-output section. The section of the environment division that names the files and the external media required by a program or method and that provides information required for transmission and handling of data at run time. * input-output statement. A statement that causes files to be processed by performing operations upon individual records or upon the file as a unit. The input-output statements are: ACCEPT (with the identifier phrase), CLOSE, DELETE, DISPLAY, OPEN, READ, REWRITE, SET (with the TO ON or TO OFF phrase), START, and WRITE. * input procedure. A set of statements, to which control is given during the execution of a SORT statement, for the purpose of controlling the release of specified records to be sorted. instance data. Data defining the state of an object instance. Instance data is declared in the working-storage section of the object paragraph of a class definition. Also called object instance data. Each object instance has its own copy of instance data. Instance data is equivalent to private nonstatic member data in a Java class. instance method. A method defined in the object paragraph of a class definition. Instance methods are equivalent to public nonstatic methods in Java. * integer. (1) A numeric literal that does not include any digit positions to the right of the decimal point. (2) A numeric data item defined in the data division that does not include any digit positions to the right of the decimal point. (3) A numeric function whose definition provides that all digits to the right of the decimal point are zero in the returned value for any possible evaluation of the function. * integer function. A function whose category is numeric and whose definition does not include any digit positions to the right of the decimal point. interlanguage communication (ILC). The ability of routines written in different programming languages to communicate. ILC support allows the application writer to readily build applications from component routines written in a variety of languages. intermediate result. An intermediate field containing the results of a succession of arithmetic operations.
* internal data. The data described in a program excluding all external data items and external file connectors. Items described in the linkage section of a program are treated as internal data. * internal data item. A data item which is described in one program in a run unit. An internal data item can have a global name. internal decimal item. A format in which each byte in a field except the rightmost byte represents two numeric digits. The rightmost byte contains one digit and the sign. For example, the decimal value +123 is represented as 0001 0010 0011 1111. Synonymous with packed decimal item. * internal file connector. A file connector that is accessible to only one object program in the run unit. intrinsic function. A function defined as part of the COBOL language. In some programming languages, this is called a built-in function. * invalid key condition. A condition, at run time, caused when a specific value of the key associated with an indexed or relative file is determined to be invalid. * I-O mode. The state of a file after execution of an OPEN statement, with the I-O phrase specified, for that file and before the execution of a CLOSE statement without the REEL or UNIT phase for that file. * I-O status. A conceptual entity which contains the two-character value indicating the resulting status of an input-output operation. This value is made available to the program through the use of the FILE STATUS clause in the file control entry for the file.
J
Java Native Interface (JNI). A programming interface that allows Java code running inside a Java virtual machine (JVM) to interoperate with applications and libraries written in other programming languages.
K
K. When referring to storage capacity, two to the tenth power; 1024 in decimal notation. * key. A data item that identifies the location of a record, or a set of data items which serve to identify the ordering of data. * key of reference. The key, either prime or alternate, currently being used to access records within an indexed file. * keyword. A reserved word or function-name whose presence is required when the format in which the word appears is used in a source unit.
590
Language Reference
kilobyte (KB). One kilobyte equals 1024 bytes.
L
* language-name. A system-name that specifies a particular programming language. last-used state. The state of storage in which internal values remain the same as when the program or method was exited (are not reset to their initial values on reentry). * letter. A character belonging to one of the following two sets: v Uppercase letters: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z v Lowercase letters: a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z * level indicator. Two alphabetic characters that identify a specific type of file or a position in a hierarchy. The level indicators in the data division are: CD, FD, and SD. * level-number. A user-defined word, expressed as a two-digit number, which indicates the hierarchical position of a data item or the special properties of a data description entry. Level-numbers in the range from 1 through 49 indicate the position of a data item in the hierarchical structure of a logical record. Level-numbers in the range 1 through 9 can be written either as a single digit or as a zero followed by a significant digit. Level-numbers 66, 77 and 88 identify special properties of a data description entry. * library-name. A user-defined word that names a COBOL library that is to be used by the compiler for a given compilation. * library text. A sequence of text words, comment lines, the separator space, or the separator pseudo-text delimiter in a COBOL library. Lilian date. The number of days since the beginning of the Gregorian calendar. Day one is Friday, October 15, 1582. The Lilian date format is named in honor of Luigi Lilio, the creator of the Gregorian calendar. * LINAGE-COUNTER. A special register whose value points to the current position within the page body. linkage section. The section in the data division of an activated unit (a called program or an invoked method) that describes data items available from the activating unit (a program or a method). These data items can be referred to by both the activated unit and the activating unit. literal. A character-string whose value is specified either by the ordered set of characters comprising the string, or by the use of a figurative constant.
little-endian. The default format that Intel hardware uses to store binary data. In this format, the most significant digit is at the highest address. See also big-endian. local-storage section. The section of the data division that defines storage that is allocated and freed on a per-invocation basis, depending on the value assigned in their VALUE clauses. * logical operator. One of the reserved words AND, OR, or NOT. In the formation of a condition, either AND, or OR, or both can be used as logical connectives. NOT can be used for logical negation. * logical record. The most inclusive data item. The level-number for a record is 01. A record can be either an elementary item or a group of items. The term is synonymous with record. * low order end. The rightmost character of a string of characters.
M
main program. In a hierarchy of programs and subroutines, the first program to receive control when the programs are run. * mass storage. A storage medium in which data can be organized and maintained in both a sequential and nonsequential manner. * mass storage device. A device having a large storage capacity; for example, magnetic disk, magnetic drum. * mass storage file. A collection of records that is assigned to a mass storage medium. MBCS. See multibyte character set (MBCS). * megabyte (M). One megabyte equals 1,048,576 bytes. * merge file. A collection of records to be merged by a MERGE statement. The merge file is created and can be used only by the merge function. method. Procedural code that defines one of the operations supported by an object. Method procedural code is executed by a COBOL INVOKE statement on a specific object instance. A method can be invoked by a Java invocation expression. A method can be a factory method or an instance method. * method identification entry. An entry in the METHOD-ID paragraph of the identification division that contains clauses that specify the method-name and assign selected attributes to the method definition. method invocation. (1) The act of invoking a method. (2) The programming language syntax used to invoke a method (the INVOKE statement in COBOL, a method invocation expression in Java).
Glossary
591
* method-name. A name that identifies a method, specified as the content of an alphanumeric or national literal in the METHOD-ID paragraph, and as the content of an alphanumeric literal, national literal, alphanumeric data item, or national data item in the INVOKE statement. method hiding. See hide. method overloading. See overload. method overriding. See override. * mnemonic-name. A user-defined word that is associated in the environment division with a specified implementor-name. multibyte character. Any character that is represented in 2 or more bytes in a multibyte character set. For example, a DBCS character or any UTF-8 character that is represented in two or more bytes. UTF-16 characters are not multibyte characters because UTF-16 is not a multibyte character set. multibyte character set (MBCS). A coded character set that is composed of characters represented in a varying number of bytes. Examples are: Extended Unix Code, UTF-8, and character sets composed of a mixture of single-byte and double-byte EBCDIC or ASCII characters.
* next executable statement. The next statement to which control will be transferred after execution of the current statement is complete. * next record. The record that logically follows the current record of a file. * noncontiguous items. Elementary data items in the working-storage and linkage sections that bear no hierarchic relationship to other data items. nondate. Any of the following: v A data item whose date description entry does not include the DATE FORMAT clause v A literal v A date field that has been converted using the UNDATE function v A reference-modified date field v The result of certain arithmetic operations that can include date field operands; for example, the difference between two compatible date fields null. Figurative constant used to assign the value of an invalid address to pointer data items. NULLS can be used wherever NULL can be used. * numeric character. A character that belongs to the following set of digits: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9. numeric-edited item. A data item that contains numeric data in a form suitable for use in printed output. It can consist of external decimal digits from 0 through 9, the decimal separator, commas, the currency sign, sign control characters, and other editing characters. * numeric function. A function whose class and category are numeric but which for some possible evaluation does not satisfy the requirements of integer functions. * numeric item. A data item whose description restricts its content to a value represented by characters chosen from the digits from 0 through 9; if signed, the item can also contain a +, -, or other representation of an operational sign. * numeric literal. A literal composed of one or more numeric characters. It can contain either a decimal point, or an algebraic sign, or both. The decimal point must not be the rightmost character. The algebraic sign, if present, must be the leftmost character.
N
national character. A character in a national data item or national literal. national character position. See character position. national data item. data item described implicitly or explicitly with usage NATIONAL. * native character set. The implementor-defined character set associated with the computer specified in the OBJECT-COMPUTER paragraph. * native collating sequence. The implementor-defined collating sequence associated with the computer specified in the OBJECT-COMPUTER paragraph. * negated combined condition. The NOT logical operator immediately followed by a parenthesized combined condition. * negated simple condition. The NOT logical operator immediately followed by a simple condition. nested program. A program that is directly contained within another program. * next executable sentence. The next sentence to which control will be transferred after execution of the current statement is complete.
O
object. An entity that has state (its data values) and operations (its methods). An object is a way to encapsulate state and behavior.
592
Language Reference
object code. Output from a compiler or assembler that is itself executable machine code or is suitable for processing to produce executable machine code. * object-computer. The name of an environment division paragraph in which the computer environment, within which the program is executed, is described. object deck. A portion of an object program suitable as input to a linkage editor. The term is synonymous with object module and text deck. object instance. A single object, of possibly many, instantiated from the specifications in the object paragraph of a COBOL class definition. An object instance has a copy of all the data described in its class definition and all inherited data. The methods associated with an object instance includes the methods defined in its class definition and all inherited methods. An object instance can be an instance of a Java class. object module. Synonym for object deck or text deck. * object of entry. A set of operands and reserved words, within a data division entry of a COBOL program, that immediately follows the subject of the entry. object program. A set or group of executable machine language instructions and other material designed to interact with data to provide problem solutions. In this context, an object program is generally the machine language result of the operation of a COBOL compiler on a source program or on the methods of an object-oriented class definition. Where there is no danger of ambiguity, the word program alone can be used in place of the phrase object program. object reference. A data item that can contain the information needed to invoke or refer to an object. An object reference is defined in COBOL with the OBJECT REFERENCE phrase in the USAGE clause of a data description entry. See also typed object reference and universal object reference. * object time. The time at which an object program is executed. The term is synonymous with the terms execution time and run time. * obsolete element. A COBOL language element in Standard COBOL 85 that was deleted from Standard COBOL 2002. ODO object. In the example below, WORKING-STORAGE SECTION 01 TABLE-1. 05 X 05 Y OCCURS 3 TIMES DEPENDING ON X
X is the object of the OCCURS DEPENDING ON clause (ODO object). The value of the ODO object determines how many of the ODO subject appear in the table. ODO subject. In the example above, Y is the subject of the OCCURS DEPENDING ON clause (ODO subject). The number of Y ODO subjects that appear in the table depends on the value of X. * open mode. The state of a file after execution of an OPEN statement for that file and before the execution of a CLOSE statement without the REEL or UNIT phrase for that file. The particular open mode is specified in the OPEN statement as either INPUT, OUTPUT, I-O or EXTEND. operand. Data that is operated upon. In this document, any lowercase word (or words) that appears in a statement or entry format is an operand in that it is a reference to the data identified by that word (or words). * operational sign. An algebraic sign, associated with a numeric data item or a numeric literal, to indicate whether its value is positive or negative. * optional file. A file that is declared as being not necessarily present each time the object program is executed. The object program causes an interrogation for the presence or absence of the file. * optional word. A reserved word that is included in a specific format only to improve the readability of the language and whose presence is optional to the user when the format in which the word appears is used in a source unit. * output file. A file that is opened in either the OUTPUT mode or EXTEND mode. * output mode. The state of a file after execution of an OPEN statement, with the OUTPUT or EXTEND phrase specified, for that file and before the execution of a CLOSE statement without the REEL or UNIT phrase for that file. * output procedure. A set of statements to which control is given during execution of a SORT statement after the sort function is completed, or during execution of a MERGE statement after the merge function reaches a point at which it can select the next record in merged order when requested. overflow condition. A condition that occurs when a portion of the result of an operation exceeds the capacity of the intended unit of storage. overload. To define a method with the same name as another method available in the same class, but with a different signature. See also signature. override. To redefine (in a subclass) an instance method inherited from a parent class.
Glossary
PICS9. PIC X.
593
P
package. In Java, a group of related classes that can be imported individually or as a whole. packed decimal item. See internal decimal item. * padding character. An alphanumeric character used to fill the unused character positions in a physical record. page. A vertical division of output data representing a physical separation of such data, the separation being based on internal logical requirements or external characteristics of the output medium. * page body. That part of the logical page in which lines can be written or spaced. * paragraph. In the procedure division, a paragraph-name followed by a separator period and by zero, one, or more sentences. In the identification and environment divisions, a paragraph header followed by zero, one, or more entries. * paragraph header. A reserved word, followed by the separator period, that indicates the beginning of a paragraph. * paragraph-name. A user-defined word that identifies and begins a paragraph in the procedure division. password. A unique string of characters that a program, computer operator, or user must supply to meet security requirements before gaining access to data. * phrase. An ordered set of one or more consecutive COBOL character-strings that form a portion of a COBOL procedural statement or of a COBOL clause. * physical record. See block. pointer data item. A data item in which address values can be stored. Data items are explicitly defined as pointers with the USAGE IS POINTER clause. ADDRESS OF special registers are implicitly defined as pointer data items. Pointer data items can be compared for equality or moved to other pointer data items. portability. The ability to transfer an application from one application platform to another with relatively few changes to the source code. * prime record key. A key whose contents uniquely identify a record within an indexed file. * priority-number. A user-defined word that classifies sections in the procedure division for purposes of segmentation. Segment-numbers can contain only the characters 0,1, . . ., 9. A segment-number can be expressed either as a one- or two-digit number.
private. In object orientation, data that is accessible only by methods of the class that defines the data. Instance data is accessible only by instance methods; factory data is accessible only by factory methods. Thus, instance data is private to instance methods defined in the same class definition; factory data is private to factory methods defined in the same class definition. * procedure. A paragraph or group of logically successive paragraphs, or a section or group of logically successive sections, within the procedure division. * procedure branching statement. A statement that causes the explicit transfer of control to a statement other than the next executable statement in the sequence in which the statements are written in the source unit. The procedure branching statements are: ALTER, CALL, EXIT, EXIT PROGRAM, GO TO, MERGE (with the OUTPUT PROCEDURE phrase), PERFORM, SORT (with the INPUT PROCEDURE or OUTPUT PROCEDURE phrase), and XML PARSE. procedure division. The division of a program or method that contains procedural statements for performing operations at run time. * procedure-name. A user-defined word that is used to name a paragraph or section in the procedure division. It consists of a paragraph-name (which can be qualified) or a section-name. procedure pointer. A data item in which a pointer to an entry point can be stored. A data item defined with the USAGE IS PROCEDURE-POINTER clause contains the address of a procedure entry point. * program-name. In the identification division and the end program marker, a user-defined or a literal that identifies a COBOL source program. * pseudo-text. A sequence of text words, comment lines, or the separator space in a source unit or COBOL library bounded by, but not including, pseudo-text delimiters. * pseudo-text delimiter. Two contiguous equal sign characters (==) used to delimit pseudo-text. * punctuation character. A character that belongs to the following set: Character , ; : . ( ) Meaning Comma Semicolon Colon Period (full stop) Quotation mark Left parenthesis Right parenthesis Space
594
Language Reference
Character =
Meaning Equal sign
recording mode. The format of the logical records in a file. Recording mode can be F (fixed-length), V (variable-length), S (spanned), or U (undefined). recursion. A program calling itself or being directly or indirectly called by a one of its called programs. recursively capable. A program is recursively capable (can be called recursively) if the RECURSIVE clause is on the PROGRAM-ID statement. reel. A discrete portion of a storage medium that contains part of a file, all of a file, or any number of files. The term is synonymous with unit and volume. reentrant. The attribute of a program or routine that allows more than one user to share a single copy of a load module. * reference format. A format that provides a standard method for writing COBOL source code. reference modification. A method of defining a new data item by specifying the leftmost character position and length relative to the leftmost character position of another data item. * reference-modifier. A syntactically correct combination of character-strings and separators that defines a unique data item. It includes a delimiting left parenthesis separator, the leftmost character position, a colon separator, optionally a length, and a delimiting right parenthesis separator. * relation. See relational operator or relation condition. * relation character. A character that belongs to the following set: Character > < = Meaning Greater than Less than Equal to
Q
QSAM (Queued Sequential Access Method). An extended version of the basic sequential access method (BSAM). When this method is used, a queue is formed of input data blocks that are awaiting processing or of output data blocks that have been processed and are awaiting transfer to auxiliary storage or to an output device. * qualified data-name. An identifier that is composed of a data-name followed by one or more sets of either of the connectives OF and IN followed by a data-name qualifier. * qualifier. (1) A data-name or a name associated with a level indicator which is used in a reference either together with another data-name which is the name of an item that is subordinate to the qualifier or together with a condition-name. (2) A section-name that is used in a reference together with a paragraph-name specified in that section. (3) A library-name that is used in a reference together with a text-name associated with that library.
R
* random access. An access mode in which the program-specified value of a key data item identifies the logical record that is obtained from, deleted from, or placed into a relative or indexed file. * record. See logical record. * record area. A storage area allocated for the purpose of processing the record described in a record description entry in the file section of the data division. In the file section, the current number of character positions in the record area is determined by the explicit or implicit RECORD clause. * record description. See record description entry. * record description entry. The total set of data description entries associated with a particular record. The term is synonymous with record description. record key. A key whose contents identify a record within an indexed file. * record-name. A user-defined word that names a record described in a record description entry in the data division of a COBOL program. * record number. The ordinal number of a record in the file whose organization is sequential.
* relation condition. The proposition, for which a truth value can be determined, that the value of an arithmetic expression, data item, alphanumeric literal, or index-name has a specific relationship to the value of another arithmetic expression, data item, alphanumeric literal, or index name. See also relational operator. * relational operator. A reserved word, a relation character, a group of consecutive reserved words, or a group of consecutive reserved words and relation characters used in the construction of a relation condition. The permissible operators and their meanings are: Character IS GREATER THAN IS > Meaning Greater than Greater than
Glossary
595
Character IS NOT GREATER THAN IS NOT > IS IS IS IS IS IS IS IS LESS THAN < NOT LESS THAN NOT < EQUAL TO = NOT EQUAL TO NOT =
Meaning Not greater than Not greater than Less than Less than Not less than Not less than Equal to Equal to Not equal to Not equal to
* run unit. A stand-alone object program, or several object programs, that interact via COBOL CALL or INVOKE statements and function at run time as an entity.
S
SBCS (Single Byte Character Set). See Single Byte Character Set (SBCS). scope terminator. A COBOL reserved word that marks the end of certain procedure division statements. It can be either explicit (END-ADD, for example) or implicit (a separator period, for example). * section. A set of zero, one or more paragraphs or entities, called a section body, the first of which is preceded by a section header. Each section consists of the section header and the related section body. * section header. A combination of words followed by a separator period that indicates the beginning of a section. For example, WORKING-STORAGE SECTION. * section-name. A user-defined word that names a section in the procedure division. * sentence. A sequence of one or more statements, the last of which is terminated by a separator period. * separately compiled program. A program which, together with its contained programs, is compiled separately from all other programs. * separator. A character or two or more contiguous characters used to delimit character-strings. * separator comma. A comma (,) followed by a space used to delimit character-strings. * separator period. A period (.) followed by a space used to delimit character-strings. * separator semicolon. A semicolon (;) followed by a space used to delimit character-strings. * sequential access. An access mode in which logical records are obtained from or placed into a file in a consecutive predecessor-to-successor logical record sequence determined by the order of records in the file. * sequential file. A file with sequential organization. * sequential organization. The permanent logical file structure in which a record is identified by a predecessor-successor relationship established when the record is placed into the file. serial search. A search in which the members of a set are consecutively examined, beginning with the first member and ending with the last.
IS GREATER THAN OR EQUAL Greater than or equal to TO IS >= Greater than or equal to IS LESS THAN OR EQUAL TO Less than or equal to IS <= Less than or equal to * relative file. A file with relative organization. * relative key. A key whose contents identify a logical record in a relative file. * relative organization. The permanent logical file structure in which each record is uniquely identified by an integer value greater than zero, which specifies the records logical ordinal position in the file. * relative record number. The ordinal number of a record in a file whose organization is relative. This number is treated as a numeric literal that is an integer. * reserved word. A COBOL word specified in the list of words that can be used in a COBOL source unit, but that must not appear in the program as user-defined words or system-names. * resource. A facility or service, controlled by the operating system, that can be used by an executing program. * resultant identifier. A user-defined data item that is to contain the result of an arithmetic operation. routine. A set of statements in a COBOL program that causes the computer to perform an operation or series of related operations. In Language Environment, refers to either a procedure, function, or subroutine. * routine-name. A user-defined word that identifies a procedure written in a language other than COBOL. * run time. The time at which an object program is executed. The term is synonymous with object time. run-time environment. The environment in which a COBOL program executes.
596
Language Reference
* 77-level-description-entry. A data description entry that describes a noncontiguous data item with the level-number 77. * sign condition. The proposition, for which a truth value can be determined, that the algebraic value of a data item or an arithmetic expression is either less than, greater than, or equal to zero. signature. The name of a method and the number and types of its formal parameters. * simple condition. Any single condition chosen from the set: v Relation condition v Class condition v Condition-name condition v Switch-status condition v Sign condition Single Byte Character Set (SBCS). A set of characters in which each character is represented by a single byte. See also EBCDIC (Extended Binary-Coded Decimal Interchange Code). slack bytes (within records). Bytes inserted by the compiler between data items to ensure correct alignment of some elementary data items. Slack bytes contain no meaningful data. The SYNCHRONIZED clause instructs the compiler to insert slack bytes when they are needed for proper alignment. slack bytes (between records). Bytes inserted by the programmer between blocked logical records of a file, to ensure correct alignment of some elementary data items. In some cases, slack bytes between records improve performance for records processed in a buffer. * sort file. A collection of records to be sorted by a SORT statement. The sort file is created and can be used by the sort function only. * sort-merge file description entry. An entry in the file section of the data division that is composed of the level indicator SD, followed by a file-name, and then followed clauses that describe the attributes of the sort-merge file. source unit. A unit of COBOL source code that can be separately compiled: a program or a class definition. Also known as compilation unit. * special character. A character that belongs to the following set: Character + * / = Meaning Plus sign Minus sign (hyphen) Asterisk Forward slash Equal sign
Character $ , ; . ( ) > < :
Meaning Currency sign Comma (decimal point) Semicolon Period (decimal point, full stop) Quotation mark Left parenthesis Right parenthesis Greater than symbol Less than symbol Colon
SPECIAL-NAMES. The name of an environment division paragraph in which environment-names are related to user-specified mnemonic-names. * special registers. Certain compiler-generated storage areas whose primary use is to store information produced in conjunction with the use of a specific COBOL feature. Standard COBOL 85. The COBOL language defined by the ANSI and ISO standards identified in Appendix G, Industry specifications, on page 577. Standard COBOL 2002. The COBOL language defined by the following standards: v INCITS/ISO/IEC 1989-2002, Information Technology - Programming Languages - COBOL v ISO/IEC 1989:2002, Information technology Programming languages COBOL * statement. A COBOL language construct that specifies one or more actions to be performed. Statements can be procedural statements or compiler-directing statements. An example of a procedural statement is the ADD statement; an example of a compiler-directing statement is the USE statement. structured programming. A technique for organizing and coding a computer program in which the program comprises a hierarchy of segments, each segment having a single entry point and a single exit point. Control is passed downward through the structure without unconditional branches to higher levels of the hierarchy. subclass. A class that inherits from another class. When two classes in an inheritance relationship are considered together, the subclass is the inheriting class; the superclass is the inherited class. A subclass is also referred to as a child class or derived class. * subject of entry. An operand or reserved word that appears immediately following the level indicator or the level-number in a data division entry. * subprogram. Any called program.
Glossary
597
* subscript. An occurrence number represented by either an integer, a data-name optionally followed by an integer with the operator + or -, or an index-name optionally followed by an integer with the operator + or -, that identifies a particular element in a table. A subscript can be the word ALL when the subscripted identifier is used as a function argument for a function allowing a variable number of arguments. * subscripted data-name. An identifier that is composed of a data-name followed by one or more subscripts enclosed in parentheses. superclass. A class that is inherited by another class. When two classes in an inheritance relationship are considered together, the subclass is the inheriting class; the superclass is the inherited class. The superclass is also referred to as the parent class. surrogate pair. In the UTF-16 format of Unicode, a pair of encoding units that together represents a single Unicode character. The first unit of the pair is called a high surrogate and the second a low surrogate. The code value of a high surrogate is in the range XD800 through XDBFF. The code value of a low surrogate is in the range XDC00 through XDFFF. Surrogate pairs provide for more characters than the 65,536 characters that fit in the Unicode 16-bit coded character set. switch-status condition. The proposition, for which a truth value can be determined, that an UPSI switch, capable of being set to an on or off status, has been set to a specific status. * symbolic-character. A user-defined word that specifies a user-defined figurative constant. syntax. (1) The relationship among characters or groups of characters, independent of their meanings or the manner of their interpretation and use. (2) The structure of expressions in a language. (3) The rules governing the structure of a language. (4) The relationship among symbols. (5) The rules for the construction of a statement. * system-name. A COBOL word that is used to communicate with the operating environment.
* text word. A character or a sequence of contiguous characters between margin A and margin R in COBOL source code. A text word can be: v A separator, except for: space; a pseudo-text delimiter; and the opening and closing delimiters for alphanumeric literals. The right parenthesis and left parenthesis characters, regardless of context within the library, source unit, or pseudo-text, are always considered text words. v A literal including, in the case of alphanumeric literals, the opening quotation mark and the closing quotation mark that bound the literal. v Any other sequence of contiguous COBOL characters except comment lines and the word COPY bounded by separators that are neither a separator nor a literal. trailer-label. (1) A file or data set label that follows the data records on a unit of recording medium. (2) Synonym for end-of-file label. * truth value. The representation of the result of the evaluation of a condition in terms of one of two values: true or false. typed object reference. An object reference data item that can reference only an object of a specified class or one of its subclasses.
U
* unary operator. A plus (+) or a minus (-) sign that precedes a variable or a left parenthesis in an arithmetic expression and that has the effect of multiplying the expression by +1 or -1, respectively. Unicode. A coded character set that encodes all the characters required for the written expression of any of the languages of the modern world. There are multiple formats for representing Unicode, including UTF-8, UTF-16, and UTF-32. Enterprise COBOL supports Unicode using UTF-16 big-endian format as the representation for the national data type. unit. A module of direct access, the dimensions of which are determined by IBM. universal object reference. An object reference data item that can contain a reference to an object of any class. * unsuccessful execution. The attempted execution of a statement that does not result in the execution of all the operations specified by that statement. UPSI switch. A program switch that performs the functions of a hardware switch. Eight are provided: UPSI-0 through UPSI-7.
T
* table. A set of logically consecutive items of data that are defined in the data division by means of the OCCURS clause. * table element. A data item that belongs to the set of repeated items comprising a table. text deck. Synonym for object deck or object module. * text-name. A user-defined word that identifies library text.
598
Language Reference
* user-defined word. A COBOL word that must be supplied by the user to satisfy the format of a clause or statement. The maximum length of a user-defined word is 30 bytes.
* word. A character-string that forms a user-defined word, a system-name, a reserved word, or a function-name. * working-storage section. The section of the data division that describes working-storage data items, composed either of noncontiguous items or working-storage records, or both.
V
* variable. A data item whose value can be changed by the application at run time. * variable-length record. A record associated with a file whose file description or sort-merge description entry permits records to contain a varying number of character positions. * variable-occurrence data item. A variable-occurrence data item is a table element which is repeated a variable number of times. Such an item must contain an OCCURS DEPENDING ON clause in its data description entry, or be subordinate to such an item. variably located group. A group item following, and not subordinate to, a variable-length table in the same level-01 record. variably located item. A data item following, and not subordinate to, a variable-length table in the same level-01 record. volume. A module of external storage. For tape devices it is a reel; for direct-access devices it is a unit. volume switch procedures. System procedures executed automatically when the end of a unit or reel has been reached before end-of-file has been reached.
X
XML. Extensible Markup Language. A metalanguage for defining markup languages that was derived from and is a subset of SGML. XML omits the more complex and less-used parts of SGML and makes it much easier to: v Write applications to handle document types v Author and manage structured information v Transmit and share structured information across diverse computing systems XML is being developed under the auspices of the World Wide Web Consortium (W3C). XML data. Data that is organized into a hierarchical structure with XML elements. The data definitions are defined in XML element type declarations. XML declaration. XML text that specifies characteristics of the XML document such as the version of XML being used and the encoding of the document. XML document. A data object that is well formed as defined by the W3C XML specification.
W
white space characters. Characters that introduce space into a document. They are: v Space v Horizontal tabulation v Carriage return v Line feed v Next line as named in the Unicode Standard. windowed date field. A date field containing a windowed (two-digit) year. See also date field and windowed year. windowed year. A date field that consists only of a two-digit year. This two-digit year can be interpreted using a century window. For example, 05 could be interpreted as 2005. See also century window. Compare with expanded year.
Z
zoned decimal item. See external decimal item.
Glossary
599
600
Language Reference
List of resources
Compiler and Run-Time Migration Guide, GC27-1409 Customization Guide, GC27-1410 Debug Tool Reference and Messages, SC18-9010 Debug Tool Users Guide, SC18-9012 Fact Sheet, GC27-1407 Language Reference, SC27-1408 Licensed Program Specifications, GC27-1411 Programming Guide, SC27-1412 Checkpoint/Restart, SC26-7401 Macro Instructions for Data Sets, SC26-7408 Program Management, SC27-1130 Using Data Sets, SC26-7410 Utilities, SC26-7414 DFSORT Application Programming Guide, SC33-4035 Installation and Customization, SC33-4034 IMS Application Programming: Database Manager, SC27-1286 Application Programming: Design Guide, SC27-1287 Application Programming: EXEC DLI Commands for CICS and IMS, SC27-1288 Application Programming: Transaction Manager, SC27-1289 IMS Connect Guide and Reference, SC27-0946 IMS Java Users Guide, SC27-1296 z/OS ISPF Dialog Developers Guide and Reference, SC34-4821 Users Guide Vol. 1, SC34-4822 Users Guide Vol. 2, SC34-4823 z/OS Language Environment Application Programming and SQL Guide, SC26-9933 Command Reference, SC26-9934 SQL Reference, SC26-9944 z/OS DFSMS Access Method Services for Catalogs, SC26-7394
Related publications
COBOL Report Writer Precompiler Programmers Manual, SC26-4301 CICS Transaction Server for z/OS Application Programming Guide, SC34-5993 Application Programming Reference, SC34-5994 Customization Guide, SC34-5989 External Interfaces Guide, SC34-6006 z/OS C/C++ Programming Guide, SC09-4765 Run-Time Library Reference, SA22-7821 DB2 UDB for OS/390 and z/OS
Concepts Guide, SA22-7567 Customization, SA22-7564 Debugging Guide, GA22-7560 Programming Guide, SA22-7561
601
Programming Reference, SA22-7562 Run-Time Messages, SA22-7566 Run-Time Migration Guide, GA22-7565 Writing Interlanguage Communication Applications, SA22-7563 z/OS MVS JCL Reference, SA22-7597 JCL Users Guide, SA22-7598 System Commands, SA22-7627 z/OS TSO/E
The Java Language Specification, Second Edition, by Gosling et al., java.sun.com/docs/books/jls/ second_edition/html/j.title.doc.html The Java Native Interface, java.sun.com/j2se/ 1.3/docs/guide/jni/index.html Java 2 on the OS/390 and z/OS Platforms, www.ibm.com/servers/eserver/zseries/ software/java/ The Java 2 Enterprise Edition Developers Guide, java.sun.com/j2ee/j2sdkee/devguide1_2_1.pdf New IBM Technology featuring Persistent Reusable Java Virtual Machines, www.ibm.com/servers/ eserver/zseries/software/java/pdf/jtc0a100.pdf WebSphere Application Server for z/OS
Command Reference, SA22-7782 Assembling J2EE Applications, SA22-7836 Primer, SA22-7787 XML Users Guide, SA22-7794 XML specification, www.w3c.org/XML/ z/OS UNIX System Services Command Reference, SA22-7802 Programming: Assembler Callable Services Reference, SA22-7803 Users Guide, SA22-7801 z/Architecture Principles of Operation, SA22-7832 Softcopy publications for z/OS The following collection kit contains z/OS and related product publications: z/OS CD Collection Kit, SK3T-4269 Unicode and character representation Unicode, www.unicode.org/ Character Data Representation Architecture Reference and Registry, SC09-2190 z/OS Support for Unicode: Using Conversion Services, SA22-7649 Java
602
Language Reference
Index Special characters

- (minus) insertion character 199, 200 SIGN clause 208 symbol in PICTURE clause 192 , (comma) insertion character 198 symbol in PICTURE clause 190, 192 : (colon) description 36 required use of 514 / (slash) insertion character 198 symbol in PICTURE clause 192 (/) comment line 46 (period), symbol in PICTURE clause 190 $ (default currency symbol) in PICTURE clause 192 insertion character 199, 200 symbol in PICTURE clause 190 *, symbol in PICTURE clause 190 *CBL (*CONTROL) statement 506 *CONTROL (*CBL) statement 506 > (greater than) 251 >= (greater than or equal to) 251 < (less than) 251 <= (less than or equal to) 251 + (plus) insertion character 199, 200, 201 SIGN clause 208 symbol in PICTURE clause 192 = (equal) 251 access mode description 130 dynamic DELETE statement 311 description 131 READ statement 388 random DELETE statement 311 description 131 READ statement 387 sequential DELETE statement 311 description 131 READ statement 385 ACCESS MODE clause 130 accessibility of Enterprise COBOL xi of this book xii using z/OS xi ACOS function 469 ADD statement common phrases 272 CORRESPONDING phrase 292 description and format 290 END-ADD phrase 292 GIVING phrase 291 NOT ON SIZE ERROR phrase 292 ON SIZE ERROR phrase 292 ROUNDED phrase 292 ADDRESS OF special register 14 advanced function printing 443 ADVANCING phrase 438 AFTER phrase INSPECT statement 343 PERFORM statement 376 with REPLACING 340 with TALLYING 338 WRITE statement 438 ALL literal 12 STOP statement 419 STRING statement 421 UNSTRING statement 429 ALL phrase INSPECT statement 338, 340 SEARCH statement 399 UNSTRING statement 429 ALL subscripting 464 ALPHABET clause 109 alphabet-name 9, 51 description 109 MERGE statement 355 PROGRAM COLLATING SEQUENCE clause 105 SORT statement 412 alphabetic arguments 462 alphabetic character in ACCEPT 286 alphabetic class and category 153 ALPHABETIC class test 248 alphabetic item alignment rules 154 elementary move rules 361 alphabetic item (continued) PICTURE clause 193 ALPHABETIC-LOWER class test 248 ALPHABETIC-UPPER class test 248 alphanumeric arguments 462 alphanumeric class and category alignment rules 154 description 153 alphanumeric functions 460, 461 alphanumeric item alignment rules 154 elementary move rules 361 PICTURE clause 195 alphanumeric literal with DBCS characters 26 alphanumeric literals 25, 28 alphanumeric literals in hexadecimal notation 27 alphanumeric operands, comparing 257 alphanumeric-edited item alignment rules 154 elementary move rules 361 PICTURE clause 195 ALSO phrase ALPHABET clause 110 EVALUATE statement 322 ALTER statement description and format 293 GO TO statement and 330 segmentation considerations 293 altered GO TO statement 330 ALTERNATE RECORD KEY clause 133 AND logical operator 262 ANNUITY function 470 ANSI COBOL standards 577 APPLY WRITE-ONLY clause 142 Area A (cols. 8-11) 42 Area B (cols. 12-72) 43 arguments 462 arithmetic expression COMPUTE statement 308 description 241 EVALUATE statement 322 relation condition 250 arithmetic operator description 242 permissible symbol pairs 243 arithmetic operators 10 arithmetic statements ADD 290 common phrases 272 COMPUTE 308 DIVIDE 316 list of 276 multiple results 277 MULTIPLY 365 operands 276 programming notes 277 SUBTRACT 425 ASCENDING KEY phrase collating sequence 183
Numerics
0 insertion character 198 symbol in PICTURE clause 192 0, symbol in PICTURE clause 189 66, RENAMES data description entry 205 77, item description entry 153 88 level item 153 88, condition-name data description entry 172 9, symbol in PICTURE clause 189, 192
A
A, symbol in PICTURE clause 188 abbreviated combined relation condition examples 267 using parentheses in 266 ACCEPT statement description and format 286 FROM phrase 286 mnemonic name in 286 overlapping operands, unpredictable results 277 system information transfer 287 Copyright IBM Corp. 1991, 2004
603
ASCENDING KEY phrase (continued) description 353 MERGE statement 353 OCCURS clause 182 SORT statement 410 ASCII collating sequence 552 specifying in SPECIAL-NAMES paragraph 109 ASCII considerations 573 ASSIGN clause 574 CODE-SET clause 575 environment division 573 procedure division 575 ASCII standard 577 ASIN function 470 ASSIGN clause ASCII considerations 574 description 122 format 119 SELECT clause and 121 assigning index values 402 assignment-name 10 ASSIGN clause 122 RERUN clause 138 assistive technologies xi asterisk (*) comment line 46 insertion character 201 AT END phrase READ statement 384 RETURN statement 392 SEARCH statement 397 AT END-OF-PAGE phrases 439 at-end condition READ statement 387 RETURN statement 392 ATAN function 471 AUTHOR paragraph description 99 format 91
BLOCK CONTAINS clause description 162 format 157 branching GO TO statement 329 out-of-line PERFORM statement BY CONTENT phrase CALL statement 297 BY REFERENCE phrase CALL statement 297 BY VALUE phrase CALL statement 298 INVOKE statement 347 byte order mark 220
374
C
CALL statement CANCEL statement and 302 description and format 295 linkage section 238 ON OVERFLOW phrase 295 procedure division header 235, 238 program termination 295 subprogram linkage 295 transfer of control 70 USING phrase 238 called and calling programs, description 295 CANCEL statement 302 carriage control character 438 category of data alphabetic items 193 alphanumeric items 195 alphanumeric-edited items 195 DBCS items 195 national items 195 numeric items 193 numeric-edited items 194 relationship to class of data 153 CBL (PROCESS) statement 506 CCSID 5 century window definition 73 CHAR function 471 character code set, specifying 109 character encoding unit 5 character sets 5 character-strings 7 COBOL words 7 representation in PICTURE clause 192 size determination 155 CHARACTERS BY phrase 340 CHARACTERS phrase BLOCK CONTAINS clause 162 INSPECT statement 338 MEMORY SIZE clause 105 USAGE clause and 162 characters, valid in COBOL program 3 checkpoint processing, RERUN clause 138 class 83 class and category of functions 153 of group items 153 of literals 153
B
B insertion character 198 symbol in PICTURE clause 188 basic character set 3 BASIS statement 505 basis-name 50 batch compile 78 BEFORE phrase INSPECT statement 343 PERFORM statement 376 with REPLACING 340 with TALLYING 338 WRITE statement 438 big-endian 5, 220 binary arithmetic operators 242 binary data item, DISPLAY statement 313 BINARY phrase in USAGE clause 216 binary search 399 blank lines 47 BLANK WHEN ZERO clause description and format 173 INDEX phrase in USAGE clause 219
CLASS clause 112 class condition 247, 248 class definition class procedure division 233 CLASS-ID paragraph 96 configuration section 103 description 83 effect of SELF and SUPER 345 identification division 92 requirements for indexed tables 183 class identification division 91, 96 class name, OO 51 class procedure division 233 CLASS-ID paragraph 96 class-name 9, 51 class-name class test 248 classes of data 153 clauses 40 CLOSE statement format and description 304 COBOL class definition 83 language structure 3 method definition 87 program structure 77 reference format 41 COBOL classes 83 COBOL objects 83 COBOL standards 577 COBOL words 7 with DBCS characters 7 with single-byte characters 7 code page names 5 code pages 5 CODE-SET clause ALPHABET clause and 111 ASCII considerations 575 description 170 format 157 NATIVE phrase and 170 CODEPAGE compiler option 5 collating sequence ASCENDING/DESCENDING KEY phrase and 183 ASCII 552 EBCDIC 549 specified in OBJECT-COMPUTER paragraph 105 specified in SPECIAL-NAMES paragraph 109 COLLATING SEQUENCE phrase 105 ALPHABET clause 109 MERGE statement 355 SORT statement 411 colon character description 36 required use of 514 column 7 indicator area 44 specifying comments 46 combined condition description 263 evaluation rules 264 logical operators and evaluation results 264 order of evaluation 265 permissible element sequences 264
604
Language Reference
comma (,) DECIMAL-POINT IS COMMA clause 114 insertion character 198 comment lines description 46 in identification division 99 in library text 510 comments 34 COMMON clause 96 common processing facilities 278 COMP-1 through COMP-5 data items 217 comparison alphanumeric operands 257 cycle, INSPECT statement 343 DBCS operands 259 in EVALUATE statement 323 numeric and alphanumeric operands 258 numeric operands 255 of index data items 258 of index-names 258 of national and other operands 259 of national operands 259 rules for COPY statement 512 compatible date field definition 73 compiler limits 545 compiler options 506 ADV 439 controlling output from 506 DATEPROC 71 NUMPROC 261 specifying 506 THREAD 183 TRUNC 155 Compiler options CODEPAGE 5 PGMNAME 302 compiler-directing statements 46, 505 *CBL (*CONTROL) 506 *CONTROL (*CBL) 506 BASIS 505 CBL (PROCESS) 506 COPY 508 DELETE 515 EJECT 516 ENTER 516 INSERT 517 PROCESS (CBL) 506 READY TRACE 517 REPLACE 518 RESET TRACE 517 SERVICE LABEL 522 SERVICE RELOAD 522 SKIP1 522 SKIP2 522 SKIP3 522 TITLE 523 USE 524 complex conditions abbreviated combined relation 265 combined condition 263 description 262 negated simple 263
complex OCCURS DEPENDING ON (CODO) 186 composite of operands 276 COMPUTATIONAL data items 216 COMPUTATIONAL phrases in USAGE clause 217 COMPUTE statement common phrases 273 description and format 308 computer-name 9, 10, 104 condition abbreviated combined relation 265 class 247 combined 263 complex 262 condition-name 249 EVALUATE statement 322 IF statement 331 negated simple 263 PERFORM UNTIL statement 376 relation 250 SEARCH statement 398 sign 261 simple 246 switch-status 262 condition-name 9, 50, 59 and conditional variable 172 description and format 249 rules for values 226 SEARCH statement 400 SET statement 405 SPECIAL-NAMES paragraph 109 switch status condition 109 conditional expression comparing index-names and index data items 258 comparison of DBCS operands 259 description 246 order of evaluation of operands 264 parentheses in abbreviated combined relation conditions 266 conditional statements description 270 GO TO statement 329 IF statement 331 list of 270 PERFORM statement 376 conditional variable 172 configuration section description (programs, classes, methods) 103 REPOSITORY paragraph 114 SOURCE-COMPUTER paragraph 104 SPECIAL-NAMES paragraph 106 conformance rules SET...USAGE OBJECT REFERENCE 407 contained programs 77 continuation area 41 lines 44, 46 CONTINUE statement 310 CONTROL statement (*CONTROL) 506 control transfer 69 conversion of data, DISPLAY statement 313
CONVERTING phrase 341 COPY libraries 56 COPY statement comparison rules 512 description and format 508 example 513 replacement rules 512 REPLACING phrase 511 SUPPRESS option 511 CORRESPONDING (CORR) phrase ADD statement 292 description 292 MOVE statement 359 SUBTRACT statement 426 with ON SIZE ERROR phrase 275 COS function 471 COUNT IN phrase UNSTRING statement 430 XML GENERATE statement 446 CR (credit) insertion character 199 symbol in PICTURE clause 190 cs (currency symbol) in PICTURE clause 188 CURRENCY SIGN clause description 112 Euro currency sign 112 NUMVAL-C function, restrictions 489 currency sign value 112 currency symbol in PICTURE clause 190 specifying in CURRENCY SIGN clause 112 currency symbol, default ($) 199 CURRENT-DATE function 472
D
data alignment 154 categories 153, 154, 193 classes 153, 154 hierarchies used in qualification 151 organization 127 signed 156 truncation of 155, 181 data category alphabetic items 193 alphanumeric items 195 alphanumeric-edited items 195 DBCS items 195 national items 195 numeric items 193 numeric-edited items 194 data conversion, DISPLAY statement 313 data description entry BLANK WHEN ZERO clause 173 data-name 173 DATE FORMAT clause 174 description and format 171 FILLER phrase 173 GLOBAL clause 180 indentation and 153 JUSTIFIED clause 180
Index
605
data description entry (continued) level-66 format (previously defined items) 172 level-88 format (conditionnames) 172 level-number description 172 OCCURS clause 181 OCCURS DEPENDING ON (ODO) clause 184 PICTURE clause 187 REDEFINES clause 202 RENAMES clause 205 SIGN clause 207 SYNCHRONIZED clause 208 USAGE clause 214 USAGE IS NATIONAL clause and 180 VALUE clause 223 data division ASCII considerations 574 data description entry 171 data relationships 150 file description (FD) entry 160 in factory definition 145 in object definition 145 levels of data 151 linkage section 149 local-storage section 148 sort description (SD) entry 160 working-storage section 147 data division names 57 data flow STRING statement 422 UNSTRING statement 432 data item data description entry 171 description entry definition 147 EXTERNAL clause 179 record description entry 171 data item description entry 148 data manipulation statements ACCEPT 286 INITIALIZE 333 list of 277 MOVE 359 overlapping operands 277 READ 383 RELEASE 389 RETURN 391 REWRITE 393 SET 402 STRING 420 UNSTRING 428 WRITE 436 data organization access modes and 131 indexed 127 line-sequential 128 relative 128 sequential 127 DATA RECORDS clause description 167 format 157 data transfer 286 data types instance data 150 object instance data 150
data units factory data 150 file data 149 method data 150 program data 150 data-name data description entry 173 data-names 50 precedence if duplicate 145 DATE 288 date field addition 244 arithmetic 243 compatible 73 DATE FORMAT clause 174 DATEPROC compiler option 71 DATEVAL function 474 definition 72 expansion of windowed date fields before use 175 group items that are date fields 177 in relation conditions 251 in sign conditions 261 MOVE statement, behavior in 363 nondate 73 purpose 71 restrictions 176 size errors 245, 274 storing arithmetic results 245 subtraction 244 trigger values 176 UNDATE function 497 windowed date field conditional variables 250 date format definition 72 DATE FORMAT clause 174 combining with other clauses 176 date functions 466 DATE YYYYMMDD 288 DATE-COMPILED paragraph description 99 format 91 DATE-OF-INTEGER function 473 DATE-TO-YYYYMMDD function 474 DATE-WRITTEN paragraph description 99 format 91 DATEPROC compiler option 71 DATEVAL function 474 DAY 288 DAY YYYYDDD 289 DAY-OF-INTEGER function 475 DAY-OF-WEEK 289 DAY-TO-YYYYDDD function 476 DB (debit) insertion character 199 symbol in PICTURE clause 190 DBCS (Double-Byte Character Set) class and category 153 elementary move rules 362 PICTURE clause and 195 use with relational operators 253 using in comments 99 DBCS arguments 462 DBCS character set 3
DBCS characters in COBOL words 8 in literals 27 DBCS class condition 248 DBCS items in ACCEPT 286 DBCS literals 30 in ACCEPT 286 DBCS notation xv de-editing 362 DEBUG-CONTENTS 15 DEBUG-ITEM special register 14, 558 DEBUG-LINE 15 DEBUG-NAME 15 debugging 557 DEBUGGING declarative 524, 528 debugging lines 47, 104, 557 DEBUGGING MODE clause 104, 528, 557 debugging sections 557 decimal point (.) 273 DECIMAL-POINT IS COMMA clause description 114 declarative procedures description and format 238 PERFORM statement 373 USE statement 239 declaratives DEBUGGING 528 EXCEPTION/ERROR 524 LABEL 526 precedence rules for nested programs 526 DECLARATIVES key word begin in Area A 43 description 239 declaratives section 238 DELETE statement description and format 515 dynamic access 311 format and description 311 INVALID KEY phrase 311 random access 311 sequential access 311 DELIMITED BY phrase STRING 421 UNSTRING statement 429 delimited scope statement 271 delimiter INSPECT statement 340 UNSTRING statement 429 DELIMITER IN phrase, UNSTRING statement 430 DEPENDING phrase GO TO statement 329 OCCURS clause 184 derived class 84 DESCENDING KEY phrase 182 collating sequence 183 description 353 MERGE statement 353 SORT statement 410 DISPLAY phrase in USAGE clause 218 DISPLAY statement description and format 313 external 155, 196 DISPLAY-OF function 477
606
Language Reference
DIVIDE statement common phrases 273 description and format 316 REMAINDER phrase 318 division header format, environment division 103 format, identification division 91 format, procedure division 235 specification of 42 DO-UNTIL structure, PERFORM statement 376 DO-WHILE structure, PERFORM statement 376 Double-Byte Character Set (DBCS) class and category 153 PICTURE clause and 195 use with relational operators 253 using in comments 99 DOWN BY phrase, SET statement 403 duplicate data-names, precedence 145 DUPLICATES phrase SORT statement 411 dynamic access mode data organization and 131 DELETE statement 311 description 131 READ statement 388
E
E, symbol in PICTURE clause 188 EBCDIC code page 1140 549 CODE-SET clause and 170 collating sequence 549 specifying in SPECIAL-NAMES paragraph 109 editing fixed insertion 199 floating insertion 200 replacement 201 signs 156 simple insertion 198 special insertion 198 suppression 201 editing sign control symbol 190 eject page 46 EJECT statement 516 elementary item alignment rules 154 alphanumeric operand comparison 258 basic subdivisions of a record 151 classes and categories 153 MOVE statement 360 size determination in program 155 size determination in storage 155 elementary items 151 elementary move rules 360 ELSE NEXT SENTENCE phrase 331 encoding units 5 end class marker 43 END DECLARATIVES key word 239 end markers 43 end method marker 43 END PROGRAM 78 end program marker 43
END-ADD phrase 292 END-CALL phrase 301 END-IF phrase 331 END-INVOKE phrase 349 end-of-file processing 304 END-OF-PAGE phrases 439 END-PERFORM phrase 375 END-SUBSTRACT phrase 427 END-XML phrase XML GENERATE statement 446 XML PARSE statement 453 entries 39 entry definition 39 ENTRY statement description and format 320 subprogram linkage 320 environment division ASCII considerations 573 configuration section ALPHABET clause 109 CURRENCY SIGN clause 112 OBJECT-COMPUTER paragraph 104 REPOSITORY paragraph 114 SOURCE-COMPUTER paragraph 104 SPECIAL-NAMES paragraph 106, 112 SYMBOLIC CHARACTERS clause 111 input-output section FILE-CONTROL paragraph 118 REPOSITORY paragraph 114 environment-name 9, 287, 442 SPECIAL-NAMES paragraph 108 EOP phrases 439 equal sign (=) 250 EQUAL TO relational operator 250 Euro currency sign 550 specifying in CURRENCY SIGN clause 112 EVALUATE statement comparing operands 323 determining truth value 322 format and description 321 evaluation rules combined conditions 264 EVALUATE statement 323 nested IF statement 332 EXCEPTION/ERROR declarative 524 CLOSE statement 305 DELETE statement 311 description and format 524 execution flow ALTER statement 293 PERFORM statement 373 EXIT METHOD statement format and description 326 EXIT PROGRAM statement format and description 327 EXIT statement format and description 325 PERFORM statement 374 expanded date field definition 72
expanded year definition 72 expansion of windowed date fields before use 175 explicit scope terminators 271 explicit attributes, of data 66 exponentiation exponential expression 241 expression, arithmetic 241 EXTEND phrase OPEN statement 368 extended character set 3 extension language elements 533 EXTERNAL clause with data item 179 with file name 161 external decimal item DISPLAY statement 313 external floating-point alignment rules 155 DISPLAY statement 313 PICTURE clause and 196 external floating-point in ACCEPT 286 external-class-name 9, 115
F
FACTORIAL function 478 factory data 84 factory data division 145 data division 145 factory data divsion 145 factory definition FACTORY paragraph 97 format and description 86 factory identification division 91, 97 factory method 84, 88 FACTORY paragraph 97 factory procedure division header 235 factory working-storage 148 FALSE phrase 322 FD (file description) entry BLOCK CONTAINS clause 162 DATA RECORDS clause 167 description 160 format 157 GLOBAL clause 161 LABEL RECORDS clause 166 level indicator 151 VALUE OF clause 166 figurative constant ALL literal 12 DISPLAY statement 314 HIGH-VALUE/HIGH-VALUES 11 LOW-VALUE/LOW-VALUES 11 NULL/NULLS 12 QUOTE/QUOTES 12 SPACE/SPACES 11 STOP statement 419 STRING statement 421 symbolic-character 12 UNSTRING statement 429 ZERO/ZEROS/ZEROES 11 figurative constants 11 file definition 149 Index
607
file (continued) labels 166 file organization definition 131 LINAGE clause 167 line-sequential 128 types of 127 file position indicator description 284 READ statement 387 file section 146, 160 EXTERNAL clause 161 RECORD clause 163 FILE STATUS clause DELETE statement and 311 description 135 file status key 278 format 119 INVALID KEY phrase and 282 file status key common processing facility 278 value and meaning 278 FILE-CONTROL paragraph ASSIGN clause 122 description and format 118 FILE STATUS clause 135 ORGANIZATION clause 126 PADDING CHARACTER clause 129 RECORD KEY clause 132 RELATIVE KEY clause 134 RESERVE clause 126 SELECT clause 121 file-description-entry 146 file-name 50 file-name, specifying on SELECT clause 121 FILLER phrase 171 CORRESPONDING phrase 173 data description entry 173 fixed insertion editing 199 fixed-length item, maximum length 171 records 162 floating insertion editing 200 floating-point DISPLAY statement 313 internal 155 floating-point literals 29 FOOTING phrase of LINAGE clause 167 FOR REMOVAL phrase 304, 305 format notation, rules for xiii FROM phrase ACCEPT statement 286 REWRITE statement 393 SUBTRACT statement 425 with identifier 283 WRITE statement 438 function arguments 462 class and category 153 description 459 function arguments 462 function definitions 465 function pointer 174, 218 in SET statement 402 function type 460
function-identifier 66 function-names 10 function-pointer data items relation condition 254 SET statement 406 FUNCTION-POINTER phrase in USAGE clause 218 functions class and category of 153 rules for usage 461 types of functions 460
G
G, symbol in PICTURE clause 188 garbage collection 83 GIVING phrase ADD statement 291 arithmetic 273 DIVIDE statement 319 MERGE statement 356 MULTIPLY statement 366 SORT statement 413 SUBTRACT statement 426 GLOBAL clause with data item 180 with file name 161 GO TO statement 293 altered 330 conditional 329 format and description 329 MORE-LABELS 330 SEARCH statement 397 unconditional 329 GO TO, DEPENDING ON phrase 293 GOBACK statement 328 graphic character 5 GREATER THAN OR EQUAL TO symbol (>=) 250 GREATER THAN symbol (>) 250 group items 151 alphanumeric operand comparison 258 class and category of 153 description 151 MOVE statement 364 group move rules 364
H
halting execution 419 hexadecimal notation for alphanumeric literals 27 for national literals 32 hiding 99 HIGH-VALUE/HIGH-VALUES 11 HIGH-VALUE(S) figurative constant hyphen (-), in indicator area 44
111
I
I-O-CONTROL paragraph APPLY WRITE-ONLY clause 142 checkpoint processing in 138 description 117, 136 MULTIPLE FILE TAPE clause 141
I-O-CONTROL paragraph (continued) order of entries 137 RERUN clause 138 SAME AREA clause 139 SAME RECORD AREA clause 140 SAME SORT AREA clause 141 SAME SORT-MERGE AREA clause 141 IBM extensions xii, 533 identification division CLASS-ID paragraph 96 FACTORY paragraph 97 format (program, class, method) 91 METHOD-ID paragraph 98 OBJECT paragraph 98 optional paragraphs 99 PROGRAM-ID paragraph 94 identifier 57, 239, 241 IF statement 331 imperative statement 268 implementor-name 9 implicit redefinition of storage area 160, 203 scope terminators 272 implicit attributes, of data 66 in-line PERFORM statement 373 indentation 44, 153 index data item 258, 359 relative indexing 63 SET statement 63 index data item 61 index name assigning values 402 comparisons 258 OCCURS clause 184 PERFORM statement 382 SET statement 402 INDEX phrase in USAGE clause 219 index-name 51, 60 INDEXED BY phrase 183 indexed files CLOSE statement 305 DELETE statement 311 FILE-CONTROL paragraph format 119 I-O-CONTROL paragraph format 137 organization 127 permissible statements for 371 READ statement 387 REWRITE statement 394 START statement 417 indexed organization description 127 FILE-CONTROL paragraph format 119 I-O-CONTROL paragraph format 137 indexing description 63 MOVE statement evaluation 360 OCCURS clause 63, 181 relative 63 SET statement and 63 indicator area 41 industry specifications 577
608
Language Reference
inheritance 84, 97 INHERITS clause 96 INITIAL clause 96 initial state of program 96 INITIALIZE statement format and description 333 overlapping operands, unpredictable results 277 input file, label processing 369 INPUT phrase OPEN statement 368 USE statement 524 INPUT PROCEDURE phrase RELEASE statement 389 SORT statement 413 Input-Output section description 117 file control paragraph 117 FILE-CONTROL paragraph 118 format 117 I-O-CONTROL paragraph 136 input-output statements ACCEPT 286 CLOSE 304 common processing facilities 278 DELETE 311 DISPLAY 313 EXCEPTION/ERROR procedures 525 general description 277 OPEN 367 READ 383 REWRITE 393 START 416 WRITE 436 INSERT statement 517 insertion editing fixed (numeric-edited items) 199 floating (numeric-edited items) 200 simple 198 special (numeric-edited items) 198 INSPECT statement AFTER phrase 340 BEFORE phrase 340 comparison cycle 343 CONVERTING phrase 341 overlapping operands, unpredictable results 277 REPLACING phrase 338 INSTALLATION paragraph description 99 format 91 instance data 83, 87 instance definition format and description 86 instance method 83, 87 instance variable 85 integer arguments 462, 463 INTEGER function 479 integer functions 461, 462 INTEGER-OF-DATE function 479 INTEGER-OF-DAY function 480 INTEGER-PART function 480 internal floating-point alignment rules 155 DISPLAY statement 313
INTO phrase DIVIDE statement 316 READ statement 383 RETURN statement 391 STRING statement 421 UNSTRING statement 430 with identifier 283 intrinsic functions 459 ACOS 469 alphanumeric functions 460 ANNUITY 470 ASIN 470 ATAN 471 CHAR 471 COS 471 CURRENT-DATE 472 DATE-OF-INTEGER 473 DATE-TO-YYYYMMDD 474 DATEVAL 474 DAY-OF-INTEGER 475 DAY-TO-YYYYDDD 476 DISPLAY-OF 477 FACTORIAL 478 floating-point literals 463 INTEGER 479 integer functions 460 INTEGER-OF-DATE 479 INTEGER-OF-DAY 480 INTEGER-PART 480 LENGTH 481 LOG 482 LOG10 482 LOWER-CASE 482 MAX 483 MEAN 484 MEDIAN 484 MIDRANGE 485 MIN 485 MOD 486 national functions 460 NATIONAL-OF 487 numeric functions 460 NUMVAL 488 NUMVAL-C 489 ORD 490 ORD-MAX 491 ORD-MIN 491 PRESENT-VALUE 492 RANDOM 493 RANGE 493 REM 494 REVERSE 494 SIN 495 SQRT 495 STANDARD-DEVIATION 496 SUM 496 summary of 466 TAN 497 UNDATE 497 UPPER-CASE 497 VARIANCE 498 WHEN-COMPILED 499 YEAR-TO-YYYY 500 YEARWINDOW 501 invalid key condition 282 INVALID KEY phrase DELETE statement 311
INVALID KEY phrase (continued) READ statement 384 REWRITE statement 394 START statement 416 WRITE statement 440 INVOKE statement BY VALUE phrase 347 format and description 345 LENGTH OF special register 347 NEW phrase 346 NOT ON EXCEPTION phrase 349 ON EXCEPTION phrase 349 RETURNING phrase 347 SELF special object identifier 345 SUPER special object identifier 345 USING phrase 347 ISCII processing considerations 573 ISCII standard 577 ISO COBOL standards 577
J
Java class-name 115 package 115 Java classes 83 Java interoperability 83 data types 347, 349, 351 literal types 347 Java interoperation 83 Java Native Interface (JNI) 16, 83, 85 Java objects 83 Java String data 83 java.lang.Object 85 JNI environment pointer 85 JNIENVPTR special register 16, 85 JUSTIFIED clause description and format 180 effect on initial settings 181 STRING statement 421 truncation of data 181 USAGE IS INDEX clause and 180 VALUE clause and 224
K
Kanji 248 key of reference 127 KEY phrase OCCURS clause 182 READ statement 384 SEARCH statement 397 SORT statement 410 START statement 416 keyboard navigation xi
L
LABEL declarative 524, 526 label processing, OPEN statement 369 LABEL RECORDS clause description 166 format 157 Language Environment Callable Services description 295 language-name 9 Index
609
LEADING phrase INSPECT statement 338, 340 SIGN clause 208 LENGTH function 481 LENGTH OF special register 16 INVOKE statement 347 LESS THAN OR EQUAL TO symbol (<=) 251 LESS THAN symbol (<) 250 level 01 item 151 02-49 item 151 66 item 153 77 item 153 88 item 153 indicator, definition of 151 level indicator (FD and SD) 43 level-number 46, 171 (01 and 77) 43 definition 151 description and format 172 FILLER phrase 173 library-name 9, 50 COPY statement 509 limit values, date field 176 limits of the compiler 545 LINAGE clause 439 description 167 diagram of phrases 168 format 157 LINAGE-COUNTER special register description 17 WRITE statement 439 line advancing 438 line-sequential file organization 128 LINE/LINES, WRITE statement 438 LINES AT BOTTOM phrase 167 LINES AT TOP phrase 167 linkage section called subprogram 238 description 149 requirement for indexed items 183 VALUE clause 223 list of resources 601 literal alphanumeric operand comparison 258 and arithmetic expressions 241 ASSIGN clause 122 CODE-SET clause and ALPHABET clause 111 CURRENCY SIGN clause 112 description 25 null-terminated alphanumeric 28 STOP statement 419 VALUE clause 224 literals, class and category of 153 little-endian 220 local-storage 148 defining with RECURSIVE clause 95 requirement for indexed items 183 LOG function 482 LOG10 function 482 logical operator complex condition 262
logical operator (continued) in evaluation of combined conditions 264 list of 262 logical record definition 149 file data 149 program data 150 record description entry and 150 RECORDS phrase 163 LOW-VALUE/LOW-VALUES 11 LOW-VALUE(S) figurative constant 111 LOWER-CASE function 482
M
MAX function 483 maximum index value 63 MEAN function 484 MEDIAN function 484 MEMORY SIZE clause 105 MERGE statement ASCENDING/DESCENDING KEY phrase 353 COLLATING SEQUENCE phrase 355 format and description 353 GIVING phrase 356 OUTPUT PROCEDURE phrase 357 USING phrase 356 method data division 145 method definition data division 145 effect of SELF and SUPER 345 format and description 87 identification division 94 inheritance rules 97 method procedure division 233 METHOD-ID paragraph 98 method hiding 99 method identification division 91, 98 method local-storage 148 method overloading 98 method overriding 98 method procedure division 233, 234 method procedure division header 236 method working-storage 147 METHOD-ID paragraph 98 method-name 50 methods available to subclasses 97 exiting 326 invoking 345 recursively reentering 95 reusing 96 MIDRANGE function 485 millennium language extensions syntax 71 millennium language extensions (MLE) description 71 MIN function 485 minus sign (-) COBOL character 3 fixed insertion symbol 199 floating insertion symbol 200, 201 SIGN clause 208 mnemonic-name 9, 51, 286
mnemonic-name (continued) ACCEPT statement 286 DISPLAY statement 314 SET statement 404 SPECIAL-NAMES paragraph 109 WRITE statement 438 MOD function 486 MORE-LABELS GO TO statement 330 MOVE statement CORRESPONDING phrase 359 elementary moves 360 format and description 359 group moves 364 record area 364 MULTIPLE FILE TAPE clause 141 multiple record processing, READ statement 385 multiple results, arithmetic statements 277 MULTIPLY statement common phrases 273 format and description 365 multivolume files READ statement 386 WRITE statement 441
N
N, symbol in PICTURE clause 188 national arguments 463 national class and category 153 national data items 195, 219 alignment of 155 elementary move rules 361 in a class condition 247 in ACCEPT 286 in SEARCH statement 400 in UNSTRING statement 428 national functions 460, 461 national literals 3, 31 in ACCEPT 286 national literals in hexadecimal notation 32 NATIONAL phrase in USAGE clause 219 NATIONAL-OF function 487 native binary data item 217 native character set 109 native collating sequence 109 negated combined condition 263 negated simple condition 263 NEGATIVE in sign condition 261 nested IF structure description 332 EVALUATE statement 321 nested programs description 77 precedence rules for 526 NEW phrase INVOKE statement 346 NEXT RECORD phrase, READ statement 383 NEXT SENTENCE phrase IF statement 331 SEARCH statement 398 NO ADVANCING phrase, DISPLAY statement 314
610
Language Reference
NO REWIND phrase 304 OPEN statement 368 nondate definition 73 nonreel file, definition 305 NOT AT END phrase READ statement 384 RETURN statement 392 NOT INVALID KEY phrase DELETE statement 311 READ statement 385 REWRITE statement 394 START statement 416 NOT ON EXCEPTION phrase CALL statement 300 INVOKE statement 349 XML GENERATE statement 446 XML PARSE statement 453 NOT ON OVERFLOW phrase STRING statement 422 UNSTRING statement 432 NOT ON SIZE ERROR phrase ADD statement 292 DIVIDE statement 319 general description 274 MULTIPLY statement 366 SUBTRACT statement 427 Notices 579 NSYMBOL compiler option 3 null block branch, CONTINUE statement 310 null-terminated alphanumeric literals NULL/NULLS data pointer 254, 405 figurative constant 12, 228 function-pointer 255, 407 object reference 255, 408 procedure-pointer 255, 407 numeric arguments 462, 463 numeric class and category 153 NUMERIC class test 248 numeric functions 460, 461 numeric item 193 numeric literals 29 numeric operands, comparing 255 numeric-edited item alignment rules 154 editing signs 156 elementary move rules 361 PICTURE clause 194 NUMVAL function 488 NUMVAL-C function 489
28
O
object data division 145 object definition OBJECT paragraph 98 object identification division 91, 98 OBJECT paragraph 98 object program 77 object reference 85 in SET statement 402 OBJECT REFERENCE phrase 220 object working-storage 147 OBJECT-COMPUTER paragraph 104 object-oriented class-name 51
object-oriented COBOL class definition 83 comparison rules 255 conformance rules SET...USAGE OBJECT REFERENCE 407 effect of GLOBAL clause 147 factory definition 86 identification division (class and method) 91 INHERITS clause 96 INVOKE statement 345 method definition 87 method-name 50 object definition 86 OBJECT REFERENCE phrase in USAGE clause 220 OO class name 51 procedure division (class and method) 233 REPOSITORY paragraph 114 SELF and SUPER special object identifiers 10 specifying configuration section 103 subclasses and methods 97 objects in EVALUATE statement 322 obsolete language elements xii OCCURS clause ASCENDING/DESCENDING KEY phrase 182 description 181 INDEXED BY phrase 183 restrictions 181 variable-length tables format 184 OCCURS DEPENDING ON (ODO) clause complex 186 description 185 format 184 object of 185 RECORD clause 163 REDEFINES clause and 181 SEARCH statement and 181 subject and object of 185 subject of 181, 185 subscripting 61 OFF phrase, SET statement 404 OMITTED phrase 297, 298 ON EXCEPTION phrase CALL statement 300 INVOKE statement 349 XML GENERATE statement 446 XML PARSE statement 453 ON OVERFLOW phrase CALL statement 300 STRING statement 421, 432 ON phrase, SET statement 404 ON SIZE ERROR phrase ADD statement 292 arithmetic statements 274 COMPUTE statement 309 DIVIDE statement 319 MULTIPLY statement 366 SUBTRACT statement 427 OPEN statement for new/existing files 368 format and description 367
OPEN statement (continued) I-O phrase 368 label processing 369 phrases 367 programming notes 370 system dependencies 371 operands comparison of alphanumeric 257 comparison of numeric 255 composite of 276 overlapping 277 operation of XML GENERATE statement 447 operational sign algebraic, description of 156 SIGN clause and 156 USAGE clause and 156 optional words, syntax notation xiii ORD function 490 ORD-MAX function 491 ORD-MIN function 491 order of entries clauses in FILE-CONTROL paragraph 118 I-O-CONTROL paragraph 137 order of evaluation in combined conditions 265 ORGANIZATION clause description 126 format 119 INDEXED phrase 127 LINE SEQUENTIAL phrase 127 RELATIVE phrase 127 SEQUENTIAL phrase 127 out-of-line PERFORM statement 374 outermost programs, debugging 528 output file, label processing 370 OUTPUT phrase 368 OUTPUT PROCEDURE phrase MERGE statement 357 RETURN statement 391 SORT statement 414 OVERFLOW phrase CALL statement 300 STRING statement 421, 432 overlapping operands invalid in arithmetic statements 277 data manipulation statements 277 overloading 98 overriding 98
P
P, symbol in PICTURE clause 189 PACKED-DECIMAL phrase in USAGE clause 217 PADDING CHARACTER clause 129 page eject 46 paragraph description 39, 239 header, specification of 42 termination, EXIT statement 325 paragraph-name 9, 50 description 239 specification of 42 parent class 84
Index
611
parentheses combined conditions, use 264 in arithmetic expressions 242 partial listings 506 PASSWORD clause description 135 system dependencies 135 PERFORM statement branching 374 conditional 376 END-PERFORM phrase 375 EVALUATE statement 321 execution sequences 374 EXIT statement 325 format and description 373 in-line 374 out-of-line 374 TIMES phrase 375 VARYING phrase 377, 379 period (.) actual decimal point 198 PGMNAME compiler option CANCEL statement 302 phrase, definition 40 phrases 40 physical record BLOCK CONTAINS clause 162 definition 149 file data 149 file description entry and 150 RECORDS phrase 163 PICTURE character-strings 33 PICTURE clause and class condition 248 computational items and 216 CURRENCY SIGN clause 112 data categories in 193 DECIMAL-POINT IS COMMA clause 114, 187 description 187 editing 197 format 187 sequence of symbols 190 symbols used in 187 PICTURE SYMBOL phrase 113 picture symbols 188 plus (+) fixed insertion symbol 199 floating insertion symbol 200, 201 insertion character 201 SIGN clause 208 pointer data items relation condition 253 SET statement 405 USAGE clause 221 POINTER phrase STRING statement 421 UNSTRING statement 431 POINTER phrase in USAGE clause 221 POSITIVE in sign condition 261 PRESENT-VALUE function 492 print files, WRITE statement 442 priority-number 106 procedure branching GO TO statement 329 statements, executed sequentially 285 procedure branching statements 285
procedure division ASCII considerations 575 declarative procedures 239 format (programs, methods, classes) 233 header 235 statements 285 procedure division header RETURNING phrase 238 USING phrase 236 procedure division names 57 procedure-name GO TO statement 329 MERGE statement 357 PERFORM statement 373 SORT statement 413 procedure-pointer data items relation condition 254 SET statement 406 USAGE clause 222 PROCEDURE-POINTER phrase in USAGE clause 222 procedure, description 239 PROCESS (CBL) statement 506 PROCESSING PROCEDURE phrase, in XML PARSE 451 PROGRAM COLLATING SEQUENCE clause ALPHABET clause 109 SPECIAL-NAMES paragraph and 105 program data division 145 program identification division 91 program local-storage 148 program procedure division header 235 program termination GOBACK statement 328 STOP statement 419 PROGRAM-ID paragraph description 94 format 91 program-name 50 program-name, rules for referencing 80 program, separately compiled 77 programming interface information 580 programming notes ACCEPT statement 286 altered GO TO statement 293 arithmetic statements 277 data manipulation statements 420, 428 DELETE statement 311 EXCEPTION/ERROR procedures 526 OPEN statement 370 PERFORM statement 375 RECORD clause 163 STRING statement 420 UNSTRING statement 428 programming structures 376 programs, recursive 95 pseudo-text continuation rules 520 COPY statement operand 511 description 47 pseudo-text delimiters 37 punch files, WRITE statement 442
Q
qualification 55 quotation mark () character QUOTE/QUOTES 12 44
R
railroad track format, how to read xiii random access mode data organization and 131 DELETE statement 311 description 131 READ statement 387 RANDOM function 493 RANGE function 493 READ statement AT END phrases 384 dynamic access mode 388 format and description 383 INTO identifier phrase 283, 383 INVALID KEY phrase 282, 384 KEY phrase 384 multiple record processing 385 multivolume files 386 NEXT RECORD phrase 383 overlapping operands, unpredictable results 277 programming notes 388 random access mode 387 READY TRACE statement 517 receiving field COMPUTE statement 308 MOVE statement 359 multiple results rules 277 SET statement 402 STRING statement 421 UNSTRING statement 430 record area description 163 elementary items 151 fixed-length 162 logical, definition of 149 physical, definition of 149 record area MOVE statement 364 RECORD clause description and format 163 omission of 163 RECORD CONTAINS 0 CHARACTERS 164 record description entry levels of data 151 logical record 150 RECORD KEY clause description 132 format 119 record key in indexed file 312 record-name 50 RECORDING MODE clause 169 RECORDS phrase BLOCK CONTAINS clause 163 RERUN clause 139 RECURSIVE clause 95 recursive methods 345 recursive programs 95 requirement for indexed items 183
612
Language Reference
REDEFINES clause description 202 examples of 205 format 202 general considerations 204 OCCURS clause restriction 203 SYNCHRONIZED clause and 209 undefined results 205 VALUE clause and 204 redefinition, implicit 160 REEL phrase 304, 305 reference format 41 reference-modification description 64 MOVE statement evaluation 360 reference, methods of simple data 57 relation character COPY statement 511 INITIALIZE statement 333 INSPECT statement 338 relation condition abbreviated combined 265 comparison of numeric and alphanumeric operands 255 comparison with alphanumeric second operand 257 comparison with numeric second operand 256 description 250 operands of equal size 257 operands of unequal size 257 relational operator in abbreviated combined relation condition 266 meaning of each 251 relation condition use 250 relational operators 10 relative files access modes allowed 132 CLOSE statement 305 DELETE statement 311 FILE-CONTROL paragraph format 119 I-O-CONTROL paragraph format 137 organization 128 permissible statements for 371 READ statement 385 RELATIVE KEY clause 132, 134 REWRITE statement 395 START statement 417 RELATIVE KEY clause description 134 format 119 relative organization access modes allowed 132 description 128 FILE-CONTROL paragraph format 119 I-O-CONTROL paragraph format 137 RELEASE statement 277, 389 REM function 494 REMAINDER phrase of DIVIDE statement 318 RENAMES clause 153
RENAMES clause (continued) description and format 205 INITIALIZE statement 333 level 66 item 153, 205 PICTURE clause 187 repeated words, syntax notation xiii REPLACE statement comparison operation 520 continuation rules for pseudo-text 520 description and format 518 special notes 521 replacement editing 201 replacement rules for COPY statement 512 REPLACING phrase COPY statement 511 INITIALIZE statement 333 repository paragraph 116 REPOSITORY paragraph 114 required words, syntax notation xiii RERUN clause checkpoint processing 138 description 138 format 137 RECORDS phrase 138 sort/merge 139 RESERVE clause description 126 format 119 reserved words 10, 559 RESET TRACE statement 517 resolution of names 52 result field GIVING phrase 273 NOT ON SIZE ERROR phrase 274 ON SIZE ERROR phrase 274 ROUNDED phrase 273 RETURN statement AT END phrase 392 description and format 391 overlapping operands, unpredictable results 277 RETURN-CODE special register 18 RETURNING phrase CALL statement 299 INVOKE statement 347 procedure division header 238 reusing logical records 394 REVERSE function 494 REWRITE statement description and format 393 FROM identifier phrase 283 INVALID KEY phrase 394 ROUNDED phrase ADD statement 292 COMPUTE statement 309 description 273 DIVIDE statement 318 MULTIPLY statement 366 size error checking and 275 SUBTRACT statement 427 rules for syntax notation xiii run unit description 77 termination with CANCEL statement 303
S
S, symbol in PICTURE clause 189 SAME clause 139 SAME RECORD AREA clause description 140 format 137 SAME SORT AREA clause description 141 format 137 SAME SORT-MERGE AREA clause description 141 format 137 scope of names 49 scope terminator explicit 271 implicit 272 SD (sort file description) entry data division 160 DATA RECORDS clause 167 description 160 level indicator 151 SD (Sort File Description) entry description 157 SEARCH statement AT END phrase 397 binary search 399 description and format 396 INDEX phrase in USAGE clause 219 serial search 397 SET statement 397 VARYING phrase 398 WHEN phrase 397 section 39, 239 section header description 239 specification of 42 section-name 9, 50 description 239 in EXCEPTION/ERROR declarative 524 SECURITY paragraph description 99 format 91 SEGMENT-LIMIT clause 106 segmentation considerations 293 SELECT clause ASSIGN clause and 121 format 119 specifying a file name 121 SELECT OPTIONAL clause CLOSE statement 305 description 121 format 119 specification for sequential I-O files 121 selection objects in EVALUATE statement 322 selection subjects in EVALUATE statement 322 SELF 255 SELF special object identifier 10, 345 sending field MOVE statement 359 SET statement 402 STRING statement 420 UNSTRING statement 428 sentences 40 Index
613
sentences (continued) COBOL, definition 40 description 239 SEPARATE CHARACTER phrase of SIGN clause 208 separately compiled program 77 separators 35, 226 separators, rules for 35 sequence number area (cols. 1-6) 41 sequential access mode data organization and 131 DELETE statement 311 description 131 READ statement 385 REWRITE statement 394 sequential files access mode allowed 131 CLOSE statement 304, 305 description 127 file description entry 157 FILE-CONTROL paragraph format 119 LINAGE clause 167 OPEN statement 367 PASSWORD clause valid with 135 permissible statements for 370 READ statement 385 REWRITE statement 394 SELECT OPTIONAL clause 121 serial search PERFORM statement 377 SEARCH statement 397 SERVICE LABEL statement 522 SERVICE RELOAD statement 522 SET statement description and format 402 DOWN BY phrase 403 function-pointer data items 218, 406 index data item 219 INDEX phrase in USAGE clause 219 object reference data items 407 OFF phrase 404 ON phrase 404 overlapping operands, unpredictable results 277 pointer data items 405 procedure-pointer data items 406 requirement for indexed items 183 SEARCH statement 403 TO phrase 402 TO TRUE phrase 404 UP BY phrase 403 sharing data 180 sharing files 162 SHIFT-IN special register 18 SHIFT-OUT special register 18 sibling program 77 SIGN clause 207 sign condition 261 SIGN IS SEPARATE clause 208 signed numeric item, definition 194 operational signs 156 simple condition combined 263 description and types 246 negated 263
simple data reference 57 simple insertion editing 198 SIN function 495 size-error condition 274 skip to next page 46 SKIP1 statement 522 SKIP2 statement 522 SKIP3 statement 522 slack bytes between 213 within 211 slash (/) comment lines 46 insertion character 198 symbol in PICTURE clause 189 SORT statement ASCENDING KEY phrase 410 COLLATING SEQUENCE phrase 411 DESCENDING KEY phrase 410 description and format 409 DUPLICATES phrase 411 GIVING phrase 413 INPUT PROCEDURE phrase 413 OUTPUT PROCEDURE phrase 414 USING phrase 412 SORT-CONTROL special register 19, 415 SORT-CORE-SIZE special register 19, 415 SORT-FILE-SIZE special register 20, 415 SORT-MESSAGE special register 20, 415 SORT-MODE-SIZE special register 20, 415 SORT-RETURN special register 21, 415 Sort/Merge feature I-O-CONTROL paragraph format 137 MERGE statement 353 RELEASE statement 389 RERUN clause 139 RETURN statement 391 SAME SORT AREA clause 141 SAME SORT-MERGE AREA clause 141 SORT statement 409 Sort/Merge file statement phrases ASCENDING/DESCENDING KEY phrase 353 COLLATING SEQUENCE phrase 355 GIVING phrase 356 OUTPUT PROCEDURE phrase 357 USING phrase 356 source code library, programming notes 513 listing 507 source code format 41 source language debugging 557 source program standard COBOL reference format 41 SOURCE-COMPUTER paragraph 104 SPACE/SPACES 11 special insertion editing 198 special object identifiers SELF 10 SUPER 10 special registers 13
special registers (continued) ADDRESS OF 14 DEBUG-ITEM 14 JNIENVPTR 16 LENGTH OF 16 LINAGE-COUNTER 17 RETURN-CODE 18 SHIFT-OUT, SHIFT-IN 18 SORT-CONTROL 19 SORT-CORE-SIZE 19 SORT-FILE-SIZE 20 SORT-MESSAGE 20 SORT-MODE-SIZE 20 SORT-RETURN 21 TALLY 21 WHEN-COMPILED 21 XML-CODE 22 XML-EVENT 22 XML-NTEXT 24 XML-TEXT 24 SPECIAL-NAMES paragraph ACCEPT statement 286 ALPHABET clause 109 ASCII-encoded file specification 170 CLASS clause 112 CODE-SET clause and 170 CURRENCY SIGN clause 112 DECIMAL-POINT IS COMMA clause 114 description 106 format 106 mnemonic-name 109 SQRT function 495 standard alignment JUSTIFIED clause 181 rules 154 STANDARD-1 phrase 109 STANDARD-2 phrase 109 STANDARD-DEVIATION function 496 standards 577 START statement description and format 416 indexed file 417 INVALID KEY phrase 282, 416 relative files 417 status key considerations 416 statement operations common phrases 272 file position indicator 284 INTO and FROM phrases 283 statements 40 categories of 268 conditional 270 data manipulation 277 delimited scope 271 description 40, 239 imperative 268 input-output 277 procedure branching 285 static data 84 static method 84 status key common processing facility 278 file processing 525 STOP RUN statement 419 STOP statement 419
614
Language Reference
storage map listing 508 MEMORY SIZE clause 105 REDEFINES clause 202 STRING statement description and format 420 execution of 422 overlapping operands, unpredictable results 277 structure of the COBOL language 3 structured programming DO-WHILE and DO-UNTIL 376 subclass 84, 85 subclasses and methods 97 subjects in EVALUATE statement 322 subprogram linkage CALL statement 295 CANCEL statement 302 ENTRY statement 320 subprogram termination CANCEL statement 302 EXIT PROGRAM statement 327 GOBACK statement 328 subscripting definition and format 61 INDEXED BY phrase of OCCURS clause 183 MOVE statement evaluation 360 OCCURS clause specification 181 table references 61 using data-names 62 using index-names (indexing) 63 using integers 62 substitution characters DISPLAY-OF 477 NATIONAL-OF 487 substitution field of INSPECT REPLACING 338 substrings, specifying (reference-modification) 64 SUBTRACT statement common phrases 272 description and format 425 SUM function 496 SUPER special object identifier 10, 11, 345 superclass 84, 85 SUPPRESS option, COPY 511 suppress output 506 suppression editing 201 switch-status condition 262 SYMBOLIC CHARACTERS clause 111 symbolic-character 9, 12, 51 symbols in PICTURE clause 187 SYNCHRONIZED clause 208, 209 VALUE clause and 224 syntax notation, rules for xiii system considerations, subprogram linkage CALL statement 295 CANCEL statement 302 system information transfer, ACCEPT statement 287 system input device, ACCEPT statement 286 system-names 9, 104 computer-name 104
system-names (continued) SOURCE-COMPUTER paragraph 104
type conformance SET...USAGE OBJECT REFERENCE 407 types of functions 460
T
table references indexing 63 subscripting 61 TALLY special register 21 TALLYING phrase INSPECT statement 338 UNSTRING statement 431 TAN function 497 termination of execution EXIT METHOD statement 326 EXIT PROGRAM statement 327 GOBACK statement 328 STOP RUN statement 419 terminators, scope 271 text words 510 text-name 9, 51 literal-1 509 THREAD compiler option 183 requirement for indexed items 183 THROUGH (THRU) phrase ALPHABET clause 110 CLASS clause 112 EVALUATE statement 322 PERFORM statement 373 RENAMES clause 205 VALUE clause 225 TIME 289 TIMES phrase of PERFORM statement 375 TITLE statement 523 TO phrase, SET statement 402 TO TRUE phrase, SET statement 404 trademarks 580 transfer of control ALTER statement 293 explicit 69 GO TO statement 329 IF statement 332 implicit 69 PERFORM statement 373 XML PARSE statement 451 transfer of data ACCEPT statement 286 MOVE statement 359 STRING statement 420 UNSTRING statement 428 trigger values, date field 176 trimming of generated XML data 449 truncation of data arithmetic item 155 JUSTIFIED clause 181 ROUNDED phrase 273 TRUNC compiler option 155 truth value complex conditions 262 EVALUATE statement 322 IF statement 331 of complex condition 263 sign condition 261 with conditional statement 270
U
unary operator 242 unconditional GO TO statement 329 UNDATE function 497 Unicode 3, 5 uniqueness of reference 55 unit file, definition 305 UNIT phrase 304 universal object reference 220 unsigned numeric item, definition 194 UNSTRING statement description and format 428 execution 432 overlapping operands, unpredictable results 277 receiving field 430 sending field 428 UP BY phrase, SET statement 403 UPON phrase, DISPLAY 314 UPPER-CASE function 497 UPSI-0 through UPSI-7, program switches and switch-status condition 262 condition-name 109 processing special conditions 109 SPECIAL-NAMES paragraph 108 USAGE clause BINARY phrase 216 CODE-SET clause and 170 COMPUTATIONAL phrases 217 description 214 DISPLAY phrase 218 DISPLAY-1 phrase 218 elementary item size 155 format 214 FUNCTION-POINTER phrase 218 INDEX phrase 219 NATIONAL phrase 219 OBJECT REFERENCE phrase 215 operational signs and 156 PACKED-DECIMAL phrase 217 POINTER phrase 221 PROCEDURE-POINTER phrase 222 VALUE clause and 224 USAGE DISPLAY class condition identifier 247 STRING statement and 421 USAGE DISPLAY-1 STRING statement and 421 USAGE OBJECT REFERENCE phrase 345 USE FOR DEBUGGING declarative 558 USE statement format and description 524 user labels DEBUGGING declarative 528 LABEL declarative 526 user-defined words 8 USING phrase CALL statement 296 in procedure division header 235 INVOKE statement 347 Index
615
USING phrase (continued) MERGE statement 356 procedure division header SORT statement 412 subprogram linkage 238 UTF-16 3, 5
236
V
V, symbol in PICTURE clause 189 VALUE clause condition-name 225 effect on object-oriented programs 147 format 223, 225 level 88 item 153 NULL/NULLS figurative constant 219, 228 rules for condition-name entries rules for literal values 224 VALUE OF clause description 166 format 157 variable-length tables 184, 185 VARIANCE function 498 VARYING phrase PERFORM statement 377 SEARCH statement 398
XML GENERATE statement (continued) format conversion 448 operation 447 trimming 449 XML PARSE statement control flow 454 exception event 453 XML processing XML-CODE special register 22 XML-EVENT special register 22 XML-NTEXT special register 24 XML-TEXT special register 24 XML-CODE special register 22 use in XML GENERATE 446 use in XML PARSE 453 XML-EVENT special register 22, 454 XML-NTEXT special register 24, 455 XML-TEXT special register 24, 455 226
Y
year-last date field definition 72 YEAR-TO-YYYY function 500 YEARWINDOW compiler option century window 73 YEARWINDOW function 501
W
WHEN phrase EVALUATE statement 322 SEARCH statement 397 WHEN-COMPILED function 499 WHEN-COMPILED special register 21 windowed date field definition 72 expansion before use 175 WITH DEBUGGING MODE clause 104, 528, 557 WITH DUPLICATES phrase, SORT statement 411 WITH FOOTING phrase 167 WITH NO ADVANCING phrase 314 WITH NO REWIND phrase, CLOSE statement 305 WITH POINTER phrase STRING statement 421 UNSTRING statement 431 working-storage section 147 WRITE statement AFTER ADVANCING 438, 442 ALTERNATE RECORD KEY 443 BEFORE ADVANCING 438, 442 description and format 436 END-OF-PAGE phrases 439 FROM identifier phrase 283 sequential files 438
Z
Z insertion character 201 symbol in PICTURE clause 189 zero filling, elementary moves 360 suppression and replacement editing 201 ZERO in sign condition 261 ZERO/ZEROS/ZEROES 11
X
X, symbol in PICTURE clause 189 XML GENERATE statement element name formation 449 exception event 446
616
Language Reference
Readers Comments Wed Like to Hear from You

Enterprise COBOL for z/OS Language Reference Version 3 Release 3 Publication No. SC27-1408-02 Overall, how satisfied are you with the information in this book? Very Satisfied Overall satisfaction h Satisfied h Neutral h Dissatisfied h Very Dissatisfied h
How satisfied are you that the information in this book is: Very Satisfied Accurate Complete Easy to find Easy to understand Well organized Applicable to your tasks h h h h h h Satisfied h h h h h h Neutral h h h h h h Dissatisfied h h h h h h Very Dissatisfied h h h h h h
Please tell us how we can improve this book:
Thank you for your responses. May we contact you?
h Yes
h No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you.
Name Company or Organization Phone No.
Address
___________________________________________________________________________________________________
Readers Comments Wed Like to Hear from You

SC27-1408-02
Cut or Fold Along Line
Fold and _ _ _ _ _ _ _ _ _ _Fold and_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Tape _ _ _ _ _ _ _ _ Tape _ _ _ _ do not _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE
IBM Corporation H150/090 555 Bailey Avenue San Jose, CA U.S.A. 95141-9989
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape
SC27-1408-02
Cut or Fold Along Line
Program Number: 5655-G53
Printed in USA
SC27-1408-02

Cobol Lang Ref

Uploaded by

Copyright:

Available Formats

Cobol Lang Ref

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 Lang Ref

Uploaded by

Copyright:

Available Formats

Enterprise COBOL for z/OS

Enterprise COBOL for z/OS

Chapter 5. Sections and paragraphs . . 39

Part 1. COBOL language structure . . 1

Chapter 6. Reference format . . . . . 41

Chapter 7. Scope of names . . . . . . 49

Chapter 16. Input-Output section . . . 117

Part 2. COBOL source unit structure . . . . . . . . . . . . . 75

Part 3. Identification division . . . . 89

Part 5. Data division . . . . . . . 143

Part 4. Environment division . . . 101

153 154 155 156 156 156

Chapter 18. Data divisionfile description entries . . . . . . . . . 157

Part 6. Procedure division . . . . . 229

Chapter 19. Data divisiondata description entry . . . . . . . . . . 171

273 274 276 276 277 277 278

Chapter 21. Procedure division statements . . . . . . . . . . . . 285

Part 7. Intrinsic functions . . . . . 457

522 522 523 524 524 526 526 528

Part 9. Appendixes . . . . . . . . 531

Appendix D. Source language debugging. . . . . . . . . . . . . 557

Appendix E. Reserved words

Part 8. Compiler-directing statements . . . . . . . . . . . . 503

Appendix F. ASCII considerations. . . 573

Appendix G. Industry specifications

Glossary . . . . . . . . . . . . . 581 List of resources . . . . . . . . . . 601

Copyright IBM Corp. 1991, 2004

About this document

Accessing softcopy documentation and support information

Using assistive technologies

Keyboard navigation of the user interface

Copyright IBM Corp. 1991, 2004

Accessibility of this document

Obsolete language elements

v RERUN clause v REVERSED phrase

How to read the syntax diagrams

Optional items appear below the main path. Format

(1) STATEMENT identifier-1 literal-1

(2) (3) item 1

(4) TO identifier-3 ROUNDED (5) SIZE ERROR imperative-statement-1 ON END-STATEMENT (6)

Version 3 Release 3 (February 2004)

Version 3 Release 2 (September 2002)

Version 3 Release 1 (November 2001)

How to send your comments

About this document

Part 1. COBOL language structure

Chapter 4. Separators . . . . . . . . . . 35 Rules for separators . . . . . . . . . . . 35 Chapter 5. Sections and paragraphs .

Copyright IBM Corp. 1991, 2004

Chapter 2. Character sets and code pages

Character encoding units

COBOL words with single-byte characters

Copyright IBM Corp. 1991, 2004

COBOL words with DBCS characters

User-defined word Program-name Record-name Section-name Symbolic-character Text-name

DBCS characters allowed? No Yes Yes Yes No

Special registers See Special registers on page 13.

SORT-CONTROL SORT-CORE-SIZE SORT-FILE-SIZE SORT-MESSAGE SORT-MODE-SIZE SORT-RETURN TALLY

FILLER DEBUG-SUB-3 FILLER DEBUG-CONTENTS

PICTURE PICTURE PICTURE PICTURE

First nondeclarative procedure