As Tony said, they are all WTO messages. JES decides where it wants to put the message (or not do anything with it).
I suspect that some WTO messages are never written in USS as opposed to not being captured. I suspect that IBM disabled them for a reason.UNIX does so much allocation that it could easily flood the SSI (WTO's). I can image that issuing a make command would produce ton's of alloc / dealloc. As for capturing messages USS mesages placing them into the appropriate job, this may be more than you expect. Some of the problems would be: 1. Which parent/grandparent should receive the messages? 2. Will the messages truly be helpful since it will be more difficult to associate messages to issuing process. 3. BPXAS can be reused once the processes have terminated. In a busy UNIX environment, this could either amount to a large number of messages for many different processes that may or may not be related. Maybe a better alternative would be to use BPX_SHAREAS to share the address space with related processes but it still leaves the problem where address space reuse with unrelated processes. I'm not trying to discourage you in doing. Just trying to make sure you know about some of the hurdles. Jon Perryman On Tuesday, May 13, 2014 11:18 AM, "Farley, Peter x23353" <[email protected]> wrote: Oops. You are absolutely correct, I got the names backwards. > >So what it putatively says is that allocation and initiation/termination >messages are captured, but WTO's and other "console" messages are NOT captured? > >Weird. > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Tony Harminc >Sent: Tuesday, May 13, 2014 1:02 PM >To: [email protected] >Subject: Re: Where are the allocation messages of a USS process? > >On 13 May 2014 12:08, Farley, Peter x23353 <[email protected]> wrote: >> Perhaps because (at that link which Kirk posted) there is this note: >> >> "Messages that would normally go to the JESYSMSG data set are captured, but >> messages that go to JESMSGLG are not captured." >> >> Allocation messages go to JESMSGLG, and so it would seem are not captured. >> One wonders which bit-bucket they disappear into. > >I think this is backwards, at least if using the SDSF terminology. >What SDSF calls JESYSMSG contains allocation messages (IGD and IEF), >while JESMSGLOG is the JESn-captured extract of WTOs written to the >system SYSLOG. JESYSMSG also contains *some* application program WTOs, >but I haven't put the effort into figuring out which ones. Maybe it's >as simple as those with ROUTCDE 11. > >I've thought about a WTO exit of one sort or another that would >capture WTOs from BPXAS processes, and write them to the JES log of >their parent process. Of course the parent may have gone away, and >there are various other problems, but it should be doable. At least >they are already available in the system-wide SYSLOG, but things like >allocation messages do indeed seem to go into a bit-bucket. > >Tony H. >-- > > >This message and any attachments are intended only for the use of the >addressee and may contain information that is privileged and confidential. If >the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. > > > >---------------------------------------------------------------------- >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
