Tom,

speaking for consoles: For at least the past 25 years the 'reasonable' standard 
has been just what the health check tells you:
- Do NOT send all routing codes or all routing codes except 11 (programmer 
information) to either the consoles or the hardcopy log.
- Do NOT configure the MSCOPE for messages so that they automatically get sent 
to another system. This is a performance issue.
I believe that that is even documented.

I have my consoles  set up like this (we don't have MCS consoles anymore):

DEFAULT ROUTCODE(1-10,12-128) HOLDMODE(YES)                       
CONSOLE DEVNUM(SYSCONS) ROUTCODE(1-10,12-128) INTIDS(Y) LEVEL(ALL)
        UNKNIDS(Y)                                                
CONSOLE DEVNUM(HMCS) NAME(HMCS&SYSNAME.) AUTH(MASTER) MSCOPE(*)   
        INTIDS(Y) LEVEL(ALL) UNKNIDS(Y) ROUTCODE(1-10,12-128)     
        PFKTAB(PFKTAB1) TIMEOUT(10)                               

Both SYSCONS and HMCS are represented as EMCS consoles in the system. Both 
definitions violate the rule 'all routcodes except 11'. That may be the reason 
I deleted the health check. (Since I did the delete when we still had MCS 
consoles, I may need to revisit that deletion). As far as I am concerned, 
syscons and HMCS are only seldom active and I need to see what's going on and 
cannot limit the route codes to (1-10,12-16) for these two consoles.

In another shop we had one product that *required* MSCOPE *ALL. We identified 
the messages that were needed there, gave them a certain routing code and set 
the product console (admittedly an MCS console) to only receive that routing 
code. That console then got MSCOPE(sys1,sys2,sys3,sys4). At the time, that 
seemed to satisfy the check (IIRC).

As far as I know, z/OSMF communicates via EMCS consoles. For EMCS consoles, you 
can set attributes via RACF parm. Unfortunately, when the product defines and 
activates the EMCS console, it can overwrite what you had RACF-defined. We 
don't run z/OSMF (yet), so I cannot check for myself, but I am guessing that 
z/OSMF has either MSCOPE *ALL or all routing codes or both hardcoded. If that 
is the case, then you should open a PMR with IBM and ask them why z/OSMF 
violates best practises. 

If you delete the health check (as I did), just make sure that all your MCS 
defaults are 'reasonable' as stated above and that you don't have other 
products that set EMCS consoles with ROUT(ALL) and MSCOPE(*ALL). And remember 
that these two settings are really really bad for performance, as all messages 
need to get sent via XCF to all the systems.

Having said all that, which consoles are shown when you do the requested 
commands:
DISPLAY CONSOLES,L,FULL                                     
DISPLAY EMCS,FULL,STATUS=L
Are they all z/OSMF consoles? Or are there several products involved?

Best regards, Barbara

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

Reply via email to