John McKee wrote:

What I neglected to add to my stripped down program was this:

ADDENVVAR ENVVAR(QIBM_QSH_CMD_ESCAPE_MSG) VALUE(Y) +
REPLACE(*YES)

The above tells QSH to send *ESC instead of *COMP, making it something that can
be monitored.

My test program now correctly includes the non-zero return code for an invalid
command. Interesting that I use the MONMSG to catch a QSH0005 when sent as an
*ESC message and needed to add logic to receive it when it was sent as a *COMP
message. When I use a valid command, QSH0005 is still sent as *COMP.

I think I finally have it now. Tomorrow is another day.

John:

Now that you have it...

I'd recommend that you not use STRQSH in the first place in a compiled CL program. Especially if at V5R4, use ILE CL and the QzshSystem() API:

http://tinyurl.com/davgwf or
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahz/qzshsyst.htm

I've been _very_ pleased with results in coding I've done with it. Very easy to get started with.

Tom Liotta


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.