On Thu, 26 Jul 2007 12:56:37 +0200, Barbara Nitz <[EMAIL PROTECTED]> wrote:
>yes, that helps quite a bit. So I guess internally everything that was directly sent to a console z/OS 1.6 and lower is now first queued to this EMCS console that another task/tcb will then probably output to the actual green screen/3270 emulation session. > >Oh, and that EMCS console is active even when that system doesn't have its own green screen. The main point of the first Console Restructure deliverable (z/OS 1.4.2 feature) was to improve the RAS for message delivery. This was accomplished (in part) by centralizing all message delivery through the much more modern EMCS code, rather than in the crunky old (and 24-bit) MCS code. The old code now sits behind the *DIDCS console (which takes on the aggregate routing characteristics of the active (S)MCS consoles on the system). Now, a failure in this code (either due to a message flood or a coding error) no longer impacts all the other key message consumers (EMCS, OPERLOG, SYSLOG). "Comm Task" is active and running, regardless of whether or not there are any active green screen consoles on the system. The *DIDCS console consumes 1 whole EMCS control block entry and shares the message dataspace with all other EMCS consoles defined by the CONSOLE address space (ROUTE, OPERLOG, SYSLOG). Ergo, it costs the system essentially nothing. Scott Fagen z/OS Core Technology Design IBM Poughkeepsie ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
