|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.