In the examples provided to me, a verify statement preceded the pick statement. Sorry I didn't show that. While the VERIFY is good programming, my primary interest is the PICK stage. Steve
-----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, October 30, 2013 4:57 PM To: [email protected] Subject: Re: pipe question On 2013-10-30 14:35, Gentry, Steve wrote: > Yes. Here's the method I ended up using. Provide by a member on another list. > > ... > '|pick 2.2 >= /0/ & 2.2 <=/24/', > ... > I'll give that one only half a point: pipe literal 24:00 | pick 2.2 >= /0/ & 2.2 <= /24/ | console consl pipe literal 24:00 | pick 2.2 >= /0/ & 2.2 <= /24/ | console 24:00 Good. pipe literal 25:00 | pick 2.2 >= /0/ & 2.2 <= /24/ | console consl pipe literal 25:00 | pick 2.2 >= /0/ & 2.2 <= /24/ | console (Nothing.) Good. pipe literal xy:00 | pick 2.2 >= /0/ & 2.2 <= /24/ | console consl pipe literal xy:00 | pick 2.2 >= /0/ & 2.2 <= /24/ | console PIPPIC1038E Not a decimal number: xy. PIPMSG003I ... Issued from stage 2 of pipeline 1. PIPMSG001I ... Running "pick 2.2 >= /0/ & 2.2 <= /24/". *-* 'callpipe' rest +++ RC(1038) +++ Not so good. And: pipe literal xy:00 | pick 2.2 >>= /0/ & 2.2 <<= /24/ | console (Again, nothing.) Good. But: pipe literal 1y:00 | pick 2.2 >>= /0/ & 2.2 <<= /24/ | console consl pipe literal 1y:00 | pick 2.2 >>= /0/ & 2.2 <<= /24/ | console 1y:00 Not so good. -- gil
