Bill,
I read that also.
I assume that when I listen for event 48, I am listening across the
entire LPAR.
The exit can be driven for events that are not related to my log stream.
They can be events for other log streams or events specific to the
logger only.
I have writer sub-task and a reader/deleter sub-task both connected to
the same log stream.
They may both at the same time get a reason code stating to wait for an
ENF 48 event. And that event would force the exit to POST both
sub-tasks. Or there could be 2 separate events, I think.
I'm developing at Dallas and I've got a vanilla system. There isn't
much going on with other log streams as far as I can tell.
I'm modifying my code to dump all ENF 48 events to see whats going on.
Thankks abd regards, Pierre.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
