On 9/11/2015 11:21 AM, J O Skip Robinson wrote:
Thanks to Jim for both answers. I opted for the second choice--add exit to
LPA--because it seems a lot simpler, but it's nice to know that there exists a
bouncing ball method as well. I doubt that there's enough demand for this sort
of thing to create a standard interface. Of course I would not be asking this
question if I didn't have a problem.
Which BTW is to turn selected non-rolling messages into rolling. These are
messages that from SME point of view are informational but are coded to stay on
the console and incite questions from Ops about what 'they' are supposed to do.
We have an ancient WTO exit that is supposed to do that, but it's not working.
For the record, these are the relevant instructions:
MVC CTXTDC1(L'CTXTDC1+L'CTXTDC2),SETSTATS
OI CTXTRFB1,CTXTRCRC+CTXTRCDC CHANGE CODES NOW
...
SETSTATS DC AL1(CTXTDC04),X'00' SYSTEM STATUS WILL DO NICELY
I need SLIP trace just to see if the exit is even getting called.
Skip,
We have a number of MPF requirements submitted to hopefully make MPF
exits nearly obsolete, perhaps z/OS V2Rmumble will enable them. We have
ROUTE, DESCRIPTOR, COLOR, OFFSET and LENGTH I believe in the hopper.
If one of those doesn't cover your scenario, you should open a
requirement so we can group these together.
Thanks,
Tom
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
