active-to-active inputs or outputs
Posted: Thu Sep 08, 2005 6:45 am
We are using DataStage 7.1 on Windows Servers.
When we have certain stages going directly to each other (in this case, a Link Collector directly to a Transform stage), we get an error saying that the stage does not support in-process active-to-active inputs or outputs. In the past, we simply put a file stage in between the 2 to get around this. However, when we recently (a few months ago) had a DataStage Class with version 7.5, the instructor showed us where we could just turn that off, by selecting "Inter-Process" buffering. What I'm wondering is.... why would I not want to do this in my "project properties", so it works across every single one of my programs? I would like to select this as my "default".
When we have certain stages going directly to each other (in this case, a Link Collector directly to a Transform stage), we get an error saying that the stage does not support in-process active-to-active inputs or outputs. In the past, we simply put a file stage in between the 2 to get around this. However, when we recently (a few months ago) had a DataStage Class with version 7.5, the instructor showed us where we could just turn that off, by selecting "Inter-Process" buffering. What I'm wondering is.... why would I not want to do this in my "project properties", so it works across every single one of my programs? I would like to select this as my "default".