DSXchange

Aren't we all, scripted by the ultimate ENTITY

Dsnew wrote:That might not work in this case, ganesh123

Well, if you add the fourth column in the grouping, I dont see why It wont work. You will get 1,1,2.

You completely lost me. Can we get some more explanation with data?

It looks like a goup change detection and giving a running number. Its been covered a lot. Search the forum for various ways. One has been described by gateleys.

Ok well it was worth a try. The environment variables are defined in the
Datastage Administrator.
Do this, in the before stage subroutine put,

And to get the PID, specify the following in the stage variable


Hope that will work.

Yes, where you see NAME...Initial Value bla bla bla, specify a name, give an initial value of 0 specify it as integer. Hit ok. Then in the transformer you will see your stage variable on the right hand side on the top. If you dont see it, click the fourth icon from the right. That icon, present at t...

Right click ont he greyed area and define a stage variable. WHen you do, open the window , right click, go to functions, its under utility. Pass $$ as parameter to GetEnvironment().

I havent used combine stage so cannot comment on its throughput against transformer. Build the entire job using your stage variables and run it with your sample data. If time is acceptable stick to it. In the mean time, maybe some one can throw light on how to get this working using combine stage or...

It means what it says. A character was encounterd which is not a standard according to ISO-8859.

ray.wurlod wrote:You could employ the Transformer stage function GetEnvironment($$) when intializing a stage variable (for the Transformer stage's process ID) or GetEnvironment($PPID) for the job's process ID.

That does'nt work for you

Well before I burn my brain cells further, even if you use routines, you will have to call them from within the transformer. So the usage of a transformer is inevitable. To reduce complexity, you can use stage variables. Boy, feels like we arrived at a point where we originally started.

Search on keywords "disabling memory sharing". Do an exact search.

I like the sud's footer note. Nice ....

Actually, according to the docs, any child job is supposed to inherit the warning limit of the job that calls it. Which means it all goes back to the limit on the 'main' top level Sequence. That is true. But just because the child encountered 50 warnings, the main sequence wont have 50 warnings. Th...