DSXchange

In Server, is there a method of ending a flow of logic without writing to a file? Ie. Something equivalent to Ab Initio Trash component? I have situation where I was running a stage for side effect purposes and don't really want to write any output.

gsherry1 wrote:In Server, is there a method of ending a flow of logic without writing to a file? Ie. Something equivalent to Ab Initio Trash component? I have situation where I was running a stage for side effect purposes and don't really want to write any output.

I don't undesrstand what side effects you are looking for.....

but if you want see the counts on the link but do not want to write the data,

Use Sequential file stage with file name
.

That will do it.

Kris~

Hi Kris,

Have you used /dev/null and tried job , was it not giving you any error.

Please let me know.

Any inputs are most welcome,

Thank you all

Hi All,


Have any one used /dev/null and tried job , was it not giving you any error.

Please let me know.

Any inputs are most welcome,

Thank you all

You can limit the number of rows read at job start up. You can also limit the number of rows written with a constraint.

Hi Duke ,

Thank very much for ur quick response, but i didnot get what u are saying, that means by limiting the number of rows /dev/null can be used in the sequential stage as file name with out any errors???


Thank you all once again and any help would be greatly appreciated.

Can you elabarate side effect purposes ?

/dev/null is a "black hole" - it can accept any number of rows. I usually make the output rule "append" when writing to /dev/null.

On Windows you can use .\NUL since there is a NUL file in every folder.

Thank you Ray very much !!!!! for ur answer and one more point i want to
get clarified is do i need use "append" in order make use of /dev/null.

Thanks once Again ur are really great!!!!!!!!!!

Can say words for a nice forum like this.........

Cannnot say in words , how great the forum is.......... :D

sorry for my typo.

I'm never really certain what attempting to overwrite /dev/null implies, and it may be different on different variants of UNIX. That's why I always choose "append". YMMV.

Thank you very much and makes sense.