home.social

#jcl — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jcl, aggregated by home.social.

  1. 🚀 WOW! Finally, an AI agent that lets you relive the thrill of navigating #TN3270 and writing #JCL, just like it's 1974! 🕰️ Because who doesn't want to debug jobs on #zOS from their "modern" development environment? 🤖✨
    hypercubic.ai/hopper #AIagent #nostalgia #techhumor #HackerNews #ngated

  2. 🚀 WOW! Finally, an AI agent that lets you relive the thrill of navigating #TN3270 and writing #JCL, just like it's 1974! 🕰️ Because who doesn't want to debug jobs on #zOS from their "modern" development environment? 🤖✨
    hypercubic.ai/hopper #AIagent #nostalgia #techhumor #HackerNews #ngated

  3. 🚀 WOW! Finally, an AI agent that lets you relive the thrill of navigating #TN3270 and writing #JCL, just like it's 1974! 🕰️ Because who doesn't want to debug jobs on #zOS from their "modern" development environment? 🤖✨
    hypercubic.ai/hopper #AIagent #nostalgia #techhumor #HackerNews #ngated

  4. 🚀 WOW! Finally, an AI agent that lets you relive the thrill of navigating #TN3270 and writing #JCL, just like it's 1974! 🕰️ Because who doesn't want to debug jobs on #zOS from their "modern" development environment? 🤖✨
    hypercubic.ai/hopper #AIagent #nostalgia #techhumor #HackerNews #ngated

  5. 🚀 WOW! Finally, an AI agent that lets you relive the thrill of navigating #TN3270 and writing #JCL, just like it's 1974! 🕰️ Because who doesn't want to debug jobs on #zOS from their "modern" development environment? 🤖✨
    hypercubic.ai/hopper #AIagent #nostalgia #techhumor #HackerNews #ngated

  6. 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... 😱

    #ProgrammingHorrorStories 😱

  7. 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... 😱

    #ProgrammingHorrorStories 😱

  8. 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... 😱

    #ProgrammingHorrorStories 😱

  9. »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

  10. »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

  11. »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

  12. »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

  13. »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

  14. Fascinating. Why didn't I look this up 20 years ago??

    en.wikipedia.org/wiki/Dd_(Unix

    (Ok, 18+ years ago. The oldest versions of the article don't have the name explanation)

  15. Fascinating. Why didn't I look this up 20 years ago??

    en.wikipedia.org/wiki/Dd_(Unix

    (Ok, 18+ years ago. The oldest versions of the article don't have the #JCL name explanation)

    #dd #UNIX

  16. Fascinating. Why didn't I look this up 20 years ago??

    en.wikipedia.org/wiki/Dd_(Unix

    (Ok, 18+ years ago. The oldest versions of the article don't have the #JCL name explanation)

    #dd #UNIX

  17. Fascinating. Why didn't I look this up 20 years ago??

    en.wikipedia.org/wiki/Dd_(Unix

    (Ok, 18+ years ago. The oldest versions of the article don't have the #JCL name explanation)

    #dd #UNIX

  18. Fascinating. Why didn't I look this up 20 years ago??

    en.wikipedia.org/wiki/Dd_(Unix

    (Ok, 18+ years ago. The oldest versions of the article don't have the #JCL name explanation)

    #dd #UNIX

  19. 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.

    #shell #unix #posix #jcl

  20. 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.

    #shell #unix #posix #jcl

  21. 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.

    #shell #unix #posix #jcl

  22. 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.

  23. 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.

  24. 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.

  25. 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.

  26. 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.

  27. @dingodog19 I use much. For #Python, \( LaTeX \), #Markdown with \( LaTeX \), #Java, #JCL for mainframes, #Jupyter notebooks...
    And you may have profiles with different extensions for different purposes and share configuration among platforms.
    It is the one thing MS has done well.

  28. @dingodog19 I use much. For #Python, \( LaTeX \), #Markdown with \( LaTeX \), #Java, #JCL for mainframes, #Jupyter notebooks...
    And you may have profiles with different extensions for different purposes and share configuration among platforms.
    It is the one thing MS has done well.

  29. @dingodog19 I use much. For #Python, \( LaTeX \), #Markdown with \( LaTeX \), #Java, #JCL for mainframes, #Jupyter notebooks...
    And you may have profiles with different extensions for different purposes and share configuration among platforms.
    It is the one thing MS has done well.

  30. @dingodog19 I use much. For #Python, \( LaTeX \), #Markdown with \( LaTeX \), #Java, #JCL for mainframes...
    And you may have profiles with different extensions for different purposes and share configuration among platforms.
    It is the one thing MS has done well.

  31. @dingodog19 I use much. For #Python, \( LaTeX \), #Markdown with \( LaTeX \), #Java, #JCL for mainframes, #Jupyter notebooks...
    And you may have profiles with different extensions for different purposes and share configuration among platforms.
    It is the one thing MS has done well.

  32. Nice blog post from Joe Winchester about some of the ways the Open Mainframe Project #Zowe has been modernizing interaction with the #mainframe

    For instance, yes, you still need #JCL, but what if you could automate a syntax check before you submit it? No problem! 🤖

    community.ibm.com/community/us

  33. Nice blog post from Joe Winchester about some of the ways the Open Mainframe Project #Zowe has been modernizing interaction with the #mainframe

    For instance, yes, you still need #JCL, but what if you could automate a syntax check before you submit it? No problem! 🤖

    community.ibm.com/community/us

  34. Nice blog post from Joe Winchester about some of the ways the Open Mainframe Project #Zowe has been modernizing interaction with the #mainframe

    For instance, yes, you still need #JCL, but what if you could automate a syntax check before you submit it? No problem! 🤖

    community.ibm.com/community/us

  35. Nice blog post from Joe Winchester about some of the ways the Open Mainframe Project #Zowe has been modernizing interaction with the #mainframe

    For instance, yes, you still need #JCL, but what if you could automate a syntax check before you submit it? No problem! 🤖

    community.ibm.com/community/us

  36. Nice blog post from Joe Winchester about some of the ways the Open Mainframe Project #Zowe has been modernizing interaction with the #mainframe

    For instance, yes, you still need #JCL, but what if you could automate a syntax check before you submit it? No problem! 🤖

    community.ibm.com/community/us

  37. #Kubernetes makes my brain hurt. #EKS is a nifty layer of abstraction (complete with its own set of impenetrable acronyms) that acts as a force multiplier for the hurt #k8s brings.

    Man do I miss the simplicity of #COBOL and #JCL, maybe a little #CICS, sometimes.

  38. makes my brain hurt. is a nifty layer of abstraction (complete with its own set of impenetrable acronyms) that acts as a force multiplier for the hurt brings.

    Man do I miss the simplicity of and , maybe a little , sometimes.

  39. For the older folks who are not on the #chatGPT train yet, I've asked chatGPT to write some #JCL code ("Write JCL to store a dataset called ChatGPT on tape.").

    My JCL knowledge is rusty these days and I don't have access to a #Mainframe to verify if it works, but here's waht chatGPT came up with:

    #AI

  40. For the older folks who are not on the #chatGPT train yet, I've asked chatGPT to write some #JCL code ("Write JCL to store a dataset called ChatGPT on tape.").

    My JCL knowledge is rusty these days and I don't have access to a #Mainframe to verify if it works, but here's waht chatGPT came up with:

    #AI

  41. For the older folks who are not on the #chatGPT train yet, I've asked chatGPT to write some #JCL code ("Write JCL to store a dataset called ChatGPT on tape.").

    My JCL knowledge is rusty these days and I don't have access to a #Mainframe to verify if it works, but here's waht chatGPT came up with:

    #AI