use axrwto.

ITschak​

On Wed, Jun 7, 2017 at 11:47 PM, Tony Harminc <t...@harminc.net> wrote:

> What causes the AXR0500I message
>
> AXR0500I AXREXX OUTPUT DISPLAY 093
> EXECNAME=TESTX REQTOKEN=0000400000000000D29FAA504703A808
> 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. I want to
> avoid it - I never want to see any indication of the Rexx program running,
> unless it issues a message itself or there is a serious error within System
> Rexx. I don't want that REQTOKEN and such cluttering the console stream.
>
> Also, what is the real meaning of the CONSDATA=YES option on AXREXX? Again,
> the book is vague: "CONSDATA=YES Indicates that the exec is invoked as a
> system command." Does this mean that any WTOs issued by the AXR[ML]WTO
> functions are marked with DESC=5? I don't know what else this might mean.
>
> There is an example in the book of issuing an MVS command from Rexx,
> retrieving and parsing the command output, and using AXRMLWTO to write the
> result to an extended MCS console set up with MCSOPER in the program that
> invoked AXREXX. Maybe a bit far-fetched, but I tried the example, and all
> of the command+output goes to SYSLOG, as well as to the extended  console.
> But there is no option to specify DESC or ROUTCDE or any other WTO options
> on AXR[ML]WTO. I would also like to avoid all this stuff going to SYSLOG.
>
> Thanks... Tony H.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
ITschak Mugzach
*|** IronSphere Platform* *|** An IT GRC for Legacy systems* *| Automated
Security Readiness Reviews (SRR) **|*

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to