>
>The exit 6 that I modified from the version done by Glenn Harper at
>[snip]
Exit 6 is JES2 Exit 6, I assume, and this is run in a JES2 context, so it has
access to JES2 "data", such as the JESYSMSG ACB. I doubt SMS has access to that
information when writing IGD* message upon data set
[Default] On 27 Oct 2016 03:32:19 -0700, in bit.listserv.ibm-main
p...@gmx.ch (Peter Hunkeler) wrote:
>>It is route code 11. specify that on your WTO macro .
>
>
>No, it s not. As I wrote, WTO with route code 11 goes to JESMSGLG and JESYSMSG
>(and also to consoles which receive route code 11).
> Isn't your finding what I wrote to you few emails ago...?
I was asking how to write a message to JESYSMSG, only. You answered, a WTO
with route code 11 will do that. At least this is how I understood. If this is
what you are referring to, then no. WTO with route code 11 writes to
Peter Hunkeler wrote:
>After reading about IEFACTRT in "Installation Exits" I conclude that IEFYScan
>only be used by this exit. You need what is passed in R12 to IEFACTRT to be
>able to address the parameter list for IEFYS. And again this text talks about
>"...writing to the JOBLOG..." which
>From IEFACTRT we write to JESYSMSG with the IEFYS routine.
After reading about IEFACTRT in "Installation Exits" I conclude that IEFYScan
only be used by this exit. You need what is passed in R12 to IEFACTRT to be
able to address the parameter list for IEFYS. And again this text talks about
>>It is route code 11. specify that on your WTO macro .
>No, it s not. As I wrote, WTO with route code 11 goes to JESMSGLG and JESYSMSG
>(and also to consoles which receive route code 11).
At last I found the following in the *authorized* assembler service reference:
WTO
...
A WTO message
>It is route code 11. specify that on your WTO macro .
No, it s not. As I wrote, WTO with route code 11 goes to JESMSGLG and JESYSMSG
(and also to consoles which receive route code 11).
I'm wondering how to write to JESYSMGS *only*.
--
Peter Hunkeler
