Many of the application teams use “tags” in columns 1-6 of their Cobol modules to keep track of specific changes made to the code. One of the application teams has reported seeing a discrepancy in the lines of code where these “tags” are displayed. New tags are showing up on lines of old code changes or on change levels where they are not expected to be. The concern is not with the actual code but with the tags (present in columns 1-6).
One example provided was tag “SG6413”. These lines were added at level 0151:
%+0151 SG6413 05 WS-ACC-PTOTST-VISITS PIC S9(03) VALUE +0
%+0151 SG6413 COMP-3.
Type COBOL is defined as follows for all systems defined to Endevor. Data in columns 1-6 is not considered as part of the comparison of changes:
----------------- ELEMENT OPTIONS -------------------
DELTA FORMAT(F/R/I/L) ===> R SOURCE LEN ===> 80 ELE RECFM(N/F/V) ===> N
COMPRESS/ENCRYPT(Y/N) ===> Y COMPARE FROM ===> 7 DFLT PROC ===> SRCONLY
AUTO CONSOL (Y/N) ===> Y COMPARE TO ===> 72 LANGUAGE ===> DATA
CONSOL AT LVL ===> 96 REGRESSION ===> 50 PV/LB LANG ===> DATA
LVLS TO CONSOL ===> 46 REG SEV(I/W/C/E) ===> C DATA FORMAT(T/B) ===> T
USS RECFM(COMP/CR/CRLF/CRNL/F/LF/NL/V) ===> NL FILE EXT ===>
As Endevor does not consider the first 6 columns while comparing, it ends up creating this confusion with the code tags whenever the new code that is being added is same as already existing code with only difference being in the Code Tag?
Release : 18.1
Component : CA Endevor Software Change Manager
The type is set up to only check columns 7 to 72 for changes. Anything outside those columns is not considered a change. When a change is detected, the entire line is updated, including the excluded columns. That can present some unexpected results when looking at those columns with a reverse delta.