> > But I am fairly sure that, IN THIS CONTEXT, the CEA which was being > > mentioned in the thread was not Common Event Adapter, which has _nothing_ > > to do with multiple TSO logons that I can see, but was referred to z/OSMF > > and its ability to allow multiple TSO sessions for a single user. I guess > > we will need to revisit the USS wars from days of yore. <grin/> > > CEA used by z/OSMF is Common Event Adapter.
I believe CEA started out in z/OS 1.9 as a system address space, but I may be wrong. z/OSMF came with 1.11? In any case, the common event adapter CEA address space needs to run in full function mode (which it does nicely with the definitions delivered by IBM). And it needs a bit of RACF setup detailed somewhere in samplib, primarily for the z/OSMF 3270 function which uses the same interfaces. Documentation for these interfaces (commonly called "CEA launched TSO address space") is in chapter 5 of MVS Programming: Callable Services for High-Level Languages for release 1.13. The actual JSON format used for communication is only documented in the 2.1 books for ISPF. Essentially, the screen and the keyboard of a 3270 user are replaced by a USS message queue which is owned (or initiated) by the CEA address space. TSO and ISPF write their JSON format to that message queue, a client can retrieve the "screen" and send the "keystrokes" back to the USS message queue where it is read by TSO/ISPF. Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
