On Fri, 7 Sep 2018 18:06:51 -0700, Charles Mills wrote: >I freely admit that this is basically a newbie type question (despite the >mainframe gray hairs I have earned). > >Based on advice on another thread I am now calling errno2() on certain >socket errors. I get back an integer that I dutifully display in hex: > >XXX0123I errno2 = x'12345678'. Look up using BPXMTEXT. > >That message kind of offends me. When I get a basic library error I use >strerror() to convert it to text. I would like to convert errno2() to text, >rather than telling customers to go look it up for themselves. > >If I wanted to call BPXMTEXT from within my program and capture the text >output, what would I to do? I'm sure I could solve this with enough >experimentation but the gray hairs have made me impatient. > Rexx SYSCALL strerror does it.
o Is there an easier way to get to Rexx than BPXWUNIX? Is BPXWUNIX even practical? o And you'd need to pass the result back. Memory buffer? Sockets? Descriptors? Does BPXWUNIX preserve descriptors? o Invoke Rexx with spawnp()? Pass it all the descriptors you need. o And you need a place to keep the Rexx code. Exec-in-storage interface? o Non-Rexx approaches? I suspect Rexx SYSCALL strerror is implemented outside the standard library. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
