This is what I went with. Thanks again to all that replied, and for the
explanations!
'PIPE (name QCHPID.EXEC:2)',
'|xrange 00-FF ',
'| deblock 1 ',
'| specs /QUERY CHPID/ 1 1.1 c2x nw ',
'| cp ',
'| nfind No ', /* remove undefined chpids from report */
'| console'
On Wed, Jul 21, 2010 at 8:31 AM, Frank M. Ramaekers
<framaek...@ailife.com>wrote:
> Just curious, why:
>
> pipe literal|dup *|take 256...
>
> Instead of
>
> pipe literal|dup 255...
>
> pipe literal|dup 255|count lines|console
> 256
>
> Is there some advantage to doing it the way you specified?
>
> Frank M. Ramaekers Jr.
>
>
>
> -----Original Message-----
> From: CMSTSO Pipelines Discussion List [mailto:cms-pipeli...@vm.marist.edu]
> On Behalf Of John P. Hartmann
> Sent: Tuesday, July 20, 2010 8:24 AM
> To: CMS-PIPELINES@VM.MARIST.EDU
> Subject: Re: [CMS-PIPELINES] CP oddity?
>
> Of course I really meant
>
> pipe literal|dup *|take 256|spec /QUERY CHPID/ 1 number from 0 d2x
> nw|cp|console
>
> Oh well, can't win them all.
>
> On 20 July 2010 15:21, John P. Hartmann <jphartm...@gmail.com> wrote:
> > Another attempt at reducing entropy or time travel. It is a rite of
> > passage; everyone has tried it.
> >
> > Make that
> >
> > pipe literal|dup *|take 256|spec /QUERY CHPID/ 1 w1 d2x nw|cp|console
> >
> > This also gets you rid of the loop.
> >
> > You need to understand exactly why your pipeline was doomed from the
> > outset. You'll understand it better if you work it out for yourself,
> > but if that fails, ask again.
> >
>
> _____________________________________________________
> This message contains information which is privileged and confidential and
> is solely for the use of the
> intended recipient. If you are not the intended recipient, be aware that
> any review, disclosure,
> copying, distribution, or use of the contents of this message is strictly
> prohibited. If you have
> received this in error, please destroy it immediately and notify us at
> privacy...@ailife.com.
>
