COBOL User Groups Logo COBOL COBOL Programming
Home to COBOL | Discussions Forums | Join COBUG | Change COBUG Profile | Donations | Advertise with us | Contact us | About us | Site Map | Search Website |
 COBOL Training:  4-day COBOL Training Course

COBOL Jobs
 >  Job Listing
 >  Job Seekers
 >  Employers
 >  Interview Questions
 >  Job Resources

COBOL Resources
 >  Blogs
 >  COBOL Books
 >  Computer Timeshare
 >  COBOL Examples
 >  Forums
 >  Knowledge Bases
 >  Magazines
 >  Manuals
 >  Portals
 >  Support
 >  Syntax/Commands
 >  COBOL Training
 >  COBOL Tutorials
 >  User Groups
 >  White Papers

COBOL Software
 >  Change Management
 >  COBOL Compilers
 >  Data Access
 >  Database
 >  Documentation
 >  Editors
 >  File Conversion
 >  Free COBOL Software
 >  GUI
 >  Legacy Migration
 >  Legacy Modernization
 >  Mainframe Security
 >  Report Generators
 >  COBOL Sort
 >  Terminal Emulators
 >  COBOL Test
 >  COBOL Tools
 >  Trans. Processing

COBOL Information
 >  Events
 >  News Articles
 >  Newsletters
 >  Product News
 >  COBOL Standards

COBOL Email List Rental
You can reach a highly targeted, qualified, opt-in audience of COBOL users by renting the COBUG email list. Contact us today advertise@cobug.com for details about our email list and rental rates.

Website Advertisement
Advertise on the COBUG website and reach tens of thousands of COBOL users. Increase your sales leads. Contact COBUG at advertise@cobug.com for advertising rates.

Support COBUG
COBOL Donation
 

COBOL Syntax/Commands

 

COBOL syntax, commands, verbs, statements and clauses such as COBOL accept, COBOL call, initialize, Set, occurs clause, open, COBOL read, unstring, COBOL write, and other commands in COBOL.
 
 >  COBOL Accept
 >  COBOL Add
 >  COBOL Alter
 >  COBOL Array
 >  COBOL Call
 >  COBOL Cancel
 >  COBOL Close
 >  COBOL Commit
 >  COBOL Comp, Comp-3, Binary, Data Types
 >  COBOL Compute
 >  COBOL Continue
 >  COBOL Copy
 >  COBOL Date
 >  COBOL Delete
 >  COBOL Disable
 >  COBOL Display
 >  COBOL Divide
 >  COBOL Drop
 >  COBOL Enable
 >  COBOL Enter
 >  COBOL Entry
 >  COBOL Evaluate
 >  COBOL Examine
 >  COBOL Exclusive
 >  COBOL Exec
 >  COBOL Exhibit
 >  COBOL Exit
 >  COBOL FD
 >  COBOL FIller
 >  COBOL Function
 >  COBOL Generate
 >  COBOL Goback
 >  COBOL Go To
 >  COBOL If
 >  COBOL Initialize
 >  COBOL Initiate
 >  COBOL Inspect
 >  COBOL Invoke
 >  COBOL Merge
 >  COBOL Move
 >  COBOL Multiply
 >  COBOL NEXT SENTENCE
 >  COBOL Note
 >  COBOL Occurs
 >  COBOL On
 >  COBOL Open
 >  COBOL Perform
 >  COBOL Pic
 >  COBOL Pointer
 >  COBOL Raise
 >  COBOL Read
 >  COBOL Ready Trace / Reset Trace
 >  COBOL Redefines
 >  COBOL Reference Modification
 >  COBOL Release
 >  COBOL Replace
 >  COBOL Resume
 >  COBOL Return
 >  COBOL Rewrite
 >  COBOL Rollback
 >  COBOL Search & Search All
 >  COBOL Service
 >  COBOL Set
 >  COBOL Sort
 >  COBOL Start
 >  COBOL Stop
 >  COBOL String
 >  COBOL Subtract
 >  COBOL Suppress
 >  COBOL Sync
 >  COBOL Table
 >  COBOL Terminate
 >  COBOL Transform
 >  COBOL Try
 >  COBOL Unlock
 >  COBOL Unstring
 >  COBOL Use
 >  COBOL Write
 >  COBOL XML Generate
 >  COBOL XML Parse
 

COBOL Accept

 > ACCEPT in COBOL - HP COBOL II/XL
The ACCEPT in COBOL statement can be used for low volume input from a specified device. The COBOL ACCEPT statement has three general formats.

 > ACCEPT in COBOL Statement Examples
The COBOL ACCEPT verb is used to read from the keyboard and write to the screen. Simple examples using the COBOL ACCEPT and DISPLAY verbs are shown.

 > COBOL ACCEPT Statement - IBM COBOL/400
The ACCEPT in COBOL statement transfers data into the specified identifier. There is no editing or error checking of the incoming data. The COBOL ACCEPT statement has seven formats.

 

[ Go to Top of Page ]
 

COBOL Alter

 > ALTER in COBOL, IBM COBOL/400
The COBOL ALTER statement changes the transfer point specified in a COBOL GO TO statement. The COBOL ALTER statement is an obsolete language element and encourages the use of unstructured programming practices. It is to be deleted from the next revision of the ANSI Standard. The COBOL EVALUATE statement provides the same function as the ALTER in COBOL statement and helps ensure that your program will be well-structured.

 > COBOL ALTER Statement, HP COBOL II/XL
The ALTER in COBOL statement is an obsolete feature of the 1985 ANSI COBOL standard. The COBOL ALTER statement allows you to modify a predetermined sequence of operations.

 > COBOL ALTER Statement Diagram
Provides a diagram for the COBOL ALTER syntax.

 

[ Go to Top of Page ]
 

COBOL Commit

 > COMMIT in COBOL, ILE COBOL
The COMMIT in COBOL statement provides a way of synchronizing changes to data base records while preventing other jobs from modifying those records until the COBOL COMMIT is performed.

 > COBOL COMMIT Statement
When the COBOL COMMIT statement is executed, all changes made to files under commitment control since the previous commitment boundary are made permanent.

 > COBOL COMMIT Statement, HP COBOL II/XL
The COMMIT in COBOL statement ends your database transaction, makes permanent all changes made to the database since the last quiet point, and establishes a new quiet point for this run unit.

 > COBOL COMMIT Statement
The COBOL COMMIT statement releases all record locks in all files held by this run unit. For COBOL systems that support the WITH...ROLLBACK clause of the SELECT statement as other than documentary, COBOL COMMIT indicates the end of the current transaction and makes the effects of that transaction permanent.

 > Diagram of COBOL COMMIT Verb
Provides a diagram for the COBOL COMMIT syntax.

 

[ Go to Top of Page ]
 

COBOL Compute

 > COMPUTE Statement in COBOL - IBM Enterprise COBOL
The COBOL COMPUTE command assigns the value of an arithmetic expression to a specified reference. The COMPUTE in COBOL keyword cannot be abbreviated.

 > COBOL COMPUTE Statement - IBM COBOL/400
The COBOL COMPUTE statement assigns the value of an arithmetic expression to one or more data items. The COBOL COMPUTE statement allows you to combine arithmetic operations without the restrictions on receiving data items that the rules for the ADD, SUBTRACT, MULTIPLY, and DIVIDE statements impose.

 > COBOL COMPUTE Statement - HP COBOL II/XL
The COBOL COMPUTE statement evaluates an arithmetic expression and assigns the result to one or more data items.

 > COBOL COMPUTE Verb
The COBOL COMPUTE verb allows you to combine several math operations in one statement, using familiar symbols instead of English-like sentances.

 > Example of COBOL COMPUTE Statement
All the arthemetic, that can done using verb ADD, SUBTRACT, MULTIPLY, DIVIDE verbs can be done using COMPUTE statement.

 

[ Go to Top of Page ]
 

COBOL Continue

 > COBOL CONTINUE Clause
The COBOL CONTINUE expression is used: a) to avoid performing any operation if a condition exists. b) to execute instructions only when the ELSE condition is met. When used, the COBOL CONTINUE (or NEXT SENTENCE) must be the only clause following a condition, since it indicates that no action is to be performed. COBOL NEXT SENTENCE is used in place of CONTINUE in COBOL 74.

 > COBOL CONTINUE Statement, HP COBOL II/XL
The COBOL CONTINUE statement indicates that no executable statement is present. The CONTINUE in COBOL statement can be used anywhere a conditional statement or an imperative statement is used. An example of the CONTINUE statement is provided.

 > COBOL CONTINUE Statement, IBM COBOL for AIX
The COBOL CONTINUE statement is a no operation statement. It indicates that no executable instruction is present.

 > CONTINUE Statement, IBM COBOL/400
The COBOL CONTINUE statement allows you to specify a no operation statement. It indicates that no executable instruction is present. You can use the COBOL CONTINUE statement anywhere a conditional statement or an imperative statement may be used. It has no effect on the execution of the program.

 > CONTINUE in COBOL Statement, Micro Focus Enterprise Developer
The COBOL CONTINUE statement is a no operation statement, indicating that no executable statement is present. The CONTINUE in COBOL statement has no effect on the execution of the program.

 > CONTINUE vs NEXT SENTENCE in COBOL
What exactly is the difference between the COBOL CONTINUE and COBOL NEXT SENTENCE?

 

[ Go to Top of Page ]
 

COBOL Disable

 > COBOL DISABLE Statement
COBOL DISABLE Syntax Circa 1988.

 > COBOL DISABLE Statement
COBOL DISABLE statement flagged.

 

[ Go to Top of Page ]
 

COBOL Drop

 > COBOL DROP Statement
The COBOL DROP statement releases a program device acquired by a TRANSACTION file.

 

[ Go to Top of Page ]
 

COBOL Enable

 > COBOL ENABLE Statement
COBOL ENABLE Syntax Circa 1988.

 > ENABLE in COBOL
ENABLE in COBOL statement flagged.

 

[ Go to Top of Page ]
 

COBOL Enter

 > COBOL ENTER Statement, Micro Focus
The COBOL ENTER statement provides a means of allowing the use of more than one language in the same program. The COBOL ENTER statement is classed as an obsolete element in the ANSI'85 standard and is scheduled to be deleted from the next full revision of the ANSI Standard.

 > COBOL ENTER Statement, COBOL/400
The COBOL ENTER statement is obsolete and will be deleted from the next revision of the ANSI Standard. It is syntax-checked during compilation, but has no effect on the execution of the program. The ENTER in COBOL allows the use of more than one source language in the same source program.

 > ENTER Statement in COBOL, HP COBOL II/XL
The ENTER in COBOL provides a means of allowing the use of more than one language in the same program.

 

[ Go to Top of Page ]
 

COBOL Entry

 > COBOL ENTRY Statement, HP COBOL II/XL
The COBOL ENTRY statement is an HP extension to the ANSI COBOL standard. The COBOL ENTRY statement establishes a secondary entry point in an HP COBOL II subprogram. In nested programs, this statement must begin in Area A. However, like all other COBOL statements in the PROCEDURE DIVISION, the ENTRY in COBOL statement must be in a paragraph.

 > COBOL ENTRY Statement, COBOL for AIX
The COBOL ENTRY statement establishes an alternate entry point into a COBOL called subprogram. 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 in COBOL statement.

 > COBOL ENTRY Statement, Micro Focus Enterprise Developer for Visual Studio
The COBOL ENTRY statement is a data type attribute that declares a constant or variable whose value is an entry point, and describes the attributes of the parameters, if any, that are declared for the entry point.

 > ENTRY Statement in COBOL, Micro Focus
Diagram of the COBOL ENTRY syntax.

 

[ Go to Top of Page ]
 

COBOL Exclusive

 > COBOL EXCLUSIVE, Micro Focus Enterprise Developer for Visual Studio
Abbreviation: EXCL. The COBOL EXCLUSIVE attribute specifies that the records in a file can be locked when accessed by one process to prevent access by another process. When the COBOL EXCLUSIVE attribute is used, the entire file is locked.

 > EXCLUSIVE in COBOL Statement, HP COBOL II/XL
The COBOL EXCLUSIVE statement is an HP extension to the ANSI COBOL standard. The EXCLUSIVE in COBOL statement provides you with a method for locking a file that has been opened for shared access.

 > COBOL UN-EXCLUSIVE Statement, HP COBOL II/XL
The COBOL UN-EXCLUSIVE statement is an HP extension to the ANSI COBOL standard. The COBOL UN-EXCLUSIVE statement releases a file that has been previously locked by the COBOL EXCLUSIVE statement.

 

[ Go to Top of Page ]
 

COBOL EXEC - Execute

 > COBOL EXEC CICS Statement, Developer for System z
Building COBOL and PL/I source containing EXEC CICS statements. The COBOL EXEC statement is provided as a linkage mechanism to allow control to be passed to non-COBOL subsystems.

 > COBOL EXEC CICS Statement, CICS Commands
A list of the common COBOL EXEC CICS commands and their COBOL syntax.

 > EXEC in COBOL, Cataloged Procedure, Developer for System z
If a parameter of an EXEC in COBOL statement that invokes a cataloged procedure has an unqualified name, the parameter applies to all the COBOL EXEC statements in the cataloged procedure.

 > EXEC in COBOL JCL
The EXEC in COBOL JCL, represents one step. You would code one EXEC Statement in your Job, for each step. If your job has a dozen steps, you must code a dozen COBOL EXEC Statements in your JCL.

 

[ Go to Top of Page ]
 

COBOL Exhibit

 > COBOL EXHIBIT Statement
OS/VS COBOL accepted the COBOL EXHIBIT statement; Enterprise COBOL does not. With Enterprise COBOL, you can use DISPLAY statements to replace the COBOL EXHIBIT statements. However, the DISPLAY statement does not perform all the functions of the COBOL EXHIBIT statement.

 > COBOL EXHIBIT Statement
The COBOL EXHIBIT statement with neither the CHANGED nor the NAMED option behaves as if the NAMED option were specified.

 

[ Go to Top of Page ]
 

COBOL EXIT

 > COBOL EXIT, COBOL/400
The COBOL EXIT PROGRAM statement specifies the end of a called program and returns control to the calling program.

 > COBOL EXIT Statement, COBOL/400
The COBOL EXIT statement provides a common end point for a series of paragraphs. The EXIT in COBOL statement must be preceded by a paragraph-name and must appear in a sentence by itself.

 > COBOL EXIT Statement, Micro Focus
The COBOL EXIT statement provides a common end point for a series of procedures. It can also exit an inline PERFORM, a paragraph or a section. The COBOL EXIT PROGRAM statement marks the logical end of a called program. The EXIT METHOD in COBOL statement marks the logical end of an invoked method. The COBOL EXIT FUNCTION statement marks the logical end of the execution of a function.

 > COBOL EXIT Statement, COBOL for AIX
The COBOL EXIT statement provides a common end point for a series of procedures. The EXIT in COBOL statement enables you to assign a procedure-name to a given point in a program. The COBOL EXIT statement is treated as a CONTINUE statement. Any statements following the COBOL EXIT statement are executed.

 > EXIT Syntax, Micro Focus
Illustrates the format of the COBOL EXIT, EXIT FUNCTION, EXIT METHOD, EXIT PERFORM, EXIT Paragraph and COBOL EXIT PROGRAM syntax.

 > EXIT Verb, Syntax of COBOL Circa 1988
Provides a diagram for the COBOL EXIT verb Circa 1988.

 > EXIT Statement in COBOL, HP COBOL II/XL
The EXIT in COBOL provides a common end point for a series of procedures. EXIT in COBOL must appear in a sentence by itself. EXIT statement must be the only sentence in a paragraph. It serves only to enable you to terminate a procedure and has no other effect on the compilation or execution of the program.

 

[ Go to Top of Page ]
 

COBOL FD

 > COBOL FD, COBOL/400
COBOL FD, file description entry represents the highest level of organization in the File Section. COBOL FD provides information a bout the physical structure and identification of a file, and gives the record names associated with that file.

 > COBOL FD - File Description, Micro Focus Developer, Net Express for Eclipse
The COBOL FD, file description comprises information concerning the physical structure, identification, and record-names pertaining to a given file. The FD in COBOL, file description entry also determines whether a file-name is a local name or a global name.

 > FD - File Description, COBOL for AIX
The COBOL 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 COBOL FD or SD entry is not important.

 > FD - Syntax of COBOL Circa 1988
COBOL FD: File_definition::=("FD" file_name...

 > FD in COBOL, Course Notes
FD in COBOL stands for File Description. The FD in COBOL statement exists in the DATA DIVISION, FILE SECTION (not working-storage section). File-name matches the file-name on the SELECT.

 

[ Go to Top of Page ]
 

COBOL FILLER

 > COBOL FILLER, Rational Programming Patterns for System z
COBOL FILLER definition. FILLERs are not defined in the repository. They are used as alignment fields, and do not contain any information.

 > COBOL FILLER, ILE COBOL
The COBOL FILLER item is treated as if it were an item with a level number equal to that of the preceding item.

 > FILLER in COBOL Tutorials
The COBOL FILLER is a special type of COBOL field. It is a reserved word, and you can have as many COBOL FILLER fields in a record as you want -- the name does not have to be unique as field names generally must be. FILLER in COBOL can also be used to create a field, or place holder, that you will never need to refer to by name, so you might find it contains actual data, not just blank space.

 > FILLER in COBOL
Explanation of FILLER in COBOL. It is a reserved word. The COBOL FILLER is used immediately following a level number and preceding a PICTURE clause that defines a field┐s size and data type. COBOL restricts the use of FILLER in COBOL to the Data Division.

 

[ Go to Top of Page ]
 

COBOL GENERATE

 > COBOL GENERATE Statement, COBOL Circa 1988
Provides a diagram for the COBOL GENERATE syntax Circa 1988.

 > GENERATE in COBOL, Debug Tool for z/OS
COBOL GENERATE statement flagged.

 > GENERATE in COBOL Statement, COBOL-85 Tutorial
GENERATE in COBOL can be used in two situations: a) with a data name b) with a report name.

 

[ Go to Top of Page ]
 

COBOL GOBACK

 > COBOL GOBACK, COBOL/400
The COBOL GOBACK statement specifies the logical end of a called program. It functions like the EXIT PROGRAM statement when coded as a part of a called program, and like the STOP RUN statement when coded in a main program. In a sentence, the COBOL GOBACK statement should appear as the only statement or as the last statement in a series of imperative statements, because any statements following COBOL GOBACK are not executed.

 > COBOL GOBACK Statement, HP COBOL II/XL
The COBOL GOBACK statement must be the only statement in a sentence. If used in a series of imperative statements, it must be the last statement in the series. The GOBACK statement marks the logical end of a program. The GOBACK in COBOL statement is an HP extension to the ANSI COBOL standard.

 > COBOL GOBACK Statement, COBOL for AIX
The COBOL GOBACK statement functions like the EXIT PROGRAM statement when it is coded as part of a called program (or the EXIT METHOD statement when GOBACK in COBOL 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.

 > GOBACK in COBOL Verb, Micro Focus
Illustrates the format of the COBOL GOBACK statement.

 

[ Go to Top of Page ]
 

COBOL GO TO

 > GO TO Statement, COBOL/400
The COBOL GO TO statement transfers control from one part of the Procedure Division to another. GO TO in COBOL has three formats.

 > COBOL GO TO, Micro Focus Developer
The COBOL GO TO statement causes control to be transferred from one part of the Procedure Division to another. The option of omitting procedure-name-1 in a Format 1 GO TO statement is classed as an obsolete element in the ANSI'85 standard and is scheduled to be deleted from the next full revision of the ANSI Standard. All dialects in this COBOL implementation fully support this syntax.

 > COBOL GO TO Syntax, COBOL Circa 1988
Provides a diagram for the COBOL GO TO syntax Circa 1988.

 > COBOL GO TO Verb, Micro Focus
Illustrates the format of the COBOL GO TO verb.

 > GO TO in COBOL, COBOL for AIX
The GO TO in COBOL statement transfers control from one part of the procedure division to another. The types of COBOL GO TO statements are: Unconditional, Conditional and Altered.

 

[ Go to Top of Page ]
 

COBOL Initialize

 > COBOL INITIALIZE, HP COBOL II/XL
The COBOL INITIALIZE statement sets selected types of data fields to predefined values. It can set numeric data to zeros or alphanumeric data to spaces.

 > COBOL INITIALIZE Statement, COBOL/400
The COBOL INITIALIZE statement sets selected categories of data fields to predetermined values; it is functionally equivalent to one or more MOVE statements.

 > COBOL INITIALIZE, Example Code
A discussion on how COBOL initializes fields and how the COBOL INITIALIZE statement would treat FILLER items in WORKING-STORAGE.

 > INITIALIZE in COBOL Example
Presents an example and discussion of using the COBOL INITIALIZE verb.

 > INITIALIZE in COBOL, Micro Focus Enterprise Developer for Visual Studio
The INITIALIZE in COBOL statement provides the ability to set selected data items to specified values.

 > INITIALIZE Statement, COBOL for AIX
The INITIALIZE in COBOL sets selected categories of data fields to predetermined values. The COBOL INITIALIZE is functionally equivalent to one or more MOVE statements.

 

[ Go to Top of Page ]
 

COBOL Invoke

 > COBOL INVOKE Statement - Enterprise COBOL
The COBOL INVOKE statement can create object instances of a COBOL or Java class and can invoke a method defined in a COBOL or Java class.

 > COBOL INVOKE Statement - IBM AIX
The INVOKE in COBOL statement can create object instances of a COBOL or Java class and can invoke a method defined in a COBOL or Java class.

 > COBOL INVOKE Statement
The COBOL INVOKE statement causes a method to be invoked in Object COBOL.

 > COBOL INVOKE Statement
The COBOL INVOKE statement allows the name of the method to be invoked to be contained in a variable. In addition, parameters can be passed BY CONTENT (by value) or BY REFERENCE, and these options can be specified separately for each parameter in different COBOL INVOKE statements.

 > INVOKE Statement in COBOL - Micro Focus Visual COBOL
The INVOKE statement in COBOL causes a method to be invoked.

 

[ Go to Top of Page ]
 

COBOL Multiply

 > COBOL MULTIPLY, COBOL/400
The COBOL MULTIPLY statement multiplies numeric items and sets the values of data items equal to the results. The MULTIPLY in COBOL statement has two formats.

 > COBOL MULTIPLY Statement, COBOL for AIX
The COBOL MULTIPLY statement multiplies numeric items and sets the values of data items equal to the results.

 > MULTIPLY in COBOL, Micro Focus Enterprise Developer for Eclipse (Windows)
The COBOL MULTIPLY statement causes numeric data items to be multiplied and sets the values of data items equal to the results.

 > MULTIPLY in COBOL, HP COBOL II/XL
The MULTIPLY in COBOL statement multiplies a number by one or more other numbers and stores the result in one or more locations.

 

[ Go to Top of Page ]
 

COBOL NEXT SENTENCE

 > COBOL NEXT SENTENCE Example
Example of the COBOL NEXT SENTENCE statement.

 > COBOL NEXT SENTENCE Phrase - IBM ILE COBOL
The COBOL NEXT SENTENCE phrase causes the transfer of control to an implicit COBOL CONTINUE statement immediately preceding the next separator period. If the NEXT SENTENCE in COBOL phrase is specified, the END-SEARCH phrase must not be specified

 > COBOL NEXT SENTENCE Statement - IBM COBOL/400
COBOL NEXT SENTENCE Statement can be specified with END-IF.

 > NEXT SENTENCE in COBOL - Micro Focus Enterprise Developer
The NEXT SENTENCE in COBOL transfers control to the next COBOL sentence, that is, following the next period. It does not transfer control to the logically next COBOL verb as occurs with the CONTINUE verb. The COBOL NEXT SENTENCE statement can be used anywhere a conditional statement or an imperative-statement can be used.

 

[ Go to Top of Page ]
 

COBOL Note

 > COBOL NOTE Statement, IBM Enterprise COBOL for z/OS
OS/VS COBOL accepted the COBOL NOTE statement. Enterprise COBOL does not accept the COBOL NOTE statement. Therefore, for Enterprise COBOL delete all COBOL NOTE statements and use comment lines instead for the entire NOTE paragraph.

 > COBOL NOTE Statement, Micro Focus Enterprise Developer
The COBOL NOTE statement introduces a sentence or paragraph that will be treated as comments. If a COBOL NOTE statement is the first sentence of a paragraph, the entire paragraph is treated as comment.

 > COBOL NOTE Statement, Unisys COBOL
The COBOL NOTE statement allows the programmer to write commentary which is produced on the listing but not compiled. Standard COBOL 1974 has replaced the NOTE in COBOL statement by a generalized comment facility. An asterisk (*) in character position 7 identifies any line as a comment line.

 > NOTE in COBOL Statement, Micro Focus Visual COBOL
The NOTE in COBOL statement introduces a sentence or paragraph that will be treated as comments. If a NOTE in COBOL statement is the first sentence of a paragraph, the entire paragraph is treated as comment. If a COBOL NOTE statement appears as other than the first sentence of a paragraph, text up to the next separator period is treated as comment.

 

[ Go to Top of Page ]
 

COBOL Occurs

 > COBOL Occurs Depending On - Disc Interchange
The number of times a table repeats is specified by the COBOL OCCURS clause. COBOL also permits tables that occur a variable number of times, DEPENDING ON the value in some other field.

 > COBOL Occurs Clause - HP COBOL II/XL
The COBOL OCCURS clause is used to define a table containing up to seven dimensions. The OCCURS in COBOL eliminates the need for separate entries to describe repeated data items, and provides information required for the application of subscripts or indices.

 > COBOL Occurs Clause - Micro Focus Reference Manual
The COBOL OCCURS clause is used in defining tables and other homogenous sets of repeated data items. The COBOL OCCURS clause eliminates the need for separate entries for repeated data items and supplies information required for the application of subscripts or indices.

 > Occurs in COBOL Courses Notes - Department of Computer Science and Engineering at the Ohio State University
OCCURS in COBOL is used to define a table.

 > Occurs Depending Clause in COBOL - Microsoft
Using the OCCURS DEPENDING Clause in COBOL to Define Variable-length Table.

 

[ Go to Top of Page ]
 

COBOL On

 > COBOL ON Statement - Micro Focus Visual COBOL
The COBOL ON statement allows selective execution of procedural statements on a periodic basis. Prior to the first execution of each ON statement in COBOL, a counter, implicitly defined for that COBOL ON statement (the implicit-ON-counter), is initialized to be zero.

 

[ Go to Top of Page ]
 

COBOL Open

 > COBOL OPEN Statement - HP COBOL II/XL
The COBOL OPEN statement opens a specified file or files. It also performs checking and writing of labels, and other input or output operations.

 > COBOL OPEN Statement - Micro Focus Visual COBOL
The COBOL OPEN statement initiates the processing of files. It performs checking and/or writing of labels and other input-output operations.

 > OPEN Statement in COBOL - Enterprise COBOL for z/OS
The COBOL OPEN statement initiates the processing of files. The OPEN statement in COBOL also checks or writes labels, or both.

 > OPEN Statement in COBOL - IBM AIX
The OPEN statement in COBOL initiates the processing of files. It also checks or writes labels, or both.

 

[ Go to Top of Page ]
 

COBOL Raise

 > COBOL RAISE Statement - Micro Focus Visual COBOL
The COBOL RAISE statement raises an exception.

 > RAISE Statement in COBOL - Object-Oriented COBOL By Edmund C. Arranga, Frank P. Coyle
COBOL RAISE Statement diagram proposed in COBOL 97 language syntax. The RAISE statement in COBOL: RAISE exception-name-1 - causes execution of corresponding USE procedure - can be used for user-defined conditions and for testing purposes.

 

[ Go to Top of Page ]
 

COBOL Read

 > COBOL Read Example Programs
The COBOL READ verb is demonstrated in COBOL program examples on how to process sequential files.

 > COBOL Read Language Reference - HP COBOL II/XL
The COBOL READ statement makes a record of a file available to your program. There are three formats depending on the type of organization of the file from which a record is made available.

 > COBOL Read Statement - IBM COBOL/400
The COBOL READ statement makes a record available to the program. For sequential access, it makes the next logical record from a file available to the object program. For random access, it makes a specified record from a direct-access file available to the object program. When the COBOL READ statement is executed, the associated file must be open in INPUT or I-O mode.

 > COBOL Read Statement - Micro Focus COBOL
For sequential access, the COBOL READ statement makes available the next or previous logical record from a file. For random access, the COBOL READ statement makes available a specified record from a mass storage file.

 > Read Statement in COBOL - IBM AIX
For sequential access, the READ statement in COBOL makes the next logical record from a file available to the object program. For random access, the COBOL READ statement makes a specified record from a direct-access file available to the object program.

 

[ Go to Top of Page ]
 

COBOL Ready Trace / Reset Trace

 > COBOL Ready Trace / COBOL Reset Trace - Enterprise COBOL for z/OS
The COBOL READY TRACE or COBOL RESET TRACE statement was designed to trace the execution of procedures. The COBOL READY TRACE or COBOL RESET TRACE statement can appear only in the procedure division, but has no effect on your program.

 > COBOL Ready Trace / COBOL Reset Trace - Enterprise COBOL for z/OS
OS/VS COBOL allowed the COBOL READY TRACE and COBOL RESET TRACE statements. Enterprise COBOL does not support these statements. To get function similar to the COBOL READY TRACE statement, you can use either Debug Tool, or the COBOL language available in the Enterprise COBOL compiler.

 

[ Go to Top of Page ]
 

COBOL Redefines

 > COBOL REDEFINES
Can the COBOL REDEFINES clause be used at 01 level?

 > COBOL REDEFINES Clause
This is a discussion about the COBOL REDEFINES clause, what it is, why it is used, and how to deal with it on a PC.

 > COBOL REDEFINES Clause
This is a question about the COBOL REDEFINES clause.

 > COBOL REDEFINES Clause
The COBOL REDEFINES clause allows you to have multiple field definitions for the same piece of storage.

 > COBOL REDEFINES Example
This ia a COBOL program example of the COBOL REDEFINES clause.

 > REDEFINES in COBOL
How can I use the COBOL REDEFINES clause to define a PIC X(13) by redefining it to be a numeric so that I can compare it for zeros?

 > REDEFINES in COBOL Group Data Items
If you declare a member of a group data item with the COBOL REDEFINES clause, and that group data item is referred to as a whole in an SQL statement, any subordinate items containing the COBOL REDEFINES clause are not expanded.

 > Using REDEFINES in COBOL
The is a COBOL example that shows the COBOL REDEFINES clause.

 

[ Go to Top of Page ]
 

COBOL Replace

 > COBOL Replace Statement - HP COBOL II/XL
The COBOL REPLACE statement is used to replace source program text. The COBOL REPLACE statement statement may appear anywhere in a program, from the IDENTIFICATION DIVISION to the end of the PROCEDURE DIVISION.

 > COBOL Replace Statement - ILE COBOL
The COBOL REPLACE statement can occur anywhere in the source program where a character-string can occur. The COBOL REPLACE statement must be preceded by a separator period except when it is the first statement in a separately compiled program. The COBOL REPLACE statement must be terminated by a separator period.

 

[ Go to Top of Page ]
 

COBOL Resume

 

[ Go to Top of Page ]
 

COBOL ROLLBACK

 > COBOL Rollback Statement - COBOL/400
The COBOL ROLLBACK statement provides a way to cancel one or more changes to database records when the changes should not remain permanent.

 > COBOL Rollback Statement - ILE COBOL
The COBOL ROLLBACK statement provides a way to cancel one or more changes to database records when the changes should not remain permanent. When the COBOL ROLLBACK statement is executed, any changes made to files under commitment control since the last commitment boundary are removed from the database.

 > COBOL Rollback Statement - Micro Focus Server Express
The COBOL ROLLBACK statement releases all record locks in all files held by this run unit. Provides a diagram for the COBOL ROLLBACK syntax.

 > Rollback Statement in COBOL - Micro Focus Visual COBOL
The ROLLBACK statement in COBOL releases all record locks in all files held by this run unit. Execution of the COBOL ROLLBACK statement causes all record locks in all files held by the run unit to be released. The file lock on an exclusive file is not affected by the COBOL ROLLBACK statement.

 

[ Go to Top of Page ]
 

COBOL Service

 > COBOL Service Statement - Micro Focus Visual COBOL
The SERVICE statement in COBOL is used to establish addressability to Linkage Section items usually in a CICS program.

 

[ Go to Top of Page ]
 

COBOL Start

 > COBOL Start Statement - COBOL/400
The COBOL START statement positions an indexed or relative file for subsequent sequential record retrieval. When the COBOL START statement is executed, the associated indexed or relative file must be open in either INPUT or I-O mode.

 > Start Statement in COBOL - IBM AIX
The START statement in COBOL provides a means of positioning within an indexed or relative file for subsequent sequential record retrieval. When the COBOL START statement is executed, the associated indexed or relative file must be open in either INPUT or I-O mode.

 > COBOL Start Statement - HP COBOL II/XL
The COBOL START statement provides a basis for logical positioning within a relative or indexed file, in sequential or dynamic access mode, for subsequent retrieval of records.

 > Start Statement in COBOL - Micro Focus Visual COBOL
The START statement in COBOL provides a basis for logical positioning within a relative or indexed file for subsequent retrieval of records. The COBOL START statement is not available for files with sequential organization. The START statement in COBOL initiates execution of a thread, either synchronously or asynchronously.

 

[ Go to Top of Page ]
 

COBOL Stop

 > COBOL Stop Statement - HP COBOL II/XL
The COBOL STOP statement provides a means of temporarily suspending execution of your object program, as well as a means of stopping it completely.

 > COBOL Stop Statement - ILE COBOL
The COBOL STOP statement halts execution of the object program either permanently or temporarily.

 > COBOL Stop Statement - Micro Focus Net Express
The COBOL STOP statement causes a permanent or temporary suspension of the execution of the run unit. The COBOL STOP literal statement is classed as an obsolete element in the ANSI'85 Standard and is scheduled to be deleted from the next full revision of the ANSI Standard.

 > Stop Statement in COBOL - IBM AIX
The STOP statement in COBOL halts execution of the object program either permanently or temporarily. Do not use COBOL STOP RUN or COBOL STOP literal in programs compiled with the THREAD compiler option. The COBOL STOP RUN statement closes all files defined in any of the programs in the run unit.

 > Stop Statement in COBOL - Micro Focus Visual COBOL
The STOP statement in COBOL causes a permanent or temporary suspension of the execution of the run unit. The COBOL STOP literal statement is classed as an obsolete element in the ANSI'85 Standard and is scheduled to be deleted from the next full revision of the ANSI Standard. If a COBOL STOP RUN statement appears in a consecutive sequence of imperative statements within a sentence, it must appear as the last statement in that sequence.

 

[ Go to Top of Page ]
 

COBOL Suppress

 > COBOL Suppress Verb - Syntax of COBOL Circa 1988
COBOL Suppress_Verb::= "SUPPRESS PRINTING"|"SUPPRESS. The COBOL SUPPRESS statement provides the object time facility to suppress the printing of an entire report group.

 

[ Go to Top of Page ]
 

COBOL Sync

 > COBOL SYNC Statement - Micro Focus Visual COBOL
The COBOL SYNC statement marks a statement block as a critical section by obtaining the mutual-exclusion lock for a given object, executing a block of statements, and then releasing the lock.

 

[ Go to Top of Page ]
 

COBOL Terminate

 > COBOL Terminate Statement - HP COBOL
The COBOL TERMINATE statement causes the RWCS to complete the processing of the specified report.

 > COBOL Terminate Statement - IBM System z
COBOL statements flagged. Report Writer section - COBOL TERMINATE statement flagged.

 > COBOL Terminate Verb - Syntax of COBOL Circa 1988
COBOL TERMINATE_Verb::= "TERMINATE " list(report_name)

 

[ Go to Top of Page ]
 

COBOL Transform

 > COBOL Transform Statement - IBM System z
Language elements that are not supported: COBOL TRANSFORM statement. OS/VS COBOL supported the COBOL TRANSFORM statement. Enterprise COBOL does not support the COBOL TRANSFORM statement, but it does support the INSPECT statement. Therefore, any COBOL TRANSFORM statements in your OS/VS COBOL program must be replaced by INSPECT CONVERTING statements.

 > COBOL Transform Statement - Micro Focus Visual COBOL
The COBOL TRANSFORM statement is used to alter characters according to a transformation rule. The TRANSFORM statement in COBOL scans identifier-3 for occurrences of individual characters from identifier-1 or nonnumeric-literal-1.

 

[ Go to Top of Page ]
 

COBOL Try

 > COBOL TRY Statement - Micro Focus Visual COBOL
The COBOL TRY...CATCH...FINALLY...END-TRY structure is the basis for structured exception handling. Execution of the TRY statement in COBOL begins with imperative-statement-1.

 

[ Go to Top of Page ]
 

COBOL Unlock

 > COBOL Unlock Statement - HP COBOL
The COBOL UNLOCK statement removes a record lock from the current record or from all locked records in the file. On Alpha and I64 systems, the X/Open standard the UNLOCK statement in COBOL always removes the record lock from all locked records in the file.

 > COBOL Unlock Statement - Micro Focus Visual COBOL
The COBOL UNLOCK statement releases all record locks held by the run unit on a named file.

 

[ Go to Top of Page ]
 

COBOL Unstring

 > COBOL UNSTRING Statement - HP COBOL II/XL
The COBOL UNSTRING statement divides data in a sending field and places the segments of the data into multiple receiving fields.

 > COBOL UNSTRING Statement - IBM COBOL AIX
The COBOL UNSTRING statement causes contiguous data in a sending field to be separated and placed into multiple receiving fields.

 > COBOL UNSTRING Statement - IBM COBOL/400 iSeries
You can use one COBOL UNSTRING statement instead of multiple MOVE statements. All subscripting and reference modification is performed only once, at the beginning of the execution of the UNSTRING in COBOL statement.

 > COBOL UNSTRING Verb - Course Notes
The COBOL UNSTRING verb is described in COBOL course notes including the UNSTRING DELIMITED BY and TALLYING IN phrases. The syntax, functioning and rules of the COBOL UNSTRING verb are examined, and abstract and pratical COBOL program examples are provided.

 > UNSTRING in COBOL
The UNSTRING in COBOL verb is used to divide a string into sub-strings. The COBOL UNSTRING copies characters from the source string, to the destination strings, until a delimiter encountered that terminates data transfer.

 > UNSTRING in COBOL Example
The following example illustrates some of the considerations that apply to the UNSTRING in COBOL statement.

 > UNSTRING in COBOL - Micro Focus Visual COBOL
The UNSTRING in COBOL statement causes contiguous data in a sending field to be separated and placed into multiple receiving fields.

 

[ Go to Top of Page ]
 

COBOL Use

 > COBOL Use Statement - HP COBOL II/XL
The COBOL USE statement specifies procedures for input-output error handling, user label processing, and debugging. There are three general formats of the COBOL USE statement.

 > COBOL Use Statement - HP COBOL OpenVMS
The COBOL USE statement specifies Declarative USE procedures to handle input/output exceptions and errors. It can also specify procedures to be executed before the program processes a specific report group.

 > COBOL Use Statement - ILE COBOL
The COBOL USE statement specifies procedures for input/output exception or error handling that are to be executed in addition to the system-defined procedures. Although the COBOL USE statement is a compiler-directing statement, it can appear only in the Procedure Division, and it can begin only in Area B.

 > COBOL Use Statement - Micro Focus Visual COBOL
The COBOL USE statement specifies procedures for input-output error handling, that are in addition to the standard procedures provided by the input-output control system. A COBOL USE statement, when present, must immediately follow a section header in the Declaratives Section and must be followed by a period followed by a space. The USE statement in COBOL itself is never executed; it merely defines the conditions calling for the execution of the USE procedures.

 

[ Go to Top of Page ]
 

COBOL Write

 > COBOL Write Verb
The COBOL WRITE verb is demonstrated in COBOL program examples on how to process sequential files.

 > COBOL Write Statement - HP COBOL II/XL
The COBOL WRITE statement releases a logical record. To use the COBOL WRITE statement for a sequential file, the file must be opened in the OUTPUT or EXTEND mode. To use the COBOL WRITE statement with an indexed, relative, or random file, the file must be opened in either OUTPUT, I-O mode, or EXTEND for access mode sequential. For sequential files, the COBOL WRITE statement may additionally be used for vertical positioning of lines within a logical page.

 > COBOL Write Statement
The COBOL WRITE statement releases a logical record for an output or input/output file. When the WRITE statement in COBOL is executed, the associated sequential file must be open in OUTPUT or EXTEND mode; the associated indexed or relative file must be open in OUTPUT, I-O, or EXTEND mode.

 > Write Statement in COBOL - IBM AIX
The COBOL WRITE statement releases a logical record to an output or input/output file.

 > Write Statement in COBOL - Micro Focus Visual COBOL
The COBOL WRITE statement releases a logical record for an output or input-output file. The COBOL phrases ADVANCING PAGE and END-OF-PAGE must not both be specified in a single WRITE statement in COBOL.

 

[ Go to Top of Page ]
 

COBOL XML Generate

 > COBOL XML GENERATE Statement - IBM COBOL AIX
The COBOL XML GENERATE statement converts data to XML format.

 > COBOL XML GENERATE Statement - Micro Focus Visual COBOL
The COBOL XML GENERATE statement converts data to XML format.

 > Operation of the COBOL XML GENERATE Statement - ILE COBOL
Describes the operation of the COBOL XML GENERATE statement.

 > Using XML and COBOL Together - Micro Focus Net Express
Describes support for XML including an explanation of XML, XML schemas, and how XML fits in with COBOL.

 > XML GENERATE Statement in COBOL - ILE COBOL
The XML GENERATE statement in COBOL converts data to XML format.

 

[ Go to Top of Page ]
 

COBOL XML Parse

 > COBOL XML PARSE Statement - IBM COBOL AIX
The COBOL XML PARSE statement is the COBOL language interface to the high-speed XML parser that is part of the COBOL run time. The XML PARSE statement in COBOL parses an XML document into its individual pieces and passes each piece, one at a time, to a user-written processing procedure. COBOL XML PARSE statements must not be specified in declarative procedures.

 > Processing XML input - COBOL for AIX
You can process XML input in your COBOL program by using the XML PARSE statement in COBOL. The COBOL XML PARSE statement is the COBOL language interface to the high-speed XML parser, which is part of the COBOL run time. You start this exchange of control with the COBOL XML PARSE statement, which specifies a processing procedure that receives control from the XML parser to handle the parser events.

 > XML PARSE in COBOL - COBOL for AIX
COBOL for AIX provides an event-based interface that enables you to parse XML documents and transform them to COBOL data structures. The XML parser finds fragments (associated with XML events) within the document, and your processing procedure acts on these fragments.

 
[ Go to Top of Page ]
Visual COBOL Ad
COBOL Database Tool - Faircom Database Technology Ad
COBOL Application Modernization - Fresche Legacy Ad
COBOL Application Modernization - EvolveWare Ad
NetCOBOL - GT Software Ad
COBOL Legacy Mainframe Migration - Transoft Ad
COBOL Interpreter - McKinney Ad








COBOL Job Seekers
COBOL Jobs Looking for a COBOL job? Submit your resume here and have it viewed by employers and recruiters hiring for COBOL positions.

Employers & Recruiters
Post COBOL Jobs Do you need to fill a COBOL position? Post your COBOL jobs here and find the most qualified COBOL candidates to fill your COBOL position.

Call for Articles
COBOL Newsletters Articles are being sought for the COBUG newsletters.
Will you help us in our efforts to provide newsletters for the COBOL community at large? Contribute to the COBUG newsletters! Answer this call for COBOL and related legacy articles.

Local COBOL User Groups
COBOL User Group Check out the list of local COBOL user groups from around the world and join a user group near you.


Call for User Group Leaders!
COBOL User Groups Get Involved! We are looking for user group leaders to help organize and coordinate a local COBOL user group.

Join COBUG!
COBOL User Groups Become a part of COBUG and the global COBOL community today. Join Now ...


COBOL Forums
COBOL Forum Try our COBOL forums for help!
Let the COBUG members help you. Post your issues!


COBOL (c) Information Computing Services. All Rights Reserved. COBOL