| In a Mainframe environment, changes done to program source-code should be well-documented. This makes the source-code easier to understand. Most COBOL Programs have a Modification Log. The Modification-Log is not executable source code, rather it is a block of comments. It is a the list of all changes(modifications) done to the program, in chronological order. A description of the change in about two-to-three lines, the date of the change and the author(programmer) is also mentioned. The Modification Log helps you track all changes done to program, right from its inception, to-date, its like the program’s diary(log). Each entry in the Modification Log has a tag, to identify it. This tag forms its unique identity. The practise adopted by Mainframe programmers is to supply a tag for all the lines of source-code they modify, and then add an entry to Modification Log, under the same tag, thus providing a brief description of their change. Here's a picture of the Modification log in one of my programs.
Have a look at the illustration below on, how the same modification tag QC3962 is used to highlight the modified lines of code.
|
| Several people have asked for a way to automatically add a tag, and flag each changed line in an ISPF Edit Session. The COBOL Code Tagger is an Edit Macro that runs SuperC against the original dataset and adds tags in a user-specified column. After the tagging is complete, you are shown the lines to which flags have been added. You’ll probably need to change it to meet your needs, but it should be a reasonable starting point.
|
| It is very easy to use the COBOL Code Tagger. In the ISPF Editor, while editing a COBOL Program, merely type TAG <tag-name> <start-column> to add tags to all lines you have changed. I type the command TAG QC0624 01 to tag all the lines I have modified, in this COBOL Program with QC0610, beginning from Column Position=01.
On pressing ENTER, the Macro tags the lines, you modified in this EDIT Session.
|