On Tue, 13 May 2014 14:58:01 -0700, Jon Perryman wrote:

>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.
>
Indeed.  Lately I did a "cp" of a couple hundred-member PDSE to a UNIX 
directory.
Merely on elapsed time I can suspect that for each member it was doing
ALLOCATE; OPEN; copy; CLOSE; FREE.  (And catalog search?)

>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.
>
This could be a problem with any child process that writes to a descriptor 
inherited
from a parent process.  AFAIK, it has been solved; perhaps as simply as by not
reusing the address space until all such descriptors are closed.

>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.
>
Writing such messages to a suitably propagated descriptor might be an
effective alternative to S/360-think which appears to be the current approach.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to