It is route code 11. specify that on your WTO macro . ITschak
On Thu, Oct 27, 2016 at 10:28 AM, Vernooij, Kees (ITOPT1) - KLM < [email protected]> wrote: > From IEFACTRT we write to JESYSMSG with the IEFYS routine. > > Kees. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jesse 1 Robinson > Sent: 26 October, 2016 23:47 > To: [email protected] > Subject: Re: How to write messages to JESYSMSG only? (was: Randomly > disappearing IGD101I messages) > > I can help a bit with the first question but not the other two. We have an > ancient and venerable JES2 EXIT 6 that writes messages to JESYSMSG only. It > uses the IFGRPL macro (AMODGEN). I did not write this part of the code, but > I could send you a sample if you'd like. It's based on PUT with the parm > RPL. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-302-7535 Office > [email protected] > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Peter Hunkeler > Sent: Friday, October 21, 2016 1:22 PM > To: [email protected] > 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 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 messages, be > it the SMS ones IDG10xI, or the non-SMS IEFxxxx ones, are only ever > written to JESYSMSG. Only for STC running under MSTR (and in BPXAS?) will > the messages be prefixed with IEF196I and written to syslog/operlog. > > > > I knew there is the "WTP" service which is actually a WTO with route code > 11, only. It is described as to be writing the message to the *JESYSMSG* > data set. However from experience, and I verified today, a WTO with route > code 11 writes the message to JESYSMSG *and* to the JESMSGLG data set. The > doc is not complete here, it seems. > > > So, while I thought the IDG10xI messages are written as WTO ROUTCDE=11, I > now doubt, since they are not seen anywhere else than JESYSMSG (exception > see IEF196I above). > > > > But, the MVS messages manual documents for all of the IGD10xI messages: > Route Code 2, Descriptor Code 4. Route code 2 is for the consoles (and the > syslog/operlog). Again, the doc seems to be incomplete and possibly in > error, because the IGD10xI messages are not seen in syslog/operlog and not > on consoles. Contradiction #1. > > > > Next surprise: By chance, I saw a few IGD103I and IGD104I messages in > operlog, *not* prefixed by IEF196I! How comes?? I was looking at the STC > that was the source of the WTO. To my astonishment, I found not only in the > JESYSMGS but also in the JESMSGLG of the STC. So far, I had only seen > IDG103I and IGD104 in the same places and format as the IDG101I. > A WTO seen in all of those three places would have routing codes 11 plus > (at least) one of the "console" routing codes. Again the MVS msg manuals > say route code 2, only. > Contradiction #2. > > > > > Anyone to shed some light on this? > > > Questions to answer: > > a) How does one write a message to JESYSMSG *only". > b) What determines whether IDG10xI messages are written to JESYSMSG only, > or to JESYSMSG, JESMSGLG *and* operlog? > c) Are the IGD10xI messages really WTOs with route code 2 and descriptor > code 4, only? > > > -- > Peter Hunkeler > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ******************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. If > you are not the addressee, you are notified that no part of the e-mail or > any attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, and may > be unlawful. If you have received this e-mail by error, please notify the > sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission > of this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > ******************************************************** > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
