ビリヤード: JCLリーグ (2025-hyogo-momiji-9) に参加して、東京での“2025 JCL Final”に出てみた記録 - RemoteRoom https://remoteroom.jp/diary/2025-12-13/
ビリヤード: JCLリーグ (2025-hyogo-momiji-9) に参加して、東京での“2025 JCL Final”に出てみた記録 - RemoteRoom https://remoteroom.jp/diary/2025-12-13/
You want to know what 80's #Programming Terror 😱 looked like....?!!? Are you sure.....?
When you finish writing your IBM System-370 Assembler code 😱 and now you have to write the #JCL 😱 to upload it and execute it... 😱
»Friends who use Unix tell me that it is a much more ›interactive‹ way of communicating with a computer, and thus much more appropriate to the PC era than, say, IBM JCL was. (I realise that ›JCL‹ is an unknown term – church elders and other geriatric types wiil be happy to explain it, and happy that you asked them.)«
Source: Your Computer, issue June 1990.
#vintagecomputing #techhistory #unix #jcl
Fascinating. Why didn't I look this up 20 years ago??
https://en.wikipedia.org/wiki/Dd_(Unix)#History
(Ok, 18+ years ago. The oldest versions of the article don't have the #JCL name explanation)
And then there is dd. Famously complicated in its native JCL habitat, the Unix Fifth Edition (1974) utility by that name inherited a JCL-like syntax. As POSIX says: "In this version of this volume of POSIX.1-2024, dd retains its curious JCL-like syntax due to the large number of applications that depend on the historical implementation."
Anybody who thinks about reinventing the Shell is well advised to understand what people were thinking half a century ago.
And of course #TSOE - with #ISPF. The TSO commands however look still very familiar. Same with procedures/modules in SYS1.PROCLIB, even with the #IEFBR14 "do nothing" program still very useful in #JCL.
The University of Konstanz still had a #Comparex IBM compatible mainframe running, and I wrote a better version of the existing IRC client in REXX. I added the file transfer functions and fixed the EBCDIC-ASCII conversion. Those were the times.