Re: Distributing source maintenance without sequence numbers was Re: git, z/OS and COBOL

2017-10-10 Thread Paul Gilmartin
On Tue, 10 Oct 2017 21:59:54 -0300, Clark Morris wrote:
>
>>>From what you say, diff and patch will not know or understand where the 
>>>source being supplied to update the original source goes.
>>> 
>>Patch uses a combination of relative line numbers and context lines (such as 
>>appear
>>in a SuperC listing).  It works.
>>
>>>So, I don't think your method is going to fly with source coming from a 
>>>vendor that has to be updated via IEBUPDTE, nor is it going to fly with one 
>>>of our groups that uses IEBUPDTE to update their source...
>>> 
>>Do those groups create their IEBUPDTE command files by hand?
>
>Other than by total replacement, how would you distribute source
>maintenance other than by an IEBUPDTE like maintenance mechanism that
>depends on sequence numbers?
> 
"patch" works.  It does not depend on sequence numbers.  It's widely used.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Distributing source maintenance without sequence numbers was Re: git, z/OS and COBOL

2017-10-10 Thread Clark Morris
[Default] On 10 Oct 2017 17:30:54 -0700, in bit.listserv.ibm-main
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) wrote:

>On Tue, 10 Oct 2017 17:21:29 -0700, stevet wrote:
>>
>>So how does one merge fixes into source if the "source" numbering is removed? 
>>The fixes may issue delete of lines, addition of lines and replace of lines 
>>and there may be multiple delta decks to be applied anytime one wants to do 
>>changes to the source. This is not a spec I'm providing, this is a 
>>requirement I would have to live with.
>>
>>From what you say, diff and patch will not know or understand where the 
>>source being supplied to update the original source goes.
>> 
>Patch uses a combination of relative line numbers and context lines (such as 
>appear
>in a SuperC listing).  It works.
>
>>So, I don't think your method is going to fly with source coming from a 
>>vendor that has to be updated via IEBUPDTE, nor is it going to fly with one 
>>of our groups that uses IEBUPDTE to update their source...
>> 
>Do those groups create their IEBUPDTE command files by hand?
>

Other than by total replacement, how would you distribute source
maintenance other than by an IEBUPDTE like maintenance mechanism that
depends on sequence numbers?

Clark Morris
>-- gil
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN