A friend of mine made a comment to me maybe 30 years ago about something
similar to this subject. He said the darkest day in the history of computer
operations was the day when applications programming realized an application
would run in production with our without documentation.
Mitch McCluhan
-----Original Message-----
From: Ed Gould <edgould1...@comcast.net>
To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
Sent: Sat, Jan 4, 2014 8:53 pm
Subject: Re: Literate JCL?
On Jan 4, 2014, at 8:15 PM, Shmuel Metz (Seymour J.) wrote:
> In <8d0d6ab843cdf6c-15b0-11...@webmail-m245.sysops.aol.com>, on
01/03/2014
at 09:59 AM, Mitch <mitc...@aol.com> said:
> I will talk with someone at a vendor site that may be able to do
> something close to this. May I ask for other input from anyone
> else that sees value in this?
I liked the idea when Knuth first published it, and see no reason that
it wouldn't work for JCL. The hard part is convincing management that
documentation needs to be a basic part of development, not an
afterthought.
--
ot only in the beginning but as part of the change cycle.
Ed
----------------------------------------------------------------------
or IBM-MAIN subscribe / signoff / archive access instructions,
end 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
