I have done some very neat things in Rexx, I have called 'IRXJCL' in a AC(1) STC and was able to call a program via 'LINKMVS' and call a program to perform RACF extracts and return the output in SYSTSPRT.
So rexx is a big favorite, even though I write in HLASM, LE Cobol, C and other languages. Scott IDMWORKS On Wed, Mar 30, 2016 at 8:32 AM, Scott Ford <[email protected]> wrote: > David, > > I appreciate the comments, trying to get the "hang of OO", proving you can > teach an old dog new tricks :) . I am also pretty big on comments. But > also feel there are this pseudo techies who just read comments and not the > language and what it entails.. > > > Regards, > Scott > > > On Wednesday, March 30, 2016, Elardus Engelbrecht < > [email protected]> wrote: > >> David Crayford wrote: >> >> >I was joking! I forgot the use a smiley, sorry :) >> >> It is all right with me! Many thanks! No need to say sorry. I was very >> afraid that I offended someone. >> >> >> >I think Assembler is the one domain where heavy commenting is still >> required because it's such an arcane language. But high-level languages >> should be pretty much self-documenting, which in fact is the great strength >> of COBOL. It has it's detractors but it's not a read only language. >> >> I agreed. >> >> >> >Don't comment tricky code, re-write it until you can understand it. We >> should strive to write code to be read and understood by humans without >> requiring short essays every few LOC. >> >> Agreed. >> >> >> >Go and take a look at zLinux IPL code >> >http://lxr.free-electrons.com/source/arch/s390/kernel/ipl.c. >> >> This is a fantastic example. Yes, I could see what each part is doing >> despite the long page (2070+ lines). >> >> >> >There's not many comments in that module but it's crystal clear what >> it's doing because of a good naming convention, good constant defintions, >> functional decomposition and well crafted code. When you see a comment you >> know you should read it because it's important. >> >> Agreed. Such methods should help newbies learning that language. >> Debuggers should modify the code in a flash. >> >> >> >You see, now I'm being dogmatic! >> >> Hahahaha! That makes two of us. ;-) >> >> >> >Simple script to perform both full and incremental backups. You have to >> love the Unix philosophy :) >> > >> http://www.cyberciti.biz/faq/linux-tape-backup-with-mt-and-tar-command-howto/ >> >> Another interesting page. Thanks for kindly sharing it. I am still >> teaching myself (and loving philosophy of) Unix, Linux and friends. >> >> David, please keep up with your postings. I appreciate them and learn >> from them. >> >> Thanks and have a very great day! >> >> Groete / Greetings >> Elardus Engelbrecht >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
