COBOL syntax, commands, verbs, statements and clauses such as COBOL inspect, accept, COBOL call, initialize, Set,

COBOL string, occurs, COBOL read, sort, 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 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 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 Table COBOL Terminate COBOL Transform COBOL Try COBOL Unlock COBOL Unstring COBOL Use COBOL Write COBOL XML Generate COBOL XML Parse
COBOL Accept

> ACCEPT Statement in COBOL The ACCEPT statement in COBOL can be used for low volume input from a specified device. The ACCEPT statement in COBOL has three general formats. > COBOL ACCEPT Verb The COBOL ACCEPT and DISPLAY verbs are 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 The COBOL ACCEPT 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. > COBOL ACCEPT Statement The COBOL ACCEPT statement is described as it is presented in the Compaq COBOL User Manual. The COBOL ACCEPT statement (Formats 3, 4, and 5) are described. [ Go to Top of Page ] COBOL ASSIGN TO PRINTER This statement allows for you to print on a local printer port. Be careful not to overuse as to save cartridge ink. COBOL ASSIGN TO LPT1 An acceptable variation to ASSIGN TO PRINTER to print to the default printer. NETWORK PRINTING To print on a network printer you would use the command "net use lpt1 \\pcname\printer-name" from your command prompt window.
COBOL Alter

> ALTER Statement in COBOL 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 COBOL ALTER statement and helps ensure that your program will be well-structured. > COBOL ALTER Statement The ALTER statement in COBOL 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

> COBOL COMMIT Statement The COBOL COMMIT 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 The COBOL COMMIT statement in COBOL 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

> COBOL COMPUTE Command The COBOL COMPUTE command assigns the value of an arithmetic expression to a specified reference. The COBOL COMPUTE keyword cannot be abbreviated. > COBOL COMPUTE Statement 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 The COBOL COMPUTE statement evaluates an arithmetic expression and stores the result in one or more data items. > COBOL COMPUTE Statement 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. > Examples of COBOL COMPUTE Statement Using parentheses in the COBOL COMPUTE statement to clarify as well as to group operations. [ Go to Top of Page ]
COBOL Continue

> COBOL CONTINUE Clause It explains the purpose of the COBOL CONTINUE clause and describes how it is used. COBOL NEXT SENTENCE is used in place of CONTINUE in COBOL 74. > COBOL CONTINUE Statement The COBOL CONTINUE statement allows you to specify a no operation statement. COBOL CONTINUE 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. > COBOL CONTINUE Statement The COBOL CONTINUE statement can be used anywhere a conditional statement or an imperative statement is used. > COBOL CONTINUE Verb The COBOL CONTINUE verb is most useful within a conditional phrase of another statement when no action is desired when the condition occurs. > COBOL CONTINUE vs COBOL NEXT SENTENCE The COBOL CONTINUE verb means "do nothing." NEXT SENTENCE in COBOL is actually an unconditional branch to whatever follows the next period. In effect, it is a restricted form of the COBOL GO TO. > COBOL CONTINUE vs

NEXT SENTENCE in COBOL What exactly is the difference between the COBOL CONTINUE and COBOL NEXT SENTENCE? > COBOL NEXT SENTENCE Phrase This phrase causes the transfer of control to an implicit COBOL CONTINUE statement immediately preceding the next separator period. If the COBOL NEXT SENTENCE phrase is specified, the END-SEARCH phrase must not be specified. [ Go to Top of Page ]
COBOL Disable

> COBOL DISABLE Statement COBOL DISABLE Syntax Circa 1988. > COBOL DISABLE Statement COBOL DISABLE statement flagged. > COBOL DISABLE Statement The COBOL DISABLE statement notifies the MCS to inhibit data transfer between specified output queues and destinations for output or between specified sources and input queues for input. The KEY phrase of the COBOL DISABLE 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. [ 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. > COBOL ENABLE Statement COBOL ENABLE statement flagged. > COBOL ENABLE Statement The COBOL ENABLE statement notifies the MCS to allow data transfer between specified output queues and destinations for output or between specified sources and input queues for input. The KEY phrase of the COBOL ENABLE 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. [ Go to Top of Page ]
COBOL Enter

> COBOL ENTER Statement 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 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 COBOL ENTER statement allows the use of more than one source language in the same source program. The COBOL/400 compiler allows only COBOL in the source program. > COBOL ENTER Statement 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 COBOL ENTER statement allows the use of more than one source language in the same source program. > COBOL ENTER Statement The ENTER statement 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 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 COBOL ENTRY statement must be in a paragraph. > COBOL ENTRY Statement 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 COBOL ENTRY statement. > COBOL ENTRY Statement The COBOL ENTRY statement establishes an alternate entry point into a called COBOL program. The COBOL ENTRY statement cannot be used in a program that is nested within another program. > ENTRY Statement in COBOL Diagram of the COBOL ENTRY syntax. > Multiple Entry Points in COBOL If there are multiple entry points in COBOL, only one of them (at most) can have the same name as the module. It is harder to guess the module name from the entry point name. [ Go to Top of Page ]
COBOL EXECute

> COBOL EXEC(UTE) Statement The COBOL EXEC(UTE) statement is provided as a linkage mechanism to allow control to be passed to non-COBOL subsystems. > COBOL EXEC(UTE) Statement The COBOL EXEC(UTE) statement is provided as a linkage mechanism to allow control to be passed to non-COBOL subsystems. The formats COBOL EXEC(UTE) CICS, COBOL EXEC(UTE) SQL, and COBOL EXEC(UTE) DLI cause the appropriate system component (variously known as preprocessors, co-processors and external compiler modules) to be called to process text-data if the corresponding Compiler directive is specified that invokes that system component. > COBOL EXEC SQL Statement SQL statements are embedded in COBOL using the EXEC SQL and END-EXEC delimiters. [ 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. > EXHIBIT in COBOL The EXHIBIT statement in COBOL causes an (optionally conditional) display of the literals, and/or identifiers (optionally preceded by the identifier name) specified in the statement. Literals and identifiers displayed by the COBOL EXHIBIT statement are separated by a space on the displayed line. [ Go to Top of Page ]
COBOL EXIT

> COBOL EXIT PROGRAM Statement The COBOL EXIT PROGRAM statement specifies the end of a called program and returns control to the calling program. > COBOL EXIT Statement The COBOL EXIT statement provides a common end point for a series of paragraphs. The COBOL EXIT statement must be preceded by a paragraph-name and must appear in a sentence by itself. > COBOL EXIT Statement The COBOL EXIT statement provides a common end point for a series of procedures. The COBOL EXIT statement 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 COBOL EXIT METHOD 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 The COBOL EXIT statement provides a common end point for a series of procedures. The COBOL EXIT 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. > COBOL EXIT Syntax Illustrates the format of the COBOL EXIT, COBOL EXIT FUNCTION, COBOL EXIT METHOD, COBOL EXIT PERFORM, COBOL EXIT Paragraph and COBOL EXIT PROGRAM syntax. > COBOL EXIT Verb Provides a diagram for the COBOL EXIT verb Circa 1988. > EXIT Statement in COBOL The EXIT statement in COBOL provides a common end point for a series of procedures. EXIT in COBOL must appear in a sentence by itself. EXIT in COBOL must be the only sentence in a paragraph. The COBOL EXIT statement 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 - File Description - 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 The COBOL FD, file description comprises information concerning the physical structure, identification, and record-names pertaining to a given file. The COBOL FD, file description entry also determines whether a file-name is a local name or a

global name. > COBOL FD - File Description - IBM 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. > COBOL FD - Syntax of COBOL Circa 1988 COBOL FD: File_definition::=("FD" file_name... [ Go to Top of Page ]
COBOL FILLER

> COBOL Filler - HP COBOL II/XL The keyword, COBOL FILLER, implies that you are specifying an elementary item of the logical record being described that cannot be referenced explicitly. If this clause is omitted, the record is treated as though COBOL FILLER had been specified. Although you may not refer to a COBOL FILLER item explicitly, the keyword COBOL FILLER may be used as a conditional variable (format 3) because the use of it in this manner does not require explicit reference to the COBOL FILLER item, but to its value. > 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. > COBOL Filler - Tutorial The COBOL FILLER is a special type of COBOL field. COBOL FILLER 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. COBOL FILLER 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. [ Go to Top of Page ]
COBOL GENERATE

> COBOL GENERATE Statement The COBOL GENERATE statement directs the Report Writer Control System (RWCS) to produce a report according to the Report Description entry (RD) in the Report Section of the Data Division. > COBOL GENERATE Statement Provides a diagram for the COBOL GENERATE syntax Circa 1988. > COBOL GENERATE Statement COBOL GENERATE statement flagged. > COBOL GENERATE Statement The COBOL GENERATE statement directs the RWCS to produce a report in accordance with the Report Description specified in the Report Section of the Data Division. > COBOL GENERATE Statement COBOL GENERATE 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 Statement - 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 COBOL GOBACK statement marks the logical end of a program. The COBOL GOBACK statement is an HP extension to the ANSI COBOL standard. > COBOL GOBACK Statement - IBM 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 COBOL GOBACK statement specifies the logical end of a called program or invoked method. > COBOL GOBACK Verb - Micro Focus COBOL Illustrates the format of the COBOL GOBACK statement. > GOBACK in COBOL - Micro Focus COBOL The COBOL GOBACK statement marks the logical end of a called program. If a COBOL GOBACK 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 GO TO

> COBOL GO TO Statement The COBOL GO TO statement transfers control from one part of the Procedure Division to another. COBOL GO TO has three formats. > COBOL GO TO Statement 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 COBOL 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 Provides a diagram for the COBOL GO TO syntax Circa 1988. > COBOL GO TO Verb Illustrates the format of the COBOL GO TO verb. > GO TO in COBOL The GO TO statement in COBOL 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 Statement The COBOL INITIALIZE statement sets selected types of data fields to predefined values. The COBOL INITIALIZE can set numeric data to zeros or alphanumeric data to spaces. > COBOL INITIALIZE Statement 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 Verb A discussion on how COBOL INITIALIZE verb would treat FILLER items in

WORKING-STORAGE. > COBOL INITIALIZE Verb Presents an example and discussion of using the COBOL INITIALIZE verb. > INITIALIZE in COBOL - Micro Focus The INITIALIZE statement in COBOL provides the ability to set selected data items to specified values. > INITIALIZE in COBOL - IBM AIX The INITIALIZE statement in COBOL sets selected categories of data fields to predetermined values. The COBOL INITIALIZE statement is functionally equivalent to one or more MOVE statements. [ Go to Top of Page ]
COBOL Inspect

> COBOL INSPECT Statement The COBOL INSPECT statement specifies that characters in a data item are to be counted (tallied) or replaced, or both. > COBOL INSPECT Statement ILE COBOL examples illustrate some uses of the COBOL INSPECT statement. > COBOL INSPECT Statement COBOL examples illustrate how the COBOL INSPECT statement is use in COBOL programs. > COBOL INSPECT Verb The COBOL INSPECT verb is presented in a COBOL example program. The way the COBOL INSPECT works is explained and its modifying phrases are explored in COBOL string handling. [ 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 statement in COBOL 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 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. > COBOL INVOKE Statement The COBOL INVOKE statement causes a method to be invoked. > INVOKE Statement in COBOL - Micro Focus Visual COBOL The INVOKE statement in COBOL causes a method to be invoked. > INVOKE Statement in COBOL Diagram of the COBOL INVOKE syntax. [ Go to Top of Page ]
COBOL Multiply

> COBOL MULTIPLY Statement The COBOL MULTIPLY statement multiplies numeric items and sets the values of data items equal to the results. The COBOL MULTIPLY statement has two formats. > COBOL MULTIPLY Statement - IBM AIX The MULTIPLY statement in COBOL multiplies numeric items and sets the values

of data items equal to the results. > COBOL MULTIPLY Statement The COBOL MULTIPLY statement multiplies two numeric operands and stores the product in one or more data items. > COBOL MULTIPLY Statement - Micro Focus Visual COBOL The COBOL MULTIPLY statement causes numeric data items to be multiplied and sets the values of data items equal to the results. > MULTIPLY Statement in COBOL The MULTIPLY statement in COBOL multiplies a number by one or more other numbers and stores the result in one or more locations. [ Go to Top of Page ]
COBOL Note

> COBOL NOTE Statement - HP 3000 For OSVS only, the COBOL NOTE statement introduces a sentence or paragraph that will be treated as comments. > COBOL NOTE Statement - IBM Enterprise COBOL for z/OS Enterprise COBOL does not support the following OS/VS COBOL language elements. 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 Server Express The NOTE statement in COBOL introduces a sentence or paragraph that will be treated as comments. > COBOL NOTE Statement - Micro Focus Visual COBOL The COBOL NOTE statement introduces a sentence or paragraph that will be treated as comments. If a NOTE statement in COBOL 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 Service Company 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, Compaq COBOL Reference Manual The COBOL OCCURS clause defines tables and provides the basis for subscripting and indexing. It eliminates the need for separate entries for repeated data items. > COBOL Occurs Clause, Digital Equipment Corp. The COBOL OCCURS clause defines tables and provides the basis for subscripting and indexing. It eliminates the need for separate entries for repeated data items. > COBOL Occurs Clause, HP COBOL II/XL Reference Manual The COBOL OCCURS clause is used to define a table containing[REV BEG] up to seven dimensions.[REV END] Its use 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. [ 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-ONcounter), is initialized to be zero. [ Go to Top of Page ]
COBOL Open

> COBOL OPEN Statement - Compaq COBOL The COBOL OPEN statement creates an access stream to the file, makes the file available to the program, begins the processing of a file, and specifies file sharing. > COBOL OPEN Statement - HP COBOL II/XL The COBOL OPEN statement opens a specified file or files. The COBOL OPEN statement 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. The COBOL OPEN also performs checking and/or writing of labels and other input-output operations. > COBOL OPEN Statement - System z, COBOL for Windows 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. The COBOL OPEN statement 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. > COBOL RAISE Statement netCOBOL 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 The COBOL READ statement makes a record of a file available to your program. There are three formats to COBOL READ depending on the type of organization of the file from which a record is made available. > COBOL Read Statement The COBOL READ statement makes a record available to the program. For sequential access, the COBOL READ statement 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. When the COBOL READ statement is executed, the associated file must be open in INPUT or I-O mode. > COBOL Read Statement 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. > COBOL Read Relative File The COBOL READ statement is described in reading a relative file sequentially, randomly, and dynamically. > Read Statement in COBOL 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. > COBOL Ready Trace - HP-UX COBOL The COBOL READY TRACE statement is a debugging feature which causes each section and paragraph name subsequently reached to appear on the screen in order of execution. [ Go to Top of Page ]
COBOL Redefines

> COBOL REDEFINES Can the COBOL REDEFINES clause be used at 01 level? > COBOL REDEFINES Clause The COBOL REDEFINES clause allows different data description entries to describe the same storage area. > 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 the same computer memory area to be described by different data items. > 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 - Compaq COBOL The COBOL REPLACE statement is used to replace source program text. A COBOL REPLACE statement can be inserted anywhere that a character-string can be used. > 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

> COBOL RESUME Statement - netCOBOL RESUME statement in COBOL: RESUME AT NEXT STATEMENT procedurename - transfers control from declarative to program body. [ 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 - HP 3000 / Micro Focus COBOL The COBOL SERVICE statement is used to establish addressability to Linkage Section items usually in a CICS program. > 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. > COBOL Start Statement - Compaq COBOL The COBOL START statement establishes the logical position of the File Position Indicator in an indexed or relative file. > 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 - 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. > 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 String

> COBOL STRING Example The COBOL STRING verb is presented in a COBOL example program. > STRING in COBOL The COBOL STRING statement is described in the HP COBOL II/XL Reference Manual, and STRING COBOL examples are provided in programs. The COBOL STRING statement concatenates the partial or complete contents of two or more data items into a single data item. > STRING in COBOL The COBOL STRING statement is described in the COBOL/400, iSeries Language Help Manual. The STRING statement in COBOL strings together the partial or complete contents of two or more data items or literals into one single data item. One STRING COBOL statement can replace a series of MOVE statements. When the COBOL STRING statement is executed, data is transferred from the sending field to the receiving field. Any subscripting and reference modification is performed only once, at the beginning of the execution of the COBOL STRING statement. [ Go to Top of Page ]
COBOL Suppress

> COBOL Suppress Statement - Compaq COBOL The COBOL SUPPRESS statement causes the Report Writer Control System (RWCS) to inhibit the presentation of a report group. The COBOL SUPPRESS statement can appear only in a USE BEFORE REPORTING Declarative procedure. > COBOL Suppress Statement - HP MPE/iX The COBOL SUPPRESS statement provides the object time facility to suppress the printing of an entire report group. > COBOL Suppress Verb - Syntax of COBOL Circa 1988 COBOL Suppress_Verb::= "SUPPRESS PRINTING"|"SUPPRESS > Suppress Statement in COBOL - COBOL/HP-UX The SUPPRESS statement in COBOL causes the RWCS to inhibit the presentation of a report group. The COBOL SUPPRESS statement can only appear in a USE BEFORE REPORTING procedure. [ Go to Top of Page ]
COBOL Terminate

> COBOL Terminate Statement - Compaq COBOL The COBOL TERMINATE statement causes the Report Writer Control System (RWCS) to complete the processing of the specified report. > 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 - Compaq COBOL COBOL UNLOCK statement removes a record lock from the current record or from all locked records in the file. The X/Open standard COBOL UNLOCK statement always removes the record lock from all locked records in the file. > 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 Examples The COBOL UNSTRING verb is presented in a COBOL example program. > COBOL UNSTRING Statement The COBOL UNSTRING verb is described in COBOL course notes. The syntax, functioning and rules of the COBOL UNSTRING verb are examined, and abstract and pratical COBOL program examples are provided. > COBOL UNSTRING

Statement The COBOL UNSTRING statement divides data in a sending field and places the segments of the data into multiple receiving fields. > COBOL UNSTRING Verb The COBOL UNSTRING statement separates contiguous data in a sending field and stores it in one or more 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 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 highspeed 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