On Mon, 20 Oct 2008 08:43:00 -0400, Bob Bolch <[EMAIL PROTECTED]> wrote:
>All execution of CMS linkage interfaces (CMSCALL, SVC 204, SVC202, etc.) and >most common direct branch interfaces to CMS services executed on a non-b ase >CPU result in running intercept code that switches that thread back to t he >base CPU for execution of the service. Another way to say it is that all the >code in the CMS Nucleus only runs on the base processor. > >Each CP service defines how it executes on a non-base processor. Things like >IUCV and most Diagnose codes work just fine. In CMS Multitasking, non-ba se >processors are intended for pure code not requiring CMS services. > >Bob Bolch Does this apply to CMSIUCV support also? Are you using CMSIUCV, or only C P IUCV? You didn't mention semaphores, but if you are using them, have a look at: APAR Identifier ...... VM64489 Last Changed ........ 08/09/10 SEMAPHORE FAILS IF MULTIPLE SUBTASKS WAITING_ Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
