You probably could. That's a little trickier. And I don't have time to "fiddle around" with it right now. Using an unnamed pipe is where I'd start.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Paul Gilmartin > Sent: Monday, August 15, 2011 11:15 AM > To: [email protected] > Subject: Re: TSO/E NSLOOKUP and DIG deprecation > > On Mon, 15 Aug 2011 09:29:23 -0500, McKown, John wrote: > > >The UNIX command "dig" can easily be run in a TSO REXX > program using BPXWUNIX. That interface can easily trap the > "line mode" output which normally goes to stdout and stderr > into REXX stem variables. I do it all the time to run UNIX > commands in TSO. Most of these types of commands are > "utility" commands and the output is just plain old lines > like would print on an old style teletype. No reason why such > lines cannnot be trapped and then displayed via SAY. If you > don't trap stdout from bpxwunix(), the stdout and stderr line > mode just come back to the TSO user like a line mode TSO > command (such as LISTDS). You can't run "vi" this way > <shudder>. But "dig" should be simple. > > > I'm unfamiiar with "dig" (I've just glanced at the man page). > I use nslookup, > usually in an interactive mode: start the program and type > queries to stdin. > > As I imagine it, the problem is less how to display the > output than at what > point to prompt for input and unlock the keyboard. > > As an example/POC, how would one wrap "cat -u" simply to read > lines from > the keyboard and echo them to the display? > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
