Scott,
The message is a result of using say. Axrwro does not print the msg, just
the required text.
ITschak
בתאריך 10 ביונ 2017 00:23, "scott Ford" כתב:
Tony,
I think ITschak is saying is it possible to use AXRWTO instead of what your
doing and it would not that issue.
Tony,
I think ITschak is saying is it possible to use AXRWTO instead of what your
doing and it would not that issue.
Scott
On Thu, Jun 8, 2017 at 11:28 AM, Tony Harminc wrote:
> Thanks, but I don't see how this relates to my questions.
>
> Tony H.
>
> On 8 June 2017 at
Thanks, but I don't see how this relates to my questions.
Tony H.
On 8 June 2017 at 02:59, IronSphere by SecuriTeam Software <
imugz...@gmail.com> wrote:
> use axrwto.
>
> ITschak
>
> On Wed, Jun 7, 2017 at 11:47 PM, Tony Harminc wrote:
>
> > What causes the AXR0500I message
use axrwto.
ITschak
On Wed, Jun 7, 2017 at 11:47 PM, Tony Harminc wrote:
> What causes the AXR0500I message
>
> AXR0500I AXREXX OUTPUT DISPLAY 093
> EXECNAME=TESTX REQTOKEN=4000D29FAA504703A808
> TESTX running - output from SAY
>
> to be written to Syslog?
What causes the AXR0500I message
AXR0500I AXREXX OUTPUT DISPLAY 093
EXECNAME=TESTX REQTOKEN=4000D29FAA504703A808
TESTX running - output from SAY
to be written to Syslog? Clearly that last line is from a SAY statement of
mine, but I seem to always get the AXR0500I even without a SAY.