On Thursday, 10/13/2005 at 09:11 ZE8, John Summerfied <[EMAIL PROTECTED]> wrote: > > But why lock? CP can handle multiple parralel diag8 > > As I recall someone asserted there's a problem getting the proper cp > feedback at present. VM return codes don't map to *x return codes, so > another action is needed to get the VM return code and publish it some > place a script can use it. > > Without locking, this will fail from time to time.
All output data areas and registers must be stashed in instance-specific memory such as that associated with a file descriptor. But this is normal coding practice in file/network drivers. Implicit locks would be appropriate for those diagnose functions that are stateful. E.g. you can't have two processes using diag 14 at the same time. But there's no reason they can't both issue diag 210 (for example). Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
