Thanks for the info. I received this from IBM: The manuals do not provide much information on CEA. CEA stands for Common Event Adapter (CEA). This new component is is responsible for delivering zos events notification to Unix System Services (USS) applications using C-language facilities. The documentation is still weak. As products start using it, you will see the documentation increasing. Already, the following manuals have been updated to help sysprogs better install zos19: i) zos19 Planning for Installation- GA22-7504-18 Chapter 5. Preparing for customization and test ii) zos19 Migration manual - GA22-7499-12 2.2.13 Accommodate new address spaces 2.2.14 Accommodate new SCOPE=COMMON data spaces iii) zos19 Init and TUning Reference- SA22-7592-16 BPXPRMxx MAXSOCKETS : when CEA is active, each CEA client requires two sockets connection tot he CEA server . Info apar OA23747 was also openned to clear some issues with early installs of zos19. The Component Trace member is still not documented. You need to start zos with the provided CTICEA00 parmlib member
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Scott Fagen Sent: Thursday, July 03, 2008 7:05 PM To: [email protected] Subject: Re: CEA - Common Event Adapter On Thu, 3 Jul 2008 07:08:31 -0400, Dean Montevago <[EMAIL PROTECTED]> wrote: >Hi, > >Is there any doc on what the function of this address space is ? I >found a couple of hits in the 1.9 books but it doesn't go into any >detail. > >TIA >Dean "Common event adapter (CEA) is a component of the BCP that provides the ability to deliver z/OS events to C-language clients, such as the z/OS CIM server. A CEA address space is started automatically during initialization of every z/OS system." Well, the wording is quite clunky, probably written by someone for whom English is not their first language. A better explanation might be: "The Common Event Adapter (CEA) is a component of the BCP that enables USS processes, written in C, to be able to receive z/OS system generated events (WTO, ENF, SSI, maybe others, who knows?). Examples of such processes are the CIM providers included with the CIM Server (see z/OS V1R9.0 Common Information Model User's Guide). The CEA address space is automatically started during z/OS system initialization." On Thu, 3 Jul 2008 09:32:15 -0500, Hal Merritt <[EMAIL PROTECTED]> wrote: >Interesting. Next time, might ask for a formal statement to that effect >that we can show our auditors. We are expected to know and manage every >process. > Nonsense. As stated by the documentation (and reinforced by Bob's interaction with IBM development), CEA is a part of the base operating system with no customer facing externals. There might be some disagreement as to whether or not the security and setup instructions are correct/complete (I've never tried, so I can't comment), but, on it's face, the information appears complete. The need for security clearly comes from the fact that these are unauthorized processes that need access to authorized programming resources. There's nothing to 'understand' or 'manage', other than to follow the installation instructions. Scott Fagen Enterprise Systems Management ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
