DSXchange

Hi, Can someone tell me which port number RTI Agent uses to communicate to the DataStage server? The problem I face is that when I attach the DS jobs to the Agent, after some time the jobs just dissapear. This happens everytime I do it. We have tried restaring Web Sphere server / UNIX server / RTI A...

????

I tried searching some orchestare manuals for this, but found none. the ones I referred are DevGuide, UserGuuide, OperatorsRef.pdf. I also tried to search the ibm website but could not get much help. Can someone guide me to the location / name of the orchestrate manual where I can find this info? Ch...

Thanks for the details Ray. I got around this problem by adding this variable in the User Defined section.

However, this brings me to a quesiton as to then where can I find the complete list for reference purposes? Can you suggest some document / site etc?

Cheers
Aakash

Hi,

Can some one guide me as to in which category in the PX environment variables, I can find this variable :

APT_PM_CONDUCTOR_TIMEOUT.

I can see APT_PM_NODE_TIMEOUT, but not the above one....

Thanks
Aakash

Or.... use @INROWNUM while running the target stage on 1 node using the node constraints (assuming that the target stage is not one of the stages which do not allow node / resource constraints)

Sorry if the question sounds naive, but you are not talking about job variables isnt it???

If yes, then pls ignore my quesiton and if you can let me know a few of the ds env variables you are trying to set, then I can dig into it...

Cheers
Aakash

Here it is:

??

Firstly, Type 1 and Type 19 and hashed files which DS uses to store its structures and I am really not sure if they can be used for user purposes (i.e., they can be accessed using the DS pallette). However you can create them using the universe shell as you have done. Never tried working with them, ...

By observing the lookup file set descriptor file, I come to know the nodes and segment file location: Here is my descriptor file: --Orchestrate File Set v2 --LFile node1:/vol/DataStage/tmp/Datasets/lookuptable.20080306.aj0zfqc --Schema record {LUTVersion="1"} ( KeyCol: int32 {dropped}; tex...

By observing the lookup file set descriptor file, I come to know the nodes and segment file location: Here is my descriptor file: --Orchestrate File Set v2 --LFile node1:/vol/DataStage/tmp/Datasets/lookuptable.20080306.aj0zfqc --Schema record {LUTVersion="1"} ( KeyCol: int32 {dropped}; tex...

Too small may be either less than 32KB or less than 128KB (or other, depending upon certain environment variables) Can you please explain what environment variables are those? P.S:- The reason I have reopend this topic is that I just tried to write a lookup file set 52 MBs in size and it still got ...

Just to build on ArndW's suggestion, use dsjob -report to extract the run times for the job concerned. Put the data into a file and then with a simple shell script, you could find out the average.

Hope it helps.

Cheers
Aakash

Ok. I guess that explains it.

But on the same note, how can I make out before hand that which stage is gonna be optimised 'out' of my job at run time???