Hm, that cautionary tale gets me thinking.  When I'm writing a REXX of any 
complexity, say more than 100 lines, I find it useful to write a bit of it, run 
it to debug, then add the next piece, run it again, and so on.  Otherwise 
debugging is much more difficult; my way, when the program bombs I can be 
pretty sure what part of it to look in for the problem because all he other 
parts already worked.

REXX is interpreted, not compiled, but you've got me wondering now whether I'm 
doing a disservice to everyone else at my shop.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* Instead of shooting clays on Thanksgiving, you can play great games with 
your family, like Monopoly: Nothing brings a family together like Monopoly!  
-from _Top 10 Reasons You Should Just Turn Your Guns Over to the Government 
TODAY_ (the Babylon Bee) */

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Tom 
Brennan
Sent: Wednesday, August 18, 2021 13:18

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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to