On 2017-12-11, at 07:22:18, Charles Mills wrote: > I eliminated them several years ago when I realized I had probably dropped a > deck on the computer room floor for the last time. > ... > - FTP is or was not tolerant of them in its INPUT (command) file, so DD * > sequence numbers are a problem. > Many other utilities with a UNIX heritage come to mind. POSIX shell, for example.
> -----Original Message----- > From: John McKown > Sent: Monday, December 11, 2017 5:53 AM > > I know that in the past, they were handy for when you dropped your deck of > physical cards. And if guess that they can still be handy if you distribute > source modifications in a format suitable for processing by IEBUPDTE, like > IBM does at times. > Many other suppliers distribute or accept source modifications in diff/patch format. Alas, IBM's patch doesn't support the "unified diff" files which are the mode. > But I'm having trouble figuring out why I would want to do this with my own > code. The reason I'm even considering stopping is because I really prefer to > keep my HLASM code in a UNIX directory rather than a PDS. > Doesn't IEBUPDTE accept UNIX files as input? Ironically, SuperC accepts UNIX files as OLD and NEW, but not as DELTA. HLASM generously accommodates UNIX files by providing pathname and relative line number with each diagnostic message. Has anyone an Edit macro to scan SYSTERM or SYSPRINT for these messages and open the cited source file at the cited line? -- gil
