Re: QP2SHELL output

Hello Justin and everyone,

Since these article links for UNIXCMD are now dead, I blogged about this in my new blog for COMMON.
https://www.common.org/scotts-iland-blog/scotts-iland-unix-open-source-program/

So, if you're still interested in this, please check it out. Also, this blog is brand new, so please help me out by spreading the word! It's completely free.

Thanks!

-SK



On 1/8/2018 1:44 PM, Justin Taylor wrote:

The three article links on the UNIXCMD page are all dead. Are they available somewhere else? I downloaded the tool, and it doesn't contain any CL examples.

Thanks




-----Original Message-----
From: Scott Klement [mailto:midrange-l@xxxxxxxxxxxxxxxx]
Sent: Monday, January 08, 2018 12:09 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: QP2SHELL output

I agree with Bryan... you should use QSH. I'm not aware of anything that wouldn't work that way (aside from people who do not understand Unix shells getting confused by stuff like PATH, etc.)

QSH not only works better from CL programs, but also works in situations where QP2SHELL fails due to the fact that (without you doing extra coding, anyway) QP2SHELL tries to use the ILE stdin/stdout/stderr, which can sometimes cause problems.

Also, Kevin Bucknum's suggestion of using the shell redirect should work. I can't see any reason it wouldn't -- again, aside from you not understanding how to call it properly.

If you really can't use QShell, then consider using a tool like UnixCmd.
I realize that it's an extra program to download/install, but it is free, and gives you a lot more control.

---
This email has been checked for viruses by AVG.
http://www.avg.com