Dunno whether I'm right, but I associate "script" with "macro", both of which (still in my own head) I think of as a list of commands without logic branches. Like the old PC DOS batch files: Do this, then do this, then do this... Or QMF (unless QMF has added IF statements since I last used it). Or basic JCL (first this step, then this, then this...). Once you've added branching and other such complexities to a language, the result is no longer a "macro" but a program. So when I write something for Excel or Outlook, it's not a VBA macro, it's a VBA program.
I see I got sucked into one of my standard rants. Anyway, I tend to think of a script as more like a macro in that sense. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* If you can't eat all your chocolate, it will keep in the freezer. But if you can't eat all your chocolate, it may be a sign of a deeper problem. */ -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Mark Pace Sent: Wednesday, June 8, 2022 07:52 Long time VMer - I've always said "A Rexx Exec". Not sure why I don't like the term script. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
