The pipeline is dead in the water while the CMS command is executing; no way it can force a timeout. If you have two virtual machines to play with, the situation is different. Then you can send the command and wait for a response with STARMSG and send HX when it times out. Whether CMS reacts to the HX is another matter.
On 21 December 2010 22:47, Schuh, Richard <[email protected]> wrote: > Look at the beat stage. It may work for this problem. > > Regards, > Richard Schuh > > > >> -----Original Message----- >> From: CMSTSO Pipelines Discussion List >> [mailto:[email protected]] On Behalf Of Ackerman, Alan >> Sent: Tuesday, December 21, 2010 1:52 PM >> To: [email protected] >> Subject: Time out a CMS command >> >> Is there a PIPELINE idiom to force a CMS command to timeout >> after a certain length of time? >> >> >> >> I am issuing >> >> >> >> 'PIPE command LISTDIR SFSLNB00:SFSADMIN.GETSMTP | stem emsg.' >> >> >> >> Occasionally (about once a week), this hangs for a long time >> (18 hours the last time) and then returns with RC = 55. >> >> >> >> I can live with RC=55, but not with my virtual machine being >> tied up for >> 18 hours. (There are other VMSCHED jobs it should be running.) >> >> >> >> >> >> ---------------------------------------------------------------------- >> This message w/attachments (message) is intended solely for >> the use of the intended recipient(s) and may contain >> information that is privileged, confidential or proprietary. >> If you are not an intended recipient, please notify the >> sender, and then please delete and destroy all copies and >> attachments, and be advised that any review or dissemination >> of, or the taking of any action in reliance on, the >> information contained in or attached to this message is prohibited. >> Unless specifically indicated, this message is not an offer >> to sell or a solicitation of any investment products or other >> financial product or service, an official confirmation of any >> transaction, or an official statement of Sender. Subject to >> applicable law, Sender may intercept, monitor, review and >> retain e-communications (EC) traveling through its >> networks/systems and may produce any such EC to regulators, >> law enforcement, in litigation and as required by law. >> The laws of the country of each sender/recipient may impact >> the handling of EC, and EC may be archived, supervised and >> produced in countries other than the country in which you are >> located. This message cannot be guaranteed to be secure or >> free of errors or viruses. >> >> References to "Sender" are references to any subsidiary of >> Bank of America Corporation. Securities and Insurance >> Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * >> May Lose Value * Are Not a Bank Deposit * Are Not a Condition >> to Any Banking Service or Activity * Are Not Insured by Any >> Federal Government Agency. Attachments that are part of this >> EC may have additional important disclosures and disclaimers, >> which you should read. This message is subject to terms >> available at the following link: >> http://www.bankofamerica.com/emaildisclaimer. By messaging >> with Sender you consent to the foregoing. >>
