Good answer, and it's there because in one application there was another stage which wouldn't go to ready (commit 0) until everyone else did. In most cases it's a harmless artifact.
-- Mike Harding z/VM System Support mhard...@us.ibm.com mike.b.hard...@kp.org mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) IM: VMBearDad (AIM), mbhcpcvt (Y!) The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on 07/20/2011 02:45:41 PM: > From: Scott Rohling <scott.rohl...@gmail.com> > To: IBMVM@LISTSERV.UARK.EDU > Date: 07/20/2011 02:46 PM > Subject: Re: Capturing response from SCS > Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > It's a plumbing thing .. HELP PIPE COMMIT .. > > commit 0 requests that the commit level of the TCOMMT stage be raised to > 0. The TCOMMT stage is then suspended until all the other stages in the > pipeline have committed at least to level 0 or have ended. The return code > from COMMIT is then set to the current aggregate code. > > That explains it - right? ;-) > > Scott Rohling > > On Wed, Jul 20, 2011 at 2:34 PM, Fran Hensler <f...@zvm.sru.edu> wrote: > What is line 78 supposed to do? > 'Commit 0' /* hot to trot */ > /Fran Hensler at Slippery Rock University of Pennsylvania USA for 48 years > mailto:f...@zvm.sru.edu http://zvm.sru.edu/~fjh +1.724.794.6172 > "Yes, Virginia, there is a Slippery Rock"
