Good point. I do the same kind of thing already with dataset names; I keep a table at each client for my own libraries, and no matter where I go my general REXX library is XG, my JCL library is JG, a scratch data library is DG and so on. There are other abbreviations; XT is the "team" exec library where I put routines that should be available to everyone on my team. No need to think about what I had to name it here; the RENDSN function looks up the alias and returns the correct DSN.
Of course I also put shortcuts in there for long-winded names of production libraries that I have to refer to frequently enough. Anyway, yeah, makes sense to do that for command names too. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* No one would talk much in society if he knew how often he misunderstands others. -Goethe */ -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Mark Zelden Sent: Thursday, January 25, 2024 14:50 2) A common / easy name to quickly invoke a product or some other menu option. For example, I have "shortcuts" like HCD, IPCS, SMPE, ISMF, WLM, ISHell, CA1, CA7, SDsd, TMS (which I could point to CA1 or some other tape management product), IPL (my IPLINFO exec) as some examples. So for #2, I could have many different clients / shops I am working at and no matter which one I always type "WLM" to get to WLM.... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
