While every system can use the same UCB from an OS point of view, there are cases where that may not be a good idea or even not work.
As for the wisdom using the same device address, a sysplex can (in my view ought to) display messages from all members. Having the same console address might cause confusion for Ops. As for functionality, we use the product VCC to manage consoles for all z/OS LPARs in the enterprise. VCC uses defined console addresses to keep track of them. AFAIK VCC would not work if all consoles had the same UCB address. What we can do is use the same 'control unit' definition in our single enterprise IODF. We just make different device addresses accessible to different LPARs. So all LPARs see a console control unit at 0700, but the devices (00 - the max) are attached in the IODF uniquely to each LPAR for VCC management. While all the devices are visible via D U, trying to vary online someone else's console fails: 13.16.27 X0 v 0710,online 13.16.27 X0 IEE103I UNIT 0710 NOT BROUGHT ONLINE IEE763I NAME= IECVIOPM CODE= 0000000400000000 IOS551I NO PATHS PHYSICALLY AVAILABLE IEE764I END OF IEE103I RELATED MESSAGES I refer above to 'the max' because there seems to be a limitation of twenty-something (less than 32) that I don't understand. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Neubert, Kevin Sent: Friday, June 10, 2016 5:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Query on OSA-ICC consoles Not seeing a newer guide, but this one will walk you through it: OSA-Express Integrated Console Controller Implementation Guide (SG24-6364-01). Believe the gist you are looking for lies between the IODF RESOURCE macro statement and OSA-ICC CONFIG_SESSION source file. Let's say two systems (SYSA and SYSB) share the same UCB (C00). The pertinent part of the RESOURCE statement is (name, MIF image ID) and the equivalent piece in the CONFIG_SESSION file is IID=nn (MIF image ID). Abbreviated example below. IODF: RESOURCE PARTITION=((CSS(0),(SYSA,1),(SYSB,2)… CHPID PATH… CNTLUNIT CUNUMBR… IODEVICE ADDRESS=(C00,001)… OSA-ICC: <CONFIG_SESSION> <SESSION1> CSS= 00 IID= 01 DEVICE= C00 … </SESSION1> <SESSION2> CSS= 00 IID= 02 DEVICE= C00 … </SESSION2> </CONFIG_SESSION> Regards, Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of linda golding Sent: Friday, June 10, 2016 4:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Query on OSA-ICC consoles Thought to post this question as i couldn't find this information in any of the IBM documentation . Does anyone know how OSA-ICC devices (3270-X) are mapped in HSA ? I did a search in our systems and see that OSA-ICC devices are concurrently active on all LPARS of the sysplex . I also see that PCHID is same across all the systems . I am just trying to find out how multiple systems can write on to the same physical OSA-ICC device ?..Basically i would like to know how this happens at hardware level . Any pointers /documentation would be a great help . Linda ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
