Yep, just attach an escon channel to the other processor, do the IOCP, vary the devices online and away you go.
As long as you don't need to directly share a pack between two systems at the same time (you can vary off/vary on between systems to share), you shouldn't have any problems....from a hardware standpoint. But.... >From a software standpoint, things can be tricky. I would setup config system to vary online the "other" dasd but not to attach it to the system. You don't want an IPL of the other system to pick up your VM volumes (when you overlay spool and paging space, things get messy real fast). That duplicate volid stuff, sometimes can be real tricky. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 12/12/2005 2:10 PM >>> Hi everyone. This may sound like a dumb question but I can't find solid information on it in any document so here goes.. I need to share a DASD controller between two CPUs for a short period of time. I don't need to share the same devices on the two CPUs just access some devices on one CPU and other devices on the second CPU. Can I just ESCON attach both CPUs to the control unit and define the complete address range for the DASD in the IOCP of both processors but access the appropriate devices only on each CPU? Where can I find some examples of how to share one DASD control unit between two physical systems? Thanks
