Peter, et al: I am quite interested in git. And so I thought I would address a statement made about COBOL Numbering, and "standard" numbering locations in source.
There are some products that ship source and do use COBOL numbering while others use the 73-80 numbering (both are COBOL based products). In either case, they are generally maintained by using IEBUPDTE to insert the maintenance and/or USER changes. I know of some user source that is maintained that way because that source is used where different "mods" have to be applied (terminology not to imply any relationship to SMPE). So, where I am working, I am given to understand that there is a POC going with git. If they do not understand our shop, this could cause a headache (the stripping or ignoring 1-6 and/or 73-80). In source that I maintain, the change codes are in 73-80, while NUM COB is used (ISPF), I don't care about that information -- I care about the change codes for what I maintain. But I am just waiting for the chance to use git for ISPF panels, skeletons, COBOL source, REXX and ALC code that I am responsible for. I'd like to run into the problems before the applications people have a chance to hit it so we can head that all off. And I'd love to know the answers to this before the POC dies. So I am very interested in this thread. Regards, Steve Thompson --- [email protected] wrote: From: "Farley, Peter x23353" <[email protected]> To: [email protected] Subject: Re: [IBM-MAIN] git, z/OS and COBOL Date: Tue, 10 Oct 2017 17:50:10 +0000 Frank, The *ix compare utility is usually the "diff" command, and looking up the possible parameters for "diff" I don't see any options that would allow filtering the columns compared. It should be possible to craft a shell script to chop the line numbers off in temporary files and then do the compare with the chopped files, but the output would not, of course, reflect the line numbers in the difference listing (or "patch" compatible output file). Another possible issue would be whether it is even possible to make git use the shell script instead of "diff", and whether or not that is even desirable for any language but COBOL. Looks like an opportunity for someone to contribute to the open-source community to implement a column filter for the "diff" and "patch" suite, and maybe "git" as well. Alternatively, do your programmers really make any sensible real-world use of COBOL line numbers in columns 1-6, or is it just "tradition"? After all, no one has had to use a card sorter to re-order a program source whose card tray was dropped on the floor for some decades. I abandoned using any line numbers at all in any language many years ago, and I use those (now just comment) COBOL line number columns to "tag" changed COBOL lines during maintenance edits to identify the project for which the change was done. I use ISPF "UNNUM" on all numbered source programs when I first edit them to remove all line numbering. COBOL V5/6 implementation of line comments (*>) may somewhat alleviate the need/desire to use the COBOL line number columns for tags, but I can still see using them that way going forward. YMMV of course, I realize that it is quite hard to change the ways that people are used to working. Peter <snippage> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
