Using Link Collector

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Using Link Collector

Post by admin »

Hi All,

I've got a job like this:

seq.file input -> goes to 2 different transformstages (using a constraint)
-> one link goes through an aggregate and the other one goes directly to the
link collector, the aggregate output goes here also. I also tried it using
two sequential file inputs but this resulted in the same error...

While compiling I get the message:
"Link Collector stage does not support in-process active-to-active inputs or
outputs."

Anyone knows what I'm doing wrong?

Thanks!

Wim van Dommelen.


****************************DISCLAIMER***********************************
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere aansprakelijkheid uit die voortvloeit uit electronische verzending.

This e-mail is intended exclusively for the addressee(s), and may not be
passed on to, or made available for use by any person other than the
addressee(s). Fortis rules out any and every liability resulting from
any electronic transmission.
*******************************************************************************

_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Using Link Collector

Post by admin »

Hi Wim,

To use the link collector this way I suggest you try turning on
inter-process row buffering for your job. This is on the Job Properties
Performance tab.

Regards

- Chris Thornton

-----Original Message-----
From: Dommelen van W. (Wim) [mailto:Wim.van.Dommelen@NL.Fortis.com]
Sent: 20 February 2004 07:56
To: 'DataStage Users Discussion List'
Subject: Using Link Collector


Hi All,

I've got a job like this:

seq.file input -> goes to 2 different transformstages (using a constraint)
-> one link goes through an aggregate and the other one goes directly to the
link collector, the aggregate output goes here also. I also tried it using
two sequential file inputs but this resulted in the same error...

While compiling I get the message:
"Link Collector stage does not support in-process active-to-active inputs or
outputs."

Anyone knows what I'm doing wrong?

Thanks!

Wim van Dommelen.


****************************DISCLAIMER***********************************
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking
aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.

This e-mail is intended exclusively for the addressee(s), and may not be
passed on to, or made available for use by any person other than the
addressee(s). Fortis rules out any and every liability resulting from
any electronic transmission.
****************************************************************************
***

_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Using Link Collector

Post by admin »

Hi Wim

I would not suggest using the inter-process row buffering, as there is a
known bug in the process (at least in V6 on windows) were the last
buffer is not always correctly flushed.

In your job design you need to 'land' your files prior to the link
collector stage, ie use a 'passive' stage, like a sequential file,
rather than active to active, ie aggregator to link collector.

Regards

Chris Fuller

-----Original Message-----
From: datastage-users-bounces@oliver.com
[mailto:datastage-users-bounces@oliver.com] On Behalf Of
chris.thornton@ascentialsoftware.com
Sent: Friday, 20 February 2004 7:40 PM
To: datastage-users@oliver.com
Subject: RE: Using Link Collector

Hi Wim,

To use the link collector this way I suggest you try turning on
inter-process row buffering for your job. This is on the Job Properties
Performance tab.

Regards

- Chris Thornton

-----Original Message-----
From: Dommelen van W. (Wim) [mailto:Wim.van.Dommelen@NL.Fortis.com]
Sent: 20 February 2004 07:56
To: 'DataStage Users Discussion List'
Subject: Using Link Collector


Hi All,

I've got a job like this:

seq.file input -> goes to 2 different transformstages (using a
constraint)
-> one link goes through an aggregate and the other one goes directly to
the
link collector, the aggregate output goes here also. I also tried it
using
two sequential file inputs but this resulted in the same error...

While compiling I get the message:
"Link Collector stage does not support in-process active-to-active
inputs or
outputs."

Anyone knows what I'm doing wrong?

Thanks!

Wim van Dommelen.


****************************DISCLAIMER**********************************
*
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n).
Verstrekking
aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.

This e-mail is intended exclusively for the addressee(s), and may not be

passed on to, or made available for use by any person other than the
addressee(s). Fortis rules out any and every liability resulting from
any electronic transmission.
************************************************************************
****
***

_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users


----------------------------------------------------------------------------------
The information contained in this e-mail communication may be confidential. You should only read, disclose, re-transmit, copy, distribute, act in reliance on or commercialise the information if you are authorised to do so. If you are not the intended recipient of this e-mail communication, please immediately notify the sender by e-mail and then destroy any electronic or paper copy of this message.

Any views expressed in this e-mail communication are those of the individual sender, except where the sender specifically states them to be the views of ACP Publishing. ACP Publishing does not represent, warrant or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus or interference.
----------------------------------------------------------------------------------


_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Using Link Collector

Post by admin »

We're still on Version 6.0 here as well, and ran into that problem.
Was that bug fixxed in version 7.0?


Eric
----------
"Imagination is more important than knowledge. Knowledge is limited.
Imagination circles the world."
- Albert Einstein





"Fuller, Christopher"
To: "DataStage Users Discussion List"
Sent by:
datastage-users-bounces cc:
@oliver.com Subject: RE: Using Link Collector


02/20/2004 08:47 PM
Please respond to
DataStage Users
Discussion List






Hi Wim

I would not suggest using the inter-process row buffering, as there is a
known bug in the process (at least in V6 on windows) were the last
buffer is not always correctly flushed.

In your job design you need to 'land' your files prior to the link
collector stage, ie use a 'passive' stage, like a sequential file,
rather than active to active, ie aggregator to link collector.

Regards

Chris Fuller

-----Original Message-----
From: datastage-users-bounces@oliver.com
[mailto:datastage-users-bounces@oliver.com] On Behalf Of
chris.thornton@ascentialsoftware.com
Sent: Friday, 20 February 2004 7:40 PM
To: datastage-users@oliver.com
Subject: RE: Using Link Collector

Hi Wim,

To use the link collector this way I suggest you try turning on
inter-process row buffering for your job. This is on the Job Properties
Performance tab.

Regards

- Chris Thornton

-----Original Message-----
From: Dommelen van W. (Wim) [mailto:Wim.van.Dommelen@NL.Fortis.com]
Sent: 20 February 2004 07:56
To: 'DataStage Users Discussion List'
Subject: Using Link Collector


Hi All,

I've got a job like this:

seq.file input -> goes to 2 different transformstages (using a
constraint)
-> one link goes through an aggregate and the other one goes directly to
the
link collector, the aggregate output goes here also. I also tried it
using
two sequential file inputs but this resulted in the same error...

While compiling I get the message:
"Link Collector stage does not support in-process active-to-active
inputs or
outputs."

Anyone knows what I'm doing wrong?

Thanks!

Wim van Dommelen.


****************************DISCLAIMER**********************************
*
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n).
Verstrekking
aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.

This e-mail is intended exclusively for the addressee(s), and may not be

passed on to, or made available for use by any person other than the
addressee(s). Fortis rules out any and every liability resulting from
any electronic transmission.
************************************************************************
****
***

_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users


----------------------------------------------------------------------------------

The information contained in this e-mail communication may be confidential.
You should only read, disclose, re-transmit, copy, distribute, act in
reliance on or commercialise the information if you are authorised to do
so. If you are not the intended recipient of this e-mail communication,
please immediately notify the sender by e-mail and then destroy any
electronic or paper copy of this message.

Any views expressed in this e-mail communication are those of the
individual sender, except where the sender specifically states them to be
the views of ACP Publishing. ACP Publishing does not represent, warrant or
guarantee that the integrity of this communication has been maintained nor
that the communication is free of errors, virus or interference.
----------------------------------------------------------------------------------



_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users





_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Using Link Collector

Post by admin »

Hi Eric,

this problem is fixed in DataStage 7.

Regards,
Udo




Eric.Roufs@stpaul.com
Gesendet von: datastage-users-bounces@oliver.com
23.02.04 15:26
Bitte antworten an DataStage Users Discussion List


An: DataStage Users Discussion List
Kopie:
Thema: RE: Using Link Collector



We're still on Version 6.0 here as well, and ran into that problem.
Was that bug fixxed in version 7.0?


Eric
----------
"Imagination is more important than knowledge. Knowledge is limited.
Imagination circles the world."
- Albert Einstein





"Fuller, Christopher"
To: "DataStage
Users Discussion List"
Sent by:
datastage-users-bounces cc:
@oliver.com Subject: RE: Using
Link Collector


02/20/2004 08:47 PM
Please respond to
DataStage Users
Discussion List






Hi Wim

I would not suggest using the inter-process row buffering, as there is a
known bug in the process (at least in V6 on windows) were the last
buffer is not always correctly flushed.

In your job design you need to 'land' your files prior to the link
collector stage, ie use a 'passive' stage, like a sequential file,
rather than active to active, ie aggregator to link collector.

Regards

Chris Fuller

-----Original Message-----
From: datastage-users-bounces@oliver.com
[mailto:datastage-users-bounces@oliver.com] On Behalf Of
chris.thornton@ascentialsoftware.com
Sent: Friday, 20 February 2004 7:40 PM
To: datastage-users@oliver.com
Subject: RE: Using Link Collector

Hi Wim,

To use the link collector this way I suggest you try turning on
inter-process row buffering for your job. This is on the Job Properties
Performance tab.

Regards

- Chris Thornton

-----Original Message-----
From: Dommelen van W. (Wim) [mailto:Wim.van.Dommelen@NL.Fortis.com]
Sent: 20 February 2004 07:56
To: 'DataStage Users Discussion List'
Subject: Using Link Collector


Hi All,

I've got a job like this:

seq.file input -> goes to 2 different transformstages (using a
constraint)
-> one link goes through an aggregate and the other one goes directly to
the
link collector, the aggregate output goes here also. I also tried it
using
two sequential file inputs but this resulted in the same error...

While compiling I get the message:
"Link Collector stage does not support in-process active-to-active
inputs or
outputs."

Anyone knows what I'm doing wrong?

Thanks!

Wim van Dommelen.


****************************DISCLAIMER**********************************
*
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n).
Verstrekking
aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere
aansprakelijkheid uit die voortvloeit uit electronische verzending.

This e-mail is intended exclusively for the addressee(s), and may not be

passed on to, or made available for use by any person other than the
addressee(s). Fortis rules out any and every liability resulting from
any electronic transmission.
************************************************************************
****
***

_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users


----------------------------------------------------------------------------------

The information contained in this e-mail communication may be
confidential.
You should only read, disclose, re-transmit, copy, distribute, act in
reliance on or commercialise the information if you are authorised to do
so. If you are not the intended recipient of this e-mail communication,
please immediately notify the sender by e-mail and then destroy any
electronic or paper copy of this message.

Any views expressed in this e-mail communication are those of the
individual sender, except where the sender specifically states them to be
the views of ACP Publishing. ACP Publishing does not represent, warrant or
guarantee that the integrity of this communication has been maintained nor
that the communication is free of errors, virus or interference.
----------------------------------------------------------------------------------



_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users





_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users


_______________________________________________
datastage-users mailing list
datastage-users@oliver.com
http://www.oliver.com/mailman/listinfo/datastage-users
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Locked