I miss socializing in the line to use the keypunch. Compiles were fill-in type
work that involved operators reading in the card deck, so very controlled and
very occasional. Desk checking was required.
Cliff McNeill
________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of Tom
Brennan <[email protected]>
Sent: Wednesday, August 18, 2021 12:17 PM
To: [email protected] <[email protected]>
Subject: Re: even an old mainframer can do it
Me too, but in the early 1980's. I'd run the assembler from TSO READY
so I wouldn't have to wait for an initiator. My way of programming was
always like starting with a ball of clay generally like what I wanted,
then adding the details as I went along. That method means lots and
lots of compiles. Then one day my supervisor dropped by my desk with a
blue-bar listing titled, "Top 10 TSO CPU Users" and I think I was on the
top. Oops.
On 8/17/2021 11:35 PM, Mike Schwab wrote:
> Well, in the early 1990s, my system had 1-2 hour delays on compiles.
> So while waiting, I wrote a clist to do the same thing. Allocate,
> error handling, and deallocate of a single file took about 30 lines,
> and a few iterations of debugging. So, once I had one file allocate,
> I went through all the files, executed the program, and deallocated,
> and proceeded with the next two steps. Got it working and would go
> get a new cup of coffee while it ran instead of having to wait.
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
