AW: Re: AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-28 Thread Peter Hunkeler
> >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

Re: AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Clark Morris
[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).

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Peter Hunkeler
> 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

Re: AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Elardus Engelbrecht
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

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Itschak Mugzach
Isn't your finding what I wrote to you few emails ago...? ITschak ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professional On Thu, Oct 27, 2016 at 2:49 PM, Peter Hunkeler wrote: > > > > > >>It is route code 11. specify that on your WTO macro . >

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Peter Hunkeler
>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

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Peter Hunkeler
>From IEFACTRT we write to JESYSMSG with the IEFYS routine. Are you sure the messages go to JESYSMSG (file 3) and not JESMSGLG (file 1)? I only seem to have ever seen messages from IEFACTRT, such as step statistics, appear in JESMSGLG. But me not having seen any in JESYSMSG does not mean

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Peter Hunkeler
>>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

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Peter Hunkeler
>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

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Itschak Mugzach
IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson > Sent: 26 October, 2016 23:47 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: How to write messages to JESYSMSG only? (was: Randomly > disappearing IGD101I messages) > > I can help a

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-27 Thread Vernooij, Kees (ITOPT1) - KLM
ion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Friday, October 21, 2016 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages) Triggered by the discussion about randomly disappear

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-26 Thread Jesse 1 Robinson
Of Peter Hunkeler Sent: Friday, October 21, 2016 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages) Triggered by the discussion about randomly disappearing IGD101I message, I did some RTFM and some testing

How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

2016-10-21 Thread Peter Hunkeler
Triggered by the discussion about randomly disappearing IGD101I message, I did some RTFM and some testing to find out how to write a message only to JESYSMSG. I got contradicting information instead of an answer. So here it goes... It was may understanding from my experience that allocation