Re: CL type conversion error

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

Quoting Tom Liotta <qsrvbas@xxxxxxxxxxxx>:

> 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
>
> --
> Tom Liotta
> The PowerTech Group, Inc.
> 19426 68th Avenue South
> Kent, WA 98032
> Phone  253-872-7788 x313
>        253-479-1416
> Fax    253-872-7904
> http://www.powertech.com

Not sure I see a difference.  The description says:

The QzshSystem() function runs the specified shell command by spawning a child
process and invoking qsh in the child process. qsh interprets and runs command
and then exits.


What I see is using an API to initiate QSH instead of just running QSH 
directly.
I can see the incredible usefulness of this from within RPG or C.  But, 
what is
the advantage from within CLE?

John McKee