Re: [IBMiOSS] QIBM_QSH_CMD_ESCAPE_MSG

Thanks Richard,

I considered that possibility but I don't like it so much - trying to parse
the commands passed and then interpret the output to see if success or
failure can be identified.

Luckily the Status Code is available via the methods suggested by Jack and
Kevin.
I guess the whole point of that code is to identify errors/warnings/success
- I'm happy it was such an easy solution.

regards,
Craig

On Wed, 17 Apr 2019 at 18:44, Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

Another option might be to actually spin thru STDOUT after the QSH call
and look for expected messages.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
Phn: (612) 315-1745

----------------------------------------------------------------------

message: 1
date: Wed, 17 Apr 2019 18:20:49 +0100
from: Craig Richards <craig@xxxxxxxxxxxxxxxx>
subject: [IBMiOSS] QIBM_QSH_CMD_ESCAPE_MSG

Hi All,

In order to trap QSH errors, I've been setting QIBM_QSH_CMD_ESCAPE_MSG to
Y as a Job level Environmental Variable and it works swimmingly when I call
QSH with a single command.

But my testing seems to indicate that if I pass several semicolon
separated commands to QSH (directly in the CMD parameter), the Escape
Message is based on whether the LAST command had exit status 0 or not.

So my simple cunning plan, that at the first sign of trouble, QSH would
stop executing commands and send me a nice Escape Message I could monitor
for has fallen at the first hurdle.

I can see the errors in STDOUT which I've overridden.

I'm guessing that to get the behaviour I want (stop executing commands and
notify the caller via an escape message at the first error), I'll need to
use a script instead?

Thanks kindly,
Craig

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com