DSXchange

!!! Happy New Year to all DSXchangers !!! May your jobs compile true and run fast, may you never wait on locks, may your DBA keep your database running, let your surrogate keys be unique and your data clean 2006 - So far we've managed to postpone Orwell's predictions for 22 years and are still runni...

Kaps,

the table definitions, or metadata, used by the job are compiled within the job and are not needed at runtime.

sekr, why haven't you tested this yourself? You can go into the Manager and create your own DataStage routine and test it with your question all within a minute... The answer is that the output from TRIM() on any string that is not null will also be not null. In your example it will be the empty str...

I missed that in your original post, I see that now...

Can you see a pattern if you look at the jobs that fail and check to see what their last run status prior to the failed run was, and if the reset-if-required actually had to do a reset?

The DataStage PX developer's guide lists the date/time functions on pages B-1 and B-2; if you convert you string to a timestamp you can use those functions. Another way would be to do your own date math; convert the characters yourself into numbers representing yyyy, mm, dd and hh:mm:ss and do the m...

Kumar, 5 jobs using all available resources in DS plus other UNIX processes can still make a busy system. Which tool did you use to monitor system usage? Since you said the problem seems to be sporadic you need to look at the environment to find a cause or at least to find a reproduceable error. And...

The DS.TOOLS command can be called from the TCL command line or from the command line tool in the DataStage administrator client. There are 6 options at versions 7 and below, you will need to make sure that nobody else is using the project (including your own designer/manager/director clients) and e...

Hello Abby, from your problem description it is impossible for us to find what has caused your original issue. When a job seems to "hang" and doesn't consume a lot of CPU time it is most often due to locking; either within DataStage or within the database(s). If this happens again you can try to get...

over 1 second is a very bad latency and turnaround - but not enough to cause all your woes. If you search the forum for your second error you will find some threads that seem to point at a DS client issue on XP which can be resolved by a vendor patch. Have you gone out and done a check for project i...

Ok, that's one possible cause gone. How busy is your system - if it is very busy then some job calls might be timing out.

Kumar, if you cut-and-pasted the error message, I would concentrate on the "." after the job name. Is this a multi-instance job that you are calling up with the same instance name (namely, a blank or empty instance) more than once at the same time? This is the type of error message that you might see.

Tom, if you open up a cmd window on your PC and execute the command "tracert {hostname/host IP}" what kind of average times are you getting? The TCP/IP connection between client and host might not be the most efficient, but we used to use modems at 9600 Baud to work from home and it would suffice. I...

Roy, Thanks for joining! I initially got a bit worried about the system performance when I saw my CPU hit 100% and thought about using the CPU "choke" they have. But in reality is just replaces the normal backstop program that runs on Windows, but that one doesn't show up on the CPU meter. So even t...

Mandyli,

I think you got away for that question very easily from Ray! Be glad