Is anyone else experiencing ABENDs in PIPES when running multiple separate PIPE commands using CMS MultiTasking?
On z/VM 5.4 service level 1001 (64-bit), we're running Pipes RTL at: PIPINX560I CMS/TSO Pipelines, 5654-030/5655-A17 level 110C0002. PIPINX086I CMS/TSO Pipelines, 5654-030/5655-A17 1.0112 (Version.Release/Mod) - Generated 11 Mar 2010 at 10:24:55 Source: Princeton Runtime Distribution Every so often (a couple times each week) CA's VM:Operator r3 product experiences an ABEND PRG004 or PRG005 while executing separate PIPE commands in different CMS MultiTasking threads. VM:Operator development/support has reproduced the ABEND via a pair of small assembler programs, leaving VM:Operator completely out of the picture, so the fickle finger of fate does not point directly at Pipes. I have a long-open PMR with IBM regarding this CMS MT problem. Unfortunately they are not making much, if any progress. Who knows, perhaps Pipes is involved - having left some CMS MT setting changed after ending, affecting something that comes along behind it? I'm hoping that a wider audience of silent sufferers may be able to share their experiences, resulting in a faster resolution. Perhaps even the Piper might be intrigued as to why Pipes RTL fails when running in CMS MT threads? Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
