Michaël ,

CMS Pipelines can be pretty confusing.  It requires a change in thought 
processes from standard thinking to "pipethink".

To get a better understanding of what is happening in your Pipes as they 
run, go to the Marist University home of the "CMS/TSO Pipelines Runtime 
Library Distribution", at
http://www2.marist.edu/~pipeline/

Download the PIPEDEMO package at (it does not require the CMS/TSO 
Pipelines Runtime Library, it runs just fine with the IBM-distributed 
Pipelines, too):
http://www2.marist.edu/~pipeline/#Pipedemo

and while there, also download the PDEM MODULE, making it simpler when 
calling PIPEDEMO in an EXEC, changing 
from: 'PIPE whatever'
to:   'PDEM whatever'
instead of to: 'EXEC PIPEDEMO whatever'
(I found that sometimes inserting all those extra characters "EXEC 
pipeDEMO" caused text on that line to often exceed the screen width, so I 
wrote the PDEM MODULE front-end to PIPEDEMO EXEC).

PIPEDEMO let you watch the movement of each record as it moves through 
each stage of the pipe right on your 320 screen.  Seeing that record flow 
often points out the problem with complex pipes.

Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's.




DUGALEIX Michaël <[email protected]> 

Sent by: "CMSTSO Pipelines Discussion List" <[email protected]>
11/18/2010 10:10 AM
Please respond to
"CMSTSO Pipelines Discussion List" <[email protected]>



To
[email protected]
cc

Subject
Re: N1 records x N2 records -> N1xN2 records ?






Hello Rob,

Thanks for your answer.

Unfortunately, I've never been able to understand the "synchronize" and 
"juxtapose" stages ... :-(
("pipe ahelp ..." and "pipe help ..." don't help me, this time)

This being said, I don't understand the behaviour of your pipeline as a 
"black box", neither (maybe I have to do another job !).

On my system (z/VM 5.2.0, CMS/TSO Pipelines, 5741-A05/5655-A17 1.0110), 
the console displays the following lines :
A
X
A
Y
B
X
B
Y
C
X
C
Y

I thought I could use a "join" stage to join these, before the console 
stage, but it has no effect on the output (?!).

And if I write in a file just before the console, to see the content, I 
see this :
A
A
B
B
C
C

but I expected to see that :
AX
AY
BX
BY
CX
CY

What do I do wrong ?

Thanks
Michaël


-----Message d'origine-----
De : Rob van der Heij <[email protected]>
Envoyé : 18/11/2010 12:37
À : [email protected] 
<[email protected]>
Cc :
Objet : Re: N1 records x N2 records -> N1xN2 records ?
> On Thu, Nov 18, 2010 at 11:58 AM, DUGALEIX Michaël
> <[email protected]>  wrote:
>> Hello plumbers,
>>
>> Is there a stage which can combine an input of N1 records and an input 
of N2
>> records to give an output of N1xN2 records in the following way :
>
> Something like this:
>
> PIPE ( end \ )
>    \<  1 txt
>    | s: synch
>    | j: juxtapose
>    | cons
>    \<  2 txt
>    | instore
>    | dup *
>    | s:
>    | outstore
>    | j:
>
> With 'instore' you buffer the entire stream and get a "token" that is
> duplicated. This way 'outstore' produces multiple copies of your input
> stream. The 'synch' stage will pace the records on the first pipeline
> segment to make them flow with the tokens in the 2nd segment. This way
> a full set of records is presented at the 'juxtapose' while it is
> holding a record from the first stream.
>
> | Rob





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. 

Reply via email to