HP 3000 Manuals HP 3000 Manuals
Procedure Division in COBOL Debug For OSVS and VSC2 only: The READY TRACE Statement Function. The READY TRACE statementis a debugging feature which causes each section and paragraph name subsequently reached to appear on the screen in order of execution. For VSC2 only: General Format.General Rules. 1. The COBOL system directive TRACE must be set to on to allow execution of the statement. When the directive is not set, READY TRACE is documentary only. (See your COBOL System Reference for details on setting the TRACE directive.) 2. For VSC2 only: READY TRACE is accepted, but is treated as documenatary only. For OSVS and VSC2 only: The RESET TRACE Statement Function. For VSC2 only: The RESET TRACE statement disables the tracing of section and paragraph names on the screen. General Format.General Rules. 1. The COBOL system directive TRACE must be set to on to allow execution of the statement. When the directive is not set or when no previous READY TRACE is in effect, RESET TRACE is documentary only. (See your COBOL System Reference for details on setting the TRACE directive.) 2. For VSC2 only: RESET TRACE is accepted, but is treated as documentary only . The USE FOR DEBUGGING Statement Function. The USE FOR DEBUGGINGstatementidentifies the user items that are to be monitored by the associated debugging section. General Format.Run-time Switches. 1. The following run-time switch may impact either the syntax or semantics described in this section. See your COBOL System Reference for details. * D - Activates ANSI Debug facilities. Syntax Rules. 1. Debugging section(s), if specified, must appear together immediately after the DECLARATIVES header. 2. Except in the USE FOR DEBUGGING statement itself, there must be no reference to any non-declarative procedure in the debugging section. For OSVS, VSC2 and MF only: This restriction is not enforced. 3. Statements appearing outside of the set of debugging sections must not reference procedure-names defined in the set of debugging sections. 4. Except for the USE FOR DEBUGGING statement itself, statements appearing in a given debugging section can reference procedure-names defined in a different USE procedure only with a PERFORM statement. 5. Procedure-names defined in debugging sections must not appear in USE FOR DEBUGGING statements. 6. Any given identifier, cd-name, file-name, or procedure-name can appear in only one USE FOR DEBUGGING statement and can appear only once in that statement. 7. The ALL PROCEDURES phrasecan appear only once in a program. 8. When the ALL PROCEDURES phrase is specified, procedure-name-1 must not be specified in any USE FOR DEBUGGING statement. 9. If the data description entry of the data item referenced by identifier-1 contains an OCCURS clause or is subordinate to a data description entry that contains an OCCURS clause, identifier-1 must be specified without the subscripting or indexing normally required. 10. References to the special register DEBUG-ITEMare restricted to references from within a debugging section. General Rules. 1. Automatic execution of a debugging section is not caused by a statement appearing in a debugging section. 2. When file-name-1 is specified in a USE FOR DEBUGGING statement, that debugging section is executed: a. After the execution of any OPEN or CLOSE statement that references file-name-1, and: b. After the execution of any READ statement (after any other specified USE procedure) not resulting in the execution of an associated AT END or INVALID KEY imperative statement, and: c. After the execution of any DELETE or START statement that references file-name-1. 3. When procedure-name-1 is specified in a USE FOR DEBUGGING statementthat debugging section is executed: a. Immediately before each execution of the named procedure. b. Immediately after the execution of an ALTER statement which references procedure-name-1. 4. The ALL PROCEDURES phrasecauses the effects described in General Rule 4 to occur for every procedure-name in the program, except those appearing in a debugging section. 5. When the phrase, ALL REFERENCES OF identifier, is specified, that debugging section is executed for every statement that explicitly references identifier-1 at each of the following times: a. In the case of a WRITE or REWRITE statement immediately before the execution of that WRITE or REWRITE statement and after the execution of any implicit move resulting from the presence of the FROM phrase. b. In the case of a GO TO statement with a DEPENDING ON phrase, immediately before control is transferred and prior to the execution of any debugging section associated with the procedure-name to which control is to be transferred. c. In the case of a PERFORM statement in which a VARYING, AFTER, or UNTIL phrase references identifier-1, immediately after each initialization, modification or evaluation of the contents of the data item referenced by identifier-1. d. In the case of any other COBOL statement, immediately after execution of that statement. If identifier-1 is specified in a phrase that is not executed or evaluated, the associated debugging section is not executed. 6. When identifier-1 is specified without the ALL REFERENCES OF phrase, that debugging section is executed at each of the following times: a. In the case of a WRITE or REWRITE statement that explicitly references identifier-1, immediately before the execution of that WRITE or REWRITE statement and after the execution of any implicit move resulting from the presence of the FROM phrase. b. In the case of a PERFORM statement in which a VARYING, AFTER or UNTIL phrase references identifier-1, immediately after each initialization, modification or evaluation of the contents of the data item referenced by identifier-1. c. Immediately after the execution of any other COBOL statement that explicitly references and causes the contents of the data item referenced by identifier-1 to be changed. If identifier-1 is specified in a phrase that is not executed or evaluated, the associated debugging section is not executed. 7. The associated debugging section is not executed for a specific operand more than once as a result of the execution of a single statement, regardless of the number of times that operand is explicitly specified. In the case of a PERFORM statement which caused iterative execution of a referenced procedure, the associated debugging section is executed once for each iteration. Within an imperative statement, each individual occurrence of an imperative verb identifies a separate statement for the purpose of debugging. 8. When cd-name-1 is specified in a USE FOR DEBUGGING statement, that debugging section is executed: a. After the execution of any ENABLE, DISABLE, and SEND statement that references cd-name-1, b. After the execution of a RECEIVE statement referencing cd-name-1 that does not result in the execution of the NO DATA imperative-statement, and c. After the execution of an ACCEPT MESSAGE COUNT statement that references cd-name-1. 9. A reference to file-name-1, identifier-1, procedure-name-1 or cd-name-1 as a qualifier does not constitute reference to that item for the debugging described in the General Rules above. 10. Associated with each execution of a debugging section is the special register DEBUG-ITEM, which provides information about the conditions that caused the execution of a debugging section. DEBUG-ITEM has the following implicit description: 01 debug-item. 02 debug-line pic x(6). 02 filler pic x value space. 02 debug-name pic x(30). 02 filler pic x value space. 02 debug-sub-1 pic s9999 sign is leading separate character. 02 filler pic x value space 02 debug-sub-2 pic s9999 sign is leading separate character. 02 filler pic x value space. 02 debug-sub-3 pic s9999 sign is leading separate character. 02 filler pic x value space. 02 debug-contents pic x(n). 11. Prior to each execution of a debugging section, the contents of the data item referenced by DEBUG-ITEM are space-filled. The contents of data items subordinate to DEBUG-ITEM are then updated, according to the following general rules, immediately before control is passed to that debugging section. The contents of any data item not specified in the following general rules remains spaces. Updating is accomplished in accordance with the rules for the MOVE statement, the sole exception being the move to DEBUG-CONTENTS when the move is treated exactly as if it was an alphanumeric to alphanumeric elementary move with no conversion of data from one form of internal representation to another. 12. The contents of DEBUG-LINE is the relevant COBOL source line number. This provides the means of identifying a particular source statement. 13. DEBUG-NAME contains the first 30 characters of the name that caused the debugging section to be executed. All qualifiers of the name are separated in DEBUG-NAME by the word IN or OF. Subscripts/indices, if any, are not entered into DEBUG-NAME. 14. If the reference to a data item that causes the debugging section to be executed is subscripted or indexed, the occurrence number of each level is entered in DEBUG-SUB-1, DEBUG-SUB-2, DEBUG-SUB-3, respectively, as necessary. 15. DEBUG-CONTENTS is a data item that is large enough to contain the data required by the following General Rules. 16. If the first execution of the first nondeclarative procedure in the program causes the debugging section to be executed, the following conditions exist: * DEBUG-LINE identifies the first statement of that procedure. * DEBUG-NAME contains the name of that procedure. * DEBUG-CONTENTS contains "START PROGRAM". 17. If a reference to procedure-name-1 in an ALTER statement causes the debugging section to be executed, the following conditions exist: * DEBUG-LINE identifies the ALTER statement that references procedure-name-1. * DEBUG-NAME contains procedure-name-1. * DEBUG-CONTENTS contains the applicable procedure-name associated with the TO phrase of the ALTER statement. 18. If the transfer of control associated with the execution of a GO TO statement causes the debugging section to be executed, the following conditions exist: * DEBUG-LINE identifies the GO TO statement whose execution transfers control to procedure-name-1. * DEBUG-NAME contains procedure-name-1. 19. If reference to procedure-name-1 in the INPUT or OUTPUT phrase of a SORT or MERGE statement causes the debugging section to be executed, the following conditions exist: * DEBUG-LINE identifies the SORT or MERGE statement that references procedure-name-1. * DEBUG-NAME contains procedure-name-1. * DEBUG-CONTENTS contains: * If the reference to procedure-name-1 is the INPUT phrase of a SORT statement, "SORT INPUT". * If the reference to procedure-name-1 is in the OUTPUT phrase of a SORT statement, "SORT OUTPUT". * If the reference to procedure-name-1 is in the OUTPUT phrase of a MERGE statement, "MERGE OUTPUT". 20. If the transfer to control from the control mechanism associated with a PERFORM statement causes the debugging section associated with procedure-name-1 to be executed, the following conditions exist: * DEBUG-LINE identifies the PERFORM statement that references procedure-name-1. * DEBUG-NAME contains procedure-name-1. * DEBUG-CONTENTS contains "PERFORM LOOP". 21. If procedure-name-1 is a USE procedure that is to be executed, the following conditions exist: * DEBUG-LINE identifies the statement that causes execution of the USE procedure. * DEBUG-NAME contains procedure-name-1. * DEBUG-CONTENTS contains "USE PROCEDURE". 22. If an implicit transfer of control from the previous sequential paragraph to procedure-name-1 causes the debugging section to be executed, the following conditions exist: * DEBUG-LINE identifies the previous statement. * DEBUG-NAME contains procedure-name-1. * DEBUG-CONTENTS contains "FALL THROUGH". 23. If references to file-name-1, cd-name-1 causes the debugging section to be executed, then: * DEBUG-LINE identifies the source statement that references file-name-1, cd-name-1. * DEBUG-NAME contains the name of file-name-1, cd-name-1. * For READ, DEBUG-CONTENTS contains the entire record read. * For all other references to file-name-1, DEBUG-CONTENTS contains spaces. * For any reference cd-name-1, DEBUG-CONTENTS contains the contents of the area associated with the cd-name. 24. If a reference to identifier-1 causes the debugging section to be executed, then: * DEBUG-LINE identifies the source statement that references identifier-1, * DEBUG-NAME contains the name of identifier-1, and: * DEBUG-CONTENTS contains the contents of the data item referenced by identifier-1 at the time that control passes to the debugging section (see General Rules 5 and 6). Debugging Lines A debugging lineis any line with a "D" or "d" in the indicator area of the line. Any debugging line that consists solely of spaces from margin A to margin R is considered the same as a blank line. The contents of a debugging line must be such that a syntactically correct program is formed with or without the debugging lines being considered as comment lines. 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. Successive debugging lines are allowed. Continuation of debugging lines is permitted, except that each continuation line must contain a "D" or "d" in the indicator area, and character-strings can not be broken across two lines. A debugging line is permitted in the program only after the OBJECT-COMPUTER paragraph.
NOTE Debugging lines are part of the ANSI Nucleus and not the ANSI Debug module. Therefore, they are not obsolete and are not scheduled to be deleted from the next full revision of the ANSI Standard.
![[]](../../pic3k/M015065/FFN443c50.gif)
![[]](../../pic3k/M015065/FFN453c50.gif)
![[]](../../pic3k/M015065/FFN463c50.gif)